From: jon
Date: April 8 2006 5:26am
Subject: svn commit - mysqldoc@docsrva: r1763 - trunk/refman-5.0
List-Archive: http://lists.mysql.com/commits/4665
Message-Id: <200604080526.k385QxJi003193@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2006-04-08 07:26:59 +0200 (Sat, 08 Apr 2006)
New Revision: 1763

Log:

Fix bad merge in previous commit (rev 1762).



Modified:
   trunk/refman-5.0/ndbcluster.xml

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-04-08 05:21:15 UTC (rev 1762)
+++ trunk/refman-5.0/ndbcluster.xml	2006-04-08 05:26:59 UTC (rev 1763)
@@ -9377,6 +9377,74 @@
               
               <listitem>
                 <para>
+                  As noted elsewhere in this chapter, MySQL Cluster does
+                  not handle large transactions well; it is better to
+                  perform a number of small transactions with a few
+                  operations each than to attempt a single large
+                  transaction containing a great many operations.
+                </para>
+                
+                <para>
+                  Among other considerations, large transactions require
+                  very large amounts of memory. Because of this, the
+                  transactional behaviour of a number of MySQL
+                  statements is effected as described in the following
+                  list:
+                </para>
+                
+                <itemizedlist>
+                  <listitem>
+                    <para>
+                      <literal>TRUNCATE</literal> is not transactional
+                      when used on <literal>NDB</literal> tables. If a
+                      <literal>TRUNCATE</literal> fails to empty the
+                      table, then it is re-run until it is successful.
+                    </para>
+                  </listitem>
+                  
+                  <listitem>
+                    <para>
+                      <literal>DELETE FROM</literal> (even with no
+                      <literal>WHERE</literal> clause)
+                      <emphasis>is</emphasis> transactional. For tables
+                      containing a great many rows, you may find that
+                      performance is improved by using several
+                      <literal>DELETE FROM ... LIMIT ...</literal>
+                      statements to <quote>chunk</quote> the delete
+                      operation. If the objective is to empty the table,
+                      then you may wish to use
+                      <literal>TRUNCATE</literal> instead. 
+                    </para>
+                  </listitem>
+                  
+                  <listitem>
+                    <para>
+                      <literal>LOAD DATA INFILE</literal> is not
+                      transactional. During such an operation the
+                      <literal>NDB</literal> engine can and does commit
+                      at will.
+                    </para>
+                    
+                    <para>
+                      <literal>LOAD DATA FROM MASTER</literal> is not
+                      supported in MySQL Cluster.
+                    </para>
+                  </listitem>
+                  
+                  <listitem>
+                    <para>
+                      When copying a table as part of an <literal>ALTER
+                        TABLE</literal>, the creation of the copy is
+                      non-transactional. (In any case, this operation is
+                      rolled back when the copy is deleted.)
+                    </para>
+                  </listitem>
+                </itemizedlist>
+                
+              </listitem>
+              
+              <listitem>
+                <para>
                   <emphasis role="bold">Node Start, Stop, or
                     Restart:</emphasis>: Starting, stopping, or
                   restarting a node may give rise to temporary errors