Home » Search

About commit

161-170 of 200Refresh
Issue
1

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

(parentEntity);   entityManager.getTransaction().commit();   entityManager.getTransaction().begin ... .getChildEntityContainer().remove("01");   entityManager.flush();   entityManager.getTransaction().commit ... e = new MyEntity();         em.persist(e);         em.getTransaction().commit();         em
Forum
1

Run out of memory

("Flushing"); } } protected void onCommit() {     this.em.getTransaction().commit(); this.em.clear(); this.em.close();     System.err.println("Commit Done"); } protected void ... (); for (DatabaseData d : lotsOfData) insertDatabaseData(d); if (commit) onCommit
Forum
1

Schema Update: class hierarchy change

.persist(entity);   em.getTransaction().commit();     em.getTransaction().begin();   MyEntity ... (entityWithID1.name);   System.out.println(entityWithID1.value);   em.getTransaction().commit ... "; //  entity.value = "value123"; //  em.persist(entity); //  em.getTransaction().commit();     em
Forum
1

Some technical questions

commit yet. Can another transaction fetch this object without blocking, and will it see the old attribute? Or will the second transaction block until the first transaction either commits or rolls ... one transaction I change an attribute of an object, but don't commit yet. Can another transaction
Issue
1

stress test -> com.objectdb.o.InternalException: null

EntityManager) that had to commit changes using the connection (which has already been moved ... .getTransaction().commit();         em2.close();                 em1.createQuery("UPDATE TestEntity SET x = 1").executeUpdate();         em1.getTransaction().commit();         em1.close
Issue
1

Unexpected exception (Error 990) com.objectdb.o.InternalException

();         em.persist(new MyEntity());         em.getTransaction().commit();         // Keep a strong ... :                  em.getTransaction().begin();         embeddable.update();         em.getTransaction().commit ... ().commit();         // Keep a strong reference to the embeddable but free the entity:         List
Forum
1

Updating Entities

().begin();   this.rate = rate;   Main.paygradeDB.getTransaction().commit();   return true ... .executeUpdate(); Main.paygradeDB.getTransaction().commit(); System.out.println ... ().begin(); * this.rate = rate; * Main.paygradeDB.getTransaction().commit(); */ Main
Forum
1

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). Yes, changing the Query ... that case I can see the results of the transaction before commit in a Query... For example if I
Forum
1

Updating existing persistence entries

a transaction to be started and then committed after the setter of an persisted object is called ... more fields to a call like "session.update(objectInstance)". I can commit the session ... within an active transaction the changes are identified automatically. Of course, you have to begin and commit
Issue
1

cannot delete objects after crash (see issue 2283)

="false" mode: In this mode, commit ... of the sync mode by delaying returning from commit, gathering several concurrent committing ... the last committed transactions after recovery (just that the database will not become corrupted