Author: jstephens
Date: 2007-04-10 15:23:09 +0200 (Tue, 10 Apr 2007)
New Revision: 5800
Log:
Reformat.
Modified:
trunk/refman-4.1/mysql-cluster.xml
trunk/refman-5.0/mysql-cluster.xml
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml 2007-04-10 13:20:40 UTC (rev 5799)
+++ trunk/refman-4.1/mysql-cluster.xml 2007-04-10 13:23:09 UTC (rev 5800)
Changed blocks: 2, Lines Added: 7, Lines Deleted: 7; 1865 bytes
@@ -8930,7 +8930,7 @@
State: Waiting for event from ndbcluster
Info: NULL
</programlisting>
-
+
<important>
<para>
To participate in a MySQL Cluster, the
@@ -8938,15 +8938,15 @@
<emphasis>both</emphasis> the options
<option>--ndbcluster</option> and
<option>--ndb-connectstring</option> (or their equivalents in
- <filename>my.cnf</filename>). If <command>mysqld</command> is
+ <filename>my.cnf</filename>). If <command>mysqld</command> is
started with only the <option>--ndbcluster</option> option, or
if it is unable to contact the cluster, it is not possible to
work with <literal>NDB</literal> tables, <emphasis>nor is it
- possible to create any new tables regardless of storage
- engine</emphasis>. The latter restriction is a safety
- measure intended to prevent the creation of tables having the
- same names as <literal>NDB</literal> tables while the SQL node
- is not connected to the cluster. If you wish to create tables
+ possible to create any new tables regardless of storage
+ engine</emphasis>. The latter restriction is a safety measure
+ intended to prevent the creation of tables having the same
+ names as <literal>NDB</literal> tables while the SQL node is
+ not connected to the cluster. If you wish to create tables
using a different storage engine while the
<command>mysqld</command> process is not participating in a
MySQL Cluster, you must restart the server
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2007-04-10 13:20:40 UTC (rev 5799)
+++ trunk/refman-5.0/mysql-cluster.xml 2007-04-10 13:23:09 UTC (rev 5800)
Changed blocks: 3, Lines Added: 9, Lines Deleted: 9; 2505 bytes
@@ -8953,7 +8953,7 @@
State: Waiting for event from ndbcluster
Info: NULL
</programlisting>
-
+
<important>
<para>
To participate in a MySQL Cluster, the
@@ -8961,15 +8961,15 @@
<emphasis>both</emphasis> the options
<option>--ndbcluster</option> and
<option>--ndb-connectstring</option> (or their equivalents in
- <filename>my.cnf</filename>). If <command>mysqld</command> is
+ <filename>my.cnf</filename>). If <command>mysqld</command> is
started with only the <option>--ndbcluster</option> option, or
if it is unable to contact the cluster, it is not possible to
work with <literal>NDB</literal> tables, <emphasis>nor is it
- possible to create any new tables regardless of storage
- engine</emphasis>. The latter restriction is a safety
- measure intended to prevent the creation of tables having the
- same names as <literal>NDB</literal> tables while the SQL node
- is not connected to the cluster. If you wish to create tables
+ possible to create any new tables regardless of storage
+ engine</emphasis>. The latter restriction is a safety measure
+ intended to prevent the creation of tables having the same
+ names as <literal>NDB</literal> tables while the SQL node is
+ not connected to the cluster. If you wish to create tables
using a different storage engine while the
<command>mysqld</command> process is not participating in a
MySQL Cluster, you must restart the server
@@ -13399,8 +13399,8 @@
<para>
Beginning with MySQL 5.0.40, it is possible to restore
- selected databases, or to restore selected tables from
- a given database using the syntax shown here:
+ selected databases, or to restore selected tables from a
+ given database using the syntax shown here:
<programlisting>
ndb_restore <replaceable>other_options</replaceable> <replaceable>db_name_1</replaceable> [<replaceable>db_name_2</replaceable>[, <replaceable>db_name_3</replaceable>][, ...] | <replaceable>tbl_name_1</replaceable>[, <replaceable>tbl_name_2</replaceable>][, ...]]
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-04-10 13:20:40 UTC (rev 5799)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-04-10 13:23:09 UTC (rev 5800)
Changed blocks: 4, Lines Added: 20, Lines Deleted: 19; 3620 bytes
@@ -123,7 +123,7 @@
privileges. (Bug #27337)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (APIs): Using
@@ -133,17 +133,17 @@
changed. (Bug #27018)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Under certain rare
circumstances, <literal>DROP TABLE</literal> or
<literal>TRUNCATE</literal> of an <literal>NDB</literal> table
could cause a node failure or forced cluster shutdown. (Bug
- #27581)
+ #27581)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Memory usage of a
@@ -151,26 +151,27 @@
#27560)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: In some cases, <literal>AFTER
- UPDATE</literal> and <literal>AFTER DELETE</literal>
- triggers on <literal>NDB</literal> tables that referenced
- subject table did not see the results of operation which
- caused invocation of the trigger, but rather saw the row as it
- was prior to the update or delete operation.
+ UPDATE</literal> and <literal>AFTER DELETE</literal> triggers
+ on <literal>NDB</literal> tables that referenced subject table
+ did not see the results of operation which caused invocation
+ of the trigger, but rather saw the row as it was prior to the
+ update or delete operation.
</para>
-
+
<para>
This was most noticeable when an update operation used a
subquery to obtain the rows to be updated. An example would be
<literal>UPDATE tbl1 SET col2 = val1 WHERE tbl1.col1 IN
- (SELECT col3 FROM tbl2 WHERE c4 = val2)</literal> where
- there was an <literal>AFTER UPDATE</literal> trigger on table
- <literal>tbl1</literal>. In such cases, the trigger would fail to
- execute.
+ (SELECT col3 FROM tbl2 WHERE c4 = val2)</literal> where there
+ was an <literal>AFTER UPDATE</literal> trigger on table
+ <literal>tbl1</literal>. In such cases, the trigger would fail
+ to execute.
</para>
+
<para>
The problem occurred because the actual update or delete
operations were deferred to be able to perform them later as
@@ -180,21 +181,21 @@
this operation. (Bug #26242)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Condition pushdown did not
work with prepared statements. (Bug #26225)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: When trying to create tables
on an SQL node not connected to the cluster, a misleading
error message <errortext>Table
- '<replaceable>tbl_name</replaceable>' already
- exists</errortext> was generated. The error now generated is
+ '<replaceable>tbl_name</replaceable>' already
+ exists</errortext> was generated. The error now generated is
<errortext>Could not connect to storage engine</errortext>.
(Bug #18676)
</para>
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-04-10 13:20:40 UTC (rev 5799)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-04-10 13:23:09 UTC (rev 5800)
Changed blocks: 7, Lines Added: 22, Lines Deleted: 23; 4293 bytes
@@ -9073,7 +9073,7 @@
State: Waiting for event from ndbcluster
Info: NULL
</programlisting>
-
+
<important>
<para>
To participate in a MySQL Cluster, the
@@ -9081,15 +9081,15 @@
<emphasis>both</emphasis> the options
<option>--ndbcluster</option> and
<option>--ndb-connectstring</option> (or their equivalents in
- <filename>my.cnf</filename>). If <command>mysqld</command> is
+ <filename>my.cnf</filename>). If <command>mysqld</command> is
started with only the <option>--ndbcluster</option> option, or
if it is unable to contact the cluster, it is not possible to
work with <literal>NDB</literal> tables, <emphasis>nor is it
- possible to create any new tables regardless of storage
- engine</emphasis>. The latter restriction is a safety
- measure intended to prevent the creation of tables having the
- same names as <literal>NDB</literal> tables while the SQL node
- is not connected to the cluster. If you wish to create tables
+ possible to create any new tables regardless of storage
+ engine</emphasis>. The latter restriction is a safety measure
+ intended to prevent the creation of tables having the same
+ names as <literal>NDB</literal> tables while the SQL node is
+ not connected to the cluster. If you wish to create tables
using a different storage engine while the
<command>mysqld</command> process is not participating in a
MySQL Cluster, you must restart the server
@@ -13462,8 +13462,6 @@
</para>
</note>
-
-
<para>
Most of the options available for this program are shown in
the following table:
@@ -13655,6 +13653,7 @@
</tbody>
</tgroup>
</informaltable>
+
<para>
Beginning with MySQL 5.1.18, several additional options are
available for use with the <option>--print_data</option>
@@ -13663,7 +13662,7 @@
to some of the options used with
<command>mysqldump</command>, and are shown in the following
table:
-
+
<informaltable>
<tgroup cols="4">
<colspec colwidth="25*"/>
@@ -13741,33 +13740,33 @@
the table's hidden primary key.
</para>
</note>
-
+
<para>
- Beginning with MySQL 5.1.18, it is possible to restore
- selected databases, or to restore selected tables from
- a given database using the syntax shown here:
-
- <programlisting>
+ Beginning with MySQL 5.1.18, it is possible to restore
+ selected databases, or to restore selected tables from a
+ given database using the syntax shown here:
+
+<programlisting>
ndb_restore <replaceable>other_options</replaceable> <replaceable>db_name_1</replaceable> [<replaceable>db_name_2</replaceable>[, <replaceable>db_name_3</replaceable>][, ...] | <replaceable>tbl_name_1</replaceable>[, <replaceable>tbl_name_2</replaceable>][, ...]]
</programlisting>
-
+
In other words, you can specify either of the following to
be restored:
-
+
<itemizedlist>
-
+
<listitem>
<para>
All tables from one or more databases
</para>
</listitem>
-
+
<listitem>
<para>
One or more tables from a single database
</para>
</listitem>
-
+
</itemizedlist>
</para>
@@ -17160,8 +17159,8 @@
<programlisting>
SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;
START SLAVE;
-</programlisting>
-
+</programlisting>
+
The slave then resumes reading the master binlog from the
point where the gap was recorded.
</para>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-04-10 13:20:40 UTC (rev 5799)
+++ trunk/refman-5.1/news-5.1.xml 2007-04-10 13:23:09 UTC (rev 5800)
Changed blocks: 11, Lines Added: 37, Lines Deleted: 36; 7096 bytes
@@ -96,7 +96,7 @@
<literal>old</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: It is now possible to restore
@@ -104,12 +104,12 @@
<command>ndb_restore</command>. (Bug #26899)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Several options have been
added for use with <command>ndb_restore
- <option>--print_data</option></command> to facilitate the
+ <option>--print_data</option></command> to facilitate the
creation of data dump files. (Bug #26900)
</para>
</listitem>
@@ -130,7 +130,7 @@
privileges. (Bug #27337)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (APIs): Using
@@ -140,35 +140,35 @@
changed. (Bug #27018)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Replication): Trying to
replicate a large number of frequent updates with a relatively
small relay log (<literal>max-relay-log-size</literal> set to
- 1M or less) could cause the slave to crash. (Bug #27529)
+ 1M or less) could cause the slave to crash. (Bug #27529)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Replication): An SQL node
acting as a replication master server could be a single point
of failure; that is, if it failed, the replication slave had
no way of knowing this, which could result in a mismatch of
- data between the master and the slave. (Bug #21494)
+ data between the master and the slave. (Bug #21494)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data): <literal>CREATE
- TABLE ... LIKE
- <replaceable>disk_data_table</replaceable></literal> created
+ TABLE ... LIKE
+ <replaceable>disk_data_table</replaceable></literal> created
an in-memory <literal>NDB</literal> table. (Bug #25875)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data): Creating an
@@ -176,17 +176,17 @@
data nodes to crash. (Bug #24521)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Under certain rare
circumstances, <literal>DROP TABLE</literal> or
<literal>TRUNCATE</literal> of an <literal>NDB</literal> table
could cause a node failure or forced cluster shutdown. (Bug
- #27581)
+ #27581)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Memory usage of a
@@ -194,7 +194,7 @@
#27560)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Using more than 16GB for
@@ -202,7 +202,7 @@
variable-size columns. (Bug #27512)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: In an <literal>NDB</literal>
@@ -212,7 +212,7 @@
row was updated. (Bug #27127)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Performing <literal>ALTER
@@ -220,33 +220,34 @@
table caused <command>mysqld</command> to crash. (Bug #26898)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The Cluster table handler did
not set bits in null bytes correctly. (Bug #26591)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: In some cases, <literal>AFTER
- UPDATE</literal> and <literal>AFTER DELETE</literal>
- triggers on <literal>NDB</literal> tables that referenced
- subject table did not see the results of operation which
- caused invocation of the trigger, but rather saw the row as it
- was prior to the update or delete operation.
+ UPDATE</literal> and <literal>AFTER DELETE</literal> triggers
+ on <literal>NDB</literal> tables that referenced subject table
+ did not see the results of operation which caused invocation
+ of the trigger, but rather saw the row as it was prior to the
+ update or delete operation.
</para>
-
+
<para>
This was most noticeable when an update operation used a
subquery to obtain the rows to be updated. An example would be
<literal>UPDATE tbl1 SET col2 = val1 WHERE tbl1.col1 IN
- (SELECT col3 FROM tbl2 WHERE c4 = val2)</literal> where
- there was an <literal>AFTER UPDATE</literal> trigger on table
- <literal>tbl1</literal>. In such cases, the trigger would fail to
- execute.
+ (SELECT col3 FROM tbl2 WHERE c4 = val2)</literal> where there
+ was an <literal>AFTER UPDATE</literal> trigger on table
+ <literal>tbl1</literal>. In such cases, the trigger would fail
+ to execute.
</para>
+
<para>
The problem occurred because the actual update or delete
operations were deferred to be able to perform them later as
@@ -256,24 +257,24 @@
this operation. (Bug #26242)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: <literal>START BACKUP
NOWAIT</literal> caused a spurious <errortext>Out of backup
record</errortext> error in the management client
(<literal>START BACKUP</literal> and <literal>START BACKUP
- WAIT STARTED</literal> performed normally). (Bug #25446)
+ WAIT STARTED</literal> performed normally). (Bug #25446)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: When trying to create tables
on an SQL node not connected to the cluster, a misleading
error message <errortext>Table
- '<replaceable>tbl_name</replaceable>' already
- exists</errortext> was generated. The error now generated is
+ '<replaceable>tbl_name</replaceable>' already
+ exists</errortext> was generated. The error now generated is
<errortext>Could not connect to storage engine</errortext>.
(Bug #18676)
</para>
@@ -2244,7 +2245,7 @@
problem.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Condition pushdown did not
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5800 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 10 Apr |
