ObjectDB ObjectDB

Internal Website Search

61-70 of 151 resultsRefresh

Remove not working

earlier in the same transaction. No exception is thrown if em.flush() is invoked before em.remove ... . The fix was to do a PersistenceManager.flush() before trying to gather the Extent the second time. I did ... . transaction.begin get Extent, traverse its entries, delete an object in there // needs a flush

Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01)

); } m_EntityManager.getTransaction().commit(); m_EntityManager.flush(); m ... (); m_DataKeysCache.clear(); m_EntityManager.flush(); m_EntityManager.clear(); } When we completed import data to database we also using following code for flush all data to DB

Run out of memory

#Batch_Store_. However the problem is that it seems that even calling flush followed by clear ... ) {     this.commitCount.set(0); this.em.flush(); this.em.clear(); System.err.println("Flushing"); } } protected void onCommit() {     this.em.getTransaction().commit

Performance in large transactions

to apply changes to the database on flush/commit. This could be done by keeping a copy of every managed object and comparing copies to actual objects on every flush or commit, but this is inefficient ... comparison on every flush. To avoid this, we introduce now a new method, con.objectdb.Utilities

Cannot save or update entity on Spring App

public Language persist(Language guest) { em.persist(guest); em.flush ... .flush(); em.refresh(guest); em.clear(); em.close(); return guest ... ().commit(); em.flush(); em.clear(); em.close(); return guest

SectionClassifier message in log

.framework.ApplicationException: Error flushing queue at rbccm.felix.objectdb.messaging.ObjectDbMessagePipe.flush(Unknown Source) at rbccm.felix.objectdb.messaging.ObjectDbMessagePipe.flush(Unknown

After using the enhancer, Lazy loaded collections are no longer loading. They are set as null

Account(); entityManager.persist(account); entityManager.flush(); Project project = new Project(); project.setAccount(account); entityManager.persist(project); entityManager.flush ... ();                 Account account = new Account();         em.persist(account);         em.flush

docker documentation

>) piped.write(13) piped.flush() sleep(100) piped.println(<PASSWORD>) piped.write(13) piped.flush() sleep(100) piped.println(<LICENSE>) piped.write(13) piped.flush() } } Now here's the strange bit, the license url

Internal exception

to resolve a mapped by relationship, which required a flush before running the mapped by query (due to changes since last commit/flush) in order to retrieve the mapped by instances. The stack trace indicates a failure to cascade persist operation from unknown reason during that flush. Any

Query in nested transaction returns detached entity if lazy-loaded

that have been persisted by other transactions from within a transaction that was flushed before these objects have been persisted. This is caused due to the way that currently ObjectDB manages flushed transactions as a snapshot of the database when flush occurs. Build 2.7.4_04 includes a workaround

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