Author: jstephens
Date: 2007-02-01 15:33:07 +0100 (Thu, 01 Feb 2007)
New Revision: 4732
Log:
Updated 5.1 changes section.
Modified:
branches/telcos/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/mysql-cluster.xml
Modified: branches/telcos/refman-5.1/mysql-cluster.xml
===================================================================
--- branches/telcos/refman-5.1/mysql-cluster.xml 2007-02-01 14:29:05 UTC (rev 4731)
+++ branches/telcos/refman-5.1/mysql-cluster.xml 2007-02-01 14:33:07 UTC (rev 4732)
Changed blocks: 4, Lines Added: 36, Lines Deleted: 11; 3287 bytes
@@ -19255,7 +19255,7 @@
<secondary>resolved in current version from previous versions</secondary>
</indexterm>
- <para>
+ <para id="mysql-cluster-limitations-resolved-in-5-1">
<emphasis role="bold">MySQL Cluster issues from previous
versions that have been resolved in MySQL 5.1</emphasis>:
</para>
@@ -19460,11 +19460,11 @@
</indexterm>
<para>
- Four major new features for MySQL Cluster have been developed
- for MySQL 5.1:
+ A number of new features for MySQL Cluster have been implemented
+ in MySQL 5.1:
</para>
- <orderedlist>
+ <itemizedlist>
<listitem>
<para>
@@ -19513,12 +19513,11 @@
Users can define partitions based on columns that are part
of the primary key. It is possible to partition
<literal>NDB</literal> tables based on
- <literal>KEY</literal>, <literal>HASH</literal>,
- <literal>LINEAR KEY</literal>, and <literal>LINEAR
- HASH</literal> schemes. This feature is also available for
- most other MySQL storage engines, which support additional
- partitioning types that are not available to <literal>NDB
- Cluster</literal> tables.
+ <literal>KEY</literal> and <literal>LINEAR KEY</literal>
+ schemes. This feature is also available for many other MySQL
+ storage engines, which support additional partitioning types
+ that are not available with <literal>NDB Cluster</literal>
+ tables.
</para>
<para>
@@ -19535,8 +19534,34 @@
<xref linkend="partitioning-pruning"/>.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Autodiscovery of table schema
+ changes</emphasis>. In MySQL 5.1, you no longer need to
+ issue <literal>FLUSH TABLES</literal> or a
+ <quote>dummy</quote> <literal>SELECT</literal> in order for
+ new <literal>NDB</literal> tables or changes made to schemas of
+ existing <literal>NDB</literal> tables on one SQL node to be
+ visible on the cluster's other SQL nodes.
+ </para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: When creating a new
+ database, it is still necessary to issue the <literal>CREATE
+ DATABASE</literal> or <literal>CREATE SCHEMA</literal>
+ statement on each SQL node in the cluster.
+ </para>
+ </listitem>
- </orderedlist>
+ </itemizedlist>
+
+ <para>
+ See
+ <link linkend="mysql-cluster-limitations-resolved-in-5-1"><citetitle>MySQL
+ Cluster issues from previous versions that have been resolved in
+ MySQL 5.1</citetitle></link> for more information.
+ </para>
<remark role="todo">
[js] Update in view of varsize changes and uncomment again.
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-02-01 14:29:05 UTC (rev 4731)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-02-01 14:33:07 UTC (rev 4732)
Changed blocks: 4, Lines Added: 49, Lines Deleted: 24; 5316 bytes
@@ -19190,7 +19190,7 @@
<secondary>resolved in current version from previous versions</secondary>
</indexterm>
- <para>
+ <para id="mysql-cluster-limitations-resolved-in-5-1">
<emphasis role="bold">MySQL Cluster issues from previous
versions that have been resolved in MySQL 5.1</emphasis>:
</para>
@@ -19393,42 +19393,42 @@
<primary>MySQL Cluster</primary>
<secondary>features new in MySQL 5.1</secondary>
</indexterm>
-
+
<para>
- Four major new features for MySQL Cluster have been developed
- for MySQL 5.1:
+ A number of new features for MySQL Cluster have been implemented
+ in MySQL 5.1:
</para>
-
- <orderedlist>
-
+
+ <itemizedlist>
+
<listitem>
<para>
<emphasis role="bold">Integration of MySQL Cluster into
- MySQL replication</emphasis>: This makes it possible to
+ MySQL replication</emphasis>: This makes it possible to
update from any MySQL Server in the cluster and still have
the MySQL Replication handled by one of the MySQL Servers in
the cluster, with the state of the slave side remaining
consistent with the cluster acting as the master.
</para>
-
+
<para>
See <xref linkend="mysql-cluster-replication"/>.
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Support for disk-based
- records</emphasis>: Records on disk are now supported.
+ records</emphasis>: Records on disk are now supported.
Indexed fields including the primary key hash index must
still be stored in RAM but all other fields can be on disk.
</para>
-
+
<para>
See <xref linkend="mysql-cluster-disk-data"/>.
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Variable-sized records</emphasis>: A
@@ -19441,28 +19441,27 @@
cases.
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">User-defined partitioning</emphasis>:
Users can define partitions based on columns that are part
of the primary key. It is possible to partition
<literal>NDB</literal> tables based on
- <literal>KEY</literal>, <literal>HASH</literal>,
- <literal>LINEAR KEY</literal>, and <literal>LINEAR
- HASH</literal> schemes. This feature is also available for
- most other MySQL storage engines, which support additional
- partitioning types that are not available to <literal>NDB
- Cluster</literal> tables.
+ <literal>KEY</literal> and <literal>LINEAR KEY</literal>
+ schemes. This feature is also available for many other MySQL
+ storage engines, which support additional partitioning types
+ that are not available with <literal>NDB Cluster</literal>
+ tables.
</para>
-
+
<para>
For additional general information about user-defined
partitioning in MySQL ¤t-series;, see
<xref linkend="partitioning"/>. Specifics of partitioning
types are discussed in <xref linkend="partitioning-types"/>.
</para>
-
+
<para>
The MySQL Server can also determine whether it is possible
to <quote>prune away</quote> some of the partitions from the
@@ -19470,9 +19469,35 @@
<xref linkend="partitioning-pruning"/>.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Autodiscovery of table schema
+ changes</emphasis>. In MySQL 5.1, you no longer need to
+ issue <literal>FLUSH TABLES</literal> or a
+ <quote>dummy</quote> <literal>SELECT</literal> in order for
+ new <literal>NDB</literal> tables or changes made to schemas of
+ existing <literal>NDB</literal> tables on one SQL node to be
+ visible on the cluster's other SQL nodes.
+ </para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: When creating a new
+ database, it is still necessary to issue the <literal>CREATE
+ DATABASE</literal> or <literal>CREATE SCHEMA</literal>
+ statement on each SQL node in the cluster.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ See
+ <link linkend="mysql-cluster-limitations-resolved-in-5-1"><citetitle>MySQL
+ Cluster issues from previous versions that have been resolved in
+ MySQL 5.1</citetitle></link> for more information.
+ </para>
- </orderedlist>
-
<remark role="todo">
[js] Update in view of varsize changes and uncomment again.
</remark>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4732 - branches/telcos/refman-5.1 trunk/refman-5.1 | jon | 1 Feb |
