Internal Website Search
31-40 of 152 resultsRefreshEM close causes an exception temporary file that holds information about uncommitted flushed updates when the EntityManager ... your company. It was added to support large flush operations. Since this is a hidden feature ... in development) will add better support for large flush operations. However, we cannot provide | |
javax.persistence.EntityExistsException at flush or commit time. The current transaction, if one is active, will be marked | |
persist(entity) another PersistenceException may be thrown at flush or commit time.) | |
javax.persistence.LockTimeoutException may be thrown as part of an API call, at, flush or at commit time. The current transaction, if one is active | |
javax.persistence.OptimisticLockException when an optimistic locking conflict occurs. This exception may be thrown as part of an API call, a flush or | |
clear() made to entities that have not been flushed to the database will not be persisted. | |
preStore(event)/PersistenceManager/flush" title="Method of javax.jdo.PersistenceManager">javax.jdo.PersistenceManager.flush or | |
postStore(event)/PersistenceManager/flush" title="Method of javax.jdo.PersistenceManager">javax.jdo.PersistenceManager.flush or | |
javax.jdo.annotations.Unique to reorder database operations when flushing changes to avoid unique constraint violations. Corresponds | |
makePersistent(pc) checking is required by the application, then flush or checkConsistency should be called |