Author: paul
Date: 2006-02-21 04:26:01 +0100 (Tue, 21 Feb 2006)
New Revision: 1412
Log:
r7998@frost: paul | 2006-02-20 20:55:18 -0600
Document bugfixes:
Bug#13897
Bug#16389
Bug#16406
Bug#16752
Bug#17373
Modified:
trunk/
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:7996
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3439
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:7998
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3439
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-02-21 01:08:47 UTC (rev 1411)
+++ trunk/refman-common/news-4.1.xml 2006-02-21 03:26:01 UTC (rev 1412)
@@ -170,7 +170,7 @@
<para>
<literal>InnoDB</literal> now caches a list of unflushed files
instead of scanning for unflushed files during a table flush
- operation. This improves performance when
+ operation. This improves performance when
<option>--innodb-file-per-table</option> is set on a system
with a large number of <literal>InnoDB</literal> tables. (Bug
#15653)
@@ -184,15 +184,23 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
+ <command>mysqldump</command> tried to dump data from a view.
+ (In MySQL 4.1, this applies when connecting to a server from
+ MySQL 5.0 or higher.) (Bug #16389)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: An <literal>UPDATE</literal>
with an inner join failed to match any records if both tables
in the join did not have a primary key. (Bug #17257)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A <literal>DELETE</literal>
@@ -201,15 +209,15 @@
primary key. (Bug #17249)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: In some cases, <literal>LOAD
- DATA INFILE</literal> did not load all data into
- <literal>NDB</literal> tables. (Bug #17081)
+ DATA INFILE</literal> did not load all data into
+ <literal>NDB</literal> tables. (Bug #17081)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The <literal>REDO</literal>
@@ -218,7 +226,7 @@
#17295)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: No error message was generated
@@ -226,7 +234,7 @@
(Bug #13966)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: No error message was generated
@@ -628,8 +636,8 @@
<listitem>
<para>
<literal>DELETE</literal> could report full-text index
- corruption (<literal>Invalid key for table ...</literal>)
- if the index was built with repair-by-sort, the data in the
+ corruption (<literal>Invalid key for table ...</literal>) if
+ the index was built with repair-by-sort, the data in the
full-text index used UCA collation, and some word appeared in
the data terminated by a 0xC2A0 character as well as by other
non-letter characters. (Bug #11336)
@@ -980,12 +988,12 @@
<listitem>
<para>
<literal>CREATE TABLE <replaceable>tbl_name</replaceable>
- (...) SELECT ...</literal> could crash the server
- and write invalid data into the <filename>.frm</filename> file
- if the <literal>CREATE TABLE</literal> and
- <literal>SELECT</literal> both contained a column with the
- same name. Also, if a default value is specified in the column
- definition, it is now actually used. (Bug #14480)
+ (...) SELECT ...</literal> could crash the server and write
+ invalid data into the <filename>.frm</filename> file if the
+ <literal>CREATE TABLE</literal> and <literal>SELECT</literal>
+ both contained a column with the same name. Also, if a default
+ value is specified in the column definition, it is now
+ actually used. (Bug #14480)
</para>
</listitem>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-02-21 01:08:47 UTC (rev 1411)
+++ trunk/refman-common/news-5.0.xml 2006-02-21 03:26:01 UTC (rev 1412)
@@ -325,6 +325,23 @@
<listitem>
<para>
+ For a MySQL 5.0 server, using MySQL 4.1 tables in queries with
+ a <literal>GROUP BY</literal> clause could result in buffer
+ overrun or a server crash. (Bug #16752)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SET sql_mode =
+ <replaceable>N</replaceable></literal>, where
+ <replaceable>N</replaceable> > 31, did not work properly.
+ (Bug #13897)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: Cluster log file paths were
truncated to 128 characters. They may now be as long as
<literal>MAX_PATH</literal> (the maximum path length permitted
@@ -1523,11 +1540,11 @@
<para>
Implicit versus explicit conversion of float to integer (such
as inserting a float value into an integer column versus using
- <literal>CAST(... AS UNSIGNED</literal> before inserting
- the value) could produce different results. Implicit and
- explicit typecasts now are done the same way, with a value
- equal to the nearest integer according to the prevailing
- rounding mode. (Bug #12956)
+ <literal>CAST(... AS UNSIGNED</literal> before inserting the
+ value) could produce different results. Implicit and explicit
+ typecasts now are done the same way, with a value equal to the
+ nearest integer according to the prevailing rounding mode.
+ (Bug #12956)
</para>
</listitem>
@@ -1602,8 +1619,8 @@
<listitem>
<para>
- Within a stored procedure, inserting with <literal>INSERT
- ... SELECT</literal> into a table with an
+ Within a stored procedure, inserting with <literal>INSERT ...
+ SELECT</literal> into a table with an
<literal>AUTO_INCREMENT</literal> column did not generate the
correct sequence number. (Bug #14304)
</para>
@@ -1660,8 +1677,8 @@
<listitem>
<para>
- <literal>ALTER TABLE ... SET DEFAULT</literal> had no
- effect. (Bug #14693)
+ <literal>ALTER TABLE ... SET DEFAULT</literal> had no effect.
+ (Bug #14693)
</para>
</listitem>
@@ -1689,9 +1706,9 @@
<listitem>
<para>
<literal>CHAR(... USING ...)</literal> and
- <literal>CONVERT(CHAR(...) USING ...)</literal>,
- though logically equivalent, could produce different results.
- (Bug #14146)
+ <literal>CONVERT(CHAR(...) USING ...)</literal>, though
+ logically equivalent, could produce different results. (Bug
+ #14146)
</para>
</listitem>
@@ -1950,12 +1967,12 @@
<listitem>
<para>
<literal>CREATE TABLE <replaceable>tbl_name</replaceable>
- (...) SELECT ...</literal> could crash the server
- and write invalid data into the <filename>.frm</filename> file
- if the <literal>CREATE TABLE</literal> and
- <literal>SELECT</literal> both contained a column with the
- same name. Also, if a default value is specified in the column
- definition, it is now actually used. (Bug #14480)
+ (...) SELECT ...</literal> could crash the server and write
+ invalid data into the <filename>.frm</filename> file if the
+ <literal>CREATE TABLE</literal> and <literal>SELECT</literal>
+ both contained a column with the same name. Also, if a default
+ value is specified in the column definition, it is now
+ actually used. (Bug #14480)
</para>
</listitem>
@@ -2025,8 +2042,8 @@
procedure with the procedure name explicitly qualified with a
database name (<literal>CREATE PROCEDURE
<replaceable>db_name</replaceable>.<replaceable>proc_name</replaceable>
- ...</literal>). 2) Create another stored procedure with
- no database name qualifier. 3) Execute <literal>SHOW PROCEDURE
+ ...</literal>). 2) Create another stored procedure with no
+ database name qualifier. 3) Execute <literal>SHOW PROCEDURE
STATUS</literal>. (Bug #14569)
</para>
</listitem>
@@ -2652,16 +2669,16 @@
<listitem>
<para>
Corrected a parser precedence problem that resulted in an
- <literal>Unknown column ... in 'on clause'</literal>
- error for some joins. (Bug #13832)
+ <literal>Unknown column ... in 'on clause'</literal> error for
+ some joins. (Bug #13832)
</para>
</listitem>
<listitem>
<para>
- For <literal>LIKE ... ESCAPE</literal>, an escape
- sequence longer than one character was accepted as valid. Now
- the sequence must be empty or one character long. If the
+ For <literal>LIKE ... ESCAPE</literal>, an escape sequence
+ longer than one character was accepted as valid. Now the
+ sequence must be empty or one character long. If the
<literal>NO_BACKSLASH_ESCAPES</literal> SQL mode is enabled,
the sequence must be one character long. (Bug #12595)
</para>
@@ -6210,10 +6227,10 @@
<listitem>
<para>
- A recent optimizer change caused <literal>DELETE ...
- WHERE ... NOT LIKE</literal> and <literal>DELETE ...
- WHERE ... NOT BETWEEN</literal> to not properly identify
- the rows to be deleted. (Bug #11853)
+ A recent optimizer change caused <literal>DELETE ... WHERE ...
+ NOT LIKE</literal> and <literal>DELETE ... WHERE ... NOT
+ BETWEEN</literal> to not properly identify the rows to be
+ deleted. (Bug #11853)
</para>
</listitem>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-02-21 01:08:47 UTC (rev 1411)
+++ trunk/refman-common/news-5.1.xml 2006-02-21 03:26:01 UTC (rev 1412)
@@ -186,6 +186,29 @@
<listitem>
<para>
+ <literal>DROP DATABASE</literal> did not drop events for the
+ database. (Bug #16406)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Race conditions between event creation, dropping, and
+ execution could result in a server crash or hang. (Bug #17373)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SET sql_mode =
+ <replaceable>N</replaceable></literal>, where
+ <replaceable>N</replaceable> > 31, did not work properly.
+ (Bug #13897)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Repeated invocation of <literal>my_init()</literal> and
<literal>my_end()</literal> caused corruption of character set
data and connection failure. (Bug #6536)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1412 - in trunk: . refman-common | paul | 21 Feb |
