25 | EM close causes an exception This stack trace indicates a missing temporary file that holds information about uncommitted flushed ... . It was added to support large flush operations. Since this is a hidden feature, no similar reports from ... ) will add better support for large flush operations. However, we cannot provide information regarding |
3 | javax.persistence.OrderColumn is responsible for updating the ordering upon flushing to the database to reflect any insertion, deletion |
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 ... the database and the change was flushed but not committed yet then the database maintains |
3 | persist(entity) at flush or commit time.) IllegalArgumentException - if the instance is not an entity |
3 | javax.persistence.PessimisticLockException. This exception may be thrown as part of an API call, a flush or at commit time. The current |
0 | checkConsistency(). An implementation might flush instances as if flush were called, but it is not required |
0 | javax.jdo.Query instances of affected classes in the cache are first flushed to the datastore. Instances in the cache or |
0 | deletePersistentAll() classes in the cache are first flushed to the datastore. Instances in the cache or brought into |
0 | makePersistent(pc), then flush or checkConsistency should be called after attaching the instances. These methods have no effect |
0 | javax.jdo.annotations.Uniquejavax.jdo.annotations Annotation Unique Target: Classes and fields (including property get methods) Annotation for a database unique constraint. Used for database schema generation to create unique constraints. Also used to reorder database operations when flushing changes to avoid unique |
