About failure

11-20 of 114Refresh
Manual
18

Database Management Settings

, the recovery file can be used to fix the database. Recovery from failure is automatically applied by ... " operations (which modify the database) have to be recorded. For debugging of query failure
Manual
18

Database Transaction Replayer

is useful for two different purposes: It enables recovery from a database failure by replaying the recorded operations. It enables reproducing problems during debugging by repeating a failure. Backup
JPA Doc
13

javax.persistence.EntityManager

: the PessimisticLockException will be thrown if the database locking failure causes transaction-level rollback the LockTimeoutException will be thrown if the database locking failure causes only statement-level rollback ... will be thrown if the database locking failure causes transaction-level rollback
Result
13

Apache License, Version 2.0, January 2004

stoppage, computer failure or malfunction, or any and all other commercial damages or losses
Result
13

Eclipse Public License - v 1.0

such failure in a reasonable period of time after becoming aware of such noncompliance
Result
13

How to upgrade from ObjectDB 1.0?

is more sensitive to failure to close a PersistenceManagerFactory. The database is closed
Manual
13

Database Connection using JPA

that have already been propagated to the database prior to the failure) and a RollbackException is thrown.
Manual
13

Detached Entity Objects

invocation of rollback or by a commit failure. Explicit Merge Detached objects can be attached
Result
13

ObjectDB Object Database Features [2018-01-27]

operating system resources). Unlimited CPUs and cores. Reliability and Stability Recovery from failure by
Result
13

ObjectDB Object Database Features [2018-10-27]

operating system resources). Unlimited CPUs and cores. Reliability and Stability Recovery from failure by