MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon.stephens Date:February 14 2011 4:30pm
Subject:svn commit - mysqldoc@oter02: r25100 - trunk/refman-5.1
View as plain text  
Author: js221926
Date: 2011-02-14 17:30:19 +0100 (Mon, 14 Feb 2011)
New Revision: 25100

Log:

WL#5568 updates (Thanks. Mai!)



Modified:
   trunk/refman-5.1/information-schema.xml


Modified: trunk/refman-5.1/information-schema.xml
===================================================================
--- trunk/refman-5.1/information-schema.xml	2011-02-14 15:02:55 UTC (rev 25099)
+++ trunk/refman-5.1/information-schema.xml	2011-02-14 16:30:19 UTC (rev 25100)
Changed blocks: 6, Lines Added: 41, Lines Deleted: 23; 4677 bytes

@@ -683,9 +683,18 @@
         </para>
 
         <para>
+          For <literal role="se">NDB</literal> tables,
+          <literal>DATA_LENGTH</literal> includes data stored in main
+          memory only.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
-          7.1.11, <literal>DATA_LENGTH</literal> includes data on disk
-          as well as in main memory.
+          7.1.11, for MySQL Cluster Disk Data tables,
+          <literal>MAX_DATA_LENGTH</literal> shows the space allocated
+          for the disk part of a Disk Data table or fragment.
         </para>
       </listitem>
 

@@ -698,9 +707,9 @@
 
         <para>
           Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
-          7.1.11, <literal>DATA_FREE</literal> includes
-          <literal role="se">NDB</literal> table data on disk as well as
-          in main memory.
+          7.1.11, <literal>DATA_FREE</literal> shows the space allocated
+          on disk for, but not used by, a Disk Data table or fragment on
+          disk.
         </para>
       </listitem>
 

@@ -4219,10 +4228,16 @@
         </para>
 
         <para>
-          For partitions of <literal role="se">NDB</literal> tables,
-          whether the tables use implicit or explicit partitioning, the
-          <literal>AVG_ROW_LENGTH</literal> column value is always 0.
-          However, you can obtain equivalent information using the
+          Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
+          7.1.11, <literal>AVG_ROW_LENGTH</literal> includes statistics
+          for partitions of <literal role="se">NDB</literal> tables,
+          whether the tables use implicit or explicit partitioning.
+          (Previously the value of this column was always 0 for
+          partitions of <literal role="se">NDB</literal> tables.)
+        </para>
+
+        <para>
+          You can also obtain equivalent information using the
           <command>ndb_desc</command> utility.
         </para>
       </listitem>

@@ -4238,10 +4253,10 @@
         <para>
           Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
           7.1.11, <literal>DATA_LENGTH</literal> shows correct
-          information for <literal role="se">NDB</literal> tables.
-          Previously, for partitions of <literal role="se">NDB</literal>
-          tables, the <literal>DATA_LENGTH</literal> column value was
-          always 0.
+          information for in-memory data in
+          <literal role="se">NDB</literal> tables. Previously, for
+          partitions of <literal role="se">NDB</literal> tables, the
+          <literal>DATA_LENGTH</literal> column value was always 0.
         </para>
 
         <para>

@@ -4259,11 +4274,12 @@
 
         <para>
           Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
-          7.1.11, <literal>MAX_DATA_LENGTH</literal> shows correct
-          information for <literal role="se">NDB</literal> tables.
-          Previously, for partitions of <literal role="se">NDB</literal>
-          tables, the <literal>MAX_DATA_LENGTH</literal> column value
-          was always <literal>NULL</literal>.
+          7.1.11, <literal>MAX_DATA_LENGTH</literal> shows the space
+          allocated for the disk part of a MySQL Cluster Disk Data table
+          or fragment. (Previously, for partitions of
+          <literal role="se">NDB</literal> tables, the
+          <literal>MAX_DATA_LENGTH</literal> column value was always
+          <literal>NULL</literal>.)
         </para>
 
         <para>

@@ -4295,11 +4311,13 @@
         </para>
 
         <para>
-          Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
-          7.1.11, <literal>DATA_FREE</literal> shows correct information
-          for <literal role="se">NDB</literal> tables. Previously, for
-          partitions of <literal role="se">NDB</literal> tables, the
-          <literal>DATA_FREE</literal> column value was always 0.
+          For MySQL Cluster Disk Data tables, beginning with MySQL
+          Cluster NDB 7.0.22 and MySQL Cluster NDB 7.1.11,
+          <literal>DATA_FREE</literal> shows the space allocated on disk
+          for, but not used by, a Disk Data table or fragment on disk.
+          (Previously, for partitions of
+          <literal role="se">NDB</literal> tables, the value of this
+          column was always 0.)
         </para>
 
         <para>


Thread
svn commit - mysqldoc@oter02: r25100 - trunk/refman-5.1jon.stephens14 Feb