About lock

121-130 of 174Refresh
Result
1

ObjectDB version 2.6.5

of connections specified in configuration. Fixed optimistic lock exception on removing of a flushed
Result
1

ObjectDB version 2.6.8

Version 2.6.8 Added JPA XML validation schema files to Maven/JEE objectdb.jar. Added automatic release of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a NullPointerExeption on new index
Forum
1

Activation Issue

="." mode="write" /> <locking version-check="true" />
Forum
1

Bulk Delete and Update - best practice?

databases (in server mode the database is locked so drop can't be used). The only method I've found
Forum
1

Connection is closed Caused by: java.io.EOFException

" /> <locking version-check="true
Forum
1

Database Inconsistency or corruption

all locked objects     System.out.println("Trying to merge first object " + em.getLockMode(ov
Forum
1

Drop the entire database, Change the schema

have to stop the container to be sure the DB file is not locked - I do this anyway in the tests
Forum
1

Embedded & Activation & Scalation

folder, however I've got a few questions I couldn't find answers for: How will locking take place
Issue
1

Entity Version History

ObjectDB manages automatic entity versioning (for optimistic lock purposes). Every entity object modification is reflected by a new version number. Naturally, previous values in the entity object that are overridden by new values are discarded. Some applications may benefit from the ability
Issue
1

EOFException

internal file lock protection. Modifying the database file externally not through ObjectDB (e.g. by