Author: jstephens
Date: 2007-04-25 01:33:48 +0200 (Wed, 25 Apr 2007)
New Revision: 6171
Log:
Grab yesterday's changes to 5.1 changelog for merge file.
Modified:
trunk/refman-5.1/news-5.1-merged.xml
Modified: trunk/refman-5.1/news-5.1-merged.xml
===================================================================
--- trunk/refman-5.1/news-5.1-merged.xml 2007-04-24 23:32:35 UTC (rev 6170)
+++ trunk/refman-5.1/news-5.1-merged.xml 2007-04-24 23:33:48 UTC (rev 6171)
Changed blocks: 5, Lines Added: 102, Lines Deleted: 6; 4938 bytes
@@ -194,9 +194,7 @@
<listitem>
<para>
- The XML output representing an empty result was an empty
- string rather than an empty
- <literal><resultset/></literal> element. (Bug #27608)
+ The patches for Bug #19370 and Bug #21789 were reverted.
</para>
</listitem>
@@ -497,6 +495,90 @@
<listitem>
<para>
+ The test for the
+ <literal>MYSQL_OPT_SSL_VERIFY_SERVER_CERT</literal> option for
+ <literal>mysql_options()</literal> was performed incorrectly.
+ Also changed as a result of this bugfix: The
+ <literal>arg</literal> option for the
+ <literal>mysql_options()</literal> C API function was changed
+ from <literal>char *</literal> to <literal>void *</literal>.
+ (Bug #24121)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Comparisons using row constructors could fail for rows
+ containing <literal>NULL</literal> values. (Bug #27704)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Performing a <literal>UNION</literal> on two views that had
+ had <literal>ORDER BY</literal> clauses resulted in an
+ <literal>Unknown column</literal> error. (Bug #27786)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>CRC32()</literal> function returns an unsigned
+ integer, but the metadata was signed, which could cause
+ certain queries to return incorrect results. (For example,
+ queries that selected a <literal>CRC32()</literal> value and
+ used that value in the <literal>GROUP BY</literal> clause.)
+ (Bug #27530)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A race condition between <literal>DROP TABLE</literal> and
+ <literal>SHOW TABLE STATUS</literal> could cause the latter to
+ display incorrect information. (Bug #27499)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqldump</command> would not dump a view for which
+ the <literal>DEFINER</literal> no longer exists. (Bug #26817)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Changing a <literal>utf8</literal> column in an
+ <literal>InnoDB</literal> table to a shorter length did not
+ shorten the data values. (Bug #20095)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server did not shut down cleanly. (Bug #27310)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>SET GLOBAL</literal> to change the
+ <literal>lc_time_names</literal> system variable had no effect
+ on new connections. (Bug #22648)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The XML output representing an empty result was an empty
+ string rather than an empty
+ <literal><resultset/></literal> element. (Bug #27608)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The range optimizer could consume a combinatorial amount of
memory for certain classes of <literal>WHERE</literal>
clauses. (Bug #26624)
@@ -654,13 +736,19 @@
<listitem>
<para>
+ The binary log incompatiblity introduced by the fix for Bug
+ #22583 was corrected. (Bug #27779)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Row-based replication of <literal>MyISAM</literal> to
non-<literal>MyISAM</literal> tables did not work correctly
for <literal>BIT</literal> columns. This has been corrected,
but the fix introduces an incompatibility into the binary log
- format. We recommend that users affected by this problem wait
- for MySQL 5.1.19, which addresses the incompatibility. (Bug
- #22583)
+ format. (Bug #22583) (The incompatibility is corrected by the
+ fix for Bug #27779.)
</para>
</listitem>
@@ -4530,6 +4618,10 @@
example of such an illegal <literal>DATETIME</literal> being
<literal>'0000-00-00 11:23:45'</literal>. (Bug #21789)
</para>
+
+ <para>
+ This patch was reverted in MySQL 5.1.18.
+ </para>
</listitem>
<listitem>
@@ -9630,6 +9722,10 @@
<literal>DATETIME</literal> value to <literal>'0000'</literal>
when inserting it into a table. (Bug #19370)
</para>
+
+ <para>
+ This patch was reverted in MySQL 5.1.18.
+ </para>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6171 - trunk/refman-5.1 | jon | 25 Apr |
