Author: paul
Date: 2007-02-13 20:26:45 +0100 (Tue, 13 Feb 2007)
New Revision: 4925
Log:
r19795@polar: paul | 2007-02-13 13:25:15 -0600
Document bugfixes:
Bug#16590
Bug#23417
Bug#24780
Bug#25643
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:19788
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16183
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:19795
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16183
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2007-02-13 19:18:07 UTC (rev 4924)
+++ trunk/refman-4.1/news-4.1.xml 2007-02-13 19:26:45 UTC (rev 4925)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 890 bytes
@@ -240,6 +240,17 @@
<listitem>
<para>
+ <command>mysqld_multi</command> and
+ <command>mysqlaccess</command> looked for option files in
+ <filename>/etc</filename> even if the
+ <option>--sysconfdir</option> option for
+ <command>configure</command> had been given to specify a
+ different directory. (Bug #24780)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The arguments of the <literal>ENCODE()</literal> and the
<literal>DECODE()</literal> functions were not printed
correctly, causing problems in the output of <literal>EXPLAIN
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-02-13 19:18:07 UTC (rev 4924)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-02-13 19:26:45 UTC (rev 4925)
Changed blocks: 4, Lines Added: 33, Lines Deleted: 4; 2397 bytes
@@ -101,8 +101,9 @@
<listitem>
<para>
- <emphasis role="bold">Important</emphasis>: When using <literal>MERGE</literal> tables the definition of
- the <literal>MERGE</literal> table and the
+ <emphasis role="bold">Important</emphasis>: When using
+ <literal>MERGE</literal> tables the definition of the
+ <literal>MERGE</literal> table and the
<literal>MyISAM</literal> tables are checked each time the
tables are opened for access (including any
<literal>SELECT</literal> or <literal>INSERT</literal>
@@ -111,7 +112,7 @@
the tables then the statement will fail.
</para>
</listitem>
-
+
</itemizedlist>
<para>
@@ -122,6 +123,34 @@
<listitem>
<para>
+ <command>mysqld_multi</command> and
+ <command>mysqlaccess</command> looked for option files in
+ <filename>/etc</filename> even if the
+ <option>--sysconfdir</option> option for
+ <command>configure</command> had been given to specify a
+ different directory. (Bug #24780)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>SEC_TO_TIME()</literal> and
+ <literal>QUARTER()</literal> functions sometimes did not
+ handle <literal>NULL</literal> values correctly. (Bug #25643)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With <literal>ONLY_FULL_GROUP_BY</literal> enables, the server
+ was too strict: Some expressions involving only aggregate
+ values were rejected as non-aggregate (for example,
+ <literal>MAX(a) - MIN(a)</literal>). (Bug #23417)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The arguments of the <literal>ENCODE()</literal> and the
<literal>DECODE()</literal> functions were not printed
correctly, causing problems in the output of <literal>EXPLAIN
@@ -607,7 +636,7 @@
#24507)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-02-13 19:18:07 UTC (rev 4924)
+++ trunk/refman-5.1/news-5.1.xml 2007-02-13 19:26:45 UTC (rev 4925)
Changed blocks: 4, Lines Added: 41, Lines Deleted: 4; 3105 bytes
@@ -63,6 +63,7 @@
ANNOUNCE.
</remark>
</para>
+
<para>
This section documents all changes and bug fixes that have been
applied since the last official MySQL release. If you would like
@@ -253,6 +254,31 @@
<listitem>
<para>
+ The <literal>SEC_TO_TIME()</literal> and
+ <literal>QUARTER()</literal> functions sometimes did not
+ handle <literal>NULL</literal> values correctly. (Bug #25643)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The optimizer used a filesort rather than a
+ <literal>const</literal> table read in some cases when the
+ latter was possible. (Bug #16590)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With <literal>ONLY_FULL_GROUP_BY</literal> enables, the server
+ was too strict: Some expressions involving only aggregate
+ values were rejected as non-aggregate (for example,
+ <literal>MAX(a) - MIN(a)</literal>). (Bug #23417)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Indexes disabled with <literal>ALTER TABLE ... DISABLE
KEYS</literal> could in some cases be used by specifying
<literal>FORCE INDEX</literal>. (Bug #20604)
@@ -782,6 +808,17 @@
<listitem>
<para>
+ <command>mysqld_multi</command> and
+ <command>mysqlaccess</command> looked for option files in
+ <filename>/etc</filename> even if the
+ <option>--sysconfdir</option> option for
+ <command>configure</command> had been given to specify a
+ different directory. (Bug #24780)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>SHOW COLUMNS</literal> reported some <literal>NOT
NULL</literal> columns as <literal>NULL</literal>. (Bug
#22377)
@@ -13700,10 +13737,10 @@
suggested workaround is (1) to create a non-partitioned table
with the same table schema using a standard <literal>CREATE
TABLE</literal> statement (that is, with no partitioning
- clauses) and then (2) to issue a <literal>SELECT INTO</literal>
- to copy the data into the non-partitioned table before the
- upgrade; following the upgrade, you can partition the new
- table using <literal>ALTER TABLE ... PARTITION BY
+ clauses) and then (2) to issue a <literal>SELECT
+ INTO</literal> to copy the data into the non-partitioned table
+ before the upgrade; following the upgrade, you can partition
+ the new table using <literal>ALTER TABLE ... PARTITION BY
...</literal>. Alternatively, you can dump the table using
<command>mysqldump</command> prior to upgrading and reload it
afterwards with <literal>LOAD DATA</literal>. In either case,
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4925 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 13 Feb |