About optimistic

51-60 of 86Refresh
JDO Doc
4

isTransactional(pc)

in data store transactions; and persistent instances modified in optimistic transactions. Transient
JDO Doc
4

javax.jdo.JDOHelper

are standard key names: "javax.jdo.PersistenceManagerFactoryClass" "javax.jdo.option.Optimistic", "javax.jdo
JDO Doc
4

javax.jdo.spi.StateManager

transactions; and persistent instances modified in optimistic transactions. Transient
JPA Doc
4

javax.persistence.OptimisticLockException

Interfaces: Serializable Thrown by the persistence provider when an optimistic locking conflict occurs
JDO Doc
4

makeTransactional(pc)

before the first change in the transaction. For persistent instances read in optimistic transactions
JDO Doc
4

refresh(pc)

Method javax.jdo.PersistenceManager void refresh(   Object pc ) Refresh the state of the instance from the data store. In an optimistic transaction, the state of instances in the cache might not match the state in the data store. This method is used to reload the state of the instance from the data
JDO Doc
4

setConnectionFactory2(connectionFactory)

Method javax.jdo.PersistenceManagerFactory void setConnectionFactory2(   Object connectionFactory ) Set the second data store connection factory. This is needed for managed environments to get nontransactional connections for optimistic transactions. JDO implementations will support specific
JDO Doc
4

setConnectionFactory2Name(connectionFactoryName)

Method javax.jdo.PersistenceManagerFactory void setConnectionFactory2Name(   String connectionFactoryName ) Set the name for the second data store connection factory. This is needed for managed environments to get nontransactional connections for optimistic transactions. Parameters
JDO Doc
4

setIgnoreCache(ignoreCache)

might be able to optimize the query execution by ignoring changed values in the cache. For optimistic
JDO Doc
4

supportedOptions()

.NontransactionalRead javax.jdo.option.NontransactionalWrite javax.jdo.option.RetainValues javax.jdo.option.Optimistic