About flush

41-50 of 142Refresh
JPA Doc
3

javax.persistence.PessimisticLockException

. This exception may be thrown as part of an API call, a flush or at commit time. The current
JDO Doc
3

makePersistent(pc)

, then flush or checkConsistency should be called after attaching the instances. These methods
JPA Doc
3

persist(entity)

at flush or commit time.) IllegalArgumentException - if the instance is not an entity
JDO Doc
3

postStore(event)

Method javax.jdo.listener.StoreLifecycleListener void postStore(   InstanceLifecycleEvent event ) Invoked whenever a persistent instance is stored, for example during javax.jdo.PersistenceManager.flush or javax.jdo.Transaction.commit. It is called after the field values have been stored. Parameters: event - the store event. Since: JDO 2.0
JDO Doc
3

preStore(event)

Method javax.jdo.listener.StoreLifecycleListener void preStore(   InstanceLifecycleEvent event ) Invoked whenever a persistent instance is stored, for example during javax.jdo.PersistenceManager.flush or javax.jdo.Transaction.commit. It is called before the method StoreCallback.jdoPreStore
JDO Doc
3

setSynchronization(sync)

Method javax.jdo.Transaction void setSynchronization(   Synchronization sync ) The user can specify a Synchronization instance to be notified on transaction completions. The beforeCompletion method is called prior to flushing instances to the data store. The afterCompletion method is called
JDO Doc
3

javax.jdo.Query

instances of affected classes in the cache are first flushed to the datastore. Instances in the cache
JDO Doc
3

javax.jdo.Transaction

prior to flushing instances to the data store. The afterCompletion method is called after performing
Issue
3

Removed entities can be found by query in the same transaction

__odbtracker/m (type STA, value=Persistent-Deleted-Flushed) which shows that the entity is deleted and flushed. The bug was introduced with ObjectDB Version 2.7.4_04, therefore in the moment ... was flushed but not committed yet then the database maintains at least two different snapshots of objects
Forum
3

Remove an entity which attributes were changed - OptimisticLockException

and will fail with OptimisticLockException if user 1 is committing or flushing the changes before user 2 ... on the same object by two different users. Note that user 1 may flush the changes implicitly by running a query. You can run specific queries with COMMIT flush mode to avoid flushing changes to the database