svn commit - mysqldoc@docsrva: r6555 - trunk/refman-5.1

[stefan]

Author: shinz
Date: 2007-05-21 18:23:16 +0200 (Mon, 21 May 2007)
New Revision: 6555

Log:
Some remarks of Stefan's on Cluster limitations

Modified:
   trunk/refman-5.1/mysql-cluster.xml


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2007-05-21 16:22:04 UTC (rev 6554)
+++ trunk/refman-5.1/mysql-cluster.xml	2007-05-21 16:23:16 UTC (rev 6555)
Changed blocks: 6, Lines Added: 6, Lines Deleted: 1; 2271 bytes

@@ -21262,7 +21262,7 @@
                     <formalpara>
 
                       <title>Duplicate keys</title>
-
+		      
                       <para>
                         A duplicate key error returns the error message
                         <errortext>ERROR 23000: Can't write; duplicate

@@ -21271,6 +21271,7 @@
                       </para>
 
                     </formalpara>
+		    <remark>This looks like the standard behaviour for duplicate key errors; how is it a Cluster limitation? /SH</remark>
                   </listitem>
 
                   <listitem>

@@ -21803,6 +21804,7 @@
                             INFILE</literal> statement, the
                             <literal>NDB</literal> engine can and does
                             commit at will.
+			    <remark>What does "at will" exactly mean? Always? /SH</remark>
                           </para>
                         </important>
 

@@ -21862,6 +21864,7 @@
               <title>Temporary errors</title>
 
               <para>
+		      <remark>We need to add visual markup (CSS etc.) for the errortext element. /SH</remark>
                 When first starting a node, it is possible that you may
                 see Error 1204 <errortext>Temporary failure,
                 distribution changed</errortext> and similar temporary

@@ -22088,6 +22091,7 @@
                 <title>Transaction isolation</title>
 
                 <para>
+			<remark>What about saying "InnoDB, *for example*"? /SH</remark>
                   The only supported isolation level is <literal>READ
                   COMMITTED</literal>. (InnoDB supports <literal>READ
                   COMMITTED</literal>, <literal>READ

@@ -22327,6 +22331,7 @@
         The following are limitations specific to the
         <literal>NDBCLUSTER</literal> storage engine, and do not occur
         with <literal>MyISAM</literal> or <literal>InnoDB</literal>:
+	<remark>Why mention InnoDB and MyISAM specifically, rather than saying "with any other storage engine"? /SH</remark>
 
         <itemizedlist>