ObjectDB ObjectDB

Internal Website Search

1-10 of 149 resultsRefresh
142

em.flush(); em.clear(); loosing data and not persisting managed objects

I'm having trouble with flush() and clear() in a loop inside a transaction not persisting modified ... .persist(v); v.setRemark(sbs); if(i % 10 == 0) { System.out.println("flushing"); em.flush(); em.clear(); } System.out.println("i="+i); TestEntity t1 = em.find
80

flush()

Method javax.persistence.EntityManager void flush() Synchronize the persistence context to the underlying database. Throws: TransactionRequiredException - if there is no transaction PersistenceException - if the flush fails Since: JPA 1.0
64

Storing JPA Entity Objects

of entity objects requires special consideration. The combination of the clear and flush methods ... % 10000) == 0) { em.flush(); em.clear(); } } em.getTransaction ... are flushed to the database before clearing, otherwise they would be lost. Updates that are sent
38

Setting and Tuning of JPA Queries

on which they were invoked). Flush Mode (setFlushMode) Changes made to a database using an EntityManager ... . Therefore, before a query is executed, uncommitted database changes (if any) have to be flushed to the database in order to be visible to the query. Flush policy in JPA is represented by the FlushModeType enum
32

Database Management Settings

Explains settings and performance tuning of the ObjectDB Java object database for JPA/JDO.
28

Tracking changes to new collections (in enhancement mode) after flush

operation (e.g. flush) just before adding the last element? Does it happen consistently? is it reproducible ... element yes, there is probably a flush before adding the last element yes, it is always reproducible in ... ();         em.flush();         long id = entity.id;         entity.addValue();         em.getTransaction
28

ArrayIndexOutOfBoundsException on flush

The following exception was thrown when my app attempted to flush an objectdb database: Caused by: rbccm.felix.framework.ApplicationException: Error flushing graph container at rbccm.felix.objectdb.workflow.ObjectDbGraphContainer.flush(Unknown Source) at rbccm.felix.objectdb.workflow
28

An entityManager.flush() with many entities is not possible

The following exception occures if we call entityManager.flush() where the corresponding JPA ... .getTransaction().commit() instead of a entityManager.flush() works correctly. Unfortunately I have not found a simple example to reproduce this exception. The entity model of the flushed JPA
8

flush()

Methodjavax.jdo.PersistenceManager void flush() Flushes all dirty, new, and deleted instances to the data store. It has no effect if a transaction is not active. If a datastore transaction is active ... is held until the end of the transaction. If exceptions occur during flush, the implementation
8

flush()

Method javax.jdo.PersistenceManager void flush() Flushes all dirty, new, and deleted instances to the data store. It has no effect if a transaction is not active. If a datastore transaction is active ... is held until the end of the transaction. If exceptions occur during flush, the implementation

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