Author: jstephens
Date: 2009-09-07 13:52:13 +0200 (Mon, 07 Sep 2009)
New Revision: 16485
Log:
Fixed version references
Modified:
trunk/refman-5.1/mysql-cluster-disk-data.xml
trunk/refman-5.1/mysql-cluster-glossary.xml
trunk/refman-5.1/mysql-cluster-limitations.xml
trunk/refman-5.1/mysql-cluster-management.xml
trunk/refman-5.1/mysql-cluster-overview.xml
trunk/refman-5.1/mysql-cluster-replication.xml
trunk/refman-5.1/mysql-cluster-security.xml
trunk/refman-5.1/mysql-cluster.xml
Modified: trunk/refman-5.1/mysql-cluster-disk-data.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-disk-data.xml 2009-09-07 10:56:21 UTC (rev 16484)
+++ trunk/refman-5.1/mysql-cluster-disk-data.xml 2009-09-07 11:52:13 UTC (rev 16485)
Changed blocks: 3, Lines Added: 11, Lines Deleted: 8; 2530 bytes
@@ -253,8 +253,9 @@
<para>
Every <literal>CREATE LOGFILE GROUP</literal> and
<literal>ALTER LOGFILE GROUP</literal> statement must
- include an <literal>ENGINE</literal> clause. In MySQL
- ¤t-series;, the permitted values for this clause are
+ include an <literal>ENGINE</literal> clause. In MySQL 5.1
+ (including MySQL Cluster NDB 6.X and 7.X through 7.1), the
+ permitted values for this clause are
<literal role="se">NDBCLUSTER</literal> and
<literal role="se">NDB</literal>.
</para>
@@ -404,8 +405,9 @@
<literal>ALTER TABLESPACE</literal> statements must
contain an <literal>ENGINE</literal> clause; only tables
using the same storage engine as the tablespace can be
- created in the tablespace. In MySQL ¤t-series;, the
- only permitted values for this clause are
+ created in the tablespace. In MySQL 5.1 (including MySQL
+ Cluster NDB 6.X and 7.X through 7.1), the only permitted
+ values for this clause are
<literal role="se">NDBCLUSTER</literal> and
<literal role="se">NDB</literal>.
</para>
@@ -485,10 +487,11 @@
columns are stored on disk. This is because there are indexes
on the <literal>id</literal>, <literal>last_name</literal>,
and <literal>first_name</literal> columns, and so data
- belonging to these columns is stored in RAM. In MySQL 5.1,
- only nonindexed columns can be held on disk; indexes and
- indexed column data continue to be stored in memory. This
- tradeoff between the use of indexes and conservation of RAM is
+ belonging to these columns is stored in RAM. In MySQL 5.1
+ (including MySQL Cluster NDB 6.X and 7.X through 7.1), only
+ nonindexed columns can be held on disk; indexes and indexed
+ column data continue to be stored in memory. This tradeoff
+ between the use of indexes and conservation of RAM is
something you must keep in mind as you design Disk Data
tables.
</para>
Modified: trunk/refman-5.1/mysql-cluster-glossary.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-glossary.xml 2009-09-07 10:56:21 UTC (rev 16484)
+++ trunk/refman-5.1/mysql-cluster-glossary.xml 2009-09-07 11:52:13 UTC (rev 16485)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 5; 1090 bytes
@@ -546,11 +546,11 @@
</formalpara>
<para>
- In MySQL 5.1 and MySQL Cluster NDB 6.x, it is also possible to
- create <firstterm>Disk Data</firstterm> tables where nonindexed
- columns are stored on disk, thus reducing the memory footprint
- required by the cluster. Note that indexes and indexed column
- data are still stored in RAM. See
+ In MySQL 5.1 (including MySQL Cluster NDB 6.X and 7.X), it is
+ also possible to create <firstterm>Disk Data</firstterm> tables
+ where nonindexed columns are stored on disk, thus reducing the
+ memory footprint required by the cluster. Note that indexes and
+ indexed column data are still stored in RAM. See
<xref linkend="mysql-cluster-disk-data"/>.
</para>
</listitem>
Modified: trunk/refman-5.1/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-limitations.xml 2009-09-07 10:56:21 UTC (rev 16484)
+++ trunk/refman-5.1/mysql-cluster-limitations.xml 2009-09-07 11:52:13 UTC (rev 16485)
Changed blocks: 5, Lines Added: 16, Lines Deleted: 16; 3466 bytes
@@ -60,7 +60,7 @@
conditions just set forth. You can report any discrepancies that you
encounter to the MySQL bugs database using the instructions given in
<xref linkend="bug-reports"/>. If we do not plan to fix the problem
- in MySQL ¤t-series;, we will add it to the list.
+ in MySQL Cluster NDB 6.X or 7.X, we will add it to the list.
</para>
<para>
@@ -263,9 +263,9 @@
<para>
Geometry datatypes (<literal>WKT</literal> and
<literal>WKB</literal>) are supported in
- <literal role="se">NDB</literal> tables in MySQL
- ¤t-series;. However, spatial indexes are not
- supported.
+ <literal role="se">NDB</literal> tables in MySQL 5.1
+ (including MySQL Cluster NDB 6.X and 7.X through 7.1).
+ However, spatial indexes are not supported.
</para>
</formalpara>
@@ -294,10 +294,11 @@
<para>
Support for user-defined partitioning for MySQL Cluster in
- MySQL ¤t-series; is restricted to
- [<literal>LINEAR</literal>] <literal>KEY</literal>
- partitioning. Beginning with MySQL 5.1.12, using any other
- partitioning type with <literal>ENGINE=NDB</literal> or
+ MySQL 5.1 (including MySQL Cluster NDB 6.X and 7.X through
+ 7.1) is restricted to [<literal>LINEAR</literal>]
+ <literal>KEY</literal> partitioning. Beginning with MySQL
+ 5.1.12, using any other partitioning type with
+ <literal>ENGINE=NDB</literal> or
<literal>ENGINE=NDBCLUSTER</literal> in a
<literal role="stmt">CREATE TABLE</literal> statement
results in an error.
@@ -1489,9 +1490,9 @@
<listitem>
<para>
Maximum data file size: The theoretical limit is 64G;
- however, in MySQL ¤t-series;, the practical upper
- limit is 32G. This is equivalent to 32768 extents of 1M
- each.
+ however, in MySQL 5.1 (including MySQL Cluster NDB 6.X
+ and 7.X through 7.1), the practical upper limit is 32G.
+ This is equivalent to 32768 extents of 1M each.
</para>
<para>
@@ -2094,11 +2095,10 @@
Previously, the maximum number of
<literal role="se">NDBCLUSTER</literal> tables in a single
MySQL Cluster was 1792, but this is no longer the case in
- MySQL ¤t-series; (including MySQL Cluster NDB 6.x).
- However, the number of tables is still included in the
- total maximum number of
- <literal role="se">NDBCLUSTER</literal> database objects
- (20320). (See
+ MySQL 5.1 and later MySQL Cluster releases. However, the
+ number of tables is still included in the total maximum
+ number of <literal role="se">NDBCLUSTER</literal> database
+ objects (20320). (See
<xref linkend="mysql-cluster-limitations-database-objects"/>.)
</para>
Modified: trunk/refman-5.1/mysql-cluster-management.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-management.xml 2009-09-07 10:56:21 UTC (rev 16484)
+++ trunk/refman-5.1/mysql-cluster-management.xml 2009-09-07 11:52:13 UTC (rev 16485)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 5; 1843 bytes
@@ -1984,12 +1984,12 @@
2007-01-26 19:35:55 [MgmSrvr] INFO -- Node 4: Resource 0 min: 0 max: 639 curr: 0
2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 4: Node 9 Connected
2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 1: Node 9 Connected
-2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 1: Node 9: API version 5.1.15
+2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 1: Node 9: API &mysql-cluster-current-7.0;
2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 2: Node 9 Connected
-2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 2: Node 9: API version 5.1.15
+2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 2: Node 9: API &mysql-cluster-current-7.0;
2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 3: Node 9 Connected
-2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 3: Node 9: API version 5.1.15
-2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 4: Node 9: API version 5.1.15
+2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 3: Node 9: API &mysql-cluster-current-7.0;
+2007-01-26 19:39:42 [MgmSrvr] INFO -- Node 4: Node 9: API &mysql-cluster-current-7.0;
2007-01-26 19:59:22 [MgmSrvr] ALERT -- Node 2: Node 7 Disconnected
2007-01-26 19:59:22 [MgmSrvr] ALERT -- Node 2: Node 7 Disconnected
</programlisting>
@@ -7951,7 +7951,7 @@
<note>
<para>
- In MySQL 5.1, this statement no longer supports a
+ In MySQL 5.1 and later, this statement does not support a
<literal role="op">LIKE</literal> clause. However, you can
use <literal role="op">LIKE</literal> to filter queries
against the
Modified: trunk/refman-5.1/mysql-cluster-overview.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-overview.xml 2009-09-07 10:56:21 UTC (rev 16484)
+++ trunk/refman-5.1/mysql-cluster-overview.xml 2009-09-07 11:52:13 UTC (rev 16485)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 747 bytes
@@ -508,7 +508,7 @@
<para>
MySQL Cluster normally partitions
<literal role="se">NDBCLUSTER</literal> tables automatically.
- However, in MySQL 5.1 and MySQL Cluster NDB 6.x, it is
+ However, in MySQL 5.1 and later MySQL Cluster releases, it is
possible to employ user-defined partitioning with
<literal role="se">NDBCLUSTER</literal> tables. This is
subject to the following limitations:
Modified: trunk/refman-5.1/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication.xml 2009-09-07 10:56:21 UTC (rev 16484)
+++ trunk/refman-5.1/mysql-cluster-replication.xml 2009-09-07 11:52:13 UTC (rev 16485)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 581 bytes
@@ -303,7 +303,8 @@
<para>
The following are known problems or issues when using replication
- with MySQL Cluster in MySQL ¤t-series;:
+ with MySQL Cluster in MySQL 5.1 (including MySQL Cluster NDB 6.X
+ and 7.X through 7.1):
</para>
<itemizedlist>
Modified: trunk/refman-5.1/mysql-cluster-security.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-security.xml 2009-09-07 10:56:21 UTC (rev 16484)
+++ trunk/refman-5.1/mysql-cluster-security.xml 2009-09-07 11:52:13 UTC (rev 16485)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 5; 1059 bytes
@@ -146,11 +146,11 @@
<para>
More information is available
- <link linkend="ndbparam-api-hostname">elsewhere
- in this chapter</link> about the
- <literal>HostName</literal> parameter. Also see
- <xref linkend="mysql-cluster-quick"/>, for configuration
- examples using <literal>HostName</literal> with API nodes.
+ <link linkend="ndbparam-api-hostname">elsewhere in this
+ chapter</link> about the <literal>HostName</literal>
+ parameter. Also see <xref linkend="mysql-cluster-quick"/>,
+ for configuration examples using
+ <literal>HostName</literal> with API nodes.
</para>
</note>
</listitem>
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2009-09-07 10:56:21 UTC (rev 16484)
+++ trunk/refman-5.1/mysql-cluster.xml 2009-09-07 11:52:13 UTC (rev 16485)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 5; 1167 bytes
@@ -87,11 +87,11 @@
MySQL Cluster NDB 6.3 and MySQL Cluster NDB 7.0 (formerly known as
<quote>MySQL Cluster NDB 6.4</quote>) release series are Generally
Available (GA). MySQL Cluster NDB 6.2, a previous GA release series,
- is supported, although we recommend that new deployments use MySQL
- Cluster NDB 6.3 or MySQL Cluster NDB 7.0. MySQL Cluster NDB 7.1 is
- currently under development; we expect to make source and binaries
- built from the MySQL Cluster NDB 7.1 available for evaluation and
- testing purposes in the near future.
+ is still supported, although we recommend that new deployments use
+ MySQL Cluster NDB 6.3 or MySQL Cluster NDB 7.0. MySQL Cluster NDB
+ 7.1 is currently under development; we expect to make source and
+ binaries built from the MySQL Cluster NDB 7.1 available for
+ evaluation and testing purposes in the near future.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r16485 - trunk/refman-5.1 | jon.stephens | 7 Sep |
