Author: paul
Date: 2006-03-15 15:57:59 +0100 (Wed, 15 Mar 2006)
New Revision: 1588
Log:
r8693@frost: paul | 2006-03-15 08:55:09 -0600
Document bugfixes:
Bug#15949
Bug#16266
Bug#16853
Bug#16887
Modified:
trunk/
trunk/refman-5.0/replication.xml
trunk/refman-5.1/client-utility-programs.xml
trunk/refman-5.1/problems.xml
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:8681
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3907
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:8693
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3907
Modified: trunk/refman-5.0/replication.xml
===================================================================
--- trunk/refman-5.0/replication.xml 2006-03-15 14:49:25 UTC (rev 1587)
+++ trunk/refman-5.0/replication.xml 2006-03-15 14:57:59 UTC (rev 1588)
@@ -1591,12 +1591,13 @@
which access privileges to check at trigger invocation time.
(See <xref linkend="create-trigger"/>, for more information.)
However, if you attempt to replicate from a master server
- older than MySQL 5.0.17 to a slave running MySQL 5.0.17 or up,
- replication of <literal>CREATE TRIGGER</literal> statements
- fails on the slave with a <literal>Definer not fully
- qualified</literal> error. A workaround is to create triggers
- on the master using a version-specific comment embedded in
- each <literal>CREATE TRIGGER</literal> statement:
+ older than MySQL 5.0.17 to a slave running MySQL 5.0.17
+ through 5.0.19, replication of <literal>CREATE
+ TRIGGER</literal> statements fails on the slave with a
+ <literal>Definer not fully qualified</literal> error. A
+ workaround is to create triggers on the master using a
+ version-specific comment embedded in each <literal>CREATE
+ TRIGGER</literal> statement:
</para>
<programlisting>
@@ -1609,6 +1610,10 @@
<literal>DEFINER</literal> clause from the comment and execute
successfully.
</para>
+
+ <para>
+ This slave problem is fixed as of MySQL 5.0.20.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/client-utility-programs.xml
===================================================================
--- trunk/refman-5.1/client-utility-programs.xml 2006-03-15 14:49:25 UTC (rev 1587)
+++ trunk/refman-5.1/client-utility-programs.xml 2006-03-15 14:57:59 UTC (rev 1588)
@@ -9578,6 +9578,27 @@
<para>
<indexterm>
<primary>mysqldump</primary>
+ <secondary>events option</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>events option</primary>
+ <secondary>mysqldump</secondary>
+ </indexterm>
+
+ <option>--events</option>, <option>-E</option>
+ </para>
+
+ <para>
+ Dump events from the dumped databases. This option was
+ added in MySQL 5.1.8.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <indexterm>
+ <primary>mysqldump</primary>
<secondary>extended-insert option</secondary>
</indexterm>
Modified: trunk/refman-5.1/problems.xml
===================================================================
--- trunk/refman-5.1/problems.xml 2006-03-15 14:49:25 UTC (rev 1587)
+++ trunk/refman-5.1/problems.xml 2006-03-15 14:57:59 UTC (rev 1588)
@@ -4498,6 +4498,8 @@
</para>
</listitem>
+<!-- next one is fixed in 5.1.8 -->
+
<listitem>
<para>
Cursors in stored routines can cause a server crash. (Bug
@@ -4580,6 +4582,8 @@
</para>
</listitem>
+<!-- next one is fixed in 5.1.8 -->
+
<listitem>
<para>
<command>mysqldump</command> does not dump events. (Bug
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-03-15 14:49:25 UTC (rev 1587)
+++ trunk/refman-common/news-4.1.xml 2006-03-15 14:57:59 UTC (rev 1588)
@@ -193,6 +193,14 @@
<listitem>
<para>
+ Character set conversion of string constants for
+ <literal>UNION</literal> of constant and table column was not
+ done when it was safe to do so. (Bug #15949)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Use of <literal>TRUNCATE TABLE</literal> for a
<literal>TEMPORARY</literal> table on a master server was
propagated to slaves properly, but slaves did not decrement
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-03-15 14:49:25 UTC (rev 1587)
+++ trunk/refman-common/news-5.0.xml 2006-03-15 14:57:59 UTC (rev 1588)
@@ -221,6 +221,24 @@
<listitem>
<para>
+ Replication slaves could not replicate triggers from older
+ servers that included no <literal>DEFINER</literal> clause in
+ the trigger definition. Now the trigger executes with the
+ privileges of the invoker (which on the slave is the slave SQL
+ thread). (Bug #16266)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Character set conversion of string constants for
+ <literal>UNION</literal> of constant and table column was not
+ done when it was safe to do so. (Bug #15949)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <literal>DEFINER</literal> value for stored routines was
not replicated. (Bug #15963)
</para>
@@ -605,6 +623,13 @@
<listitem>
<para>
+ Cursors in stored routines could cause a server crash. (Bug
+ #16887)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Setting the <literal>myisam_repair_threads</literal> system
variable to a value larger than 1 could cause corruption of
large <literal>MyISAM</literal> tables. (Bug #11527)
@@ -1946,7 +1971,7 @@
<para>
<emphasis role="bold">Known issue</emphasis>: If you attempt
to replicate from a master server older than MySQL 5.0.17 to a
- slave running MySQL 5.0.17 or up, replication of
+ slave running MySQL 5.0.17 through 5.0.19, replication of
<literal>CREATE TRIGGER</literal> statements fails on the
slave with a <literal>Definer not fully qualified</literal>
error. A workaround is to create triggers on the master using
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-03-15 14:49:25 UTC (rev 1587)
+++ trunk/refman-common/news-5.1.xml 2006-03-15 14:57:59 UTC (rev 1588)
@@ -61,10 +61,11 @@
</para>
-->
-<!--
<para>
Functionality added or changed:
</para>
+
+<!--
<itemizedlist>
<listitem>
<para></para>
@@ -76,17 +77,13 @@
Bugs fixed:
</para>
+<!--
<itemizedlist>
-
<listitem>
- <para>
- <literal>NULL</literal> values were written to the
- <literal>mysql.slow_log</literal> table incorrectly. (Bug
- #17600)
- </para>
+ <para></para>
</listitem>
-
</itemizedlist>
+-->
</section>
@@ -217,6 +214,14 @@
<listitem>
<para>
+ Added the <option>--events</option> option to
+ <command>mysqldump</command> to enable events to be included
+ in the dump output. (Bug #16853)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal> (Disk Data): You can now have
only one logfile group at any one time. See
<xref linkend="create-logfile-group"/>. (Bug #16386)
@@ -422,35 +427,70 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
- A query with a <literal>WHERE <replaceable>date_column</replaceable>
- > <replaceable>date_value</replaceable></literal> condition
- failed on a table partitioned by <literal>RANGE</literal>. (Bug
- #17894)
+ Cursors in stored routines could cause a server crash. (Bug
+ #16887)
</para>
</listitem>
-
+
<listitem>
<para>
- A failed <literal>ALTER TABLE ... ADD PRIMARY KEY</literal> on a
- partitioned table would result in bad table metadata and could
- possibly crash the server. (Bug #17097)
+ Replication slaves could not replicate triggers from older
+ servers that included no <literal>DEFINER</literal> clause in
+ the trigger definition. Now the trigger executes with the
+ privileges of the invoker (which on the slave is the slave SQL
+ thread). (Bug #16266)
</para>
</listitem>
-
+
<listitem>
<para>
+ Character set conversion of string constants for
+ <literal>UNION</literal> of constant and table column was not
+ done when it was safe to do so. (Bug #15949)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NULL</literal> values were written to the
+ <literal>mysql.slow_log</literal> table incorrectly. (Bug
+ #17600)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A query with a <literal>WHERE
+ <replaceable>date_column</replaceable> >
+ <replaceable>date_value</replaceable></literal> condition
+ failed on a table partitioned by <literal>RANGE</literal>.
+ (Bug #17894)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A failed <literal>ALTER TABLE ... ADD PRIMARY KEY</literal> on
+ a partitioned table would result in bad table metadata and
+ could possibly crash the server. (Bug #17097)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
No error was reported when subpartitions were defined for a
non-subpartitioned table. (Bug #15961)
</para>
</listitem>
-
+
<listitem>
<para>
- Searches on indexed columns of partitioned tables failed to find all
- matching rows following updates of the indexed columns. (Bug #14526)
+ Searches on indexed columns of partitioned tables failed to
+ find all matching rows following updates of the indexed
+ columns. (Bug #14526)
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1588 - in trunk: . refman-5.0 refman-5.1 refman-common | paul | 15 Mar |
