ObjectDB ObjectDB

Internal Website Search

161-170 of 200 resultsRefresh

Remove a modified entity cause an optimistic lock exception

. Committing the changes. The console application is the same but without the flush. Accordingly ... ().commit();         em.close();         em = emf.createEntityManager();         em ... ();         em.flush();         em.remove(e);         em.getTransaction().commit();         em.close

Where Does ObjectDB Block/Lock?

) Does it lock at transaction.begin() if optimistic=false? 4) Does it lock at transaction.commit ... with optimistic locking, the call to transaction.commit() is where entity object locking actually happens ... are all happening concurrently up to the point where transaction.commit() is called? CBE CBE > Does this mean

What algorithm in find()

", i);    o.setParent( p );    em.persist(o);    trans.commit();    if ((i & 0xFF)==0){     end ... );    }   } The time cost of each 256 commits changed from 0.343 to 59.344 seconds, the graph attached shows ... ? gzdillon Lai Yang Slow commit might be the result of not using enhancement and not calling clear

Object belongs to another EntityManager - ERROR

[stderr] (http-- Failed to commit transaction: Object 'pbdmodel.impl.OrgJedinicaImpl ... -5) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:290) 10:29:14,895 ERROR [stderr] (http--10.23.3 ... [stderr] (http-- at com.objectdb.jpa.EMImpl.commit(EMImpl.java:287) 10:29

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

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

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

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

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

New entity objects are duplicated on merge cascading

();         em.getTransaction().begin();         em.persist(new Book());         em.getTransaction().commit ... (book);         em.getTransaction().commit();         em.close();                 em = emf ... ();         em.persist(new A());         em.getTransaction().commit();                 em.close

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

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support