Author: jstephens
Date: 2007-03-28 12:36:28 +0200 (Wed, 28 Mar 2007)
New Revision: 5599
Log:
Reformat.
Modified:
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-03-28 10:35:40 UTC (rev 5598)
+++ trunk/refman-5.1/news-5.1.xml 2007-03-28 10:36:28 UTC (rev 5599)
Changed blocks: 3, Lines Added: 8, Lines Deleted: 8; 2096 bytes
@@ -351,7 +351,7 @@
<literal>ENDS NOW()</literal>, or both. (Bug #26429)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: After putting the cluster in
@@ -360,16 +360,16 @@
would cause the second MySQL server to hang. (Bug #27254)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Cluster APIs): You can now use
the <literal>ndb_mgm_check_connection()</literal> function to
- determine whether a management server is running. See
+ determine whether a management server is running. See
<xref linkend="ndb-mgm-check-connection"/>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: <command>mysqld</command>
@@ -377,22 +377,22 @@
certain DML operations. (Bug #27169)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The management client command
<literal><replaceable>node_id</replaceable> STATUS</literal>
displayed the message <literal>Node
- <replaceable>node_id</replaceable>: not connected</literal>
+ <replaceable>node_id</replaceable>: not connected</literal>
when <replaceable>node_id</replaceable> was not the node ID of
a data node. (Bug #21715)
</para>
-
+
<note>
<para>
The <literal>ALL STATUS</literal> command in the cluster
management client still displays status information for data
- nodes only. This is by design. See
+ nodes only. This is by design. See
<xref linkend="mysql-cluster-mgm-client-commands"/>, for
more information.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5599 - trunk/refman-5.1 | jon | 28 Mar |
