About flush

81-90 of 138Refresh
Forum
1

EntityManager refresh problem

object has not been stored yet in the database. If we change the code and add a flush operation ... .persist(simpleEntity1);             entityManager.flush();             simpleEntity1.setFieldA
Forum
1

Error using query with MAX() function

) it might help in understanding the problem. If you are using EntityManager's flush you should try build 2.2 ... .flush(); em.clear(); }   Thank you for the update. I am more worried
Forum
1

Exception on creation when running multithreaded

are executed on flushed changes that have not been committed yet - this may indicate an ObjectDB bug ... would be very helpful. Yes, the query was executed on flushed changes and I also had: typedQuery
Issue
1

GC Memory

is loaded into objectdb, the EntityManager is flushed and released.  This process is repeated ... flush. So bulk load of data into the database should be done in smaller transaction (with begin
Forum
1

JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception

+ "...."  );         this.em.persist(guest);   this.em.flush();   System.out.println( "persisted: "  + guest ... ) {   System.out.println( "will persist : "  + guest + "...."  );   this.em.persist(guest);   this.em.flush
Forum
1

multi thread application, id field sporadically null

). Again, if you can provide a test case it would be helpful. we managed to overcome the problem by using flush(), clear() and refresh()  Good. See also this manual page, regarding setting a flush mode. hgzwicker
Forum
1

Need to close+open database for a commit to be taken into account

Hi, I have one case where commit (update of entity in this case) is not taken in account unless database is actually closed and re-open, no error. I tried to use flush instead of close+re-open ... entities) I would like to know if i could try anything else that flush to replace the close+open
Issue
1

Persist & remove in same transaction

I have a test case (attached) which performs the following actions: Open a new transaction Create & persist a simple entity object, EntityManager is flushed, Transaction is not committed Count ... Remove the entity object, EntityManager is flushed & cleared, Transaction is not committed Count
Forum
1

Query for objects persisted within the same transaction

was persisted. You may change the default flush mode: http://www.objectdb.com/java/jpa/query/setting#Flush
Issue
1

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

(new TestEntity());         em1.flush();                 EntityManager em2 = emf ... ;     } } It is caused as a result of running an UPDATE query on uncommitted flushed changes in some circumstances