About commit

issue

GC Memory

Hi there, I was hoping to get some support on ObjectDB regarding memory usage.  I received the following error.  Context for the error is found below. [2015-04-27 13:16:18 #20 server] ... many large objects in one transaction. Note that only commit can release memory, not flush . So bulk load of data into the ... be done in smaller transaction (with begin and commit for each, and possibly also  clear  after commit ) ...

 
release

2.4.3

... Fixed a bug in running queries between flush and commit. Fixed a deadlock ( issue #62 ). Fixed ... a bug in removing a new flushed entity object before first commit ( issue #86 ). Fixed a NullPointerException in ...

 
release

2.3.6

... a bug in removing a new flushed entity object before first commit ( issue #86 ). Fixed a NullPointerException in ... cascading persist after updating the database and before commit (issue #78 ). Fixed NullPointerException on ...

 
forum_thread

problem with lazy loading - unittest project attached

hi, i'm still testing objectdb together with spring-data-jpa. i made a test which should simulate 4 requests 1. save entity 2. read an existing entity, add onetomany relation 3. read an existing entity, add another onetomany relation 4. read entity, get relations. i have the feeling this is not the optional way to test this, because of the differnt transaction behavior. the test is not transactional, but the spring repository methods are. ... be valid for each repository method, so i guess after the commit the id is assigned?! like i said, this is properbly not the best ... allow me to call entityManager.getTransaction().begin()/commit() and i also can not set the isolation to READ_UNCOMMITTED so i ...

 
issue

Schema-Update: Rename superclass and remove one subclass

Hello, we renamed a superclass and removed one of the subclass. If we then try to open the Database (with ObjectDB-Explorer) we get a "Failed to generate dynamic type ..."   Small Example: Generate Database ... ) ; em. getTransaction ( ) . commit ( ) ;   em. close ( ) ; ... "b" ; em. getTransaction ( ) . commit ( ) ;   em. close ( ) ; ...

 
release

2.4.2

... Fixed a bug in running queries between flush and commit. Fixed a deadlock ( issue #62 ). Fixed ... a bug in removing a new flushed entity object before first commit ( issue #86 ). Fixed a NullPointerException in ...

 
manual

DELETE Queries in JPA/JPQL

Explains how to apply server side bulk delete using a JPA/JPQL query.... Applying changes to the database by calling the commit method. JPQL DELETE queries provide an alternative way ... (which use other EntityManager instances) only after commit . This page covers the following topics: ...

 
forum_thread

Problem with byte arrays in JDO - ClassCastException

A bizarre ClassCastException is thrown if I attempt to obtain a byte array field as the result of a Query: Exception in thread "main" java.lang.ClassCastException: java.lang.Boolean cannot be cast to [B at spiffy.test.ObjectdbTest.main(ObjectdbTest.java:44) ... ; pm. currentTransaction ( ) . commit ( ) ; pm. currentTransaction ( ... ; pm. currentTransaction ( ) . commit ( ) ; query = pm. newQuery ( ...

 
release

2.7.0

... Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed ... Fixed a bug in running queries between flush and commit. Fixed a deadlock ( issue #62 ). Fixed ...

 
forum_thread

Intermittent: "Attempt to reuse an existing primary key value" when persisting a new instance

Hi,   I don't have a useful test case to expose this issue, but I am getting an intermittent "Attempt to reuse an existing primary key value". In this particular instance, the error is: ... enterprise . transaction . JavaEETransactionImpl . commit ( JavaEETransactionImpl. java : 453 ) at ... . transaction . JavaEETransactionManagerSimplified . commit ( JavaEETransactionManagerSimplified. java : 857 ) ...