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

[jstephens]

Author: jstephens
Date: 2006-07-14 12:24:24 +0200 (Fri, 14 Jul 2006)
New Revision: 2734

Log:
Misc. fixes to Limitation section (thanks, Pekka!)

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


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2006-07-14 04:25:21 UTC (rev 2733)
+++ trunk/refman-5.1/mysql-cluster.xml	2006-07-14 10:24:24 UTC (rev 2734)
Changed blocks: 6, Lines Added: 23, Lines Deleted: 20; 4174 bytes

@@ -15545,14 +15545,13 @@
                 <para>
                   <emphasis role="bold">Important</emphasis>: If a
                   <literal>SELECT</literal> from a Cluster table
-                  includes a <literal>BLOB</literal>,
-                  <literal>TEXT</literal>, or <literal>VARCHAR</literal>
-                  column, the <literal>READ COMMITTED</literal>
-                  transaction isolation level is converted to a read
-                  with read lock. This is done to guarantee consistency,
-                  due to the fact that parts of the values stored in
-                  columns of these types are actually read from a
-                  separate table.
+                  includes a <literal>BLOB</literal> or
+                  <literal>TEXT</literal> column, the <literal>READ
+                    COMMITTED</literal> transaction isolation level is
+                  converted to a read with read lock. This is done to
+                  guarantee consistency, due to the fact that parts of
+                  the values stored in columns of these types are
+                  actually read from a separate table.
                 </para>
               </listitem>
 

@@ -15580,7 +15579,8 @@
                       <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.
+                      table, then it must be re-run until it is
+                      successful.
                     </para>
                   </listitem>
 

@@ -15696,7 +15696,7 @@
                   pages. As each <literal>DataMemory</literal> page is
                   used, it is assigned to a specific table; once
                   allocated, this memory cannot be freed except by
-                  deleting the table.
+                  dropping the table.
                 </para>
 
                 <para>

@@ -15755,15 +15755,16 @@
           <listitem>
             <para>
               The maximum number of tables in a Cluster database is
-              limited to 1792.
+              limited to 20320.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              The maximum number of ordered indexes per cluster,
-              including <literal>AUTO_INCREMENT</literal> columns and
-              hidden primary keys, is 2048.
+              In MySQL 5.1.10 and earlier versions, the maximum number
+              of tables having <literal>AUTO_INCREMENT</literal> columns
+              &mdash; including those belonging to hidden primary keys
+              &mdash; is 2048. 
             </para>
 
             <para>

@@ -15782,8 +15783,8 @@
             <para>
               The maximum permitted size of any one row is 8KB. Note
               that each <literal>BLOB</literal> or
-              <literal>TEXT</literal> column contributes a maximum of
-              256 bytes towards this total.
+              <literal>TEXT</literal> column contributes 256 + 8 = 264
+              bytes towards this total.
             </para>
           </listitem>
 

@@ -15864,10 +15865,12 @@
 
           <listitem>
             <para>
-              The <literal>Records in range</literal> statistic is not
-              supported, resulting in non-optimal query plans in some
-              cases. Employ <literal>USE INDEX</literal> or
-              <literal>FORCE INDEX</literal> as a workaround.
+              The <literal>Records in range</literal> statistic is
+              available but not completely tested or officially
+              supported. This may result in non-optimal query plans in
+              some cases. If necessary, you can employ <literal>USE
+                INDEX</literal> or <literal>FORCE INDEX</literal> for
+              that purpose.
             </para>
           </listitem>