About commit

91-100 of 200Refresh
JDO Doc
4

javax.jdo.PersistenceManagerFactory

is thrown. Standard values in order from low to high are: read-uncommitted read-committed repeatable ... See Also: getTransactionIsolationLevel() Constants.TX_READ_UNCOMMITTED Constants.TX_READ_COMMITTED Constants ... .TransactionIsolationLevel.read-committed javax.jdo.option.TransactionIsolationLevel.repeatable-read javax
Issue
3

Best practise loading big data

only workarounds helped to gain a lower memory footprint. One is to stupidly commit the transaction after a certain number of read accesses (every 10000 read access to commit and open a new transaction ... is not defined. Could you please repair the code? You mentioned commit as a workaround. It is unclear
Issue
3

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

.1 and then: Set DO_FORCE_COMMIT_AFTER_BUILD = false in com.greensoft.objectdb.test.mini.ejb ... and then: Ensure DO_FORCE_COMMIT_AFTER_BUILD = false in com.greensoft.objectdb.test.mini.ejb ... }. */ final static boolean DO_FORCE_COMMIT_AFTER_BUILD = false; @PersistenceContext(type
JDO Doc
3

javax.jdo.annotations.ForeignKey

Whether this foreign key is deferred (constraint is checked only at commit). Whether this foreign key is deferred (constraint is checked only at commit). Returns: whether this foreign key is deferred
JPA Doc
3

javax.persistence.EntityManager

. The EntityTransaction instance may be used serially to begin and commit multiple transactions. Returns ... the EntityExistsException or another PersistenceException may be thrown at flush or commit time.) IllegalArgumentException
JPA Doc
3

javax.persistence.RollbackException

: Serializable Thrown by the persistence provider when EntityTransaction.commit() fails. Since: JPA 1.0 See Also: javax.persistence.EntityTransaction.commit() RollbackException() Constructs a new
JDO Doc
3

setDetachAllOnCommit(flag)

the cache after commit is defined by the retainValues flag. With this flag set to true ... at commit. Loading fields and unloading fields required by the fetch plan is done after calling
JDO Doc
3

setIsolationLevel(level)

to high are: read-uncommitted read-committed repeatable-read snapshot serializable Parameters: level ... _UNCOMMITTED Constants.TX_READ_COMMITTED Constants.TX_REPEATABLE_READ Constants.TX_SNAPSHOT Constants.TX_SERIALIZABLE
JDO Doc
3

setRollbackOnly()

Method javax.jdo.Transaction void setRollbackOnly() Sets the rollback-only status of the transaction to true. After this flag is set to true, the transaction can no longer be committed, and any attempt to commit the transaction will throw JDOFatalDataStoreException. Since: JDO 2.0
JDO Doc
3

setTransactionIsolationLevel(level)

are: read-uncommitted read-committed repeatable-read snapshot serializable Parameters: level ... _UNCOMMITTED Constants.TX_READ_COMMITTED Constants.TX_REPEATABLE_READ Constants.TX_SNAPSHOT Constants.TX_SERIALIZABLE