17 | Remove an entity which attributes were changed - OptimisticLockException are local in memory and will fail with OptimisticLockException if user 1 is committing or flushing ... two different operations on the same object by two different users. Note that user 1 may flush the changes implicitly by running a query. You can run specific queries with COMMIT flush mode to avoid |
16 | On ensuring ID available after persist it did. Performing em.flush() immediately after em.persist(e) seems to work (although I'm not sure about the performance hit of flushing every time). This can be encapsulated as a wrapping persist(Object) method that also always flushes after persist(), to afford central experimentation. I |
13 | 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 |
13 | Soft Reference Object Cache Recommendation desire to have a JdoBlob2 object cache that flushes automatically when JVM full GC happens, which I ... [] to see that it did indeed get flushed from RAM and this listing after a single full GC.) I expected all byte[]s ... to see if evict() would allow the RAM to be flushed. (e.g., code like the following.) private static |
13 | evictAll() behavior one transaction and i want to reclaim memory after commit or even better after flush but I can imagine that after flush method it could be problematic so i did sth like this System.out.println("Cache ... ) { System.out.println("Cache size before flush = " + pm.getManagedObjects().size()); System.out.println(JDOHelper |
13 | Database Inconsistency or corruption.getValue()); }else{ em.persist(attr.getValue()); } em.flush(); if(em.contains(attr)){ em.merge(attr); }else{ em.persist(attr); } em.flush(); } */ ObjectValue persistedObjectValue = em.merge(ov ... to commit"); em.flush(); System.out.println("After flush " + em.getLockMode(ov)); persistedObjectValue |
13 | Visibility of changes in Transaction is not visible to a JPA QL Query JFK John Francis Please check if this is due to the default flush mode. In most JPA implementations ... are not be visible to queries with no flush. Probably you do have a flush in that code. Maybe in ... You are right! I was doing a count with the flush mode auto on... If I don't I can't see any |
13 | Remove a modified entity cause an optimistic lock exception although the former query has cause an automatically flush. Best regards btc_es BTC EmbeddedSystems ... the object. Flushing changes to the database (by running a query in FlushModeType.AUTO?) Removing the object. Committing the changes. The console application is the same but without the flush. Accordingly |
2 | 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 ... collection. Any change to entity objects after flush is not detected, as demonstrated by a simpler test |
2 | Explorer bug ? Objects seem to be missing from database in Class view, but are present as references a broken database. It might be related to the flush bugs that are being fixed in the last builds ... well (see attached odb). All the problems that you have reported till now are related to using flush extensively ... that you have reported till now are related to using flush extensively (many times until commit). Before |
