MySQL Lists are EOL. Please join:

List:Internals« Previous MessageNext Message »
From:jon Date:June 24 2005 9:13am
Subject:bk commit - mysqldoc@docsrva tree (jon:1.2872)
View as plain text  
Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2872 05/06/24 19:13:01 jon@stripped +6 -0
  Statements now causing implicit 
  commits beginning in 4.1.13 and 5.0.8.
  
  Sync refman-4.1 and refman-5.0 trees to refman tree.

  refman/sql-syntax.xml
    1.2 05/06/24 19:12:59 jon@stripped +15 -1
    implicit-commits:
    Statements causing commits as of 4.1.13/5.0.8.

  refman/innodb.xml
    1.8 05/06/24 19:12:59 jon@stripped +12 -7
    innodb-implicit-commands-or-rollbacks:
    Statements causing commits as of 4.1.13/5.0.8.

  refman-5.0/sql-syntax.xml
    1.2 05/06/24 19:12:59 jon@stripped +15 -1
    Sync with refman.

  refman-5.0/innodb.xml
    1.4 05/06/24 19:12:59 jon@stripped +12 -7
    Sync with refman.

  refman-4.1/sql-syntax.xml
    1.2 05/06/24 19:12:59 jon@stripped +15 -1
    Sync with refman.

  refman-4.1/innodb.xml
    1.4 05/06/24 19:12:58 jon@stripped +12 -7
    Sync with refman.

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	jon
# Host:	gigan.site
# Root:	/home/jon/bk/mysqldoc

--- 1.3/refman-4.1/innodb.xml	2005-06-23 13:12:08 +10:00
+++ 1.4/refman-4.1/innodb.xml	2005-06-24 19:12:58 +10:00
@@ -4000,9 +4000,10 @@
 
    <title id='title-innodb-implicit-command-or-rollback'>&title-innodb-implicit-command-or-rollback;</title>
 
-<!--  TODO: probably should merge this into the SQL chapter section that -->
-
-<!--  also lists these conditions. -->
+<!--
+      TODO: probably should merge this into the SQL chapter section that
+      also lists these conditions.
+-->
 
    <para>
     MySQL begins each client connection with autocommit mode enabled by
@@ -4038,10 +4039,14 @@
      <literal>TRUNCATE</literal>, <literal>UNLOCK TABLES</literal>.
     </para></listitem>
 
-    <listitem><para>
-     <literal>CREATE TABLE</literal> (this commits only if before MySQL
-     4.0.13 and MySQL binary logging is used).
-    </para></listitem>
+    <listitem>
+      <para>Before MySQL 4.0.13, <literal>CREATE TABLE</literal> commits
+      if binary logging is used. Starting with MySQL 4.1.13 and MySQL
+      5.0.8, the statements <literal>CREATE TABLE</literal>,
+      <literal>TRUNCATE TABLE</literal>, <literal>DROP
+      DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
+      an implicit commit.</para>
+   </listitem>
 
     <listitem><para>
      The <literal>CREATE TABLE</literal> statement in

--- 1.1/refman-4.1/sql-syntax.xml	2005-06-17 05:35:23 +10:00
+++ 1.2/refman-4.1/sql-syntax.xml	2005-06-24 19:12:59 +10:00
@@ -8725,6 +8725,17 @@
          </row>
          <row>
            <entry>
+            <literal>CREATE TABLE</literal>
+           </entry>
+           <entry>
+            <literal>&nbsp;</literal>
+           </entry>
+           <entry>
+            <literal>CREATE DATABASE</literal>
+           </entry>
+         </row>
+         <row>
+           <entry>
             <literal>DROP DATABASE</literal>
            </entry>
            <entry>
@@ -8764,7 +8775,10 @@
     <literal>UNLOCK TABLES</literal> also commits a transaction if any
     tables currently are locked. Prior to MySQL 4.0.13, <literal>CREATE
     TABLE</literal> commits a transaction if the binary update log is
-    enabled.
+    enabled. The statements <literal>CREATE TABLE</literal>,
+    <literal>TRUNCATE TABLE</literal>, <literal>DROP DATABASE</literal>,
+    and <literal>CREATE DATABASE</literal> also cause an implicit
+    commit, beginning with MySQL 4.1.13 and MySQL 5.0.8.
    </para>
 
    <para>

--- 1.3/refman-5.0/innodb.xml	2005-06-23 13:12:09 +10:00
+++ 1.4/refman-5.0/innodb.xml	2005-06-24 19:12:59 +10:00
@@ -4000,9 +4000,10 @@
 
    <title id='title-innodb-implicit-command-or-rollback'>&title-innodb-implicit-command-or-rollback;</title>
 
-<!--  TODO: probably should merge this into the SQL chapter section that -->
-
-<!--  also lists these conditions. -->
+<!--
+      TODO: probably should merge this into the SQL chapter section that
+      also lists these conditions.
+-->
 
    <para>
     MySQL begins each client connection with autocommit mode enabled by
@@ -4038,10 +4039,14 @@
      <literal>TRUNCATE</literal>, <literal>UNLOCK TABLES</literal>.
     </para></listitem>
 
-    <listitem><para>
-     <literal>CREATE TABLE</literal> (this commits only if before MySQL
-     4.0.13 and MySQL binary logging is used).
-    </para></listitem>
+    <listitem>
+      <para>Before MySQL 4.0.13, <literal>CREATE TABLE</literal> commits
+      if binary logging is used. Starting with MySQL 4.1.13 and MySQL
+      5.0.8, the statements <literal>CREATE TABLE</literal>,
+      <literal>TRUNCATE TABLE</literal>, <literal>DROP
+      DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
+      an implicit commit.</para>
+   </listitem>
 
     <listitem><para>
      The <literal>CREATE TABLE</literal> statement in

--- 1.1/refman-5.0/sql-syntax.xml	2005-06-17 05:46:22 +10:00
+++ 1.2/refman-5.0/sql-syntax.xml	2005-06-24 19:12:59 +10:00
@@ -8725,6 +8725,17 @@
          </row>
          <row>
            <entry>
+            <literal>CREATE TABLE</literal>
+           </entry>
+           <entry>
+            <literal>&nbsp;</literal>
+           </entry>
+           <entry>
+            <literal>CREATE DATABASE</literal>
+           </entry>
+         </row>
+         <row>
+           <entry>
             <literal>DROP DATABASE</literal>
            </entry>
            <entry>
@@ -8764,7 +8775,10 @@
     <literal>UNLOCK TABLES</literal> also commits a transaction if any
     tables currently are locked. Prior to MySQL 4.0.13, <literal>CREATE
     TABLE</literal> commits a transaction if the binary update log is
-    enabled.
+    enabled. The statements <literal>CREATE TABLE</literal>,
+    <literal>TRUNCATE TABLE</literal>, <literal>DROP DATABASE</literal>,
+    and <literal>CREATE DATABASE</literal> also cause an implicit
+    commit, beginning with MySQL 4.1.13 and MySQL 5.0.8.
    </para>
 
    <para>

--- 1.7/refman/innodb.xml	2005-06-23 13:12:09 +10:00
+++ 1.8/refman/innodb.xml	2005-06-24 19:12:59 +10:00
@@ -4000,9 +4000,10 @@
 
    <title id='title-innodb-implicit-command-or-rollback'>&title-innodb-implicit-command-or-rollback;</title>
 
-<!--  TODO: probably should merge this into the SQL chapter section that -->
-
-<!--  also lists these conditions. -->
+<!--
+      TODO: probably should merge this into the SQL chapter section that
+      also lists these conditions.
+-->
 
    <para>
     MySQL begins each client connection with autocommit mode enabled by
@@ -4038,10 +4039,14 @@
      <literal>TRUNCATE</literal>, <literal>UNLOCK TABLES</literal>.
     </para></listitem>
 
-    <listitem><para>
-     <literal>CREATE TABLE</literal> (this commits only if before MySQL
-     4.0.13 and MySQL binary logging is used).
-    </para></listitem>
+    <listitem>
+      <para>Before MySQL 4.0.13, <literal>CREATE TABLE</literal> commits
+      if binary logging is used. Starting with MySQL 4.1.13 and MySQL
+      5.0.8, the statements <literal>CREATE TABLE</literal>,
+      <literal>TRUNCATE TABLE</literal>, <literal>DROP
+      DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause
+      an implicit commit.</para>
+   </listitem>
 
     <listitem><para>
      The <literal>CREATE TABLE</literal> statement in

--- 1.1/refman/sql-syntax.xml	2005-06-16 09:46:58 +10:00
+++ 1.2/refman/sql-syntax.xml	2005-06-24 19:12:59 +10:00
@@ -8725,6 +8725,17 @@
          </row>
          <row>
            <entry>
+            <literal>CREATE TABLE</literal>
+           </entry>
+           <entry>
+            <literal>&nbsp;</literal>
+           </entry>
+           <entry>
+            <literal>CREATE DATABASE</literal>
+           </entry>
+         </row>
+         <row>
+           <entry>
             <literal>DROP DATABASE</literal>
            </entry>
            <entry>
@@ -8764,7 +8775,10 @@
     <literal>UNLOCK TABLES</literal> also commits a transaction if any
     tables currently are locked. Prior to MySQL 4.0.13, <literal>CREATE
     TABLE</literal> commits a transaction if the binary update log is
-    enabled.
+    enabled. The statements <literal>CREATE TABLE</literal>,
+    <literal>TRUNCATE TABLE</literal>, <literal>DROP DATABASE</literal>,
+    and <literal>CREATE DATABASE</literal> also cause an implicit
+    commit, beginning with MySQL 4.1.13 and MySQL 5.0.8.
    </para>
 
    <para>
Thread
bk commit - mysqldoc@docsrva tree (jon:1.2872)jon24 Jun