ObjectDB ObjectDB

Internal Website Search

171-180 of 200 resultsRefresh
16

Dirty checking

to capture all objects that were changed after a commit, i.e: after the transaction has succeeded ... is being called after each object is changed, separately, in the middle of a transaction which might not suceed ... yet in that transaction, and also, the entire transaction could fail. i.e: I'd really like to know
15

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
14

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
14

Mismatch client-server protocol prefix

) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit ... the Exception: @Transactional     @Override     public TrackerUser findByName(String username ... other nice exceptions: @Transactional     @Override     public Unit findByName(String unitName
3

getSingleResult()

has been set and there is no transaction PessimisticLockException - if pessimistic locking fails and the transaction is rolled back LockTimeoutException - if pessimistic locking fails and only the statement is rolled back PersistenceException - if the query execution exceeds the query timeout value set and the transaction is rolled back Since: JPA 2.0
3

getResultList()

back TransactionRequiredException - if a lock mode has been set and there is no transaction PessimisticLockException - if pessimistic locking fails and the transaction is rolled back LockTimeoutException ... execution exceeds the query timeout value set and the transaction is rolled back Since: JPA 2.0
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
0

Constants.TX_SERIALIZABLE

Static Field javax.jdo.Constants String TX_SERIALIZABLE Transaction isolation level representing the requirement to serialize transactions. Since: JDO 2.2 See Also: PersistenceManagerFactory.getTransactionIsolationLevel() Transaction.getIsolationLevel()
0

Constants.TX_REPEATABLE_READ

Static Field javax.jdo.Constants String TX_REPEATABLE_READ Transaction isolation level representing the requirement to read the same data in the same transaction. Since: JDO 2.2 See Also: PersistenceManagerFactory.getTransactionIsolationLevel() Transaction.getIsolationLevel()
0

checkConsistency()

with the datastore. This method has no effect if a transaction is not active. If a datastore transaction is active, this method verifies the consistency of instances in the cache against the datastore ... to do so. If an optimistic transaction is active, this method obtains a datastore connection and verifies

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support