Row locking with escalation to table locks.
行锁定，具有到表锁的升级。
The LOCK TABLE command can be used to lock a table instead of using the default row locking.
可使用LOCKTABLE命令来锁定一个表，而不是使用缺省的行锁定。
If many transactions will be updating individual rows, change to row locking mode for a particular table using the following SQL statement.
如果许多事务将更新一些单独的行，则使用下列sql语句将特定表更改为row locking模式。
Transactional database systems in general are not very good at generating summary tables from log tables, because in this case row locking is almost useless.
传统的数据库一般地在从日志表中生成摘要表这方面的表现不怎么好，因为在这种情况下，行记录锁几乎没用。
The pattern in this case is that when the first transaction reads a row it will "stamp" it with the identity of the user, similarly to how pessimistic session locking is handled (covered next).
本例中的模式是当第一个事务读取某个数据行时，它将加上时间戳和用户标识，这类似于悲观会话锁定的处理方式（稍后讨论）。
However, you can iterate through a set of rows and update each row individually while using optimistic locking techniques.
不过，您可以使用乐观锁定技术循环访问一组行并单独更新每个数据行。
Another special case of locking is the need to lock something where currently no database row exists.
锁定的另一个特例是需要锁定当前数据库行中不存在的项目。
Our first major problem is that we are scanning the full bills table every time we want a row out of it and locking every row we read.
我们的第一个主要问题是，当我们想要一行的内容时，我们会扫描整个账单表，并锁定我们读取的每一行。
In other words, we have sequentially scanned this table, locking every row, a lot of times.
换句话说，我们顺序地扫描了此表，锁定了每个行，操作进行了很多次。
Concurrency control Supports table and row level locking.
并发控制支持表级和行级锁。
Supports table and row level locking.
支持表级和行级锁。
For MDC tables, the selection of BLOCKINSERT may improve the performance of INSERT operations by locking at the block level and avoiding row locks for INSERT operations.
对于mdc表，选择BLOCKINSERT可以提高INSERT操作的性能，因为使用的是块级的锁，避免了为INSERT操作使用行锁。
A pessimistic locking strategy assumes that the probability is high that another user will try to modify the same row in a table that you are changing.
悲观锁定策略的前提是，另一个用户很可能试图修改您正在修改的某个表行。
Supports table and row level locking and 4 isolation levels, RR (repeatable read), rs (read stability), CS (default - cursor stability) and ur (uncommitted read).
支持表级和行级锁以及4个隔离级别：RR(可重复读)、RS(读可靠)、CS(默认——游标可靠)和UR(未提交读)。
Similar to Figure 1, Transaction 1 (Tx1) reads the balance value as 1000 without locking the row in the database.
与图1类似，事务 1（TX1）在读balance值 1000 时并没有锁定数据库的行。
To determine which tables in a database have page-level locking and need to be modified to row-level locking, I use a helpful SQL script: genlockmod.sql (see Listing 1).
为了确定数据库中的哪些表具有页面级锁定以及需要修改为行级别锁定，我使用了一段sql脚本：genlockmod . sql(参见清单1)。
Since we are not manipulating locks ourselves, the engine is locking each row (or page) as it needs it.
由于我们没有操控锁，因此引擎在需要一行(或者页)时会对其进行锁定。
The first thing every contestant needed to do was change every table to row-level locking.
每位参赛者需要做的第一件事是将每个表更改为行级别锁定。
A way to avoid this is to follow an optimistic locking strategy and assume that it is very unlikely that another user will try to change the same row that you are changing.
避免发生这种情况的方法就是使用乐观锁定策略，即假设在修改某行时，另一个用户试图对这一行进行修改的可能性极低。
This locking was done for both index scans and table access whether or not the row of data was committed or whether it would have been excluded based on the statement's predicates.
不管数据行是否被提交，以及根据语句的谓词它是否被排除，对于索引扫描和表访问都执行这样的锁定操作。
Tables created by Informix default to page-level locking, so when two or more users attempt to update a row on the same page, at least one will get a lock error.
Informix创建的表默认执行了页面级锁定，所以当两个或更多用户尝试更新同一页面中的一行时，至少一个用户将获得锁定错误。
WebSphere Process Server accesses its databases in multiple concurrent threads and USES row-level locking to ensure data consistency during its transactions.
WebSphereProcessServer通过多个并发线程访问其数据库，并使用行级锁定来确保其事务期间的数据一致性。
In fact, the only row-level locking that remains during INSERT is the next-key locks that are required to protect an INSERT from adding keys to repeatable read scanners.
实际上，在INSERT期间惟一保持的行级锁是next - key锁，这个锁用于使INSERT不会添加键到可重复的读扫描器。
This script will read the Informix system tables, find out which tables have page-level locking, and then generate another SQL script to change those tables to row-level locking.
此脚本将读取Informix系统表，找出哪些表具有页面级锁定，然后生成另一段sql脚本来将这些表更改为行级别锁定。
During an export operation, row-level locking is applied to the exporting table, which means that only one lock is held at a time.
在导出操作期间，行级别锁定应用于导出表(exportingtable)，这意味着一次只持有一个锁。
Some databases (such as SQL Server) allow you to disable the page-level locking in hopes that it won't escalate from a row-level lock to a table-level lock.
一些数据库(比如sqlServer)允许您禁用页面级锁，以期它不会从行级锁切换到表级锁。
If table locking is not used, the default USES row - level locks, unless the.
如果未使用表锁定，默认使用行级锁定，除非。
The header is used to link together consecutive records, and also in row-level locking.
这个头是用来连接连续的记录，也用于行级锁。
ROW SHARE permits concurrent access to the locked table but prohibits users from locking the entire table for exclusive access.
ROWSHARE允许并发访问被锁定的表，但是禁止用户以排他访问的方式锁定整张表 。
ROW SHARE permits concurrent access to the locked table but prohibits users from locking the entire table for exclusive access.
ROWSHARE允许并发访问被锁定的表，但是禁止用户以排他访问的方式锁定整张表 。
应用推荐