Home » Search

About failure

11-20 of 107Refresh
Forum
23

Merge failure with composite primary key

Merge failure with composite primary key
Manual
20

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
15

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
14

Apache License, Version 2.0, January 2004

stoppage, computer failure or malfunction, or any and all other commercial damages or losses
Manual
14

Database Connection using JPA

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

Detached Entity Objects

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

Eclipse Public License - v 1.0

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

ObjectDB Object Database Features

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

How to upgrade from ObjectDB 1.0?

is more sensitive to failure to close a PersistenceManagerFactory. The database is closed
JPA Doc
7

javax.persistence.LockModeType

and there is a high likelihood of deadlock or update failure among concurrent updating transactions. The persistence ... cannot be obtained, and the database locking failure results in transaction-level rollback, the provider must throw ... has been marked for rollback. When the lock cannot be obtained, and the database locking failure results in