About transaction

161-170 of 200Refresh
JDO Doc
3

makeNontransactional(pc)

Method javax.jdo.PersistenceManager void makeNontransactional(   Object pc ) Make an instance non-transactional after commit. Normally, at transaction completion, instances are evicted from the cache ... at transaction completion. Instead, the instance remains in the cache with nontransactional state
JDO Doc
3

refreshAll()

Method javax.jdo.PersistenceManager void refreshAll() Refresh the state of all applicable instances from the data store. If called with an active transaction, all transactional instances will be refreshed. If called outside an active transaction, all nontransactional instances will be refreshed. Since: JDO 1.0 See Also: refresh(Object pc)
JPA Doc
3

setRollbackOnly()

Method javax.persistence.EntityTransaction void setRollbackOnly() Mark the current resource transaction so that the only possible outcome of the transaction is for the transaction to be rolled back. Throws: IllegalStateException - if isActive() is false Since: JPA 1.0
JDO Doc
3

setTransactionIsolationLevel(level)

Method javax.jdo.PersistenceManagerFactory void setTransactionIsolationLevel(   String level ) Set the value for transaction isolation level for this PMF. Transaction isolation levels are defined in ... - the transaction isolation level Since: JDO 2.2 See Also: getTransactionIsolationLevel() Constants.TX_READ
Forum
3

Dirty checking

that were changed after a commit, i.e: after the transaction has succeeded, so that I can update views ... , separately, in the middle of a 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
Forum
3

How to Use a SF with extended Persistence Context?

Hey, I have a problem to use SF with an Extended Persistence Context Regarding to Transactions ... to the SF I get com.objectdb.o._PersistenceException: Attempt to begin a new transaction when a transaction is active. In principal The SF doesn't need to begin any transaction since it only get called by
Issue
3

Best practise loading big data

when it came to transactions with lots of entities. We have a scenario in which we need efficient data ... . When do this within one transaction without holding a reference on the retrived entities then we discover ... only workarounds helped to gain a lower memory footprint. One is to stupidly commit the transaction
Forum
3

OutofMemory error with Object DB 2.0

and inserts 200 records at a time. The transaction obtained from the PersistentManager is commited after persisting 200 records and then the same transaction object from the same PersistentManager is used to begin the transaction. With objectdb 2.x do we need to close the PersistentManager
Forum
3

Mismatch client-server protocol prefix

) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit ... . This is the code which raises the Exception: @Transactional     @Override     public ... other nice exceptions: @Transactional     @Override     public Unit findByName(String unitName) throws
Forum
3

Unexpected NoSuchFieldError exception

.NoSuchFieldError: __odbTracker 3) Attempt to start a transaction while another transaction is running ... .transact(ObjectDbDatabase.groovy:82) at app.framework.Database$transact.call(Unknown Source) at org ... .call(AbstractCallSite.java:117) at app.database.ObjectDbDatabase.transact(ObjectDbDatabase.groovy:82