Author: paul
Date: 2006-01-09 20:09:27 +0100 (Mon, 09 Jan 2006)
New Revision: 744
Log:
r6003@frost: paul | 2006-01-09 13:05:28 -0600
Clarify that SQL-level replication incompatibilities can occur
between point-releases, not just between series.
Modified:
trunk/
trunk/refman-4.1/replication.xml
trunk/refman-5.0/replication.xml
trunk/refman-5.1/replication.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6000
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6003
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994
Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml 2006-01-09 19:09:06 UTC (rev 743)
+++ trunk/refman-4.1/replication.xml 2006-01-09 19:09:27 UTC (rev 744)
@@ -1624,10 +1624,16 @@
<para>
In general, replication compatibility at the SQL level requires
that any features used be supported by both the master and the
- slave servers. For example, the <literal>GROUP_CONCAT()</literal>
- function is available in MySQL 4.1 and up. If you use this
- function on the master server, you cannot replicate to a slave
- server that is older than MySQL 4.1.
+ slave servers. If you use a feature on a master server that is
+ available only as of a given version of MySQL, you cannot
+ replicate to a slave that is older than that version. Such
+ incompatibilities are likely to occur between series, so that, for
+ example, you cannot replicate from MySQL ¤t-series; to
+ &previous-series;. However, these incompatibilities also can occur
+ for within-series replication. For example, the
+ <literal>CONVERT_TZ()</literal> function is available in MySQL
+ 4.1.3 and up. If you use this function on the master server, you
+ cannot replicate to a slave server that is older than MySQL 4.1.3.
</para>
<para>
Modified: trunk/refman-5.0/replication.xml
===================================================================
--- trunk/refman-5.0/replication.xml 2006-01-09 19:09:06 UTC (rev 743)
+++ trunk/refman-5.0/replication.xml 2006-01-09 19:09:27 UTC (rev 744)
@@ -1528,17 +1528,27 @@
<para>
In general, replication compatibility at the SQL level requires
that any features used be supported by both the master and the
- slave servers. For example, the <literal>TIMESTAMPADD()</literal>
- function was implemented in MySQL 5.0.0. If you use this function
- on the master server, you cannot replicate to a slave server that
- is older than MySQL 5.0.0. If you are planning to use replication
- between ¤t-series; and a previous version of MySQL you
- should consult the edition of the MySQL Reference Manual
- corresponding to the earlier release series for information
- regarding the replication characteristics of that series.
+ slave servers. If you use a feature on a master server that is
+ available only as of a given version of MySQL, you cannot
+ replicate to a slave that is older than that version. Such
+ incompatibilities are likely to occur between series, so that, for
+ example, you cannot replicate from MySQL ¤t-series; to
+ &previous-series;. However, these incompatibilities also can occur
+ for within-series replication. For example, the
+ <literal>SLEEP()</literal> function is available in MySQL 5.0.12
+ and up. If you use this function on the master server, you cannot
+ replicate to a slave server that is older than MySQL 5.0.12.
</para>
<para>
+ If you are planning to use replication between ¤t-series;
+ and a previous version of MySQL you should consult the edition of
+ the MySQL Reference Manual corresponding to the earlier release
+ series for information regarding the replication characteristics
+ of that series.
+ </para>
+
+ <para>
The following list provides details about what is supported and
what is not. Additional <literal>InnoDB</literal>-specific
information about replication is given in
Modified: trunk/refman-5.1/replication.xml
===================================================================
--- trunk/refman-5.1/replication.xml 2006-01-09 19:09:06 UTC (rev 743)
+++ trunk/refman-5.1/replication.xml 2006-01-09 19:09:27 UTC (rev 744)
@@ -1735,17 +1735,27 @@
<para>
In general, replication compatibility at the SQL level requires
that any features used be supported by both the master and the
- slave servers. For example, the <literal>TIMESTAMPADD()</literal>
- function was implemented in MySQL 5.0.0. If you use this function
- on the master server, you cannot replicate to a slave server that
- is older than MySQL 5.0.0. If you are planning to use replication
- between ¤t-series; and a previous version of MySQL you
- should consult the edition of the MySQL Reference Manual
- corresponding to the earlier release series for information
- regarding the replication characteristics of that series.
+ slave servers. If you use a feature on a master server that is
+ available only as of a given version of MySQL, you cannot
+ replicate to a slave that is older than that version. Such
+ incompatibilities are likely to occur between series, so that, for
+ example, you cannot replicate from MySQL ¤t-series; to
+ &previous-series;. However, these incompatibilities also can occur
+ for within-series replication. For example, the
+ <literal>SLEEP()</literal> function is available in MySQL 5.0.12
+ and up. If you use this function on the master server, you cannot
+ replicate to a slave server that is older than MySQL 5.0.12.
</para>
<para>
+ If you are planning to use replication between ¤t-series;
+ and a previous version of MySQL you should consult the edition of
+ the MySQL Reference Manual corresponding to the earlier release
+ series for information regarding the replication characteristics
+ of that series.
+ </para>
+
+ <para>
The following list provides details about what is supported and
what is not. Additional <literal>InnoDB</literal>-specific
information about replication is given in
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r744 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 9 Jan |
