ObjectDB ObjectDB

Internal Website Search

41-50 of 88 resultsRefresh
29

OptimisticLockException

Have read read the documentation on optimistic locks, still not sure how to deal ... : Optimistic lock failed for object dmoshal David Moshal perhaps I should explain the problem, which is that the optimistic lock exception fails repeatedly once the object is modified from another process. ie
6

lock(entity, lockMode)

provider must also perform optimistic version checks when obtaining the database lock ... OptimisticLockException - if the optimistic version check fails PessimisticLockException - if pessimistic locking fails
0

getOptimistic()

Method javax.jdo.Transaction boolean getOptimistic() Optimistic transactions do not hold data store locks until commit time. Returns: the value of the Optimistic property. Since: JDO 1.0
0

getOptimistic()

Method javax.jdo.PersistenceManagerFactory boolean getOptimistic() Get the default Optimistic setting for all PersistenceManager instances obtained from this factory. Returns: the default Optimistic setting. Since: JDO 1.0
0

supportedOptions()

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

getObjectById(oid, validate)

in progress, the returned instance will be persistent-clean. If there is an optimistic transaction in
0

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
0

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
0

javax.jdo.Query

the cache. For optimistic transactions, this can dramatically improve query response times
0

refresh(pc)

Methodjavax.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

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support