ObjectDB ObjectDB

Internal Website Search

51-60 of 200 resultsRefresh
2

find(entityClass, primaryKey, lockMode)

must perform optimistic version checks when obtaining the database lock. If these checks fail ... OptimisticLockException - if the optimistic version check fails PessimisticLockException - if pessimistic locking fails
2

find(entityClass, primaryKey, lockMode, properties)

and the entity has a version attribute, the persistence provider must perform optimistic version checks when obtaining the database lock. If these checks fail, the OptimisticLockException will be thrown ... - if the optimistic version check fails PessimisticLockException - if pessimistic locking fails
2

lock(entity, lockMode)

provider must also perform optimistic version checks when obtaining the database lock. If these checks fail, the OptimisticLockException will be thrown. If the lock mode type is pessimistic ... OptimisticLockException - if the optimistic version check fails PessimisticLockException - if pessimistic locking fails
0

javax.jdo.PersistenceManagerFactory

this PersistenceManagerFactory. Close this PersistenceManagerFactory. Check for JDOPermission("closePersistenceManagerFactory") and if not authorized, throw SecurityException. If the authorization check succeeds, check
0

close()

Method javax.jdo.PersistenceManagerFactory void close() Close this PersistenceManagerFactory. Check for JDOPermission("closePersistenceManagerFactory") and if not authorized, throw SecurityException. If the authorization check succeeds, check to see that all PersistenceManager instances obtained
0

javax.jdo.PersistenceManager

the consistency check. No datastore resources acquired during the execution of this method are held ... were made, then it must mark the instance dirty. No consistency checking is done during makePersistent of detached instances. If consistency checking is required by the application, then flush or checkConsistency
0

makePersistent(pc)

if changes were made, then it must mark the instance dirty. No consistency checking is done during makePersistent of detached instances. If consistency checking is required by the application
0

javax.jdo.identity.ByteIdentity

boolean equals(Object obj) Check the class and class name and object type. Check the class and class
0

javax.jdo.identity.SingleFieldIdentity

. Since: JDO 2.0 int compareTo(T arg0) Parameters: arg0 - boolean equals(Object obj) Check the class and class name and object type. Check the class and class name and object type. If restored from
0

checkAuthorizedStateManagerClass(smClass)

Static Method javax.jdo.spi.JDOImplHelper void checkAuthorizedStateManagerClass( Class smClass ) Check that the parameter instance is a class that is authorized for JDOPermission("setStateManager ... : smClass - a Class to be checked for JDOPermission("setStateManager") Since: JDO 1.0.1

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