About lock

51-60 of 180Refresh
Result
11

ObjectDB - Object Database for Java (JPA/JDO) [2017-10-18]

) Using a standard Java API (JPA / JDO) provides many benefits, including: Avoiding vendor lock in
Result
11

ObjectDB - Object Database for Java (JPA/JDO) [2018-10-30]

) Using a standard Java API (JPA / JDO) provides many benefits, including: Avoiding vendor lock in
Result
11

ObjectDB - Object Database for Java (JPA/JDO) [2018-11-03]

) Using a standard Java API (JPA / JDO) provides many benefits, including: Avoiding vendor lock in
Result
11

ObjectDB - Object Database for Java (JPA/JDO)

) Using a standard Java API (JPA / JDO) provides many benefits, including: Avoiding vendor lock in
JPA Doc
11

refresh(entity, lockMode)

, and lock it with respect to given lock mode type. If the lock mode type is pessimistic and the entity instance is found but cannot be locked: the PessimisticLockException will be thrown if the database locking failure causes transaction-level rollback the LockTimeoutException will be thrown
Issue
9

Freeze during save

.jdo.PMImpl.makePersistent(PMImpl.java:241) - locked <13f2027> (a com.spiffymap.naviupdate.model.Repository) - locked <5e745b> (a com.objectdb.jdo.PMImpl) Could you please post ... (Thread.java:748) Locked ownable synchronizers: - locked (a java.util
JPA Doc
9

PessimisticLockScope.NORMAL

for pessimistic locking. The persistence provider must lock the database row(s) that correspond ... is used, or if the entity is otherwise mapped to a secondary table, this entails locking the row(s) for the entity instance in the additional table(s). Entity relationships for which the locked entity
JPA Doc
8

PessimisticLockScope.EXTENDED

in join tables will be locked if the javax.persistence.lock.scope property is specified ... be locked (unless those entities are explicitly locked). Locking such a relationship or element collection generally locks only the rows in the join table or collection table for that relationship or
JPA Doc
6

javax.persistence.EntityNotFoundException

is called and the object no longer exists in the database. Thrown when EntityManager.lock is used with pessimistic locking is used and the entity no longer exists in the database. The current transaction ... ) EntityManager.lock(Object, LockModeType) EntityManager.lock(Object, LockModeType, java.util.Map
JDO Doc
6

javax.jdo.Transaction

Since: JDO 1.0 boolean getOptimistic() Optimistic transactions do not hold data store locks until commit time. Optimistic transactions do not hold data store locks until commit time. Returns: the value ... do not hold data store locks until commit time. Optimistic transactions do not hold data store locks