Author: jstephens
Date: 2007-03-24 03:28:47 +0100 (Sat, 24 Mar 2007)
New Revision: 5544
Log:
Documenting fix for Bug #24363 -> new behaviour/--skip-table-check
option for ndb_restore
Modified:
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-03-23 21:59:46 UTC (rev 5543)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-03-24 02:28:47 UTC (rev 5544)
Changed blocks: 3, Lines Added: 31, Lines Deleted: 2; 2998 bytes
@@ -13285,7 +13285,7 @@
</para>
<programlisting>
-ndb_restore [-c <replaceable>connectstring</replaceable>] -n <replaceable>node_id</replaceable> [-m] -b <replaceable>backup_id</replaceable> -r <replaceable>/path/to/backup/files</replaceable>
+ndb_restore [-c <replaceable>connectstring</replaceable>] -n <replaceable>node_id</replaceable> [-s] [-m] -b <replaceable>backup_id</replaceable> -r <replaceable>/path/to/backup/files</replaceable>
</programlisting>
<para>
@@ -13338,8 +13338,30 @@
restore. You should also remove manually any Disk Data files
present in the data node's <literal>DataDir</literal>.)
</para>
-
+
<para>
+ It is possible to restore data without restoring table
+ metadata. Prior to MySQL 5.1.17,
+ <command>ndb_restore</command> did not perform any checks of
+ table schemas; if a table was altered between the time the
+ backup was taken and when <command>ndb_restore</command> was
+ run, <command>ndb_restore</command> would still attempt to
+ restore the data to the altered table.
+ </para>
+
+ <para>Beginning with MySQL 5.1.17, the default behavior is for
+ <command>ndb_restore</command> is to fail with an error if
+ table data do not match the table schema; this can be
+ overridden using the <option>--skip-table-check</option> or
+ <option>-s</option> option. If this option is used, then
+ <command>ndb_restore</command> attempts to fit data into the
+ existing table schema. <emphasis>The result of restoring a
+ backup to a table schema that does not match the original
+ is unspecified and is subject to change without
+ notice</emphasis>. (Bug #24363)
+ </para>
+
+ <para>
The <option>-b</option> option is used to specify the ID or
sequence number of the backup, and is the same number shown
by the management client in the <literal>Backup
@@ -13563,6 +13585,13 @@
<entry><literal>FALSE</literal></entry>
</row>
<row>
+ <entry><option>--skip-table-check</option></entry>
+ <entry><option>-s</option></entry>
+ <entry>Do not check table schemas (Added in MySQL
+ 5.1.17)</entry>
+ <entry><literal>FALSE</literal></entry>
+ </row>
+ <row>
<entry><option>--version</option></entry>
<entry><option>-V</option></entry>
<entry>Output version information and exit</entry>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-03-23 21:59:46 UTC (rev 5543)
+++ trunk/refman-5.1/news-5.1.xml 2007-03-24 02:28:47 UTC (rev 5544)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 0; 985 bytes
@@ -215,6 +215,22 @@
<xref linkend="innodb-parameters"/>. (Bug #26598)
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Added the
+ <option>--skip-table-check</option> option (short form
+ <option>-s</option>) for <command>ndb_restore</command>, which
+ causes the restoration process to ignore any changes that may
+ have occurred in table schemas after the backup was made.
+ Previously, this was the default behavior. (Bug #24363)
+ </para>
+
+ <para>
+ See <xref linkend="mysql-cluster-restore"/>, for more
+ information.
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5544 - trunk/refman-5.1 | jon | 24 Mar |
