java.lang.Object | |
↳ | org.hibernate.LockMode |
Instances represent a lock mode for a row of a relational database table. It is not intended that users spend much time worrying about locking since Hibernate usually obtains exactly the right lock level automatically. Some "advanced" users may wish to explicitly specify lock levels.
Fields | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
FORCE | This field is deprecated. instead use PESSIMISTIC_FORCE_INCREMENT | ||||||||||
NONE | No lock required. | ||||||||||
OPTIMISTIC | Optimisticly assume that transaction will not experience contention for entities. | ||||||||||
OPTIMISTIC_FORCE_INCREMENT | Optimisticly assume that transaction will not experience contention for entities. | ||||||||||
PESSIMISTIC_FORCE_INCREMENT | Transaction will immediately increment the entity version. | ||||||||||
PESSIMISTIC_READ | Implemented as PESSIMISTIC_WRITE. | ||||||||||
PESSIMISTIC_WRITE | Transaction will obtain a database lock immediately. | ||||||||||
READ | A shared lock. | ||||||||||
UPGRADE | This field is deprecated. instead use PESSIMISTIC_WRITE | ||||||||||
UPGRADE_NOWAIT | Attempt to obtain an upgrade lock, using an Oracle-style select for update nowait. | ||||||||||
WRITE | A WRITE lock is obtained when an object is updated or inserted. |
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Check if this lock mode is more restrictive than the given lock mode.
| |||||||||||
Check if this lock mode is less restrictive than the given lock mode.
| |||||||||||
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
![]() |
This field is deprecated.
instead use PESSIMISTIC_FORCE_INCREMENT
Similiar to UPGRADE
except that, for versioned entities,
it results in a forced version increment.
No lock required. If an object is requested with this lock
mode, a READ lock will be obtained if it is
necessary to actually read the state from the database,
rather than pull it from a cache.
This is the "default" lock mode.
Optimisticly assume that transaction will not experience contention for entities. The entity version will be verified near the transaction end.
Optimisticly assume that transaction will not experience contention for entities. The entity version will be verified and incremented near the transaction end.
Transaction will immediately increment the entity version.
Implemented as PESSIMISTIC_WRITE. TODO: introduce separate support for PESSIMISTIC_READ
Transaction will obtain a database lock immediately. TODO: add PESSIMISTIC_WRITE_NOWAIT
A shared lock. Objects in this lock mode were read from the database in the current transaction, rather than being pulled from a cache.
This field is deprecated.
instead use PESSIMISTIC_WRITE
An upgrade lock. Objects loaded in this lock mode are materialized using an SQL select ... for update.
Attempt to obtain an upgrade lock, using an Oracle-style select for update nowait. The semantics of this lock mode, once obtained, are the same as UPGRADE.
A WRITE lock is obtained when an object is updated or inserted. This lock mode is for internal use only and is not a valid mode for load() or lock() (both of which throw exceptions if WRITE is specified).
Check if this lock mode is more restrictive than the given lock mode.
mode | LockMode to check |
---|
Check if this lock mode is less restrictive than the given lock mode.
mode | LockMode to check |
---|