Optimistic Locking

Due to the obvious concurrency requirement, you would first enable optimistic locking on entity classes.

由于明显的并发性需求，您应该首先在实体类上启用乐观锁。

Such a column is need for optimistic locking to implement long conversion ( application transaction).

乐观锁需要这个字段来实现长对话（应用程序事务）[译注：session译为会话，conversion译为对话，以示区别]。

While not enforced, optimistic locking is highly recommended in flow-managed persistence.

尽管不是强制实施的，但是强烈建议在流管理的持久化中使用乐观锁。

In this case, there may need to be some application restructuring, or optimistic locking may need to be used instead.

这时，可能需要修改应用程序，或使用乐观锁定方式。

Speaking of Locking, Pratik said that JPA specification defaults to optimistic locking.

谈到锁（locking），Pratik说到JPA规范默认使用乐观锁（optimistic locking）。

There are other possible optimistic locking strategies and detailed design work is needed to devise suitable concurrency schemes.

另外，还需要一些其他可能的乐观锁定策略和详细设计，以制定合适的并发方案。

This represents a simplified form of what the database world calls optimistic locking.

这是数据库调用乐观（optimistic）锁的简单方式。

For instance, if the application uses pessimistic locking, don't change the application during the migration to use optimistic locking.

例如，如果应用程序使用悲观锁定，则在迁移过程中不要将应用程序更改为使用乐观锁定。

Note that applications that do not use this programming model are not considered optimistic locking applications, and they will continue to work as before.

注意，未使用这种编程模型的应用程序被认为是非乐观锁定应用程序，它们将按照以前的方式工作。

In a multi-tiered system, you often use optimistic locking with detached objects to increase system concurrency and achieve high performance.

在多层系统中，经常可以在分离对象上使用乐观锁来提升系统并发性，达到更高的性能。

The Optimistic Locking Algorithm Based on Relative Position and Its Application in Collaborative Editing Systems

相对位置乐观锁机制及在协同编辑中的应用

Applications using this programming model will benefit from the enhanced optimistic locking feature.

使用这种编程模型的应用程序将从增强的乐观锁定特性中获益。

Read-Committed is the minimum level required for optimistic locking to work.

Read-Committed是乐观锁工作所需的最低级别。

Optimistic locking is still highly recommended for non-atomic Web flows to protect the data integrity of each user action.

对于非原子Web流还是强烈推荐使用乐观锁来保护每个用户操作的数据完整性。

Optimistic locking is an extremely efficient concurrency control method that guarantees data integrity without placing any physical lock in the database.

乐观锁是一个极其有效的并发性控制方法，它可以确保数据完整性而又无需在数据库中放置任何物理锁。

Instead, we recommend the use of an optimistic locking strategy, delegating responsibility for concurrency control to appropriate application logic.

我们建议采用乐观锁定策略，将并发控制的责任委派给相应的应用程序逻辑。

Optimistic locking will not work if Hibernate is not the sole database user, unless you create database triggers to increment the version column for the same data change by other applications.

如果Hibernate不是独占数据库用户，乐观锁会失效，除非创建数据库触发器为其他应用程序对相同数据的变更增加版本字段值。

If the workload is a read mostly workload, then solutions like caching with optimistic locking work well.

如果工作负荷主要是读取，那么诸如使用最优锁定进行缓存的解决方案可以很有效。

On the other hand, described the optimistic locking solve concurrency issues, the use of optimistic locking improves the speed of the transaction.

另一方面，叙述了乐观锁在解决并发问题中的应用，乐观锁的使用提高系统处理事务的速度。

Note that without DDL changes, optimistic locking applications may get more false negatives than with DDL changes.

注意，在不进行DDL修改的情况下，乐观锁定应用程序可能会产生更多的漏判（false negative）。

The Concurrency Controlling Algorithm of Optimistic Locking Based on Relative Position in Real-Time Distributed Cooperative Editing System

基于相对位置的分布式实时协同编辑乐观锁并发控制算法

Optimistic locking, where a record is locked only when changes are committed to the database.

乐观的锁定，只当数据库发生更改时锁定记录。