Author: paul
Date: 2006-09-25 20:23:11 +0200 (Mon, 25 Sep 2006)
New Revision: 3453
Log:
r14021@polar: paul | 2006-09-25 13:20:53 -0500
Document bugfixes:
Bug#15276
Bug#16201
Bug#16792
Bug#17620
Bug#20573
Bug#21180
Bug#21698
Bug#22251
Modified:
trunk/refman-4.1/database-administration.xml
trunk/refman-4.1/news-4.1.xml
trunk/refman-5.0/database-administration.xml
trunk/refman-5.0/news-5.0.xml
trunk/refman-5.1/database-administration.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:14020
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:8616
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10466
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:14021
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:8616
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10466
Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml 2006-09-25 18:22:59 UTC (rev 3452)
+++ trunk/refman-4.1/database-administration.xml 2006-09-25 18:23:11 UTC (rev 3453)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 2; 894 bytes
@@ -672,8 +672,11 @@
<para>
Use <replaceable>charset_name</replaceable> as the default
- server character set. This option is available as of MySQL
- 4.1.3. See <xref linkend="character-sets"/>.
+ server character set. See
+ <xref linkend="character-sets"/>. If you use this option
+ to specify a non-default character set, you should also
+ use <option>--collation-server</option> to specify the
+ collation. This option is available as of MySQL 4.1.3.
</para>
</listitem>
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2006-09-25 18:22:59 UTC (rev 3452)
+++ trunk/refman-4.1/news-4.1.xml 2006-09-25 18:23:11 UTC (rev 3453)
Changed blocks: 1, Lines Added: 26, Lines Deleted: 0; 1352 bytes
@@ -209,6 +209,32 @@
<listitem>
<para>
+ The <option>--collation-server</option> server option was
+ being ignored. With the fix for this problem, if you choose a
+ non-default character set with
+ <option>--character-set-server</option>, you should also use
+ <option>--collation-server</option> to specify the collation.
+ (Bug #15276)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A subquery that uses an index for both the
+ <literal>WHERE</literal> and <literal>ORDER BY</literal>
+ clauses produced an empty result. (Bug #21180)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Queries containing a subquery that used aggregate functions
+ could return incorrect results. (Bug #16792)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <literal>MD5()</literal>, <literal>SHA1()</literal>, and
<literal>ENCRYPT()</literal> functions should return a binary
string, but the result sometimes was converted to the
Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml 2006-09-25 18:22:59 UTC (rev 3452)
+++ trunk/refman-5.0/database-administration.xml 2006-09-25 18:23:11 UTC (rev 3453)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 5; 1737 bytes
@@ -763,7 +763,10 @@
<para>
Use <replaceable>charset_name</replaceable> as the default
server character set. See
- <xref linkend="character-sets"/>.
+ <xref linkend="character-sets"/>. If you use this option
+ to specify a non-default character set, you should also
+ use <option>--collation-server</option> to specify the
+ collation.
</para>
</listitem>
@@ -13911,14 +13914,14 @@
<para>
If there is a configuration file when Instance Manager starts,
it reads the file to find server instance sections and
- attempts to start a server for each guarded instance section that it
- finds. Instance sections have names of the form
+ attempts to start a server for each guarded instance section
+ that it finds. Instance sections have names of the form
<literal>[mysqld<replaceable>N</replaceable>]</literal>, where
<replaceable>N</replaceable> is an unsigned integer (for
example, <literal>[mysqld1]</literal>,
<literal>[mysqld2]</literal>, and so forth). specifies an
- instance. By default, Instance Manager stops all guarded server
- instances when it shuts down.
+ instance. By default, Instance Manager stops all guarded
+ server instances when it shuts down.
</para>
<warning>
Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml 2006-09-25 18:22:59 UTC (rev 3452)
+++ trunk/refman-5.0/news-5.0.xml 2006-09-25 18:23:11 UTC (rev 3453)
Changed blocks: 3, Lines Added: 70, Lines Deleted: 0; 3043 bytes
@@ -224,6 +224,39 @@
<listitem>
<para>
+ A function result in a comparison was replaced with a constant
+ by the optimizer under some circumstances when this
+ optimization was invalid. (Bug #21698)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A subquery that uses an index for both the
+ <literal>WHERE</literal> and <literal>ORDER BY</literal>
+ clauses produced an empty result. (Bug #21180)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If the <literal>auto_increment_offset</literal> setting causes
+ MySQL to generate a value larger than the column's maximum
+ possible value, the <literal>INSERT</literal> statement is
+ accepted in strict SQL mode, whereas but should fail with an
+ error. (Bug #20573)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Queries containing a subquery that used aggregate functions
+ could return incorrect results. (Bug #16792)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>EXPLAIN</literal> sometimes returned an incorrect
<literal>select_type</literal> for a <literal>SELECT</literal>
from a view, compared to the <literal>select_type</literal>
@@ -508,6 +541,27 @@
<listitem>
<para>
+ The <option>--collation-server</option> server option was
+ being ignored. With the fix for this problem, if you choose a
+ non-default character set with
+ <option>--character-set-server</option>, you should also use
+ <option>--collation-server</option> to specify the collation.
+ (Bug #15276)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The
+ <literal>index_merge</literal>/<literal>Intersection</literal>
+ optimizer could have a memory overrrun when the number of
+ table columns covered by an index is sufficiently large,
+ possibly resulting in a server crash. (Bug #16201)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
With <literal>max_sp_recursion</literal> set to 0, a stored
procedure that executed a <literal>SHOW CREATE
PROCEDURE</literal> statement for itself triggered a recursion
@@ -2128,6 +2182,22 @@
</itemizedlist>
+ <para>
+ In addition, the following problem affected the initial build of
+ 5.0.24a, but has been corrected in the RPM files now available:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The shared compatibility RPM files were missing some files.
+ (Bug #22251)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
</section>
<section id="news-5-0-24">
Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml 2006-09-25 18:22:59 UTC (rev 3452)
+++ trunk/refman-5.1/database-administration.xml 2006-09-25 18:23:11 UTC (rev 3453)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 5; 1737 bytes
@@ -977,7 +977,10 @@
<para>
Use <replaceable>charset_name</replaceable> as the default
server character set. See
- <xref linkend="character-sets"/>.
+ <xref linkend="character-sets"/>. If you use this option
+ to specify a non-default character set, you should also
+ use <option>--collation-server</option> to specify the
+ collation.
</para>
</listitem>
@@ -13910,14 +13913,14 @@
<para>
If there is a configuration file when Instance Manager starts,
it reads the file to find server instance sections and
- attempts to start a server for each guarded instance section that it
- finds. Instance sections have names of the form
+ attempts to start a server for each guarded instance section
+ that it finds. Instance sections have names of the form
<literal>[mysqld<replaceable>N</replaceable>]</literal>, where
<replaceable>N</replaceable> is an unsigned integer (for
example, <literal>[mysqld1]</literal>,
<literal>[mysqld2]</literal>, and so forth). specifies an
- instance. By default, Instance Manager stops all guarded server
- instances when it shuts down.
+ instance. By default, Instance Manager stops all guarded
+ server instances when it shuts down.
</para>
<warning>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-09-25 18:22:59 UTC (rev 3452)
+++ trunk/refman-5.1/news-5.1.xml 2006-09-25 18:23:11 UTC (rev 3453)
Changed blocks: 2, Lines Added: 62, Lines Deleted: 1; 2703 bytes
@@ -714,6 +714,67 @@
<listitem>
<para>
+ The <option>--collation-server</option> server option was
+ being ignored. With the fix for this problem, if you choose a
+ non-default character set with
+ <option>--character-set-server</option>, you should also use
+ <option>--collation-server</option> to specify the collation.
+ (Bug #15276)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A function result in a comparison was replaced with a constant
+ by the optimizer under some circumstances when this
+ optimization was invalid. (Bug #21698)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A subquery that uses an index for both the
+ <literal>WHERE</literal> and <literal>ORDER BY</literal>
+ clauses produced an empty result. (Bug #21180)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If the <literal>auto_increment_offset</literal> setting causes
+ MySQL to generate a value larger than the column's maximum
+ possible value, the <literal>INSERT</literal> statement is
+ accepted in strict SQL mode, whereas but should fail with an
+ error. (Bug #20573)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Queries containing a subquery that used aggregate functions
+ could return incorrect results. (Bug #16792)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Row-based replication failed when the query cache was enabled
+ on the slave. (Bug #17620)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The
+ <literal>index_merge</literal>/<literal>Intersection</literal>
+ optimizer could have a memory overrrun when the number of
+ table columns covered by an index is sufficiently large,
+ possibly resulting in a server crash. (Bug #16201)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <literal>MD5()</literal>, <literal>SHA1()</literal>, and
<literal>ENCRYPT()</literal> functions should return a binary
string, but the result sometimes was converted to the
@@ -1066,7 +1127,7 @@
longer available. (Bug #9678)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Direct APIs): The
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3453 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 25 Sep |
