Author: paul
Date: 2008-10-28 15:59:42 +0100 (Tue, 28 Oct 2008)
New Revision: 12175
Log:
r35034@frost: paul | 2008-10-28 10:00:58 -0500
Implicit commit:
- As of 6.0.8, most statements that caused IC before executing now do so after
as well
- Other minor revisions
Modified:
trunk/refman-4.1/sql-syntax-transactions.xml
trunk/refman-5.0/sql-syntax-transactions.xml
trunk/refman-5.1/sql-syntax-transactions.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:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:35030
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33695
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:35034
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33695
Modified: trunk/refman-4.1/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-transactions.xml 2008-10-28 14:26:39 UTC (rev 12174)
+++ trunk/refman-4.1/sql-syntax-transactions.xml 2008-10-28 14:59:42 UTC (rev 12175)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 3; 1056 bytes
@@ -267,8 +267,7 @@
<para>
The statements listed in this section (and any synonyms for them)
implicitly end a transaction, as if you had done a
- <literal>COMMIT</literal> before executing the statement. Affected
- statements fall into several categories.
+ <literal>COMMIT</literal> before executing the statement.
</para>
<itemizedlist>
@@ -316,7 +315,7 @@
<listitem>
<para>
- <emphasis role="bold">Transactional and locking
+ <emphasis role="bold">Transaction-control and locking
statements.</emphasis> <literal>BEGIN</literal>, <literal>LOCK
TABLES</literal>, <literal>SET AUTOCOMMIT=1</literal> (if the
value is not already 1), <literal>START TRANSACTION</literal>,
Modified: trunk/refman-5.0/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-transactions.xml 2008-10-28 14:26:39 UTC (rev 12174)
+++ trunk/refman-5.0/sql-syntax-transactions.xml 2008-10-28 14:59:42 UTC (rev 12175)
Changed blocks: 3, Lines Added: 7, Lines Deleted: 9; 1943 bytes
@@ -304,8 +304,7 @@
<para>
The statements listed in this section (and any synonyms for them)
implicitly end a transaction, as if you had done a
- <literal>COMMIT</literal> before executing the statement. Affected
- statements fall into several categories.
+ <literal>COMMIT</literal> before executing the statement.
</para>
<itemizedlist>
@@ -377,7 +376,7 @@
<listitem>
<para>
- <emphasis role="bold">Transactional and locking
+ <emphasis role="bold">Transaction-control and locking
statements.</emphasis> <literal>BEGIN</literal>, <literal>LOCK
TABLES</literal>, <literal>SET AUTOCOMMIT=1</literal> (if the
value is not already 1), <literal>START TRANSACTION</literal>,
@@ -419,12 +418,11 @@
<para>
<emphasis role="bold">Data loading statements.</emphasis>
<literal>LOAD MASTER DATA</literal>, <literal>LOAD DATA
- INFILE</literal>. In MySQL 5.0.25 and earlier, <literal>LOAD
- DATA INFILE</literal> caused an implicit commit for all
- storage engines. Beginning with MySQL 5.0.26, it causes an
- implicit commit only for tables using the
- <literal>NDB</literal> storage engine. For more information,
- see Bug #11151.
+ INFILE</literal>. Before MySQL 5.0.26, <literal>LOAD DATA
+ INFILE</literal> caused an implicit commit for all storage
+ engines. As of MySQL 5.0.26, it causes an implicit commit only
+ for tables using the <literal>NDB</literal> storage engine.
+ For more information, see Bug#11151.
</para>
</listitem>
Modified: trunk/refman-5.1/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-transactions.xml 2008-10-28 14:26:39 UTC (rev 12174)
+++ trunk/refman-5.1/sql-syntax-transactions.xml 2008-10-28 14:59:42 UTC (rev 12175)
Changed blocks: 5, Lines Added: 22, Lines Deleted: 23; 4191 bytes
@@ -302,8 +302,7 @@
<para>
The statements listed in this section (and any synonyms for them)
implicitly end a transaction, as if you had done a
- <literal>COMMIT</literal> before executing the statement. Affected
- statements fall into several categories.
+ <literal>COMMIT</literal> before executing the statement.
</para>
<itemizedlist>
@@ -315,18 +314,17 @@
<literal>ALTER DATABASE ... UPGRADE DATA DIRECTORY
NAME</literal>, <literal>ALTER EVENT</literal>, <literal>ALTER
FUNCTION</literal>, <literal>ALTER PROCEDURE</literal>,
- <literal>ALTER TABLE</literal>, <literal>CACHE
- INDEX</literal>, <literal>CREATE DATABASE</literal>,
- <literal>CREATE EVENT</literal>, <literal>CREATE
- FUNCTION</literal>, <literal>CREATE INDEX</literal>,
- <literal>CREATE PROCEDURE</literal>, <literal>CREATE
- TABLE</literal>, <literal>DROP DATABASE</literal>,
- <literal>DROP EVENT</literal>, <literal>DROP
- FUNCTION</literal> (for stored functions, not UDFs),
- <literal>DROP INDEX</literal>, <literal>DROP
+ <literal>ALTER TABLE</literal>, <literal>CREATE
+ DATABASE</literal>, <literal>CREATE EVENT</literal>,
+ <literal>CREATE FUNCTION</literal>, <literal>CREATE
+ INDEX</literal>, <literal>CREATE PROCEDURE</literal>,
+ <literal>CREATE TABLE</literal>, <literal>DROP
+ DATABASE</literal>, <literal>DROP EVENT</literal>,
+ <literal>DROP FUNCTION</literal> (for stored functions, not
+ UDFs), <literal>DROP INDEX</literal>, <literal>DROP
PROCEDURE</literal>, <literal>DROP TABLE</literal>,
- <literal>LOAD INDEX INTO CACHE</literal>, <literal>RENAME
- TABLE</literal>, <literal>TRUNCATE TABLE</literal>.
+ <literal>RENAME TABLE</literal>, <literal>TRUNCATE
+ TABLE</literal>.
</para>
<para>
@@ -386,7 +384,7 @@
<listitem>
<para>
- <emphasis role="bold">Transactional and locking
+ <emphasis role="bold">Transaction-control and locking
statements.</emphasis> <literal>BEGIN</literal>, <literal>LOCK
TABLES</literal>, <literal>SET AUTOCOMMIT=1</literal> (if the
value is not already 1), <literal>START TRANSACTION</literal>,
@@ -427,10 +425,10 @@
<listitem>
<para>
<emphasis role="bold">Data loading statements.</emphasis>
- <literal>LOAD DATA INFILE</literal>, In MySQL 5.1.11 and
- earlier, <literal>LOAD DATA INFILE</literal> caused an
- implicit commit for all storage engines. Beginning with MySQL
- 5.1.12, it causes an implicit commit only for tables using the
+ <literal>LOAD DATA INFILE</literal>. Before MySQL 5.1.12,
+ <literal>LOAD DATA INFILE</literal> caused an implicit commit
+ for all storage engines. As of MySQL 5.1.12, it causes an
+ implicit commit only for tables using the
<literal>NDB</literal> storage engine. For more information,
see Bug#11151.
</para>
@@ -438,11 +436,12 @@
<listitem>
<para>
- <emphasis role="bold">Database and table administrative
- statements.</emphasis> Beginning with MySQL 5.1.10,
- <literal>ANALYZE TABLE</literal>, <literal>CHECK
- TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and
- <literal>REPAIR TABLE</literal> cause an implicit commit.
+ <emphasis role="bold">Administrative statements.</emphasis>
+ <literal>CACHE INDEX</literal>, <literal>LOAD INDEX INTO
+ CACHE</literal>. Beginning with MySQL 5.1.10, <literal>ANALYZE
+ TABLE</literal>, <literal>CHECK TABLE</literal>,
+ <literal>OPTIMIZE TABLE</literal>, and <literal>REPAIR
+ TABLE</literal> cause an implicit commit.
</para>
</listitem>
Modified: trunk/refman-6.0/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-transactions.xml 2008-10-28 14:26:39 UTC (rev 12174)
+++ trunk/refman-6.0/sql-syntax-transactions.xml 2008-10-28 14:59:42 UTC (rev 12175)
Changed blocks: 4, Lines Added: 60, Lines Deleted: 22; 5113 bytes
@@ -332,8 +332,10 @@
<para>
The statements listed in this section (and any synonyms for them)
implicitly end a transaction, as if you had done a
- <literal>COMMIT</literal> before executing the statement. Affected
- statements fall into several categories.
+ <literal>COMMIT</literal> before executing the statement. As of
+ MySQL 6.0.8, most of these statements also cause an implicit
+ commit after executing; for additional details, see the end of
+ this section.
</para>
<itemizedlist>
@@ -346,20 +348,19 @@
NAME</literal>, <literal>ALTER EVENT</literal>, <literal>ALTER
FUNCTION</literal>, <literal>ALTER PROCEDURE</literal>,
<literal>ALTER TABLE</literal>, <literal>ALTER VIEW</literal>,
- <literal>CACHE INDEX</literal>, <literal>CREATE
- DATABASE</literal>, <literal>CREATE EVENT</literal>,
- <literal>CREATE FUNCTION</literal>, <literal>CREATE
- INDEX</literal>, <literal>CREATE PROCEDURE</literal>,
- <literal>CREATE TABLE</literal>, <literal>CREATE
- TRIGGER</literal>, <literal>CREATE VIEW</literal>,
- <literal>DROP DATABASE</literal>, <literal>DROP
- EVENT</literal>, <literal>DROP FUNCTION</literal> (for stored
- functions, not UDFs), <literal>DROP INDEX</literal>,
- <literal>DROP PROCEDURE</literal>, <literal>DROP
- TABLE</literal>, <literal>DROP TRIGGER</literal>,
- <literal>DROP VIEW</literal>, <literal>LOAD INDEX INTO
- CACHE</literal>, <literal>RENAME TABLE</literal>,
- <literal>TRUNCATE TABLE</literal>.
+ <literal>CREATE DATABASE</literal>, <literal>CREATE
+ EVENT</literal>, <literal>CREATE FUNCTION</literal>,
+ <literal>CREATE INDEX</literal>, <literal>CREATE
+ PROCEDURE</literal>, <literal>CREATE TABLE</literal>,
+ <literal>CREATE TRIGGER</literal>, <literal>CREATE
+ VIEW</literal>, <literal>DROP DATABASE</literal>,
+ <literal>DROP EVENT</literal>, <literal>DROP
+ FUNCTION</literal> (for stored functions, not UDFs),
+ <literal>DROP INDEX</literal>, <literal>DROP
+ PROCEDURE</literal>, <literal>DROP TABLE</literal>,
+ <literal>DROP TRIGGER</literal>, <literal>DROP VIEW</literal>,
+ <literal>RENAME TABLE</literal>, <literal>TRUNCATE
+ TABLE</literal>.
</para>
<para>
@@ -414,7 +415,7 @@
<listitem>
<para>
- <emphasis role="bold">Transactional and locking
+ <emphasis role="bold">Transaction-control and locking
statements.</emphasis> <literal>BEGIN</literal>, <literal>LOCK
TABLES</literal>, <literal>SET AUTOCOMMIT=1</literal> (if the
value is not already 1), <literal>START TRANSACTION</literal>,
@@ -463,16 +464,53 @@
<listitem>
<para>
- <emphasis role="bold">Database and table administrative
- statements.</emphasis> <literal>ANALYZE TABLE</literal>,
- <literal>BACKUP DATABASE</literal>, <literal>CHECK
- TABLE</literal>, <literal>OPTIMIZE TABLE</literal>,
- <literal>REPAIR TABLE</literal>, <literal>RESTORE</literal>,
+ <emphasis role="bold">Administrative statements.</emphasis>
+ <literal>ANALYZE TABLE</literal>, <literal>BACKUP
+ DATABASE</literal>, <literal>CACHE INDEX</literal>,
+ <literal>CHECK TABLE</literal>, <literal>LOAD INDEX INTO
+ CACHE</literal>, <literal>OPTIMIZE TABLE</literal>,
+ <literal>REPAIR TABLE</literal>, <literal>RESTORE</literal>.
</para>
</listitem>
</itemizedlist>
+ <para>
+ As of MySQL 6.0.8, most statements that previously caused an
+ implicit commit before executing also do so after executing. The
+ intent is to handle each such statement in its own special
+ transaction because it cannot be rolled back anyway. The following
+ list provides additional details pertaining to this change:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The <literal>CREATE TABLE</literal> variants (<literal>CREATE
+ TABLE</literal> for <literal>InnoDB</literal> tables and
+ <literal>CREATE TABLE ... SELECT</literal>) that previously
+ were special cases no longer are so because <literal>CREATE
+ TABLE</literal> uniformly causes an implicit commit before and
+ after executing.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>FLUSH</literal> statement causes an implicit
+ commit.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Transaction-control and locking statements behave as before.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
</section>
<section id="savepoints">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r12175 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul.dubois | 28 Oct |
