ObjectDB ObjectDB

Internal Website Search

71-80 of 151 resultsRefresh

Spring Transactions (@Transactional) within ObjectDB

Sandeep Sandeep Dhamale Build 2.5.2_01 adds support for enabling auto flush by default, by setting a system property:     System.setProperty("objectdb.temp.auto-flush", "true"); before loading ObjectDB, or as a JVM argument: > java -Dobjectdb.temp.auto-flush=true ... support Support

Querys slower when execute a query after every persist

EmbeddedSystems When entity classes are not enhanced every flush or commit requires comparison ... and should be flushed to the database. If you have more objects in the current transaction it takes more time (i.e. every query execution requires a more expensive flush). Results of your test with enhanced

remove & persist in same transaction => Attempt to reuse an existing primary key value

); // If we call a FLUSH it works. // em.flush(); System.out.println("create and persist AGAIN"); // create ... id; } } A possible workaround, that this scenario works is to call a flush (see commet) after em

Heap Limit reached although the option 'objectdb.temp.page-file' is activated

although the flush and the GC were invoked regularly. The attachments show the memory heap dump ... .flush(OBM.java:765) ~[na:na] btc_es BTC EmbeddedSystems The heap dump shows millions of entity objects ... seem related to objectdb.temp.page-file, which may work and move modified database pages (after flush

Error using query with MAX() function

If you are using EntityManager's flush you should try build 2.2.3_04 that fixes a critical bug ... the manual. if( (count % config.getUpdateFreq()) == 0) { em.flush

Duplicate Entity class names causes Exception in Query

.numberOfMapItems");   //ObjectDb demands we flush transaction to db if we wish to see its results   q ... demands we flush transaction to db if we wish to see its results q.setFlushMode(FlushModeType.COMMIT

ObjectDB 2.2.6

Fixed the "Attempt to reuse an existing primary key value" after flush bug. Fixed a bug in tracking changes to collections of new flushed entity objects. Fixed generated value (ID allocation) bug with flush and in EJB containers. Fixed a NullPointerException on getObjectsById. Fixed a server freeze

NoResultException: No matching results for a unique query

modifying the flush mode. Which flush mode are using? support Support Hi, I didn't change it so I am using the default Flush Mode (COMMIT). I don't get why this is happening, it just has happened

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

(o); if (Global.USE_OBJECTDB) { em.flush(); //ObjectDB ensure id ... .TransactionRequiredException //Attempt to flush a transaction when no transaction is active ... .persistence.TransactionRequiredException Attempt to flush a transaction when no transaction is active

com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null:

_OBJECTDB) { em.flush(); //ObjectDB ensure id exists ... ownedElement) { if (DO_PRE_FLUSH) { em.flush(); } if (owner

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