ObjectDB ObjectDB

Internal Website Search

181-190 of 200 resultsRefresh
7

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
7

@OneToMany(fetch = FetchType.LAZY) list is always null

); transaction.commit(); } catch (NotSupportedException e) { e ... ); entityManager.merge(child.getParent()); transaction.commit(); } catch ... { transaction.begin(); entityManager.persist(o); transaction.commit
6

Remove not working

retrieval works but during commit the exception above get's thrown. The weird thing is that it works ... .a); em.getTransaction().commit(); em.close(); em = emf.createEntityManager ... ); A a = em.find(A.class, 2); em.remove(a); em.getTransaction().commit
6

Performance and memory usage of queries

MyEntityElement();     myEntity.getList().add(myEntityElement);    }    em.getTransaction().commit ... .getTransaction().commit();   em.close();   emf.close(); } @Entity public static class MyEntity ...     em.getTransaction().commit(); On update ObjectDB prepares all the revised pages in memory before
6

persisting object with long[][] arrays of array

[][]. It is taking very long to persist and sometimes never finish - it hangs on getTransaction().commit ... .getTransaction().begin();         emg.persist(obj);         emg.getTransaction().commit();         emg ... (obj);         emg.getTransaction().commit();         emg.clear();         emg.close
6

find() cost unreasonable time!

@ %s %n", iNum, (System.currentTimeMillis()-start)/1000f);     trans.commit();     em.clear();     trans.begin();    }   }   trans.commit();   System.out.printf("Total: %d, Level:%d %n", iNum ... of a node, that is a big problem. gzdillon Lai Yang After commit everyone can see the changes
1

NoResultException: No matching results for a unique query

are usually (but not always) invisible to the query until commit. This behavior can be changed by ... am using the default Flush Mode (COMMIT). I don't get why this is happening, it just has happened ... . Could you please tell me why I do even get a NoResult* exception within a transaction commit that I've been using
1

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
1

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
1

NullPointer running multiple client against server

{ em.persist(obj); em.getTransaction().commit(); } catch(Exception e) { if(em ... .java:595) Caused by: com.objectdb.o._RollbackException: Failed to commit transaction: $1 at com ... .onObjectDBError(OBC.java:1443) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:277) ... 11 more Caused by: java

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