Figure 2 shows the idea behind optimistic locking.
图2展示了乐观锁定背后的思想。
Optimistic locking restrictions and considerations.
乐观锁定特性的局限性和注意事项。
First, enable optimistic locking in the deployment descriptor.
首先，在部署描述符中启用乐观锁定。
The use of optimistic locking offers more concurrent access to the data.
乐观锁定的使用能实现更多地同时数据访问。
Read-Committed is the minimum level required for optimistic locking to work.
Read-Committed是乐观锁工作所需的最低级别。
However, the schema of the table also affects the behavior of optimistic locking.
然而，表模式也会影响乐观锁定的行为。
This represents a simplified form of what the database world calls optimistic locking.
这是数据库调用乐观（optimistic）锁的简单方式。
DB2 9.5 adds support for easier and faster optimistic locking with no false positives.
DB2 V9.5支持进行更简便和快捷的乐观锁定，而且避免了误判的发生。
While not enforced, optimistic locking is highly recommended in flow-managed persistence.
尽管不是强制实施的，但是强烈建议在流管理的持久化中使用乐观锁。
The solution for this unnecessary SQL problem is to use an "optimistic locking" technique.
解决这一不必要SQL问题的方法是，采用 “乐观锁定（optimistic locking）”技术。
Optimistic locking, where a record is locked only when changes are committed to the database.
乐观的锁定，只当数据库发生更改时锁定记录。
Applications using this programming model will benefit from the enhanced optimistic locking feature.
使用这种编程模型的应用程序将从增强的乐观锁定特性中获益。
Such a column is need for optimistic locking to implement long conversion (application transaction).
乐观锁需要这个字段来实现长对话（应用程序事务）[译注：session译为会话，conversion译为对话，以示区别]。
Due to the obvious concurrency requirement, you would first enable optimistic locking on entity classes.
由于明显的并发性需求，您应该首先在实体类上启用乐观锁。
These are a basic steps to be performed in order to enable optimistic locking support in your applications
要在应用程序中启用乐观锁定支持，需要执行以下基本步骤
If the workload is a read mostly workload, then solutions like caching with optimistic locking work well.
如果工作负荷主要是读取，那么诸如使用最优锁定进行缓存的解决方案可以很有效。
Note that without DDL changes, optimistic locking applications may get more false negatives than with DDL changes.
注意，在不进行DDL修改的情况下，乐观锁定应用程序可能会产生更多的漏判(falsenegative)。
We add an extra integer column to the table for which optimistic locking is required; this holds a revision counter.
向要使用乐观锁定的表中添加一个额外的整数列；该列保存修订计数器。
However, you can iterate through a set of rows and update each row individually while using optimistic locking techniques.
不过，您可以使用乐观锁定技术循环访问一组行并单独更新每个数据行。
Optimistic locking is still highly recommended for non-atomic Web flows to protect the data integrity of each user action.
对于非原子we b流还是强烈推荐使用乐观锁来保护每个用户操作的数据完整性。
Applications using this programming model benefit from the enhanced optimistic locking feature and gain improved concurrency.
使用这种编程模型的应用程序可以从增强的乐观锁定特性受益，并且能够进一步增强并发性。
There are other possible optimistic locking strategies and detailed design work is needed to devise suitable concurrency schemes.
另外，还需要一些其他可能的乐观锁定策略和详细设计，以制定合适的并发方案。
It has much better integrity than optimistic locking but requires you to be careful with your application design to avoid Deadlocks.
它拥有比乐观锁更好的完整性，但是需要你小心设计应用程序以避免死锁。
The other approach used by SCM vendors is optimistic locking, which allows concurrent changes to an artifact by multiple developers.
SCM提供商所使用的其他方法是optimistic locking，这将使得多个开发人员能够对同一个构件进行并发的改动。
Optimistic locking instead USES a counter to communicate when an object has been updated, or to verify whether an update has happened.
乐观锁而不是使用一个计数器进行沟通时，已更新某个对象，或是否更新了。
The next statement tells Grails that the table does not have a version column. (GORM normally creates one to help facilitate optimistic locking.)
下一条语句通知Grails表没有version列（GORM通常会创建一个 version列来优化乐观锁定）。
Optimistic locking in DB2 9.5 improves scalability by minimizing the time for which a given resource is unavailable for use by other transactions.
DB2 V9.5 的乐观锁定特性最小化了给定资源对于其他事务的不可用时间，进一步改善了可伸缩性。
A collection of SDOs that has been altered also maintains a record of its original values, enabling certain sorts of optimistic locking algorithms.
一组经过变更的SDO还会维护一条其原始值的记录，从而支持某种类型的乐观性锁定算法。
Instead, we recommend the use of an optimistic locking strategy, delegating responsibility for concurrency control to appropriate application logic.
我们建议采用乐观锁定策略，将并发控制的责任委派给相应的应用程序逻辑。
Instead, we recommend the use of an optimistic locking strategy, delegating responsibility for concurrency control to appropriate application logic.
我们建议采用乐观锁定策略，将并发控制的责任委派给相应的应用程序逻辑。
应用推荐