About flush

131-138 of 138Refresh

1	Entity Management Config questions references in the persistence context (until commit or flush), regardless of this setting. Question
1	Query results are not up to date for entities, not primitives ", personID) .executeUpdate(); em2 .flush(); em2 .clear(); tr .commit
1	Sometimes cascade persist does not work during commit intermediate flush operations with complete begin-commit transactions, then this indeed should work. btc_es
1	cannot delete objects after crash (see issue 2283) returns after writing and flushing the transaction updates to the recovery file (the database file
1	ObjectDB version 2.7.5 new objects of other transactions after flush (issue #2280). Fixed a bug in version 2.7.4 in
1	Getting an error when adding activation code to conf file .flush(); em.clear(); } }); em.getTransaction().commit
1	DB persist operation results are not available for another Thread/EntityManager immdiately seems similar to issue #2280. After flush (by Thread B) a snapshot of the database is used for further queries (until build 2.7.4_04). btc_es
1	Update more than 10000 entities by an update query fails . We can confirm that this is a bug. It could be related to flush changes in recent builds. We will try

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?

Search ObjectDB website
Read the FAQ
Follow the Tutorials
View or post in the forum
Search or file an issue
Contact support