Home » Search

About PESSIMISTIC_READ

61-70 of 200Refresh
JPA Doc
4

find(entityClass, primaryKey, lockMode, properties)

is pessimistic and the entity has a version attribute, the persistence provider must perform optimistic ... will be thrown. If the lock mode type is pessimistic and the entity instance is found ... OptimisticLockException - if the optimistic version check fails PessimisticLockException - if pessimistic
JPA Doc
4

javax.persistence.Query

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

javax.persistence.PessimisticLockScope

property for pessimistic locking. This property may be passed as an argument to the methods ... the default behavior for pessimistic locking. This value defines the default behavior for pessimistic
JPA Doc
3

refresh(entity, lockMode)

, and lock it with respect to given lock mode type. If the lock mode type is pessimistic and the entity ... PessimisticLockException - if pessimistic locking fails and the transaction is rolled back LockTimeoutException - if pessimistic locking fails and only the statement is rolled back PersistenceException - if an unsupported lock call is made Since: JPA 2.0
JPA Doc
3

refresh(entity, lockMode, properties)

properties. If the lock mode type is pessimistic and the entity instance is found ... - if pessimistic locking fails and the transaction is rolled back LockTimeoutException - if pessimistic locking fails and only the statement is rolled back PersistenceException - if an unsupported lock call is made Since: JPA 2.0
JDO Doc
3

javax.jdo.PersistenceManagerFactory

getReadOnly() Gets the value for read-only for this PMF. Gets the value for read-only for this PMF. Indicates whether the datastore is read-only or writable. Returns: the readOnly setting. Since: JDO 2 ... for whether the datastore is to be considered read-only. Sets the value for whether the datastore
Manual
3

Chapter 1 - Quick Tour

This chapter demonstrates basic ObjectDB and JPA concepts by introducing a simple example program. After reading this chapter you should be able to write basic programs that create, open and close ObjectDB databases and perform basic CRUD operations (Create/Store, Retrieve, Update and Delete
Manual
3

JPA Entity Fields

should be treated as read only by the application and no mutator methods should be written
JPA Doc
3

JPA Reference (JavaDoc)

order to learn how to use JPA and ObjectDB please read the ObjectDB manual.
Result
3

ObjectDB 2.x Downloads

Please read the ObjectDB licence page. ObjectDB runtime jars are available also on theMaven Repository.