7 | Visibility of changes in Transaction is not visible to a JPA QL Query.println("Only found " + newTotal + " items expected " + (howMany + oldAmount)); } tx.commit ... the default is AUTO. In ObjectDB the default is COMMIT (which is more efficient). support Support ... commit in a Query... For example if I implement the following in Singleton; public Item findItem |
7 | Updating Entities().begin(); this.rate = rate; Main.paygradeDB.getTransaction().commit(); return true ... (); Main.paygradeDB.getTransaction().commit(); System.out.println("--------"); query ... ; * Main.paygradeDB.getTransaction().commit(); */ Main.employeeDB.getTransaction().commit |
7 | Updating existing persistence entries get it to work. The transparent update needs a transaction to be started and then committed ... can commit the session afterwards and that's it. I mean I don't need to modify the object ... are identified automatically. Of course, you have to begin and commit a transaction (when SAVE is selected |
7 | @Unique member combination not working().commit(); } finally { if (em.getTransaction().isActive()) { em ... (); em.persist(person); em.getTransaction().commit(); } finally ... to commit transaction: Unique constraint (com.objectdb.test.bug.forum.T1522$Person[name,surname]) failed |
7 | EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable serialization="false" /> <cascade-persist always="auto" on-persist="false" on-commit ... " /> <cascade-persist always="auto" on-persist="false" on-commit="true" /> <dirty ... ++) { Point p = new Point(i, i); em.persist(p); } em.getTransaction().commit |
7 | Some technical questions an attribute of an object, but don't commit yet. Can another transaction fetch this object ... transaction either commits or rolls back? Since ObjectDB implements online backups, does it implement ... of an object, but don't commit yet. Can another transaction fetch this object without blocking? Yes |
7 | how to persist an object twice into two diff. collections of two diff. classes); db.persist(tmpComp); } db.commit(); db ... .persistence.RollbackException Failed to commit transaction: Attempt to reuse an existing primary key value (ch.hsr.gymtastic.domain.Squad:1) (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:259 |
1 | Blocked by find) com.objectdb.jpa.EMImpl.commit(EMImpl.java:276) rbccm.felix.objectdb.workflow.ObjectDbDataContainer ... :662) I'm not sure how to read this but it looks like objectdb is blocked in the commit ... .jpa.EMImpl.commit(EMImpl.java:276) at rbccm.felix.objectdb.workflow.ObjectDbDataContainer.save |
1 | Query in nested transaction returns detached entity if lazy-loaded = 1) and committed, during the commit an optimistic lock exception is thrown. The version flag ... to commit transaction: Optimistic lock failed for object com.btc.ep.base.bl.internal.entities.mapping ... ) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:289) at com.btc.ep.base.transactions.internal |
1 | Removed entities can be found by query in the same transaction the database and the change was flushed but not committed yet then the database maintains ... other transactions after that flush were not visible to that transaction (until commit). Build 2.7.4_04 fixed it by creating a new snapshot on query execution if changes have been committed after the last |
