 1 | whereas my ObjectDB database file isnt being created until the first EntityManager flush, so maybe |
1 | When classes are not enhanced the persistence context cache slows commit / flush, since every entity |
1 | (or flush) optimistic lock checks verify that different transactions do not conflict. This check |
1 | );
// Flush the JDO cache
m_persistenceManager.evictAll();
m |
1 | references in the persistence context (until commit or flush), regardless of this setting. Question |
1 | ",
personID)
.executeUpdate();
em2
.flush();
em2
.clear();
tr
.commit |
1 | intermediate flush operations with complete begin-commit transactions, then this indeed should work. btc_es |
1 | returns after writing and flushing the transaction updates to the recovery file (the database file |
1 | new objects of other transactions after flush (issue #2280). Fixed a bug in version 2.7.4 in |
1 | .flush();
em.clear();
}
});
em.getTransaction().commit |