Author: paul
Date: 2006-09-13 04:51:44 +0200 (Wed, 13 Sep 2006)
New Revision: 3338
Log:
Document bugfixes:
Bug#13717
Bug#16249
Bug#16513
Bug#20695
Bug#20910
Bug#20987
Bug#21054
Bug#21058
Bug#21159
Bug#21174
Bug#21282
Bug#21390
Modified:
trunk/refman-4.1/news-4.1.xml
trunk/refman-5.0/installing.xml
trunk/refman-5.0/news-5.0.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2006-09-12 21:05:49 UTC (rev 3337)
+++ trunk/refman-4.1/news-4.1.xml 2006-09-13 02:51:44 UTC (rev 3338)
Changed blocks: 1, Lines Added: 28, Lines Deleted: 0; 1403 bytes
@@ -200,6 +200,34 @@
<listitem>
<para>
+ The <command>ndb_mgm</command> program was included in both
+ the <literal>MySQL-ndb-tools</literal> and
+ <literal>MySQL-ndb-management</literal> RPM packages,
+ resulting in a conflict if both were installed. Now
+ <command>ndb_mgm</command> is included only in
+ <literal>MySQL-ndb-tools</literal>. (Bug #21058)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>libmysqld</literal> produced some warnings to
+ <literal>stderr</literal> which could not be silenced. These
+ warnings now are suppressed. (Bug #13717)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If a column definition contained a character set declaration,
+ but a <literal>DEFAULT</literal> value began with an
+ introducer, the introducer character set was used as the
+ column character set. (Bug #20695)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Some x86_64 packages mistakenly contained 32-bit servers. (Bug
#22238)
</para>
Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml 2006-09-12 21:05:49 UTC (rev 3337)
+++ trunk/refman-5.0/installing.xml 2006-09-13 02:51:44 UTC (rev 3338)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 1; 1136 bytes
@@ -12895,6 +12895,16 @@
<listitem>
<para>
+ As of MySQL 5.0.25, <literal>TIMESTAMP</literal> columns
+ that are <literal>NOT NULL</literal> now are reported that
+ way by <literal>SHOW COLUMNS</literal> and
+ <literal>INFORMATION_SCHEMA</literal>, rather than as
+ <literal>NULL</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A new startup option named
<option>innodb_table_locks</option> was added that causes
<literal>LOCK TABLE</literal> to also acquire
@@ -16083,7 +16093,7 @@
<para role="deprecated">
As of MySQL 5.0, we don't provide binaries for Irix any more.
</para>
-
+
<para>
If you are using Irix 6.5.3 or newer,
<command>mysqld</command> is able to create threads only if
Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml 2006-09-12 21:05:49 UTC (rev 3337)
+++ trunk/refman-5.0/news-5.0.xml 2006-09-13 02:51:44 UTC (rev 3338)
Changed blocks: 2, Lines Added: 102, Lines Deleted: 0; 4172 bytes
@@ -337,6 +337,15 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ <literal>TIMESTAMP</literal> columns that are <literal>NOT
+ NULL</literal> now are reported that way by <literal>SHOW
+ COLUMNS</literal> and <literal>INFORMATION_SCHEMA</literal>.
+ (Bug #20910)
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -369,6 +378,99 @@
<listitem>
<para>
+ The <command>ndb_mgm</command> program was included in both
+ the <literal>MySQL-ndb-tools</literal> and
+ <literal>MySQL-ndb-management</literal> RPM packages,
+ resulting in a conflict if both were installed. Now
+ <command>ndb_mgm</command> is included only in
+ <literal>MySQL-ndb-tools</literal>. (Bug #21058)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A query could produce different results with and without and
+ index, if the <literal>WHERE</literal> clause contained a
+ range condition that used an invalid
+ <literal>DATETIME</literal> constant. (Bug #16249)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>libmysqld</literal> produced some warnings to
+ <literal>stderr</literal> which could not be silenced. These
+ warnings now are suppressed. (Bug #13717)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The optimizer sometimes produced an incorrect row-count
+ estimate after elimination of <literal>const</literal> tables.
+ This resulted in choosing extremely inefficient execution
+ plans in same cases when distribution of data in joins were
+ skewed. (Bug #21390)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Query results could be incorrect if the
+ <literal>WHERE</literal> clause contained
+ <literal>t.<replaceable>key_part</replaceable> NOT IN
+ (<replaceable>val_list</replaceable>)</literal>, where
+ <replaceable>val_list</replaceable> is a list of more than
+ 1000 constants. (Bug #21282)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>STR_TO_DATE()</literal> sometimes would return
+ <literal>NULL</literal> if the <literal>%D</literal> format
+ specifier was not the last specifier in the format string.
+ (Bug #20987)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>myisam_stats_method</literal> variable was
+ mishandled when set from an option file or on the command
+ line. (Bug #21054)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The optimizer assumed that if <literal>(a=x AND b=x)</literal>
+ is true, <literal>(a=x AND b=x) AND a=b</literal> is also
+ true. But that is not always so if <literal>a</literal> and
+ <literal>b</literal> have different data types. (Bug #21159)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> did not honor <literal>IGNORE
+ INDEX</literal>, which prevented using <literal>IGNORE
+ INDEX</literal> in cases where an index sort would be slower
+ than a filesort. (Bug #21174)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If a column definition contained a character set declaration,
+ but a <literal>DEFAULT</literal> value began with an
+ introducer, the introducer character set was used as the
+ column character set. (Bug #20695)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Use of <literal>MD5()</literal> with a <literal>ucs2</literal>
character column combined with <literal>GROUP BY</literal>
could return different results for <literal>MyISAM</literal>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-09-12 21:05:49 UTC (rev 3337)
+++ trunk/refman-5.1/news-5.1.xml 2006-09-13 02:51:44 UTC (rev 3338)
Changed blocks: 2, Lines Added: 84, Lines Deleted: 0; 3528 bytes
@@ -574,6 +574,15 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ <literal>TIMESTAMP</literal> columns that are <literal>NOT
+ NULL</literal> now are reported that way by <literal>SHOW
+ COLUMNS</literal> and <literal>INFORMATION_SCHEMA</literal>.
+ (Bug #20910)
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -648,6 +657,81 @@
<listitem>
<para>
+ The <command>ndb_mgm</command> program was included in both
+ the <literal>MySQL-ndb-tools</literal> and
+ <literal>MySQL-ndb-management</literal> RPM packages,
+ resulting in a conflict if both were installed. Now
+ <command>ndb_mgm</command> is included only in
+ <literal>MySQL-ndb-tools</literal>. (Bug #21058)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>libmysqld</literal> produced some warnings to
+ <literal>stderr</literal> which could not be silenced. These
+ warnings now are suppressed. (Bug #13717)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The optimizer sometimes produced an incorrect row-count
+ estimate after elimination of <literal>const</literal> tables.
+ This resulted in choosing extremely inefficient execution
+ plans in same cases when distribution of data in joins were
+ skewed. (Bug #21390)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Query results could be incorrect if the
+ <literal>WHERE</literal> clause contained
+ <literal>t.<replaceable>key_part</replaceable> NOT IN
+ (<replaceable>val_list</replaceable>)</literal>, where
+ <replaceable>val_list</replaceable> is a list of more than
+ 1000 constants. (Bug #21282)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>STR_TO_DATE()</literal> sometimes would return
+ <literal>NULL</literal> if the <literal>%D</literal> format
+ specifier was not the last specifier in the format string.
+ (Bug #20987)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, a definition for
+ <literal>mysql_set_server_option()</literal> was missing from
+ the C client library. (Bug #16513)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The optimizer assumed that if <literal>(a=x AND b=x)</literal>
+ is true, <literal>(a=x AND b=x) AND a=b</literal> is also
+ true. But that is not always so if <literal>a</literal> and
+ <literal>b</literal> have different data types. (Bug #21159)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> did not honor <literal>IGNORE
+ INDEX</literal>, which prevented using <literal>IGNORE
+ INDEX</literal> in cases where an index sort would be slower
+ than a filesort. (Bug #21174)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
For connections that required a <literal>SUBJECT</literal>
value, a check was performed to verify that the value was
correct, but the connection was not refused if not. (Bug
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3338 - in trunk: refman-4.1 refman-5.0 refman-5.1 | paul | 13 Sep |
