Author: mcbrown
Date: 2007-03-09 16:08:01 +0100 (Fri, 09 Mar 2007)
New Revision: 5279
Log:
Dev Bugs: #26616, #25507, #25628, #25463, #25306, #25167, #20141, #14194, #21490
Modified:
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-09 14:55:10 UTC (rev 5278)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-09 15:08:01 UTC (rev 5279)
Changed blocks: 1, Lines Added: 42, Lines Deleted: 0; 1828 bytes
@@ -143,6 +143,48 @@
<listitem>
<para>
+ A multi-row delayed insert with an auto increment column could
+ cause duplicate entries to be created on the slave in a
+ replication environment. (Bug #25507, #26116)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Duplicating the usage of a user variable in a stored procedure
+ or trigger would not be replicated correctly to the slave.
+ (Bug #25167)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ User defined variables used within stored procedures and
+ triggers are not replicated correctly when operating in
+ statement-based replication mode. (Bug #20141, Bug #14914)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Loading data using <literal>LOAD DATA INFILE</literal> may not
+ replicate correctly (due to character set incompatibilities)
+ if the <literal>character_set_database</literal> variable is
+ set before the data is loaded. (Bug #15126)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DROP TRIGGER</literal> statements would not be
+ filtered on the slave when using the
+ <literal>replication-wild-do-table</literal> option. (Bug
+ #24478)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
MySQL would not compile when configured using
<option>--without-query-cache</option>. (Bug #25075)
</para>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-03-09 14:55:10 UTC (rev 5278)
+++ trunk/refman-5.1/news-5.1.xml 2007-03-09 15:08:01 UTC (rev 5279)
Changed blocks: 2, Lines Added: 134, Lines Deleted: 6; 4286 bytes
@@ -73,19 +73,97 @@
additions to document.
</remark>
-<!--
<para>
Functionality added or changed:
</para>
-
+
<itemizedlist>
-
+
<listitem>
- <para></para>
+ <para>
+ <emphasis role="bold">Important change:</emphasis> The
+ following options for controlling replication master
+ configuration on a slave are now deprecated.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal> --master-host</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-user</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-password </literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-port</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-connect-retry</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-ssl</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-ssl-ca</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-ssl-capath</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-ssl-cert</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-ssl-cipher</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal> --master-ssl-key</literal>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ To change the master configuration on a slave you should use
+ the <literal>CHANGE MASTER</literal> statement. (See also
+ #21490)
+ </para>
</listitem>
-
+
</itemizedlist>
--->
<para>
Bugs fixed:
@@ -134,6 +212,56 @@
<listitem>
<para>
+ A multi-row delayed insert with an auto increment column could
+ cause duplicate entries to be created on the slave in a
+ replication environment. (Bug #25507, #26116)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <command>mysqlbinlog</command> on a binary log would
+ crash if there were a large number of row-based events related
+ to a single statement. (Bug #25628)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Duplicating the usage of a user variable in a stored procedure
+ or trigger would not be replicated correctly to the slave.
+ (Bug #25167)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ User defined variables used within stored procedures and
+ triggers are not replicated correctly when operating in
+ statement-based replication mode. (Bug #20141, Bug #14914)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Loading data using <literal>LOAD DATA INFILE</literal> may not
+ replicate correctly (due to character set incompatibilities)
+ if the <literal>character_set_database</literal> variable is
+ set before the data is loaded. (Bug #15126)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DROP TRIGGER</literal> statements would not be
+ filtered on the slave when using the
+ <literal>replication-wild-do-table</literal> option. (Bug
+ #24478)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>SHOW ENGINE MUTEX STATUS</literal> failed to produce
an <errortext>Unknown table engine</errortext> error. (Bug
#24392)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5279 - in trunk: refman-5.0 refman-5.1 | mcbrown | 9 Mar |