bk commit - mysqldoc@docsrva tree (jon:1.3565)

[jon]

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.3565 05/09/15 08:23:34 jon@stripped +4 -0
  Transaction Commands: Cluster is transaction-safe, too. (Vinay)

  refman/sql-syntax.xml
    1.72 05/09/15 08:23:32 jon@stripped +4 -3
    Cluster is transaction-safe, too.

  refman-5.1/sql-syntax.xml
    1.47 05/09/15 08:23:32 jon@stripped +5 -4
    Cluster is transaction-safe, too.

  refman-5.0/sql-syntax.xml
    1.47 05/09/15 08:23:31 jon@stripped +5 -4
    Cluster is transaction-safe, too.

  refman-4.1/sql-syntax.xml
    1.63 05/09/15 08:23:31 jon@stripped +3 -2
    Cluster is transaction-safe, too.

# 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.
# Root:	/home/jon/bk/mysqldoc2

--- 1.46/refman-5.1/sql-syntax.xml	2005-09-15 07:25:37 +10:00
+++ 1.47/refman-5.1/sql-syntax.xml	2005-09-15 08:23:32 +10:00
@@ -10166,9 +10166,10 @@
       </para>
 
       <para>
-        If you are using transaction-safe tables (like
-        <literal>InnoDB</literal> or <literal>BDB</literal>), you can
-        disable autocommit mode with the following statement:
+        If you are using a transaction-safe storage engine (like
+        <literal>InnoDB</literal>, <literal>BDB</literal> or 
+        <literal>NDB Cluster</literal>), you can disable autocommit 
+        mode with the following statement:
       </para>
 
 <programlisting>
@@ -17499,7 +17500,7 @@
 
         <para>
           <emphasis role="bold">Note</emphasis>: It is not possible in
-          MySQL 5.1 to issue <literal>FLUSH</literal> statements within
+          MySQL &current-version; to issue <literal>FLUSH</literal> statements within
           stored functions or triggers. However, you may use
           <literal>FLUSH</literal> in stored procedures, so long as
           these are not called from stored functions or triggers. See

--- 1.62/refman-4.1/sql-syntax.xml	2005-09-15 04:01:25 +10:00
+++ 1.63/refman-4.1/sql-syntax.xml	2005-09-15 08:23:31 +10:00
@@ -9259,8 +9259,9 @@
 
       <para>
         If you are using transaction-safe tables (like
-        <literal>InnoDB</literal> or <literal>BDB</literal>), you can
-        disable autocommit mode with the following statement:
+        <literal>InnoDB</literal>, <literal>BDB</literal>, or 
+        <literal>NDB Cluster</literal>), you can disable autocommit 
+        mode with the following statement:
       </para>
 
 <programlisting>

--- 1.71/refman/sql-syntax.xml	2005-09-15 04:01:25 +10:00
+++ 1.72/refman/sql-syntax.xml	2005-09-15 08:23:32 +10:00
@@ -9502,9 +9502,10 @@
       </para>
 
       <para>
-        If you are using transaction-safe tables (like
-        <literal>InnoDB</literal> or <literal>BDB</literal>), you can
-        disable autocommit mode with the following statement:
+        If you are using a transaction-safe storage engine (like
+        <literal>InnoDB</literal>, <literal>BDB</literal> or 
+        <literal>NDB Cluster</literal>), you can disable autocommit 
+        mode with the following statement:
       </para>
 
 <programlisting>

--- 1.46/refman-5.0/sql-syntax.xml	2005-09-15 04:01:25 +10:00
+++ 1.47/refman-5.0/sql-syntax.xml	2005-09-15 08:23:31 +10:00
@@ -9391,9 +9391,10 @@
       </para>
 
       <para>
-        If you are using transaction-safe tables (like
-        <literal>InnoDB</literal> or <literal>BDB</literal>), you can
-        disable autocommit mode with the following statement:
+        If you are using a transaction-safe storage engine (like
+        <literal>InnoDB</literal>, <literal>BDB</literal> or 
+        <literal>NDB Cluster</literal>), you can disable autocommit 
+        mode with the following statement:
       </para>
 
 <programlisting>
@@ -16738,7 +16739,7 @@
 
         <para>
           Using <literal>FLUSH</literal> statements within stored
-          functions or triggers is not supported in MySQL 5.0. As of
+          functions or triggers is not supported in MySQL &current-version;. As of
           MySQL 5.0.12, it is no longer possible to do so at all.
           However, you may use <literal>FLUSH</literal> in stored
           procedures, so long as these are not called from stored