Annotation Type OptimisticLocking
@Target(TYPE) @Retention(RUNTIME) public @interface OptimisticLockingSpecifies how optimistic lock checking works for the annotated entity.
Optimistic lock checking may detect that an optimistic lock has failed, and that the transaction should be aborted, by comparing either:
An optimistic lock is usually checked by including a restriction in a SQL
deletestatement. If the database reports that zero rows were updated, it is inferred that another transaction has already updated or deleted the row, and the failure of the optimistic lock is reported via an
In an inheritance hierarchy, this annotation may only be applied to the root entity, since the optimistic lock checking strategy is inherited by entity subclasses.
To exclude a particular attribute from optimistic locking, annotate the attribute
OptimisticLockType typeThe optimistic lock checking strategy.