ObjectDB ObjectDB

Internal Website Search

11-20 of 74 resultsRefresh
15

ObjectDB Object Database Features

connections and timeout. Caching L1 entity object cache (per EntityManager). L2 shared entity data
12

javax.persistence.Query

- if the statement execution exceeds the query timeout value set and only the statement is rolled back PersistenceException - if the query execution exceeds the query timeout value set and the transaction is rolled ... exceeds the query timeout value set and only the statement is rolled back TransactionRequiredException
8

javax.persistence.EntityManager

should not rely on the standard timeout hint. Depending on the database in use and the locking mechanisms ... on the standard timeout hint. Depending on the database in use and the locking mechanisms used by ... recognized, it is silently ignored. Portable applications should not rely on the standard timeout hint
6

executeUpdate()

- if there is no transaction QueryTimeoutException - if the statement execution exceeds the query timeout ... the query timeout value set and the transaction is rolled back Since: JPA 1.0
6

getSingleResult()

the query timeout value set and only the statement is rolled back TransactionRequiredException - if a lock ... and only the statement is rolled back PersistenceException - if the query execution exceeds the query timeout
6

getResultList()

execution exceeds the query timeout value set and only the statement is rolled ... exceeds the query timeout value set and the transaction is rolled back Since: JPA 1.0
6

getSingleResult()

timeout value set and only the statement is rolled back TransactionRequiredException - if a lock mode ... 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
6

getResultList()

- if the query execution exceeds the query timeout value set and only the statement is rolled ... execution exceeds the query timeout value set and the transaction is rolled back Since: JPA 2.0
4

find(entityClass, primaryKey, lockMode, properties)

. Portable applications should not rely on the standard timeout hint. Depending on the database in use
0

javax.jdo.JDOEntityManager

on the standard timeout hint. Depending on the database in use and the locking mechanisms used by the provider

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