100 | StackOverflowError after commitWe have following issue, if we execute a commit: java.lang.StackOverflowError at com.objectdb.o.ENT.D(ENT.java:411) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D(ENT.java:417) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D |
100 | Need to close+open database for a commit to be taken into accountHi, I have one case where commit (update of entity in this case) is not taken in account unless database is actually closed and re-open, no error. I tried to use flush instead of close+re-open but it does not work. So currently there is a dirty close + open + reload on each update |
100 | Failed to commit transaction: Java heap space (error 613).RollbackException Failed to commit transaction: Java heap space (error 613) We are using ObjectDB 2.4.6_10 |
100 | Query and commit simultaneouslyIs it possible to query and commit on the same persistence manager (i.e. same odb file) at the same time? jake Jake Hang Multithreading is fully supported by ObjectDB, so you can query and update the database at the same time using multiple threads. However, if all the threads share the same |
96 | Git seems not to commit objectdb.confGit seems not to commit objectdb.conf |
20 | Error on commitI get the following on commit: (v2.3.7_15) Let me know if you need more info. Caused by: com.objectdb.o.InternalException at com.objectdb.o.InternalException.f(InternalException.java:236) [:] at com.objectdb.o.SPW.aq(SPW.java:109) [:] at com.objectdb.o.PGW.am(PGW.java:210) [:] at com.objectdb |
19 | CRUD Database Operations with JPA.getTransaction().commit(); Operations that modify the content of the database (such as storing new objects ... only when the transaction is committed. The Storing Entities section in chapter 3 discusses ... .getTransaction().commit(); In the above code, p must be a managed entity object of the EntityManager em |
19 | Entity Management Settings" on-persist="false" on-commit="true" /> <dirty-tracking arrays="false" /> </entities ... the persistence context (until commit or flush), regardless of this setting. The level2 attribute specifies ... > element <cascade-persist always="auto" on-persist="false" on-commit="true" /> The <cascade |
19 | Updating JPA Entity Objects.getTransaction().begin(); employee.setNickname("Joe the Plumber"); em.getTransaction().commit(); The entity object is physically updated in the database when the transaction is committed. If the transaction is rolled back and not committed the update is discarded. On commit the persist operation |
1 | [ODB1] Chapter 2 - A Quick Tour: 37 pm.currentTransaction().commit(); 38 pm.close(); 39 } 40 ... to be stored physically in the database when the transaction is committed (line 37). Note: Memory objects ... . Lines 36-38 On transaction commit (line 37), new persistent objects (like a new ArrayList |
