Author: paul
Date: 2007-07-27 18:32:41 +0200 (Fri, 27 Jul 2007)
New Revision: 7254
Log:
r23096@frost: paul | 2007-07-27 11:30:36 -0500
Document bugfixes:
Bug#15130
Bug#28591
Bug#29070
Bug#29338
Bug#29494
Bug#29644
Bug#29661
Modified:
trunk/refman-4.1/news-4.1.xml
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:27992
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23089
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27992
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23096
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2007-07-27 16:08:20 UTC (rev 7253)
+++ trunk/refman-4.1/news-4.1.xml 2007-07-27 16:32:41 UTC (rev 7254)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 636 bytes
@@ -201,6 +201,13 @@
<listitem>
<para>
+ A field packet with <literal>NULL</literal> fields caused a
+ <literal>libmysqlclient</literal> crash. (Bug #29494)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Adding <literal>DISTINCT</literal> could cause incorrect rows
to appear in a query result. (Bug #29911)
</para>
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-27 16:08:20 UTC (rev 7253)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-27 16:32:41 UTC (rev 7254)
Changed blocks: 1, Lines Added: 57, Lines Deleted: 0; 2342 bytes
@@ -93,6 +93,63 @@
<listitem>
<para>
+ Optimization of queries with <literal>DETERMINISTIC</literal>
+ stored functions in the <literal>WHERE</literal> clause was
+ ineffective: A sequential scan was always used. (Bug #29338)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SQL_BIG_RESULT</literal> had no effect for
+ <literal>CREATE TABLE ... SELECT SQL_BIG_RESULT ...</literal>
+ statements. (Bug #15130)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>InnoDB</literal> tables, MySQL unnecessarily
+ sorted records in certain cases when the records were
+ retrieved by <literal>InnoDB</literal> in the proper order
+ already. (Bug #28591)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>EXPLAIN</literal> produced <literal>Impossible
+ where</literal> for statements of the form <literal>SELECT ...
+ FROM t WHERE c=0</literal>, where <literal>c</literal> was an
+ <literal>ENUM</literal> column defined as a primary key. (Bug
+ #29661)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, <literal>ALTER TABLE</literal> hung if records
+ were locked in share mode by a long-running transaction. (Bug
+ #29644)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A field packet with <literal>NULL</literal> fields caused a
+ <literal>libmysqlclient</literal> crash. (Bug #29494)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A byte-order issue in writing a spatial index to disk caused
+ bad index files on some systems. (Bug #29070)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqldump</command> produced output that incorrectly
discarded the <literal>NO_AUTO_VALUE_ON_ZERO</literal> value
of the <literal>SQL_MODE</literal> variable after dumping
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-07-27 16:08:20 UTC (rev 7253)
+++ trunk/refman-5.1/news-5.1.xml 2007-07-27 16:32:41 UTC (rev 7254)
Changed blocks: 1, Lines Added: 57, Lines Deleted: 0; 2311 bytes
@@ -177,6 +177,63 @@
<listitem>
<para>
+ Optimization of queries with <literal>DETERMINISTIC</literal>
+ stored functions in the <literal>WHERE</literal> clause was
+ ineffective: A sequential scan was always used. (Bug #29338)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SQL_BIG_RESULT</literal> had no effect for
+ <literal>CREATE TABLE ... SELECT SQL_BIG_RESULT ...</literal>
+ statements. (Bug #15130)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>InnoDB</literal> tables, MySQL unnecessarily
+ sorted records in certain cases when the records were
+ retrieved by <literal>InnoDB</literal> in the proper order
+ already. (Bug #28591)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>EXPLAIN</literal> produced <literal>Impossible
+ where</literal> for statements of the form <literal>SELECT ...
+ FROM t WHERE c=0</literal>, where <literal>c</literal> was an
+ <literal>ENUM</literal> column defined as a primary key. (Bug
+ #29661)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, <literal>ALTER TABLE</literal> hung if records
+ were locked in share mode by a long-running transaction. (Bug
+ #29644)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A field packet with <literal>NULL</literal> fields caused a
+ <literal>libmysqlclient</literal> crash. (Bug #29494)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A byte-order issue in writing a spatial index to disk caused
+ bad index files on some systems. (Bug #29070)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqldump</command> produced output that incorrectly
discarded the <literal>NO_AUTO_VALUE_ON_ZERO</literal> value
of the <literal>SQL_MODE</literal> variable after dumping
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7254 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 27 Jul |
