Author: paul
Date: 2006-04-04 16:05:01 +0200 (Tue, 04 Apr 2006)
New Revision: 1719
Log:
r9201@frost: paul | 2006-04-04 08:59:51 -0500
Document bugfixes:
Bug#15316
Bug#15098
Modified:
trunk/
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
trunk/refman-common/titles.en.ent
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9022
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4246
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9201
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4246
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-04-03 13:08:55 UTC (rev 1718)
+++ trunk/refman-common/news-4.1.xml 2006-04-04 14:05:01 UTC (rev 1719)
@@ -190,17 +190,36 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
+ <literal>CAST<replaceable>double</replaceable> AS SIGNED
+ INT)</literal> for large <replaceable>double</replaceable>
+ values outside the signed integer range truncates the result
+ to be within range, but the result sometimes had the wrong
+ sign. (Bug #15098)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SET</literal> value definitions containing commas
+ were not rejected. Now a definition such as
+ <literal>SET('a,b','c,d')</literal> results in an error. (Bug
+ #15316)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>MyISAM</literal>: Keys for which the first part of
the key was a <literal>CHAR</literal> or
<literal>VARCHAR</literal> column using the UTF-8 character
set and longer than 254 bytes could become corrupted. (Bug
- #17705)
+ #17705)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A timeout in the handling of
@@ -208,7 +227,7 @@
operations could yield a node failure. (Bug #18414)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A node restart immediately
@@ -217,26 +236,26 @@
2-node Clusters only. (Bug #18385)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: In event of a node failure
during a rollback, a <quote>false</quote> lock could be
established on the backup for that node, which lock could not
- be removed without restarting the node. (Bug #18352)
+ be removed without restarting the node. (Bug #18352)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The cluster created a crashed
replica of a table having an ordered index — or when
logging was not enabled, of a table having a table or unique
index — leading to a crash of the cluster following 8
- successibe restarts. (Bug #18298)
+ successibe restarts. (Bug #18298)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: When replacing a failed master
@@ -245,7 +264,7 @@
of data to write to the cluster log. (Bug #18118)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Restarting nodes were allowed
@@ -256,9 +275,9 @@
<listitem>
<para>
If <literal>InnoDB</literal> encountered a
- <literal>HA_ERR_LOCK_TABLE_FULL</literal> error and
- rolled back a transaction, the transaction was still written
- to the binary log. (Bug #18283)
+ <literal>HA_ERR_LOCK_TABLE_FULL</literal> error and rolled
+ back a transaction, the transaction was still written to the
+ binary log. (Bug #18283)
</para>
</listitem>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-04-03 13:08:55 UTC (rev 1718)
+++ trunk/refman-common/news-5.0.xml 2006-04-04 14:05:01 UTC (rev 1719)
@@ -167,6 +167,65 @@
for each individual 5.0.x release.
</para>
+ <section id="news-5-0-21">
+
+ <title>&title-news-5-0-21;</title>
+
+ <para role="release-level">
+ This is a bugfix release for the current production release
+ family.
+ </para>
+
+ <para>
+ This section documents all changes and bug fixes that have been
+ applied since the last official MySQL release. If you would like
+ to receive more fine-grained and personalised <emphasis>update
+ alerts</emphasis> about fixes that are relevant to the version and
+ features you use, please consider subscribing to <emphasis>MySQL
+ Network</emphasis> (a commercial MySQL offering). For more details
+ please see
+ <ulink url="http://www.mysql.com/network/advisors.html"/>.
+ </para>
+
+ <remark role="todo">
+ Uncomment following when there are new features or feature changes
+ to report.
+ </remark>
+
+<!--
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para></para>
+ </listitem>
+
+ </itemizedlist>
+-->
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>CAST<replaceable>double</replaceable> AS SIGNED
+ INT)</literal> for large <replaceable>double</replaceable>
+ values outside the signed integer range truncates the result
+ to be within range, but the result sometimes had the wrong
+ sign, and no warning was generated. (Bug #15098)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
<section id="news-5-0-20">
<title>&title-news-5-0-20;</title>
@@ -181,13 +240,13 @@
</remark>
<itemizedlist>
-
+
<listitem>
<para>
The <literal>NDBCluster</literal> storage engine now supports
- <literal>INSERT IGNORE</literal> and <literal>REPLACE</literal>
- statements. Previously, these statements failed with an error. (Bug
- #17431)
+ <literal>INSERT IGNORE</literal> and
+ <literal>REPLACE</literal> statements. Previously, these
+ statements failed with an error. (Bug #17431)
</para>
</listitem>
@@ -233,85 +292,85 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
A <literal>SELECT ... ORDER BY ...</literal> from a view
defined using a function could crash the server. An example of
such a view might be <literal>CREATE VIEW AS SELECT SQRT(c1)
- FROM t1</literal>. (Bug #18386)
+ FROM t1</literal>. (Bug #18386)
</para>
</listitem>
-
+
<listitem>
<para>
A <literal>DELETE</literal> using a subquery could crash the
server. (Bug #18306)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>REPAIR TABLE</literal>, <literal>OPTIMIZE
- TABLE</literal>, and <literal>ALTER TABLE</literal>
- operations on transactional tables could corrupt triggers
- referencing those tables. (Bug #18153)
+ TABLE</literal>, and <literal>ALTER TABLE</literal> operations
+ on transactional tables could corrupt triggers referencing
+ those tables. (Bug #18153)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>MyISAM</literal>: Performing a bulk insert on a table
referenced by a trigger would crash the table. (Bug #17764)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>MyISAM</literal>: Keys for which the first part of
the key was a <literal>CHAR</literal> or
<literal>VARCHAR</literal> column using the UTF-8 character
set and longer than 254 bytes could become corrupted. (Bug
- #17705)
+ #17705)
</para>
</listitem>
-
+
<listitem>
<para>
Using <literal>ORDER BY
- <replaceable>intvar</replaceable></literal> within a stored
+ <replaceable>intvar</replaceable></literal> within a stored
procedure (where <replaceable>intvar</replaceable> is an
integer variable or expression) would crash the server. (Bug
#16474)
</para>
-
+
<para>
- <emphasis role="bold">Note</emphasis>: The use of an integer
+ <emphasis role="bold">Note</emphasis>: The use of an integer
<replaceable>i</replaceable> in an <literal>ORDER BY
- <replaceable>i</replaceable></literal> clause for sorting
- the result by the
+ <replaceable>i</replaceable></literal> clause for sorting the
+ result by the
<replaceable>i</replaceable><superscript>th</superscript>
column is deprecated (and non-standard). It should
<emphasis>not</emphasis> be used in new applications. See
<xref linkend="select"/>.
</para>
</listitem>
-
+
<listitem>
<para>
Triggers created in MySQL 5.0.16 and earlier could not be
dropped after upgrading the server to 5.0.17 or later. (Bug
- #15921)
+ #15921)
</para>
</listitem>
-
+
<listitem>
<para>
A <literal>SELECT</literal> using a function against a nested
view would crash the server. (Bug #15683)
</para>
- </listitem>
-
+ </listitem>
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Certain queries using
@@ -320,7 +379,7 @@
results. (Bug #17729)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A timeout in the handling of
@@ -328,7 +387,7 @@
operations could yield a node failure. (Bug #18414)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A node restart immediately
@@ -337,26 +396,26 @@
2-node Clusters only. (Bug #18385)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: In event of a node failure
during a rollback, a <quote>false</quote> lock could be
established on the backup for that node, which lock could not
- be removed without restarting the node. (Bug #18352)
+ be removed without restarting the node. (Bug #18352)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The cluster created a crashed
replica of a table having an ordered index — or when
logging was not enabled, of a table having a table or unique
index — leading to a crash of the cluster following 8
- successibe restarts. (Bug #18298)
+ successibe restarts. (Bug #18298)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: When replacing a failed master
@@ -365,7 +424,7 @@
of data to write to the cluster log. (Bug #18118)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: If a <command>mysql</command>
@@ -374,10 +433,10 @@
cluster, the client would crash instead of returning the
appropriate error. For example, this could happen when the
client attempted to use a character set was not available to
- the <command>mysqld</command>. (Bug #17380)
+ the <command>mysqld</command>. (Bug #17380)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Restarting nodes were allowed
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-04-03 13:08:55 UTC (rev 1718)
+++ trunk/refman-common/news-5.1.xml 2006-04-04 14:05:01 UTC (rev 1719)
@@ -182,6 +182,16 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>CAST<replaceable>double</replaceable> AS SIGNED
+ INT)</literal> for large <replaceable>double</replaceable>
+ values outside the signed integer range truncates the result
+ to be within range, but the result sometimes had the wrong
+ sign, and no warning was generated. (Bug #15098)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent 2006-04-03 13:08:55 UTC (rev 1718)
+++ trunk/refman-common/titles.en.ent 2006-04-04 14:05:01 UTC (rev 1719)
@@ -1329,6 +1329,7 @@
<!ENTITY title-news-5-0-18 "Changes in release 5.0.18 (21 December 2005)">
<!ENTITY title-news-5-0-19 "Changes in release 5.0.19 (04 March 2006)">
<!ENTITY title-news-5-0-20 "Changes in release 5.0.20 (Not yet released)">
+<!ENTITY title-news-5-0-21 "Changes in release 5.0.21 (Not yet released)">
<!ENTITY title-news-5-0-2 "Changes in release 5.0.2 (01 Dec 2004)">
<!ENTITY title-news-5-0-3 "Changes in release 5.0.3 (23 Mar 2005: Beta)">
<!ENTITY title-news-5-0-4 "Changes in release 5.0.4 (16 Apr 2005)">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1719 - in trunk: . refman-common | paul | 4 Apr |
