Author: jstephens
Date: 2007-10-08 16:23:34 +0200 (Mon, 08 Oct 2007)
New Revision: 8023
Log:
Documented some general Server bugfixes:
Bug #13675, Bug #21074, Bug #25843, Bug #30593, Bug #31076
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-10-08 10:11:06 UTC (rev 8022)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-10-08 14:23:34 UTC (rev 8023)
Changed blocks: 4, Lines Added: 28, Lines Deleted: 6; 2537 bytes
@@ -47,8 +47,7 @@
alerts</emphasis> about fixes that are relevant to the version and
features you use, please consider subscribing to <emphasis>MySQL
Network</emphasis> (a commercial MySQL offering). For more details
- please see
- <ulink url="&base-url-enterprise;advisors.html"/>.
+ please see <ulink url="&base-url-enterprise;advisors.html"/>.
</para>
<para>
@@ -92,6 +91,31 @@
<listitem>
<para>
+ <literal>SHOW STATUS LIKE 'Ssl_cipher_list'</literal> from a
+ MySQL client connected via SSL returned an empty string rather
+ than a list of available ciphers. (Bug #30593)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Parameters of type <literal>DATETIME</literal> or
+ <literal>DATE</literal> in stored procedures were silently
+ converted to <literal>VARBINARY</literal>. (Bug #13675)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Under heavy load with a large query cache, invalidating part
+ of the cache could cause the server to freeze (that is, to be
+ unable to service other operations until the invalidation was
+ complete). (Bug #21074)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Reads on <literal>BLOB</literal> columns were not locked when
they needed to be, in order to guarantee consistency. (Bug
#29102)
@@ -221,8 +245,7 @@
alerts</emphasis> about fixes that are relevant to the version and
features you use, please consider subscribing to <emphasis>MySQL
Network</emphasis> (a commercial MySQL offering). For more details
- please see
- <ulink url="&base-url-enterprise;advisors.html"/>.
+ please see <ulink url="&base-url-enterprise;advisors.html"/>.
</para>
<para>
@@ -1106,8 +1129,7 @@
alerts</emphasis> about fixes that are relevant to the version and
features you use, please consider subscribing to <emphasis>MySQL
Network</emphasis> (a commercial MySQL offering). For more details
- please see
- <ulink url="&base-url-enterprise;advisors.html"/>.
+ please see <ulink url="&base-url-enterprise;advisors.html"/>.
</para>
<para>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-10-08 10:11:06 UTC (rev 8022)
+++ trunk/refman-5.1/news-5.1.xml 2007-10-08 14:23:34 UTC (rev 8023)
Changed blocks: 2, Lines Added: 35, Lines Deleted: 0; 1949 bytes
@@ -165,6 +165,33 @@
<listitem>
<para>
+ For a prepared statement <replaceable>stmt</replaceable>,
+ changing the default database following <literal>PREPARE
+ <replaceable>stmt</replaceable></literal> but before
+ <literal>EXECUTE <replaceable>stmt</replaceable></literal>
+ caused <replaceable>stmt</replaceable> to be recorded
+ incorrectly in the binary log. (Bug #25843)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SHOW STATUS LIKE 'Ssl_cipher_list'</literal> from a
+ MySQL client connected via SSL returned an empty string rather
+ than a list of available ciphers. (Bug #30593)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Parameters of type <literal>DATETIME</literal> or
+ <literal>DATE</literal> in stored procedures were silently
+ converted to <literal>VARBINARY</literal>. (Bug #13675)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Partition pruning was not used for queries having
<literal><=</literal> or <literal>>=</literal>
conditions in the <literal>WHERE</literal> clause on a table
@@ -553,6 +580,14 @@
<listitem>
<para>
+ Row-based replication from a pre-5.1.22 MySQL Server to a
+ MySQL 5.1.22 was unstable due to an uninitialized variable.
+ (Bug #31076)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
For an <literal>InnoDB</literal> table if a
<literal>SELECT</literal> was ordered by the primary key and
also had a <literal>WHERE field = value</literal> clause on a
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8023 - in trunk: refman-5.0 refman-5.1 | jon | 8 Oct |
