Home » Search

About PESSIMISTIC_READ

91-100 of 200Refresh
JPA Doc
2

getSingleResult()

mode has been set and there is no transaction PessimisticLockException - if pessimistic locking fails and the transaction is rolled back LockTimeoutException - if pessimistic locking fails
JPA Doc
2

getSingleResult()

has been set and there is no transaction PessimisticLockException - if pessimistic locking fails and the transaction is rolled back LockTimeoutException - if pessimistic locking fails
JPA Doc
2

javax.persistence.CacheStoreMode

the behavior when data is read from the database and when data is committed into the database ... /update entity data into cache when read from database and when committed into database. Insert/update entity data into cache when read from database and when committed into database. Forces refresh
JDO Doc
2

setIsolationLevel(level)

to high are: read-uncommitted read-committed repeatable-read snapshot serializable Parameters: level - the transaction isolation level Since: JDO 2.2 See Also: getIsolationLevel() Constants.TX_READ_UNCOMMITTED Constants.TX_READ_COMMITTED Constants.TX_REPEATABLE_READ Constants.TX_SNAPSHOT Constants.TX_SERIALIZABLE
JDO Doc
2

setTransactionIsolationLevel(level)

are: read-uncommitted read-committed repeatable-read snapshot serializable Parameters: level - the transaction isolation level Since: JDO 2.2 See Also: getTransactionIsolationLevel() Constants.TX_READ_UNCOMMITTED Constants.TX_READ_COMMITTED Constants.TX_REPEATABLE_READ Constants.TX_SNAPSHOT Constants.TX_SERIALIZABLE
Issue
2

Threaded Test - Failed to commit transaction: Unexpected internal exception

(                     LockModeType.PESSIMISTIC_WRITE).getSingleResult();                 em.remove(p ... thread inserts object into the "queue" database Consumer thread reads and removes an object from ... and completes ok. However, in the real case I'd like the consumer to read from the "queue" database based
JPA Doc
2

PessimisticLockScope.NORMAL

Enum Constant javax.persistence.PessimisticLockScope NORMAL This value defines the default behavior for pessimistic locking. The persistence provider must lock the database row(s) that correspond to the non-collection-valued persistent state of that instance. If a joined inheritance strategy
Issue
2

ObjectDB 2 JDO Manual

commit) pessimistic locking is something I miss, for example, and it to some degree it is a compromise ... with JDO, a couple of weeks ago, read most of the ObjectDB JPA manual and have found that ObjectDB does
Forum
2

Where Does ObjectDB Block/Lock?

and queued architecture, with high throughput, especially on read, is desired, should I use ... instances. In ObjectDB 1.x pessimistic locks were more efficient, but with ObjectDB 2.x optimistic locks
JDO Doc
1

javax.jdo.identity.ByteIdentity

IOException, ClassNotFoundException Read this object. Read this object. Read the superclass first