Author: paul
Date: 2008-11-07 20:17:08 +0100 (Fri, 07 Nov 2008)
New Revision: 12339
Log:
r35425@frost: paul | 2008-11-07 13:15:52 -0500
General transaction-related revisions
Modified:
trunk/refman-4.1/se-innodb-core.xml
trunk/refman-4.1/sql-syntax-transactions.xml
trunk/refman-5.0/se-innodb-core.xml
trunk/refman-5.0/sql-syntax-transactions.xml
trunk/refman-5.1/se-innodb-core.xml
trunk/refman-5.1/sql-syntax-transactions.xml
trunk/refman-6.0/se-innodb-core.xml
trunk/refman-6.0/sql-syntax-transactions.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:39854
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:35422
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:34100
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:39854
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:35425
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:34100
Modified: trunk/refman-4.1/se-innodb-core.xml
===================================================================
--- trunk/refman-4.1/se-innodb-core.xml 2008-11-07 19:15:11 UTC (rev 12338)
+++ trunk/refman-4.1/se-innodb-core.xml 2008-11-07 19:17:08 UTC (rev 12339)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 7; 1427 bytes
@@ -4238,14 +4238,14 @@
<para>
The default behavior (without any <literal>SESSION</literal> or
<literal>GLOBAL</literal> keyword) is to set the isolation level
- for the next (not started) transaction. If you use the
+ for the next (not started) transaction. With the
<literal>GLOBAL</literal> keyword, the statement sets the
- default transaction level globally for all connections created
- from that point on (but not for existing connections). You need
- the <literal>SUPER</literal> privilege to do this. Using the
- <literal>SESSION</literal> keyword sets the default transaction
- level for all future transactions performed within the current
- session.
+ default transaction level globally for all subsequent sessions
+ created from that point on (but not for existing connections).
+ You need the <literal>SUPER</literal> privilege to do this. With
+ the <literal>SESSION</literal> keyword, the statement sets the
+ default transaction level for all subsequent transactions
+ performed within the current session.
</para>
<para>
Modified: trunk/refman-4.1/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-transactions.xml 2008-11-07 19:15:11 UTC (rev 12338)
+++ trunk/refman-4.1/sql-syntax-transactions.xml 2008-11-07 19:17:08 UTC (rev 12339)
Changed blocks: 5, Lines Added: 45, Lines Deleted: 27; 4800 bytes
@@ -463,11 +463,11 @@
that the current transaction made to rows after the savepoint was
set are undone in the rollback, but <literal>InnoDB</literal> does
<emphasis>not</emphasis> release the row locks that were stored in
- memory after the savepoint. (Note that for a new inserted row, the
- lock information is carried by the transaction ID stored in the
- row; the lock is not separately stored in memory. In this case,
- the row lock is released in the undo.) Savepoints that were set at
- a later time than the named savepoint are deleted.
+ memory after the savepoint. (For a new inserted row, the lock
+ information is carried by the transaction ID stored in the row;
+ the lock is not separately stored in memory. In this case, the row
+ lock is released in the undo.) Savepoints that were set at a later
+ time than the named savepoint are deleted.
</para>
<para>
@@ -1070,20 +1070,44 @@
<para>
This statement sets the transaction isolation level for the next
- transaction, globally, or for the current session.
+ transaction, globally, or for the current session:
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The default behavior (without any <literal>SESSION</literal>
+ or <literal>GLOBAL</literal> keyword) is to set the isolation
+ level for the next (not started) transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With the <literal>GLOBAL</literal> keyword, the statement sets
+ the default transaction level globally for all subsequent
+ sessions created from that point on (but not for existing
+ connections). You need the <literal>SUPER</literal> privilege
+ to do this.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With the <literal>SESSION</literal> keyword, the statement
+ sets the default transaction level for all subsequent
+ transactions performed within the current session.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<para>
- The default behavior of <literal role="stmt">SET
- TRANSACTION</literal> is to set the isolation level for the next
- (not yet started) transaction. If you use the
- <literal>GLOBAL</literal> keyword, the statement sets the default
- transaction level globally for all new connections created from
- that point on. Existing connections are unaffected. You need the
- <literal>SUPER</literal> privilege to do this. Using the
- <literal>SESSION</literal> keyword sets the default transaction
- level for all future transactions performed on the current
- connection.
+ To set the initial default global isolation level for
+ <command>mysqld</command>, use the
+ <option>--transaction-isolation</option> option. See
+ <xref linkend="server-options"/>.
</para>
<para>
@@ -1098,13 +1122,6 @@
</para>
<para>
- To set the initial default global isolation level for
- <command>mysqld</command>, use the
- <option>--transaction-isolation</option> option. See
- <xref linkend="server-options"/>.
- </para>
-
- <para>
A detailed description of each isolation level in
<literal>InnoDB</literal> follows:
</para>
@@ -1119,7 +1136,7 @@
<para>
<literal role="stmt">SELECT</literal> statements are performed
in a non-locking fashion, but a possible earlier version of a
- record might be used. Thus, using this isolation level, such
+ row might be used. Thus, using this isolation level, such
reads are not consistent. This is also called a <quote>dirty
read.</quote> Otherwise, this isolation level works like
<literal>READ COMMITTED</literal>.
@@ -1169,9 +1186,10 @@
<literal role="stmt">DELETE</literal> statements that use a
unique index with a unique search condition lock only the
index record found, not the gap before it. With other search
- conditions, these operations employ next-key locking, locking
- the index range scanned with next-key or gap locks, and block
- new insertions by other users.
+ conditions, these operations employ next-key locking, so they
+ lock the index range scanned with next-key or gap locks, and
+ block insertions by other users to the gaps covered by the
+ range.
</para>
<para>
Modified: trunk/refman-5.0/se-innodb-core.xml
===================================================================
--- trunk/refman-5.0/se-innodb-core.xml 2008-11-07 19:15:11 UTC (rev 12338)
+++ trunk/refman-5.0/se-innodb-core.xml 2008-11-07 19:17:08 UTC (rev 12339)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 7; 1427 bytes
@@ -4296,14 +4296,14 @@
<para>
The default behavior (without any <literal>SESSION</literal> or
<literal>GLOBAL</literal> keyword) is to set the isolation level
- for the next (not started) transaction. If you use the
+ for the next (not started) transaction. With the
<literal>GLOBAL</literal> keyword, the statement sets the
- default transaction level globally for all connections created
- from that point on (but not for existing connections). You need
- the <literal>SUPER</literal> privilege to do this. Using the
- <literal>SESSION</literal> keyword sets the default transaction
- level for all future transactions performed within the current
- session.
+ default transaction level globally for all subsequent sessions
+ created from that point on (but not for existing connections).
+ You need the <literal>SUPER</literal> privilege to do this. With
+ the <literal>SESSION</literal> keyword, the statement sets the
+ default transaction level for all subsequent transactions
+ performed within the current session.
</para>
<para>
Modified: trunk/refman-5.0/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-transactions.xml 2008-11-07 19:15:11 UTC (rev 12338)
+++ trunk/refman-5.0/sql-syntax-transactions.xml 2008-11-07 19:17:08 UTC (rev 12339)
Changed blocks: 5, Lines Added: 50, Lines Deleted: 33; 5567 bytes
@@ -542,12 +542,12 @@
MySQL 5.0.3.) Modifications that the current transaction made to
rows after the savepoint was set are undone in the rollback, but
<literal>InnoDB</literal> does <emphasis>not</emphasis> release
- the row locks that were stored in memory after the savepoint.
- (Note that for a new inserted row, the lock information is carried
- by the transaction ID stored in the row; the lock is not
- separately stored in memory. In this case, the row lock is
- released in the undo.) Savepoints that were set at a later time
- than the named savepoint are deleted.
+ the row locks that were stored in memory after the savepoint. (For
+ a new inserted row, the lock information is carried by the
+ transaction ID stored in the row; the lock is not separately
+ stored in memory. In this case, the row lock is released in the
+ undo.) Savepoints that were set at a later time than the named
+ savepoint are deleted.
</para>
<para>
@@ -1165,20 +1165,44 @@
<para>
This statement sets the transaction isolation level for the next
- transaction, globally, or for the current session.
+ transaction, globally, or for the current session:
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The default behavior (without any <literal>SESSION</literal>
+ or <literal>GLOBAL</literal> keyword) is to set the isolation
+ level for the next (not started) transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With the <literal>GLOBAL</literal> keyword, the statement sets
+ the default transaction level globally for all subsequent
+ sessions created from that point on (but not for existing
+ connections). You need the <literal>SUPER</literal> privilege
+ to do this.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With the <literal>SESSION</literal> keyword, the statement
+ sets the default transaction level for all subsequent
+ transactions performed within the current session.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<para>
- The default behavior of <literal role="stmt">SET
- TRANSACTION</literal> is to set the isolation level for the next
- (not yet started) transaction. If you use the
- <literal>GLOBAL</literal> keyword, the statement sets the default
- transaction level globally for all new connections created from
- that point on. Existing connections are unaffected. You need the
- <literal>SUPER</literal> privilege to do this. Using the
- <literal>SESSION</literal> keyword sets the default transaction
- level for all future transactions performed on the current
- connection.
+ To set the initial default global isolation level for
+ <command>mysqld</command>, use the
+ <option>--transaction-isolation</option> option. See
+ <xref linkend="server-options"/>.
</para>
<para>
@@ -1186,21 +1210,13 @@
isolation level, see
<xref linkend="innodb-transaction-isolation"/>.
<literal>InnoDB</literal> supports each of the levels described
- here in MySQL ¤t-series;. The default level is
- <literal>REPEATABLE READ</literal>. See also
- <xref linkend="innodb-locks-set"/>, for additional information
- about how <literal>InnoDB</literal> uses locks to execute various
- types of statements.
+ here. The default level is <literal>REPEATABLE READ</literal>. See
+ also <xref linkend="innodb-locks-set"/>, for additional
+ information about how <literal>InnoDB</literal> uses locks to
+ execute various types of statements.
</para>
<para>
- To set the initial default global isolation level for
- <command>mysqld</command>, use the
- <option>--transaction-isolation</option> option. See
- <xref linkend="server-options"/>.
- </para>
-
- <para>
A detailed list of the transaction levels supported by MySQL and
the various storage engines follows:
</para>
@@ -1215,7 +1231,7 @@
<para>
<literal role="stmt">SELECT</literal> statements are performed
in a non-locking fashion, but a possible earlier version of a
- record might be used. Thus, using this isolation level, such
+ row might be used. Thus, using this isolation level, such
reads are not consistent. This is also called a <quote>dirty
read.</quote> Otherwise, this isolation level works like
<literal>READ COMMITTED</literal>.
@@ -1265,9 +1281,10 @@
<literal role="stmt">DELETE</literal> statements that use a
unique index with a unique search condition lock only the
index record found, not the gap before it. With other search
- conditions, these operations employ next-key locking, locking
- the index range scanned with next-key or gap locks, and block
- new insertions by other users.
+ conditions, these operations employ next-key locking, so they
+ lock the index range scanned with next-key or gap locks, and
+ block insertions by other users to the gaps covered by the
+ range.
</para>
<para>
Modified: trunk/refman-5.1/se-innodb-core.xml
===================================================================
--- trunk/refman-5.1/se-innodb-core.xml 2008-11-07 19:15:11 UTC (rev 12338)
+++ trunk/refman-5.1/se-innodb-core.xml 2008-11-07 19:17:08 UTC (rev 12339)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 7; 1427 bytes
@@ -4995,14 +4995,14 @@
<para>
The default behavior (without any <literal>SESSION</literal> or
<literal>GLOBAL</literal> keyword) is to set the isolation level
- for the next (not started) transaction. If you use the
+ for the next (not started) transaction. With the
<literal>GLOBAL</literal> keyword, the statement sets the
- default transaction level globally for all connections created
- from that point on (but not for existing connections). You need
- the <literal>SUPER</literal> privilege to do this. Using the
- <literal>SESSION</literal> keyword sets the default transaction
- level for all future transactions performed within the current
- session.
+ default transaction level globally for all subsequent sessions
+ created from that point on (but not for existing connections).
+ You need the <literal>SUPER</literal> privilege to do this. With
+ the <literal>SESSION</literal> keyword, the statement sets the
+ default transaction level for all subsequent transactions
+ performed within the current session.
</para>
<para>
Modified: trunk/refman-5.1/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-transactions.xml 2008-11-07 19:15:11 UTC (rev 12338)
+++ trunk/refman-5.1/sql-syntax-transactions.xml 2008-11-07 19:17:08 UTC (rev 12339)
Changed blocks: 7, Lines Added: 50, Lines Deleted: 33; 5928 bytes
@@ -563,11 +563,11 @@
that the current transaction made to rows after the savepoint was
set are undone in the rollback, but <literal>InnoDB</literal> does
<emphasis>not</emphasis> release the row locks that were stored in
- memory after the savepoint. (Note that for a new inserted row, the
- lock information is carried by the transaction ID stored in the
- row; the lock is not separately stored in memory. In this case,
- the row lock is released in the undo.) Savepoints that were set at
- a later time than the named savepoint are deleted.
+ memory after the savepoint. (For a new inserted row, the lock
+ information is carried by the transaction ID stored in the row;
+ the lock is not separately stored in memory. In this case, the row
+ lock is released in the undo.) Savepoints that were set at a later
+ time than the named savepoint are deleted.
</para>
<para>
@@ -1213,20 +1213,44 @@
<para>
This statement sets the transaction isolation level for the next
- transaction, globally, or for the current session.
+ transaction, globally, or for the current session:
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The default behavior (without any <literal>SESSION</literal>
+ or <literal>GLOBAL</literal> keyword) is to set the isolation
+ level for the next (not started) transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With the <literal>GLOBAL</literal> keyword, the statement sets
+ the default transaction level globally for all subsequent
+ sessions created from that point on (but not for existing
+ connections). You need the <literal>SUPER</literal> privilege
+ to do this.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With the <literal>SESSION</literal> keyword, the statement
+ sets the default transaction level for all subsequent
+ transactions performed within the current session.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<para>
- The default behavior of <literal role="stmt">SET
- TRANSACTION</literal> is to set the isolation level for the next
- (not yet started) transaction. If you use the
- <literal>GLOBAL</literal> keyword, the statement sets the default
- transaction level globally for all new connections created from
- that point on. Existing connections are unaffected. You need the
- <literal>SUPER</literal> privilege to do this. Using the
- <literal>SESSION</literal> keyword sets the default transaction
- level for all future transactions performed on the current
- connection.
+ To set the initial default global isolation level for
+ <command>mysqld</command>, use the
+ <option>--transaction-isolation</option> option. See
+ <xref linkend="server-options"/>.
</para>
<para>
@@ -1234,11 +1258,10 @@
isolation level, see
<xref linkend="innodb-transaction-isolation"/>.
<literal>InnoDB</literal> supports each of the levels described
- here in MySQL ¤t-series;. The default level is
- <literal>REPEATABLE READ</literal>. See also
- <xref linkend="innodb-locks-set"/>, for additional information
- about how <literal>InnoDB</literal> uses locks to execute various
- types of statements.
+ here. The default level is <literal>REPEATABLE READ</literal>. See
+ also <xref linkend="innodb-locks-set"/>, for additional
+ information about how <literal>InnoDB</literal> uses locks to
+ execute various types of statements.
</para>
<para>
@@ -1252,13 +1275,6 @@
</para>
<para>
- To set the initial default global isolation level for
- <command>mysqld</command>, use the
- <option>--transaction-isolation</option> option. See
- <xref linkend="server-options"/>.
- </para>
-
- <para>
A detailed list of the transaction levels supported by MySQL and
the various storage engines follows:
</para>
@@ -1273,7 +1289,7 @@
<para>
<literal role="stmt">SELECT</literal> statements are performed
in a non-locking fashion, but a possible earlier version of a
- record might be used. Thus, using this isolation level, such
+ row might be used. Thus, using this isolation level, such
reads are not consistent. This is also called a <quote>dirty
read.</quote> Otherwise, this isolation level works like
<literal>READ COMMITTED</literal>.
@@ -1312,7 +1328,7 @@
<note>
<para>
As of MySQL 5.1, if you use <literal>READ
- COMMITTED</literal> (which is equivalent to
+ COMMITTED</literal> (which is equivalent to enabling
<literal>innodb_locks_unsafe_for_binlog</literal> in 5.0),
you <emphasis>must</emphasis> use row-based binary logging.
</para>
@@ -1332,9 +1348,10 @@
<literal role="stmt">DELETE</literal> statements that use a
unique index with a unique search condition lock only the
index record found, not the gap before it. With other search
- conditions, these operations employ next-key locking, locking
- the index range scanned with next-key or gap locks, and block
- new insertions by other users.
+ conditions, these operations employ next-key locking, so they
+ lock the index range scanned with next-key or gap locks, and
+ block insertions by other users to the gaps covered by the
+ range.
</para>
<para>
Modified: trunk/refman-6.0/se-innodb-core.xml
===================================================================
--- trunk/refman-6.0/se-innodb-core.xml 2008-11-07 19:15:11 UTC (rev 12338)
+++ trunk/refman-6.0/se-innodb-core.xml 2008-11-07 19:17:08 UTC (rev 12339)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 7; 1427 bytes
@@ -4862,14 +4862,14 @@
<para>
The default behavior (without any <literal>SESSION</literal> or
<literal>GLOBAL</literal> keyword) is to set the isolation level
- for the next (not started) transaction. If you use the
+ for the next (not started) transaction. With the
<literal>GLOBAL</literal> keyword, the statement sets the
- default transaction level globally for all connections created
- from that point on (but not for existing connections). You need
- the <literal>SUPER</literal> privilege to do this. Using the
- <literal>SESSION</literal> keyword sets the default transaction
- level for all future transactions performed within the current
- session.
+ default transaction level globally for all subsequent sessions
+ created from that point on (but not for existing connections).
+ You need the <literal>SUPER</literal> privilege to do this. With
+ the <literal>SESSION</literal> keyword, the statement sets the
+ default transaction level for all subsequent transactions
+ performed within the current session.
</para>
<para>
Modified: trunk/refman-6.0/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-transactions.xml 2008-11-07 19:15:11 UTC (rev 12338)
+++ trunk/refman-6.0/sql-syntax-transactions.xml 2008-11-07 19:17:08 UTC (rev 12339)
Changed blocks: 7, Lines Added: 50, Lines Deleted: 33; 5881 bytes
@@ -628,11 +628,11 @@
that the current transaction made to rows after the savepoint was
set are undone in the rollback, but <literal>InnoDB</literal> does
<emphasis>not</emphasis> release the row locks that were stored in
- memory after the savepoint. (Note that for a new inserted row, the
- lock information is carried by the transaction ID stored in the
- row; the lock is not separately stored in memory. In this case,
- the row lock is released in the undo.) Savepoints that were set at
- a later time than the named savepoint are deleted.
+ memory after the savepoint. (For a new inserted row, the lock
+ information is carried by the transaction ID stored in the row;
+ the lock is not separately stored in memory. In this case, the row
+ lock is released in the undo.) Savepoints that were set at a later
+ time than the named savepoint are deleted.
</para>
<para>
@@ -1881,20 +1881,44 @@
<para>
This statement sets the transaction isolation level for the next
- transaction, globally, or for the current session.
+ transaction, globally, or for the current session:
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The default behavior (without any <literal>SESSION</literal>
+ or <literal>GLOBAL</literal> keyword) is to set the isolation
+ level for the next (not started) transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With the <literal>GLOBAL</literal> keyword, the statement sets
+ the default transaction level globally for all subsequent
+ sessions created from that point on (but not for existing
+ connections). You need the <literal>SUPER</literal> privilege
+ to do this.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With the <literal>SESSION</literal> keyword, the statement
+ sets the default transaction level for all subsequent
+ transactions performed within the current session.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<para>
- The default behavior of <literal role="stmt">SET
- TRANSACTION</literal> is to set the isolation level for the next
- (not yet started) transaction. If you use the
- <literal>GLOBAL</literal> keyword, the statement sets the default
- transaction level globally for all new connections created from
- that point on. Existing connections are unaffected. You need the
- <literal>SUPER</literal> privilege to do this. Using the
- <literal>SESSION</literal> keyword sets the default transaction
- level for all future transactions performed on the current
- connection.
+ To set the initial default global isolation level for
+ <command>mysqld</command>, use the
+ <option>--transaction-isolation</option> option. See
+ <xref linkend="server-options"/>.
</para>
<para>
@@ -1902,11 +1926,10 @@
isolation level, see
<xref linkend="innodb-transaction-isolation"/>.
<literal>InnoDB</literal> supports each of the levels described
- here in MySQL ¤t-series;. The default level is
- <literal>REPEATABLE READ</literal>. See also
- <xref linkend="innodb-locks-set"/>, for additional information
- about how <literal>InnoDB</literal> uses locks to execute various
- types of statements.
+ here. The default level is <literal>REPEATABLE READ</literal>. See
+ also <xref linkend="innodb-locks-set"/>, for additional
+ information about how <literal>InnoDB</literal> uses locks to
+ execute various types of statements.
</para>
<para>
@@ -1920,13 +1943,6 @@
</para>
<para>
- To set the initial default global isolation level for
- <command>mysqld</command>, use the
- <option>--transaction-isolation</option> option. See
- <xref linkend="server-options"/>.
- </para>
-
- <para>
A detailed list of the transaction levels supported by MySQL and
the various storage engines follows:
</para>
@@ -1941,7 +1957,7 @@
<para>
<literal role="stmt">SELECT</literal> statements are performed
in a non-locking fashion, but a possible earlier version of a
- record might be used. Thus, using this isolation level, such
+ row might be used. Thus, using this isolation level, such
reads are not consistent. This is also called a <quote>dirty
read.</quote> Otherwise, this isolation level works like
<literal>READ COMMITTED</literal>.
@@ -1980,7 +1996,7 @@
<note>
<para>
If you use <literal>READ COMMITTED</literal> (which is
- equivalent to
+ equivalent to enabling
<literal>innodb_locks_unsafe_for_binlog</literal> in MySQL
5.0), you <emphasis>must</emphasis> use row-based binary
logging.
@@ -2001,9 +2017,10 @@
<literal role="stmt">DELETE</literal> statements that use a
unique index with a unique search condition lock only the
index record found, not the gap before it. With other search
- conditions, these operations employ next-key locking, locking
- the index range scanned with next-key or gap locks, and block
- new insertions by other users.
+ conditions, these operations employ next-key locking, so they
+ lock the index range scanned with next-key or gap locks, and
+ block insertions by other users to the gaps covered by the
+ range.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r12339 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul.dubois | 7 Nov |
