Internal Website Search

171-180 of 200 resultsRefresh

Dirty checking

: after the transaction has succeeded, so that I can update views which are observing those objects. transaction which might not suceed. So, I can't calculate any views that depend on other objects, because they may not have changed yet in that transaction, and also, the entire

getSingleResult()

has been set and there is no transaction - if pessimistic locking fails and the transaction is rolled back transaction is rolled back

getResultList()

>TransactionRequiredException - if a lock mode has been set and there is no transaction transaction is rolled back - if the query execution exceeds the query timeout value set and the transaction is rolled

lock(entity, lockMode)

>PessimisticLockException will be thrown if the database locking failure causes transaction-level ... >TransactionRequiredException - if there is no transaction - if pessimistic locking fails and the transaction is rolled back

getSingleResult()

has been set and there is no transaction - if pessimistic locking fails and the transaction is rolled back transaction is rolled back

getResultList()

and there is no transaction transaction is rolled back PersistenceException - if the query execution exceeds the query timeout value set and the transaction

preStore(event)

.flush or Transaction/commit" title="Method of javax.jdo.Transaction">javax.jdo.Transaction.commit . It is called before the method

postStore(event)

.flush or Transaction/commit" title="Method of javax.jdo.Transaction">javax.jdo.Transaction.commit . It is called after the field values

checkConsistency()

. This method has no effect if a transaction is not active. If a datastore transaction ... to do so. If an optimistic transaction is active, this method obtains a datastore connection

refreshAll()

with an active transaction, all transactional instances will be refreshed. If called outside an active transaction, all nontransactional instances will be refreshed.