5 | Selective merge/cascade of detatched entity the same EntityManager for all threads, but this will likely introduce locking/synchronize issues |
5 | ObjectDB version 2.1 has been released the download). Added support of disabling optimistic locking exceptions. Added support of url |
5 | Updating Entities._OptimisticLockException: Optimistic lock failed for object application.model.Paygrade#184 (object has version 86 instead |
5 | Wrong select results="." max="128mb" /> <recording enabled="false" sync="false" path="." mode="write" /> <locking version |
5 | Should I use ObjectDB and JDO? object locking was more capable than JDO's. JPA turned out to be the right choice for me. I |
5 | Query results are not up to date for entities, not primitives" /> <locking version-check="true" /> <processing cache="1024mb" max-threads="80" /> <query-cache |
5 | Embedded & Activation & Scalation folder, however I've got a few questions I couldn't find answers for: How will locking take place |
5 | OutofMemory error with Object DB 2.0="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10" /> <query |
1 | Removed entities can be found by query in the same transaction optimistic lock exception) but you may want to check if it also solves this issue. support Support |
1 | ObjectDB 2.3.2) and then updated. Fixed retrieval with pessimistic lock to bypass cache and to force refresh. |
