ObjectDB ObjectDB

Internal Website Search

21-30 of 87 resultsRefresh
6

javax.persistence.LockModeType

phenomena can occur: P1 (Dirty read): Transaction T1 modifies a row. Another transaction T2 then reads ... on an object, the entity manager must ensure that neither of the following phenomena can occur: P1 (Dirty
0

nonBinaryCompatibleMakeDirty(pc, fieldName)

Method javax.jdo.spi.JDOImplHelper void nonBinaryCompatibleMakeDirty( Object pc, String fieldName ) Mark a non-binary-compatible instance dirty. Delegate to all registered StateInterrogation instances until one of them handles the call. Parameters: pc - the instance to mark dirty fieldName - the field to mark dirty Since: JDO 1.0
0

makeDirty(pc, fieldName)

Method javax.jdo.spi.StateInterrogation boolean makeDirty( Object pc, String fieldName ) Explicitly mark the parameter instance and field dirty. Normally, PersistenceCapable classes are able ... of the field to be marked dirty. Since: JDO 2.0 See Also: PersistenceCapable.jdoMakeDirty(String fieldName)
0

isDirty(pc)

Method javax.jdo.spi.StateInterrogation Boolean isDirty( Object pc ) Tests whether the parameter instance is dirty. Instances that have been modified, deleted, newly made persistent in the current ... to be non-dirty return Boolean.FALSE. Instances not recognized by the implementation return null
0

makePersistent(pc)

, then the implementation is not required to mark the corresponding instance dirty. If it cannot determine if changes were made, then it must mark the instance dirty. No consistency checking
0

makeDirty(pc, fieldName)

Static Method javax.jdo.JDOHelper void makeDirty( Object pc, String fieldName ) Explicitly mark the parameter instance and field dirty. Normally, PersistenceCapable classes are able to detect changes ... - the PersistenceCapable instance. fieldName - the name of the field to be marked dirty. Since: JDO 1.0 See Also: PersistenceCapable.jdoMakeDirty(String fieldName)
0

setCopyOnAttach(flag)

and change their state from detached-clean to persistent-clean or from detached-dirty to persistent-dirty. Parameters: flag - Since: JDO 2.1 See Also: getCopyOnAttach()
0

setCopyOnAttach(flag)

from detached-clean to persistent-clean or from detached-dirty to persistent-dirty. Parameters: flag - Since: JDO 2.1 See Also: getCopyOnAttach()
0

flush()

Method javax.jdo.PersistenceManager void flush() Flushes all dirty, new, and deleted instances to the data store. It has no effect if a transaction is not active. If a datastore transaction is active, this method synchronizes the cache with the datastore and reports any exceptions. If an optimistic
0

makeDirty(pc, fieldName)

Method javax.jdo.spi.StateManager void makeDirty( PersistenceCapable pc, String fieldName ) Mark the associated PersistenceCapable field dirty. The StateManager will make a copy of the field so it can be restored if needed later, and then mark the field as modified in the current transaction

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