Author: shinz
Date: 2006-09-04 17:19:58 +0200 (Mon, 04 Sep 2006)
New Revision: 3212
Log:
Add more detailed information about the removal of LOAD DATA/TABLE FROM MASTER to the respective statements, and name alternatives ( thanks, Guilhem and Trudy! )
Modified:
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/sql-syntax.xml
trunk/refman-5.1/sql-syntax.xml
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2006-09-04 14:07:36 UTC (rev 3211)
+++ trunk/refman-4.1/sql-syntax.xml 2006-09-04 15:19:58 UTC (rev 3212)
Changed blocks: 2, Lines Added: 46, Lines Deleted: 4; 3777 bytes
@@ -18363,11 +18363,32 @@
&deprecated-feature-warning;
<para>
- A feature similar to this functionality will be implemented
- with online backup in a future MySQL version.
+ Since the current implementation of <literal>LOAD DATA FROM
+ MASTER</literal> and <literal>LOAD TABLE FROM MASTER</literal>
+ is very limited, these statements are deprecated in versions
+ 4.1 of MySQL and above. We will introduce a more advanced
+ technique (called <quote>online backup</quote>) in a future
+ version. That technique will have the additional advantage of
+ working with more storage engines.
</para>
<para>
+ For MySQL 5.1 and earlier, the recommended alternative
+ solution to using <literal>LOAD DATA FROM MASTER</literal> or
+ <literal>LOAD TABLE FROM MASTER</literal>is using
+ <command>mysqldump</command> or
+ <command>mysqlhotcopy</command>. The latter requires Perl and
+ two Perl modules (<literal>DBI</literal> and
+ <literal>DBD:mysql</literal>) and works for
+ <literal>MyISAM</literal> and <literal>ARCHIVE</literal>
+ tables only. With <command>mysqldump</command>, you can create
+ SQL dumps on the master and pipe (or copy) these to a
+ <command>mysql</command> client on the slave. This has the
+ advantage of working for all storage engines, but can be quite
+ slow, since it works using <literal>SELECT</literal>.
+ </para>
+
+ <para>
This statement takes a snapshot of the master and copies it to
the slave. It updates the values of
<literal>MASTER_LOG_FILE</literal> and
@@ -18487,11 +18508,32 @@
&deprecated-feature-warning;
<para>
- A feature similar to this functionality will be implemented
- with online backup in a future MySQL version.
+ Since the current implementation of <literal>LOAD DATA FROM
+ MASTER</literal> and <literal>LOAD TABLE FROM MASTER</literal>
+ is very limited, these statements are deprecated in versions
+ 4.1 of MySQL and above. We will introduce a more advanced
+ technique (called <quote>online backup</quote>) in a future
+ version. That technique will have the additional advantage of
+ working with more storage engines.
</para>
<para>
+ For MySQL 5.1 and earlier, the recommended alternative
+ solution to using <literal>LOAD DATA FROM MASTER</literal> or
+ <literal>LOAD TABLE FROM MASTER</literal>is using
+ <command>mysqldump</command> or
+ <command>mysqlhotcopy</command>. The latter requires Perl and
+ two Perl modules (<literal>DBI</literal> and
+ <literal>DBD:mysql</literal>) and works for
+ <literal>MyISAM</literal> and <literal>ARCHIVE</literal>
+ tables only. With <command>mysqldump</command>, you can create
+ SQL dumps on the master and pipe (or copy) these to a
+ <command>mysql</command> client on the slave. This has the
+ advantage of working for all storage engines, but can be quite
+ slow, since it works using <literal>SELECT</literal>.
+ </para>
+
+ <para>
Transfers a copy of the table from the master to the slave.
This statement is implemented mainly debugging <literal>LOAD
DATA FROM MASTER</literal> operations. To use <literal>LOAD
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2006-09-04 14:07:36 UTC (rev 3211)
+++ trunk/refman-5.0/sql-syntax.xml 2006-09-04 15:19:58 UTC (rev 3212)
Changed blocks: 2, Lines Added: 48, Lines Deleted: 6; 3815 bytes
@@ -20419,11 +20419,32 @@
&deprecated-feature-warning;
<para>
- A feature similar to this functionality will be implemented
- with online backup in a future MySQL version.
+ Since the current implementation of <literal>LOAD DATA FROM
+ MASTER</literal> and <literal>LOAD TABLE FROM MASTER</literal>
+ is very limited, these statements are deprecated in versions
+ 4.1 of MySQL and above. We will introduce a more advanced
+ technique (called <quote>online backup</quote>) in a future
+ version. That technique will have the additional advantage of
+ working with more storage engines.
</para>
-
+
<para>
+ For MySQL 5.1 and earlier, the recommended alternative
+ solution to using <literal>LOAD DATA FROM MASTER</literal> or
+ <literal>LOAD TABLE FROM MASTER</literal>is using
+ <command>mysqldump</command> or
+ <command>mysqlhotcopy</command>. The latter requires Perl and
+ two Perl modules (<literal>DBI</literal> and
+ <literal>DBD:mysql</literal>) and works for
+ <literal>MyISAM</literal> and <literal>ARCHIVE</literal>
+ tables only. With <command>mysqldump</command>, you can create
+ SQL dumps on the master and pipe (or copy) these to a
+ <command>mysql</command> client on the slave. This has the
+ advantage of working for all storage engines, but can be quite
+ slow, since it works using <literal>SELECT</literal>.
+ </para>
+
+ <para>
This statement takes a snapshot of the master and copies it to
the slave. It updates the values of
<literal>MASTER_LOG_FILE</literal> and
@@ -20543,11 +20564,32 @@
&deprecated-feature-warning;
<para>
- A feature similar to this functionality will be implemented
- with online backup in a future MySQL version.
+ Since the current implementation of <literal>LOAD DATA FROM
+ MASTER</literal> and <literal>LOAD TABLE FROM MASTER</literal>
+ is very limited, these statements are deprecated in versions
+ 4.1 of MySQL and above. We will introduce a more advanced
+ technique (called <quote>online backup</quote>) in a future
+ version. That technique will have the additional advantage of
+ working with more storage engines.
</para>
-
+
<para>
+ For MySQL 5.1 and earlier, the recommended alternative
+ solution to using <literal>LOAD DATA FROM MASTER</literal> or
+ <literal>LOAD TABLE FROM MASTER</literal>is using
+ <command>mysqldump</command> or
+ <command>mysqlhotcopy</command>. The latter requires Perl and
+ two Perl modules (<literal>DBI</literal> and
+ <literal>DBD:mysql</literal>) and works for
+ <literal>MyISAM</literal> and <literal>ARCHIVE</literal>
+ tables only. With <command>mysqldump</command>, you can create
+ SQL dumps on the master and pipe (or copy) these to a
+ <command>mysql</command> client on the slave. This has the
+ advantage of working for all storage engines, but can be quite
+ slow, since it works using <literal>SELECT</literal>.
+ </para>
+
+ <para>
Transfers a copy of the table from the master to the slave.
This statement is implemented mainly debugging <literal>LOAD
DATA FROM MASTER</literal> operations. To use <literal>LOAD
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-09-04 14:07:36 UTC (rev 3211)
+++ trunk/refman-5.1/sql-syntax.xml 2006-09-04 15:19:58 UTC (rev 3212)
Changed blocks: 2, Lines Added: 48, Lines Deleted: 6; 3815 bytes
@@ -21978,11 +21978,32 @@
&deprecated-feature-warning;
<para>
- A feature similar to this functionality will be implemented
- with online backup in a future MySQL version.
+ Since the current implementation of <literal>LOAD DATA FROM
+ MASTER</literal> and <literal>LOAD TABLE FROM MASTER</literal>
+ is very limited, these statements are deprecated in versions
+ 4.1 of MySQL and above. We will introduce a more advanced
+ technique (called <quote>online backup</quote>) in a future
+ version. That technique will have the additional advantage of
+ working with more storage engines.
</para>
-
+
<para>
+ For MySQL 5.1 and earlier, the recommended alternative
+ solution to using <literal>LOAD DATA FROM MASTER</literal> or
+ <literal>LOAD TABLE FROM MASTER</literal>is using
+ <command>mysqldump</command> or
+ <command>mysqlhotcopy</command>. The latter requires Perl and
+ two Perl modules (<literal>DBI</literal> and
+ <literal>DBD:mysql</literal>) and works for
+ <literal>MyISAM</literal> and <literal>ARCHIVE</literal>
+ tables only. With <command>mysqldump</command>, you can create
+ SQL dumps on the master and pipe (or copy) these to a
+ <command>mysql</command> client on the slave. This has the
+ advantage of working for all storage engines, but can be quite
+ slow, since it works using <literal>SELECT</literal>.
+ </para>
+
+ <para>
This statement takes a snapshot of the master and copies it to
the slave. It updates the values of
<literal>MASTER_LOG_FILE</literal> and
@@ -22102,11 +22123,32 @@
&deprecated-feature-warning;
<para>
- A feature similar to this functionality will be implemented
- with online backup in a future MySQL version.
+ Since the current implementation of <literal>LOAD DATA FROM
+ MASTER</literal> and <literal>LOAD TABLE FROM MASTER</literal>
+ is very limited, these statements are deprecated in versions
+ 4.1 of MySQL and above. We will introduce a more advanced
+ technique (called <quote>online backup</quote>) in a future
+ version. That technique will have the additional advantage of
+ working with more storage engines.
</para>
-
+
<para>
+ For MySQL 5.1 and earlier, the recommended alternative
+ solution to using <literal>LOAD DATA FROM MASTER</literal> or
+ <literal>LOAD TABLE FROM MASTER</literal>is using
+ <command>mysqldump</command> or
+ <command>mysqlhotcopy</command>. The latter requires Perl and
+ two Perl modules (<literal>DBI</literal> and
+ <literal>DBD:mysql</literal>) and works for
+ <literal>MyISAM</literal> and <literal>ARCHIVE</literal>
+ tables only. With <command>mysqldump</command>, you can create
+ SQL dumps on the master and pipe (or copy) these to a
+ <command>mysql</command> client on the slave. This has the
+ advantage of working for all storage engines, but can be quite
+ slow, since it works using <literal>SELECT</literal>.
+ </para>
+
+ <para>
Transfers a copy of the table from the master to the slave.
This statement is implemented mainly debugging <literal>LOAD
DATA FROM MASTER</literal> operations. To use <literal>LOAD
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3212 - in trunk: refman-4.1 refman-5.0 refman-5.1 | stefan | 4 Sep |
