Internal Website Search

message: "Attempt to lock a non entity object". The change stays on the screen, but is not persisted

;recording enabled="false" sync="false" path="." mode="write" /> <locking version-check="true

> You can keep the refresh and also use locking. This is not related to moving

="false" path="." mode="write" /> <locking version-check="true" /> <processing cache

, and the temporary file is essential to minimize the time that the database is locked for backup (e.g

Is there a way to setup a database file that will be accessed in embedded mode, such that it is locked with a password.  Thereby making it impossible to use ObjectDB to access the contents of the file without providing the correct password when obtaining a connection.  In

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

Hello, I'm using the Java Persistence API (JPA) in a library to not lock myself in to using a specific database. In a project that uses said library, I'm using ObjectDB because it is fast and eliminates the need for another dependency to an ORM, such as Hibernate

; <locking version-check="true" />           

Attempt to solve temporary files locking issues on Linux.