ObjectDB Database Search

1-9 of 9 results


	jakarta.persistence.TypedQuery.setLockMode(LockModeType) Jakarta Persistence (JPA) Method in jakarta.persistence.TypedQuery TypedQuery setLockMode ( LockModeType lockMode ) Set the lock mode type to be used for the query execution. Parameters: lockMode - lock mode Returns: the same query instance. Throws: IllegalStateException
	jakarta.persistence.Query.setLockMode(LockModeType) Jakarta Persistence (JPA) Method in jakarta.persistence.Query Query setLockMode ( LockModeType lockMode ) Set the lock mode type to be used for the query execution. Parameters: lockMode - lock mode Returns: the same query instance. Throws: IllegalStateException - if the query is found
	Setting and Tuning of JPA Queries . Therefore, when performance is important, this issue has to be considered. Lock Mode ( setLockMode ) ObjectDB uses ... adds support for pessimistic locking . The setLockMode method sets a lock mode that has to be applied ... a pessimistic WRITE lock on all the result objects: List results = query. setLockMode
	JPA Named Queries for the setLockMode and setHint methods. Every @NamedQuery annotation is attached
	jakarta.persistence.LockModeType refresh() ), or to Query. setLockMode or TypedQuery. setLockMode . Optimistic locks are specified using
	jakarta.persistence.TypedQuery argument is not valid for the implementation. Since: Jakarta Persistence (JPA) 1.0 TypedQuery setLockMode ... Query. setLockMode Parameters: lockMode - lock mode Returns: the same query instance. Throws
	jakarta.persistence.Query setLockMode ( LockModeType lockMode ) Set the lock mode type to be used for the query execution
	jakarta.persistence.StoredProcedureQuery for the implementation. Since: Jakarta Persistence (JPA) 1.0 Query setLockMode ( LockModeType
	Duplicate Entity class names causes Exception in Query .CheckCacheThenDatabase); /* q. setLockMode (LockModeType.OPTIMISTIC); */ try { java.lang.Object r = q.getSingleResult