Home » Search

About flush

51-60 of 128Refresh
Forum
3

Remove a modified entity cause an optimistic lock exception

although the former query has cause an automatically flush. Best regards We started exploring ... the database. Modifying the object. Flushing changes to the database (by running a query in ... but without the flush. Accordingly the following console application includes flush before remove and throws
Issue
3

Remove of an entry from a @OneToMany collection is not possible if the enhancer is disabled

");   parentEntity.getChildEntityContainer().put("01", childEntity);   entityManager.flush ... .getChildEntityContainer().remove("01");   entityManager.flush();   entityManager.getTransaction().commit ... to entity objects after flush is not detected, as demonstrated by a simpler test case
Forum
3

Should derived fields of an EmbeddedId be manually maintained by app code?

(newObj); //em.flush(); return newObj; } } import java.io.Serializable; import ... "); System.err.flush(); System.out.flush(); int numberOfMapItems = container ... expected: " + numItems); } System.out.println("Done Checks"); System.err.flush
Forum
3

Soft Reference Object Cache Recommendation

to upload). I desire to have a JdoBlob2 object cache that flushes automatically when JVM full GC happens ... somewhere.  (I also had my program create a 1 GB softly referenced byte[] to see that it did indeed get flushed ... to see if evict() would allow the RAM to be flushed.  (e.g., code like the following.) private static final
Forum
3

Visibility of changes in Transaction is not visible to a JPA QL Query

from the EAR Please check if this is due to the default flush mode. In most JPA implementations ... AUTO mode? No. Changes during transaction are not be visible to queries with no flush. Probably you do have a flush in that code. Maybe in the setting of the EntityManagerFactory / EntityManager
Issue
2

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
Forum
2

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

); } m_EntityManager.getTransaction().commit(); m_EntityManager.flush(); m ... _EntityManager.flush(); m_EntityManager.clear(); } When we completed import data to database we also using following code for flush all data to DB and release memory m_EntityManager.flush
Forum
2

Remove not working

transaction. No exception is thrown if em.flush() is invoked before em.remove(a); Is it possible ... the object that was deleted. The fix was to do a PersistenceManager.flush() before trying to gather ... in there // needs a flush() here else the next statement throws the Exception get Extent
Forum
2

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
Result
2

ObjectDB version 2.2.6

Version 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