svn commit - mysqldoc@docsrva: r4053 - in trunk: refman-4.1 refman-5.0 refman-5.1

[jon]

Author: jstephens
Date: 2006-11-28 03:17:57 +0100 (Tue, 28 Nov 2006)
New Revision: 4053

Log:

Fixed ref to Disk Data being "in some future release" (Thanks, Brian Z!)



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


Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml	2006-11-27 22:10:50 UTC (rev 4052)
+++ trunk/refman-4.1/mysql-cluster.xml	2006-11-28 02:17:57 UTC (rev 4053)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 4; 1116 bytes

@@ -958,10 +958,11 @@
         commodity hardware and has no unusual requirements in this
         regard, other than for large amounts of RAM, due to the fact
         that all live data storage is done in memory. (Note that this is
-        subject to change, and that we intend to implement disk-based
-        storage in a future MySQL Cluster release.) Naturally, multiple
-        and faster CPUs will enhance performance. Memory requirements
-        for Cluster processes are relatively small.
+        not the case with Disk Data tables, which are implemented in
+        MySQL 5.1; however, we do not intend to backport this feature to
+        MySQL &current-series;.) Naturally, multiple and faster CPUs
+        will enhance performance. Memory requirements for other Cluster
+        processes are relatively small.
       </para>
 
       <remark role="todo">


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2006-11-27 22:10:50 UTC (rev 4052)
+++ trunk/refman-5.0/mysql-cluster.xml	2006-11-28 02:17:57 UTC (rev 4053)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 4; 1117 bytes

@@ -958,10 +958,11 @@
         commodity hardware and has no unusual requirements in this
         regard, other than for large amounts of RAM, due to the fact
         that all live data storage is done in memory. (Note that this is
-        subject to change, and that we intend to implement disk-based
-        storage in a future MySQL Cluster release.) Naturally, multiple
-        and faster CPUs will enhance performance. Memory requirements
-        for Cluster processes are relatively small.
+        not the case with Disk Data tables, which are implemented in
+        MySQL 5.1; however, we do not intend to backport this feature to
+        MySQL &current-series;.) Naturally, multiple and faster CPUs
+        will enhance performance. Memory requirements for other Cluster
+        processes are relatively small. 
       </para>
 
       <remark role="todo">


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2006-11-27 22:10:50 UTC (rev 4052)
+++ trunk/refman-5.1/mysql-cluster.xml	2006-11-28 02:17:57 UTC (rev 4053)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 4; 1091 bytes

@@ -958,10 +958,11 @@
         commodity hardware and has no unusual requirements in this
         regard, other than for large amounts of RAM, due to the fact
         that all live data storage is done in memory. (Note that this is
-        subject to change, and that we intend to implement disk-based
-        storage in a future MySQL Cluster release.) Naturally, multiple
-        and faster CPUs will enhance performance. Memory requirements
-        for Cluster processes are relatively small.
+        not the case with Disk Data tables &mdash; see 
+        <xref linkend="mysql-cluster-disk-data"/>, for more information
+        about these.) Naturally, multiple and faster CPUs will enhance
+        performance. Memory requirements for other Cluster processes are
+        relatively small.
       </para>
 
       <remark role="todo">