Author: paul
Date: 2007-03-19 18:57:14 +0100 (Mon, 19 Mar 2007)
New Revision: 5460
Log:
r21887@polar: paul | 2007-03-19 12:44:12 -0500
Document bugfixes:
Bug#24778
Bug#26261
Bug#26285
Bug#26672
Bug#26738
Modified:
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/news-5.1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:21886
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:17943
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:21887
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:17943
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-19 17:56:59 UTC (rev 5459)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-19 17:57:14 UTC (rev 5460)
Changed blocks: 4, Lines Added: 90, Lines Deleted: 3; 3732 bytes
@@ -37,9 +37,9 @@
<filename>refman-common</filename> directory.
</remark>
- <section id="releasenotes-es-5-0-38">
+ <section id="releasenotes-es-5-0-40">
- <title>Release Notes for MySQL Enterprise 5.0.38 (Not yet released)</title>
+ <title>Release Notes for MySQL Enterprise 5.0.40 (Not yet released)</title>
<para role="release-level">
This is a <emphasis>Monthly Rapid Update</emphasis> release of the
@@ -48,7 +48,7 @@
<para>
This section documents all changes and bug fixes that have been
- applied since the last MySQL Enterprise Server release (5.0.36).
+ applied since the last MySQL Enterprise Server release (5.0.38).
</para>
<remark>
@@ -56,6 +56,7 @@
document.
</remark>
+<!--
<para>
Functionality added or changed:
</para>
@@ -64,6 +65,92 @@
<listitem>
<para>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+-->
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For an <literal>INSERT</literal> statement that should fail
+ due to a column with no default value not being assigned a
+ value, the statement succeeded with no error if the column was
+ assigned a value in an <literal>ON DUPLICATE KEY
+ UPDATE</literal> clause, even if that clause was not used.
+ (Bug #26261)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A result set column formed by concatention of string literals
+ was incomplete when the column was produced by a subquery in
+ the <literal>FROM</literal> clause. (Bug #26738)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When using the result of <literal>SEC_TO_TIME()</literal> for
+ time value greater than 24 hours in an <literal>ORDER
+ BY</literal> clause, either directly or through a column
+ alias, the rows were sorted incorrectly as strings. (Bug
+ #26672)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If the server was started with
+ <option>--skip-grant-tables</option>, Selecting from
+ <literal>INFORMATION_SCHEMA</literal> tables causes a server
+ crash. (Bug #26285)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Adding <literal>ORDER BY</literal> clause to a query on an
+ <literal>InnoDB</literal> table could cause the statement to
+ return no result if the optimizer chose a covering index that
+ enabled it to skip the <literal>ORDER BY</literal>. (Bug
+ #24778)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="releasenotes-es-5-0-38">
+
+ <title>Release Notes for MySQL Enterprise 5.0.38 (Not yet released)</title>
+
+ <para role="release-level">
+ This is a <emphasis>Monthly Rapid Update</emphasis> release of the
+ MySQL Enterprise Server 5.0.
+ </para>
+
+ <para>
+ This section documents all changes and bug fixes that have been
+ applied since the last MySQL Enterprise Server release (5.0.36).
+ </para>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
Added the <option>--secure-file-priv</option> option for
<command>mysql-test-run.pl</command>, which limits the effect
of the <literal>load_file</literal> command for
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-03-19 17:56:59 UTC (rev 5459)
+++ trunk/refman-5.1/news-5.1.xml 2007-03-19 17:57:14 UTC (rev 5460)
Changed blocks: 1, Lines Added: 48, Lines Deleted: 0; 2150 bytes
@@ -251,6 +251,54 @@
<listitem>
<para>
+ For an <literal>INSERT</literal> statement that should fail
+ due to a column with no default value not being assigned a
+ value, the statement succeeded with no error if the column was
+ assigned a value in an <literal>ON DUPLICATE KEY
+ UPDATE</literal> clause, even if that clause was not used.
+ (Bug #26261)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A result set column formed by concatention of string literals
+ was incomplete when the column was produced by a subquery in
+ the <literal>FROM</literal> clause. (Bug #26738)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When using the result of <literal>SEC_TO_TIME()</literal> for
+ time value greater than 24 hours in an <literal>ORDER
+ BY</literal> clause, either directly or through a column
+ alias, the rows were sorted incorrectly as strings. (Bug
+ #26672)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If the server was started with
+ <option>--skip-grant-tables</option>, Selecting from
+ <literal>INFORMATION_SCHEMA</literal> tables causes a server
+ crash. (Bug #26285)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Adding <literal>ORDER BY</literal> clause to a query on an
+ <literal>InnoDB</literal> table could cause the statement to
+ return no result if the optimizer chose a covering index that
+ enabled it to skip the <literal>ORDER BY</literal>. (Bug
+ #24778)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>IN ((<replaceable>subquery</replaceable>))</literal>,
<literal>IN
(((<replaceable>subquery</replaceable>)))</literal>, and so
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5460 - in trunk: . refman-5.0 refman-5.1 | paul | 19 Mar |
