Author: jstephens
Date: 2008-03-30 22:52:37 +0200 (Sun, 30 Mar 2008)
New Revision: 10376
Log:
Documenting more CGE-6.3.11 and related bugfixes:
Bug #29562, Bug #29645, Bug #29836, Bug #30059, Bug #30252,
Bug #30331, Bug #30435, Bug #30787, Bug #30887, Bug #30889,
Bug #30998, Bug #31004, Bug #31024, Bug #31168, Bug #31194,
Bug #31222, Bug #31236, Bug #31239, Bug #31316, Bug #31331,
Bug #31552, Bug #31581, Bug #31583, Bug #31590, Bug #31609,
Bug #31887, Bug #31891, Bug #33143, Bug #33862
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/command-optvars/mysqld.xml
trunk/refman-5.0/data-types.xml
trunk/refman-5.1/data-types.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-6.0/data-types.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-03-30 09:53:42 UTC (rev 10375)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-03-30 20:52:37 UTC (rev 10376)
Changed blocks: 27, Lines Added: 200, Lines Deleted: 2; 9535 bytes
@@ -9,6 +9,178 @@
<logentry entrytype="bug">
<tags>
+ <manual type="ZEROFILL"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="31887"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Queries testing numeric constants containing leading zeroes
+ against <literal>ZEROFILL</literal> columns were not evaluated
+ correctly.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="max_sort_length"/>
+ <manual type="sort_buffer_size"/>
+ <manual type="errors"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="31590"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The server returned the error message <errortext>Out of memory;
+ restart server and try again</errortext> when the actual problem
+ was that the sort buffer was too small. Now an appropriate error
+ message is returned in such cases.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="BLOB"/>
+ <manual type="TEXT"/>
+ <manual type="upgrades"/>
+ <manual type="indexes"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="31331"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ A table having an index that included a <literal>BLOB</literal>
+ or <literal>TEXT</literal> column, and that was originally
+ created with a MySQL server using version 4.1 or earlier, could
+ not be opened by a 5.1 or later server.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="stored functions"/>
+ <manual type="alias"/>
+ <manual type="subqueries"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="30787"/>
+ <regressionof bugid="20777"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ If an alias was used to refer to the value returned by a stored
+ function within a subselect, the outer select recognized the
+ alias but failed to retrieve the value assigned to it in the
+ subselect.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="importantchange"/>
+ <manual type="CHAR"/>
+ <manual type="VARCHAR"/>
+ <manual type="TEXT"/>
+ <manual type="truncation"/>
+ <manual type="errors"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="30059"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The server handled truncation of values having excess trailing
+ spaces into <literal>CHAR</literal>, <literal>VARCHAR</literal>,
+ and <literal>TEXT</literal> columns in different ways. This
+ behavior has now been made consistent for columns of all three
+ of these types, and now follows the existing behavior of
+ <literal>VARCHAR</literal> columns in this regard; that is, a
+ <literal>Note</literal> is always issued whenever such
+ truncation occurs.
+ </para>
+
+ <para>
+ This change does not affect columns of these three types when
+ using a binary encoding; <literal>BLOB</literal> columns are
+ also unaffected by the change, since they always use a binary
+ encoding.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
<manual type="myisamchk"/>
<manual type="character sets"/>
</tags>
@@ -707,6 +879,7 @@
</bugs>
<versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -739,6 +912,7 @@
</bugs>
<versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -856,7 +1030,9 @@
<versions>
<version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
+ <version ver="6.0.5"/>
</versions>
<message>
@@ -911,6 +1087,7 @@
<versions>
<version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -1729,6 +1906,7 @@
</bugs>
<versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -2123,6 +2301,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -2360,6 +2539,7 @@
<versions>
<version ver="5.0.58"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -2367,8 +2547,8 @@
<message>
<para>
- Numerous test failures occurred in builds compiled using
- <command>icc</command> on IA64 platforms.
+ Numerous <literal>NDBCLUSTER</literal> test failures occurred in
+ builds compiled using <command>icc</command> on IA64 platforms.
</para>
</message>
@@ -3163,6 +3343,7 @@
<versions>
<version ver="5.0.56"/>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -3353,6 +3534,7 @@
<versions>
<version ver="5.0.56"/>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -3439,6 +3621,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -3468,6 +3651,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -3535,6 +3719,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -3617,6 +3802,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -4261,6 +4447,7 @@
<versions>
<version ver="5.1.23"/>
+ <version ver="6.0.5"/>
</versions>
<message>
@@ -10340,6 +10527,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -10369,6 +10557,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -10720,6 +10909,7 @@
<versions>
<version ver="5.0.56"/>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -10758,6 +10948,7 @@
<versions>
<version ver="5.0.56"/>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -10844,6 +11035,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -11161,6 +11353,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -11393,6 +11586,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -11453,6 +11647,7 @@
<versions>
<version ver="5.0.58"/>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -11483,6 +11678,7 @@
<versions>
<version ver="5.0.56"/>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -12518,6 +12714,7 @@
</bugs>
<versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -12751,6 +12948,7 @@
<versions>
<version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml 2008-03-30 09:53:42 UTC (rev 10375)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml 2008-03-30 20:52:37 UTC (rev 10376)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 557 bytes
@@ -4414,6 +4414,7 @@
<versions>
<manual version="5.1"/>
<introduced version="5.1.23-ndb-6.2.14"/>
+ <introduced version="5.1.23-ndb-6.3.11"/>
<introduced version="5.1.24"/>
<manual version="6.0"/>
<introduced version="6.0.5"/>
Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml 2008-03-30 09:53:42 UTC (rev 10375)
+++ trunk/refman-5.0/data-types.xml 2008-03-30 20:52:37 UTC (rev 10376)
Changed blocks: 2, Lines Added: 18, Lines Deleted: 0; 1581 bytes
@@ -4143,6 +4143,17 @@
</para>
<para>
+ For <literal>VARCHAR</literal> columns, excess trailing spaces
+ are truncated prior to insertion and a warning is generated,
+ regardless of the SQL mode in use. Prior to MySQL 5.0.60,
+ truncation of excess trailing spaces from values inserted into
+ <literal>CHAR</literal> columns was performed silently
+ regardless of the SQL mode; beginning with MySQL 5.0.60, a
+ warning is issued in such cases (also without regard to the SQL
+ mode in effect). (Bug #30059)
+ </para>
+
+ <para>
<literal>VARCHAR</literal> values are not padded when they are
stored. Handling of trailing spaces is version-dependent. As of
MySQL 5.0.3, trailing spaces are retained when values are stored
@@ -4576,6 +4587,13 @@
</para>
<para>
+ Beginning with MySQL 5.0.60, truncation of excess trailing
+ spaces from values to be inserted into <literal>TEXT</literal>
+ columns always generates a warning, regardless of the SQL mode.
+ (Bug #30059)
+ </para>
+
+ <para>
If a <literal>TEXT</literal> column is indexed, index entry
comparisons are space-padded at the end. This means that, if the
index requires unique values, duplicate-key errors will occur
Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml 2008-03-30 09:53:42 UTC (rev 10375)
+++ trunk/refman-5.1/data-types.xml 2008-03-30 20:52:37 UTC (rev 10376)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 0; 1661 bytes
@@ -3961,6 +3961,19 @@
</para>
<para>
+ For <literal>VARCHAR</literal> columns, excess trailing spaces
+ are truncated prior to insertion and a warning is generated,
+ regardless of the SQL mode in use. Prior to MySQL
+ 5.1.23-ndb-6.3.11 and MySQL 5.1.24, truncation of excess
+ trailing spaces from values inserted into
+ <literal>CHAR</literal> columns was performed silently
+ regardless of the SQL mode; beginning with MySQL
+ 5.1.23-ndb-6.3.11 and MySQL 5.1.24, a warning is issued in such
+ cases (also without regard to the SQL mode in effect). (Bug
+ #30059)
+ </para>
+
+ <para>
<literal>VARCHAR</literal> values are not padded when they are
stored. Trailing spaces are retained when values are stored and
retrieved, in conformance with standard SQL.
@@ -4330,6 +4343,13 @@
</para>
<para>
+ Beginning with MySQL 5.1.23-ndb-6.3.11 and MySQL 5.1.24,
+ truncation of excess trailing spaces from values to be inserted
+ into <literal>TEXT</literal> columns always generates a warning,
+ regardless of the SQL mode. (Bug #30059)
+ </para>
+
+ <para>
If a <literal>TEXT</literal> column is indexed, index entry
comparisons are space-padded at the end. This means that, if the
index requires unique values, duplicate-key errors will occur
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-03-30 09:53:42 UTC (rev 10375)
+++ trunk/refman-5.1/dba-core.xml 2008-03-30 20:52:37 UTC (rev 10376)
Changed blocks: 2, Lines Added: 7, Lines Deleted: 5; 1489 bytes
@@ -6934,9 +6934,10 @@
conflict resolution and error checking.
<literal>IDEMPOTENT</literal> mode causes suppression of
some errors, including duplicate-key and no-key-found
- errors. Beginning with MySQL 5.1.24, this mode should be
- employed in multi-master replication, circular replication,
- and some other special replication scenarios.
+ errors. Beginning with MySQL 5.1.23-ndb-6.2.14,
+ 5.1.23-ndb-6.3.11, and 5.1.24, this mode should be employed
+ in multi-master replication, circular replication, and some
+ other special replication scenarios.
<literal>STRICT</literal> mode is the default, and is
suitable for most other cases.
</para>
@@ -13105,8 +13106,9 @@
<listitem>
<para>
- Beginning with MySQL 5.1.24, when a statement refers
- to one or more system variables. (Bug #31168)
+ Beginning with MySQL 5.1.23-ndb-6.3.11 and MySQL
+ 5.1.24, when a statement refers to one or more
+ system variables. (Bug #31168)
</para>
</listitem>
Modified: trunk/refman-6.0/data-types.xml
===================================================================
--- trunk/refman-6.0/data-types.xml 2008-03-30 09:53:42 UTC (rev 10375)
+++ trunk/refman-6.0/data-types.xml 2008-03-30 20:52:37 UTC (rev 10376)
Changed blocks: 2, Lines Added: 18, Lines Deleted: 0; 1558 bytes
@@ -3957,6 +3957,17 @@
</para>
<para>
+ For <literal>VARCHAR</literal> columns, excess trailing spaces
+ are truncated prior to insertion and a warning is generated,
+ regardless of the SQL mode in use. Prior to MySQL 6.0.5,
+ truncation of excess trailing spaces from values inserted into
+ <literal>CHAR</literal> columns was performed silently
+ regardless of the SQL mode; beginning with MySQL 6.0.5, a
+ warning is issued in such cases (also without regard to the SQL
+ mode in effect). (Bug #30059)
+ </para>
+
+ <para>
<literal>VARCHAR</literal> values are not padded when they are
stored. Trailing spaces are retained when values are stored and
retrieved, in conformance with standard SQL.
@@ -4322,6 +4333,13 @@
</para>
<para>
+ Beginning with MySQL 6.0.5, truncation of excess trailing spaces
+ from values to be inserted into <literal>TEXT</literal> columns
+ always generates a warning, regardless of the SQL mode. (Bug
+ #30059)
+ </para>
+
+ <para>
If a <literal>TEXT</literal> column is indexed, index entry
comparisons are space-padded at the end. This means that, if the
index requires unique values, duplicate-key errors will occur
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10376 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.0 refman-5.1 refman-6.0 | jon | 30 Mar |
