Home » Search

About commit

161-170 of 200Refresh
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

[ObjectDB 2.2.6_02] Unexpected exception (Error 990) at com.objectdb.o.OBC.aJ(OBC.java:961)

); em.getTransaction().commit(); } catch (Exception ex ... .persist(chart); em.getTransaction().commit(); } catch (Exception ex ... (); chart = em.merge(chart); em.getTransaction().commit(); } catch (Exception ex
Forum
1

alter table

: Exception in thread "main" [ObjectDB 2.2.9_04] javax.persistence.RollbackException Failed to commit ... 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:277) at test.testString.main(testString.java:55 ... .o.OBM.bE(OBM.java:715) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:274) ... 1 more Caused by
Forum
1

Attempt to remove a detached entity object (error 613)

to merge it ... Unfortunatly, i get this error : Failed to commit transaction: Attempt to remove a detached entity object (error 613)      at com.objectdb.jpa.EMImpl.commit(EMImpl.java:290) We see in this stack trace that is a commit operation, all right ... So why does it try to remove the object
Forum
1

ClassCastException: cannot be cast to com.objectdb.spi.TrackableUserType

.makePersistent( instance ) transaction.commit() } catch( e ... .OBM.bE(OBM.java:715) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:274) at javax.jdo.Transaction$commit.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall