Fast Object Database for Java - with JPA/JDO support

Internal Website Search

41-50 of 200 resultsRefresh
20

Memory error during commit, if @ElementCollection field contains many elements

Memory error during commit, if @ElementCollection field contains many elements
18

Entity Management Settings

" on-persist="false" on-commit="true" /> commit or flush), regardless of this setting. The level2 attribute specifies the size ... commit="true" /> The
18

CRUD Database Operations with JPA

.getTransaction().commit(); Operations that modify the content of the database (such as storing new objects ... only when the transaction is committed. The Storing Entities section in chapter 3 discusses ... .getTransaction().commit(); In the above code, p must be a managed entity object of the EntityManager em
18

[ODB1] Chapter 2 - A Quick Tour

: 37 pm.currentTransaction().commit(); 38 pm.close(); 39 } 40 ... to be stored physically in the database when the transaction is committed (line 37). Note: Memory objects ... . Lines 36-38 On transaction commit (line 37), new persistent objects (like a new ArrayList
15

Locking in JPA

separately. Optimistic locking is applied on transaction commit. Any database object ... is being performed on an old version of a database object, for which another update has already been committed ... must be revealed earlier (before transaction commit) pessimistic locking can be used. When using
15

Setting and Tuning of JPA Queries

em can be visible to anyone who uses em, even before committing the transaction (but not to users ... , which has two values: AUTO - changes are flushed before query execution and on commit/flush. COMMIT - changes are flushed only on explicit commit/flush. In most JPA implementations the default is AUTO. In
11

JPA Lifecycle Events

(added to the EntityManager). @PostPersist - after storing a new entity in the database (during commit or ... the database (during commit or flush). @PreRemove - when an entity is marked for removal in the EntityManager. @PostRemove - after deleting an entity from the database (during commit or flush). An entity
11

Deleting JPA Entity Objects

); em.getTransaction().begin(); em.remove(employee); em.getTransaction().commit(); The entity object is physically deleted from the database when the transaction is committed. Embedded ... back and not committed the object is not deleted. An IllegalArgumentException is thrown by remove
11

Auto Generated Values

id; : } During a commit the AUTO strategy uses the global number generator to generate ... also generates an automatic value during commit for every new entity object. The difference is that a separate ... is persisted (i.e. before commit). This may be useful when the primary key value is needed earlier
11

Working with JPA Entity Objects

via an EntityManager’s persist method, which must be invoked within an active transaction. On transaction commit ... commit. See the Updating Entities section for more information about making changes to entities ... to Removed, and is physically deleted from the database during commit. More details on object

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