ObjectDB ObjectDB

Internal Website Search

111-120 of 200 resultsRefresh
5

Merge with Parent/Child entities not possible

();   entityManager.getTransaction().begin();   entityManager.persist(parentEntity);   parentEntity ... .assertEquals(4, parentEntity.getChildren().size());   entityManager.getTransaction().begin
5

OutofMemory error with Object DB 2.0

is used to begin the transaction. With objectdb 2.x do we need to close the PersistentManager ... ; } // are we at the start of a new transaction? if (writeItemNumber == 0 && !transaction.isActive()) { transaction.begin
5

ObjectDB CRUD Examples

")); EntityManager em = emf.createEntityManager(); em.getTransaction().begin ... .createEntityManager(); em.getTransaction().begin(); CriteriaBuilder criteriaBuilder = em
5

objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation

em = emf.createEntityManager();         em.getTransaction().begin();         em.persist(new ... ); .... } EntityManager em = emf.createEntityManager(); log_info("Persist project.."); em.getTransaction().begin
5

EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable

) {   if (WRITE_DATA_TO_DATABASE) {    em.getTransaction().begin();    for (int i = 0; i < 1000; i ... .getTransaction().begin();    for (int i = 0; i < 1000; i++) {     Point p = new Point(i, i);     em.persist(p
5

@Unique member combination not working

{             em.getTransaction().begin();             em.persist(person);             em.getTransaction ... = emf.createEntityManager();             try {                 em.getTransaction().begin
5

Rollback after commit fail

Hi, I have question regarding transaction management in ObjectDB. Consider following scenario: Thread 1: try{ EntityManager em = emf.createEntityManager(); em.getTransaction.begin ... .getTransaction.begin() persist object2 persist object1 em.getTransaction
5

How to do multithreading with embedded ObjectDB

.getTransaction().begin();         em.persist(p);         em.getTransaction().commit();         em.close ... ();                     em.getTransaction().begin();                     //Query q = em.createQuery("UPDATE Point
1

Issues with JDO Casting & Full Qualified Names

.createEntityManager();   em.getTransaction().begin();   MyEntity entity = new MyEntity();   entity ... .createEntityManager();         em.getTransaction().begin();         MyEntity entity = new MyEntity
1

preUpdate-methods are called when there is no change

Dear Support Team, we ran into some difficulties with a database. When fetching a entity using the EntityManager and afterwards calling "iterator().next()" a transaction begin/commit will end up in ... ().begin(); connection.getTransaction().commit(); // --> will result in a call of @PreUpdate

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