6 | Unable to execute update query) { System.out.println(i); em.getTransaction().commit(); em.flush |
6 | Query results are not up to date for entities, not primitives", personID) .executeUpdate(); em2 .flush(); em2 .clear(); tr .commit |
6 | finding post-persist pre-commit objectsHi, I'm wondering if there is a way to have post-persisted, pre-committed, objects show up in queries? ie: the object has been persisted, but not yet committed. Dave dmoshal David Moshal Yes, by setting the flush mode. support Support thanks, worked for me. dmoshal David Moshal |
6 | Query problem after transaction commit issue with a simple solution (e.g. changing flush mode from commit to auto could solve |
6 | PersistenceException: Failed to locate field your question re the server having access to an old version, shouldn't it automatically flush it's caches |
6 | Where Does ObjectDB Block/Lock? operations. On commit (or flush) optimistic lock checks verify that different transactions do not |
6 | Newbie : How to return the auto-generated ID value is available only after commit or flush and not after persist. If you need to have the id |
1 | ObjectDB 2.6.2Added support of entity classes with missing implemented interfaces in the Explorer. Added method com.objectdb.Utilities.newTrackable(em, cls) for improved performance. Added a temporary workaround for NullPointerException on query after flush (issue #1623). Improved title of query result windows |
1 | Getting an error when adding activation code to conf file.persist(myEntity); if(i % 5000 == 0) { em.flush(); em |
1 | ObjectDB 2.8.5Fixed a bug in using AS in SELECT NEW (breaks some Spring Data JPA queries). Fixed a bug in tracking changes to new collections after flush (issue #2640). Fixed a StackOverflowError on no access permission to objectdb.conf (issue #2643). Fixed a bug in managing pessimistic locks after using |
