List:Commits« Previous MessageNext Message »
From:stefan Date:January 9 2007 9:13am
Subject:svn commit - mysqldoc@docsrva: r4404 - trunk/refman-5.0
View as plain text  
Author: shinz
Date: 2007-01-09 10:13:15 +0100 (Tue, 09 Jan 2007)
New Revision: 4404

Log:
Merged ES 5.0.28-32 release notes into CS 5.0.33 release notes; added disclaimer that there are no binaries, just source tarballs we release for 5.0.33; added release date for 5.0.32 (20 December 2006, as per J?\195?\182rg)

Modified:
   trunk/refman-5.0/releasenotes-cs-5.0.xml
   trunk/refman-5.0/releasenotes-es-5.0.xml


Modified: trunk/refman-5.0/releasenotes-cs-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-cs-5.0.xml	2007-01-08 22:33:05 UTC (rev 4403)
+++ trunk/refman-5.0/releasenotes-cs-5.0.xml	2007-01-09 09:13:15 UTC (rev 4404)
Changed blocks: 1, Lines Added: 1709, Lines Deleted: 0; 58252 bytes

@@ -26,6 +26,1715 @@
     earlier versions, see <xref linkend="news"/>.
   </para>
 
+  <section id="releasenotes-cs-5-0-33">
+    
+    <title>Release Notes for MySQL Community Server 5.0.33 (Not yet released)</title>
+    
+    <para role="release-level">
+      This is a bugfix release for the current production release
+      family. It replaces MySQL 5.0.27.
+    </para>
+    
+    <note>
+      <para>
+        This version of MySQL Community Server has been released as a
+        source tarball only; there are no binaries built by MySQL.
+      </para>
+    </note>
+    
+    <para>
+      Functionality added or changed:
+    </para>
+    
+    <itemizedlist>
+      
+      <!-- From 5.0.32 (begin) -->
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Setting the configuration
+          parameter <literal>LockPagesInMainMemory</literal> had no
+          effect. (Bug #24461)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: It is now possible to create a
+          unique hashed index on a column that is not defined as
+          <literal>NOT NULL</literal>. <emphasis>Note that this change
+            applies only to tables using the <literal>NDB</literal>
+            storage engine</emphasis>.
+        </para>
+        
+        <para>
+          Unique indexes on columns in <literal>NDB</literal> tables do
+          not store null values because they are mapped to primary keys
+          in an internal index table (and primary keys cannot contain
+          nulls).
+        </para>
+        
+        <para>
+          Normally, an additional ordered index is created when one
+          creates unique indexes on <literal>NDB</literal> table
+          columns; this can be used to search for
+          <literal>NULL</literal> values. However, if <literal>USING
+            HASH</literal> is specified when such an index is created, no
+          ordered index is created.
+        </para>
+        
+        <para>
+          The reason for permitting unique hash indexes with null values
+          is that, in some cases, the user wants to save space if a
+          large number of records are pre-allocated but not fully
+          initialized. This also assumes that the user will
+          <emphasis>not</emphasis> try to search for null values. Since
+          MySQL does not support indexes that are not allowed to be
+          searched in some cases, the <literal>NDB</literal> storage
+          engine uses a full table scan with pushed conditions for the
+          referenced index columns to return the correct result.
+        </para>
+        
+        <para>
+          Note that a warning is returned if one creates a unique
+          nullable hash index, since the query optimizer should be
+          provided a hint not to use it with <literal>NULL</literal>
+          values if this can be avoided.
+        </para>
+        
+        <para>
+          (Bug #21507)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>DROP TRIGGER</literal> now supports an <literal>IF
+            EXISTS</literal> clause. (Bug #23703)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <literal>Com_create_user</literal> status variable was
+          added (for counting <literal>CREATE USER</literal>
+          statements). (Bug #22958)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <option>--memlock</option> option relies on system calls
+          that are unreliable on some operating systems. If a crash
+          occurs, the server now checks whether
+          <option>--memlock</option> was specified and if so issues some
+          information about possible workarounds. (Bug #22860)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The bundled yaSSL library was upgraded to version 1.5.0.
+        </para>
+      </listitem>
+      <!-- From 5.0.32 (end) -->
+      
+      <!-- From 5.0.30 (begin) -->
+      <listitem>
+        <para>
+          If the user specified the server options
+          <option>--max-connections=<replaceable>N</replaceable></option>
+          or
+          <option>--table-open-cache=<replaceable>M</replaceable></option>,
+          a warning would be given in some cases that some values were
+          recalculated, with the result that
+          <option>--table-open-cache</option> could be assigned greater
+          value.
+        </para>
+        
+        <para>
+          It should be noted that, in such cases, both the warning and
+          the increase in the <option>--table-open-cache</option> value
+          were completely harmless. Note also that it is not possible
+          for the MySQL Server to predict or to control limitations on
+          the maximum number of open files, since this is determined by
+          the operating system.
+        </para>
+        
+        <para>
+          The recalculation code has now been fixed to ensure that the
+          value of <option>--table-open-cache</option> is no longer
+          increased automatically, and that a warning is now given only
+          if some values had to be decreased due to operating system
+          limits.
+        </para>
+        
+        <para>
+          (Bug #21915)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The <literal>HELP</literal>
+          command in the Cluster management client now provides
+          command-specific help. For example, <literal>HELP
+            RESTART</literal> in <command>ndb_mgm</command> provides
+          detailed information about the <literal>START</literal>
+          command. (Bug #19620)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Added the --bind-address
+          option for <command>ndbd</command>. This allows a data node
+          process to be bound to a specific network interface. (Bug
+          #22195)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
+          <literal>Ndb_number_of_storage_nodes</literal> system variable
+          was renamed to <literal>Ndb_number_of_data_nodes</literal>.
+          (Bug #20848)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
+          <command>ndb_config</command> utility now accepts
+          <option>-c</option> as a short form of the
+          <option>--ndb-connectstring</option> option. (Bug #22295)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>SHOW STATUS</literal> is no longer logged to the slow
+          query log. (Bug #19764)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <command>mysqldump --single-transaction</command> now uses
+          <literal>START TRANSACTION /*!40100 WITH CONSISTENT SNAPSHOT
+            */</literal> rather than <literal>BEGIN</literal> to start a
+          transaction, so that a consistent snapshot will be used on
+          those servers that support it. (Bug #19660)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>mysql_upgrade</literal> now passes all the parameters
+          specified on the command line to both
+          <literal>mysqlcheck</literal> and <literal>mysql</literal>
+          using the <filename>upgrade_defaults</filename> file. (Bug
+          #20100)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          For the <literal>CALL</literal> statement, stored procedures
+          that take no arguments now can be invoked without parentheses.
+          That is, <literal>CALL p()</literal> and <literal>CALL
+            p</literal> are equivalent. (Bug #21462)
+        </para>
+      </listitem>
+      <!-- From 5.0.30 (end) -->
+
+      <!-- From 5.0.28 (begin) -->
+      <!-- There weren't any functionality changes  in 5.0.28 -->
+      <!-- From 5.0.28 (end) -->
+
+    </itemizedlist>
+    
+    <para>
+      Bugs fixed:
+    </para>
+    
+    <itemizedlist>
+      
+      <!-- From 5.0.32 (begin) -->
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Sudden disconnection of an SQL
+          or data node could lead to shutdown of data nodes with the
+          error <errortext>failed ndbrequire</errortext>. (Bug #24447)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <command>ndb_config</command>
+          failed when trying to use 2 management servers and node IDs.
+          (Bug #23887)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Cluster APIs): Using
+          <literal>BIT</literal> values with any of the comparison
+          methods of the <literal>NdbScanFilter</literal> class caused
+          the cluster's data nodes to fail. (Bug #24503)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The failure of a data node
+          failure during a schema operation could lead to additional
+          node failures. (Bug #24752)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: A committed read could be
+          attempted before a data node had time to connect, causing a
+          timeout error. (Bug #24717)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Cluster APIs): Some MGM API
+          function calls could yield incorrect return values in certain
+          cases where the cluster was operating under a very high load,
+          or experienced timeouts in inter-node communications. (Bug
+          #24011)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: A unique constraint violation
+          was not ignored by an <literal>UPDATE IGNORE</literal>
+          statement when the constraint violation occurred on a
+          non-primary key. (Bug #18487, Bug #24303)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The stack size for NetWare binaries was increased to 128KB to
+          prevent problems caused by insufficient stack size. (Bug
+          #23504)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Attempting to use a view containing <literal>DEFINER</literal>
+          information for a non-existent user resulted in an error
+          message that revealed the definer account. Now the definer is
+          revealed only to superusers. Other users receive only an
+          <literal>access denied</literal> message. (Bug #17254)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <command>mysql_upgrade</command> failed if the
+          <literal>--password</literal> (or <option>-p</option>) option
+          was given. (Bug #24896)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          For a nonexistent table, <literal>DROP TEMPORARY
+            TABLE</literal> failed with an incorrect error message if
+          <literal>read_only</literal> was enabled. (Bug #22077)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The code for generating <literal>USE</literal> statements for
+          binary logging of <literal>CREATE PROCEDURE</literal>
+          statements resulted in confusing output from
+          <command>mysqlbinlog</command> for <literal>DROP
+            PROCEDURE</literal> statements. (Bug #22043)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <literal>InnoDB</literal> mutex structure was simplified
+          to reduce memory load. (Bug #24386)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <literal>REPEAT()</literal> function could return
+          <literal>NULL</literal> when passed a column for the count
+          argument. (Bug #24947)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Accuracy was improved for comparisons between
+          <literal>DECIMAL</literal> columns and numbers represented as
+          strings. (Bug #23260)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>InnoDB</literal> crashed while performing XA recovery
+          of prepared transactions. (Bug #21468)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>ROW_COUNT()</literal> did not work properly as an
+          argument to a stored procedure. (Bug #23760)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The size of <literal>MEMORY</literal> tables and internal
+          temporary tables was limited to 4GB on 64-bit Windows systems.
+          (Bug #24052)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          For queries that select from a view, the server was returning
+          <literal>MYSQL_FIELD</literal> metadata inconsistently for
+          view names and table names. For view columns, the server now
+          returns the view name in the <literal>table</literal> field
+          and, if the column selects from an underlying table, the table
+          name in the <literal>org_table</literal> field. (Bug #20191)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          It was possible to use <literal>DATETIME</literal> values
+          whose year, month, and day parts were all zeroes but whose
+          hour, minute, and second parts contained nonzero values, an
+          example of such an illegal <literal>DATETIME</literal> being
+          <literal>'0000-00-00 11:23:45'</literal>. (Bug #21789)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          It was possible to set the backslash character
+          (<quote><literal>\</literal></quote>) as the delimiter
+          character using <literal>DELIMITER</literal>, but not actually
+          possible to use it as the delimiter. (Bug #21412)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The loose index scan optimization for <literal>GROUP
+            BY</literal> with <literal>MIN</literal> or
+          <literal>MAX</literal> was not applied within other queries,
+          such as <literal>CREATE TABLE ... SELECT ...</literal>,
+          <literal>INSERT ... SELECT ...</literal>, or in the
+          <literal>FROM</literal> clauses of subqueries. (Bug #24156)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>ALTER ENABLE KEYS</literal> or <literal>ALTER TABLE
+            DISABLE KEYS</literal> combined with another <literal>ALTER
+            TABLE</literal> option other than <literal>RENAME TO</literal>
+          did nothing. In addition, if ALTER TABLE was used on a table
+          having disabled keys, the keys of the resulting table were
+          enabled. (Bug #24395)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Queries using a column alias in an expression as part of an
+          <literal>ORDER BY</literal> clause failed, an example of such
+          a query being <literal>SELECT mycol + 1 AS mynum FROM mytable
+            ORDER BY 30 - mynum</literal>. (Bug #22457)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Trailing spaces were not removed from Unicode
+          <literal>CHAR</literal> column values when used in indexes.
+          This resulted in excessive usage of storage space, and could
+          affect the results of some <literal>ORDER BY</literal> queries
+          that made use of such indexes.
+        </para>
+        
+        <para>
+          <emphasis role="bold">Note</emphasis>: When upgrading, it is
+          necessary to re-create any existing indexes on Unicode
+          <literal>CHAR</literal> columns in order to take advantage of
+          the fix. This can be done by using a <literal>REPAIR
+            TABLE</literal> statement on each affected table.
+        </para>
+        
+        <para>
+          (Bug #22052)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Warnings were generated when explicitly casting a character to
+          a number (for example, <literal>CAST('x' AS
+            SIGNED)</literal>), but not for implicit conversions in simple
+          arithmetic operations (such as <literal>'x' + 0</literal>).
+          Now warnings are generated in all cases. (Bug #11927)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>STR_TO_DATE()</literal> returned
+          <literal>NULL</literal> if the format string contained a space
+          following a non-format character. (Bug #22029)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          yaSSL crashed on pre-Pentium Intel CPUs. (Bug #21765)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Selecting into variables sometimes returned incorrect wrong
+          results. (Bug #20836)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Inserting <literal>DEFAULT</literal> into a column with no
+          default value could result in garbage in the column. Now the
+          same result occurs as when inserting <literal>NULL</literal>
+          into a <literal>NOT NULL</literal> column. (Bug #20691)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <filename>mysql_fix_privilege_tables.sql</filename> altered
+          the <literal>table_privs.table_priv</literal> column to
+          contain too few privileges, causing loss of the
+          <literal>CREATE VIEW</literal> and <literal>SHOW
+            VIEW</literal> privileges. (Bug #20589)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A query with a subquery that references columns of a view from
+          the outer <literal>SELECT</literal> could return an incorrect
+          result if used from a prepared statement. (Bug #20327)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A server crash occurred when using <literal>LOAD
+            DATA</literal> to load a table containing a <literal>NOT
+            NULL</literal> spatial column, when the statement did not load
+          the spatial column. Now a <literal>NULL supplied to NOT NULL
+            column</literal> error occurs. (Bug #22372)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Unsigned <literal>BIGINT</literal> values treated as signed
+          values by the <literal>MOD()</literal> function. (Bug #19955)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Compiling PHP 5.1 with the MySQL static libraries failed on
+          some versions of Linux. (Bug #19817)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <literal>DELIMITER</literal> statement did not work
+          correctly when used in an SQL file run using the
+          <literal>SOURCE</literal> statement. (Bug #19799)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>VARBINARY</literal> column values inserted on a MySQL
+          4.1 server had trailing zeroes following upgrade to MySQL 5.0
+          or later. (Bug #19371)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Constant expressions and some numeric constants used as input
+          parameters to user-defined functions were not treated as
+          constants. (Bug #18761)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Subqueries of the form <literal>NULL IN (SELECT ...)</literal>
+          returned invalid results. (Bug #8804, Bug #23485)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <option>--extern</option> option for
+          <command>mysql-test-run.pl</command> did not function
+          correctly. (Bug #24354)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>INET_ATON()</literal> returned a signed
+          <literal>BIGINT</literal> value, not an unsigned value. (Bug
+          #21466)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>ALTER TABLE</literal> statements that performed both
+          <literal>RENAME TO</literal> and <literal>{ENABLE|DISABLE}
+            KEYS</literal> operations caused a server crash. (Bug #24089)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <command>myisampack</command> wrote to unallocated memory,
+          causing a crash. (Bug #17951)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Some small double precision numbers (such as
+          <literal>1.00000001e-300</literal>) that should have been
+          accepted were truncated to zero. (Bug #22129)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <command>mysql.server</command> script used the
+          <command>source</command> command, which is less portable than
+          the <command>.</command> command; it now uses
+          <command>.</command> instead. (Bug #24294)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>DATE_ADD()</literal> requires complete dates with no
+          <quote>zero</quote> parts, but sometimes did not return
+          <literal>NULL</literal> when given such a date. (Bug #22229)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Using <literal>FLUSH TABLES</literal> in one connection while
+          another connection is using <literal>HANDLER</literal>
+          statements caused a server crash. (Bug #21587)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>FLUSH LOGS</literal> or <command>mysqladmin
+            flush-logs</command> caused a server crash if the binary log
+          was not open. (Bug #17733)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Subqueries for which a pushed-down condition did not produce
+          exactly one key field could cause a server crash. (Bug #24056)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>LAST_DAY('0000-00-00')</literal> could cause a server
+          crash. (Bug #23653)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Through the C API, the member strings in
+          <literal>MYSQL_FIELD</literal> for a query that contains
+          expressions may return incorrect results. (Bug #21635)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>mysql_affected_rows()</literal> could return values
+          different from <literal>mysql_stmt_affected_rows()</literal>
+          for the same sequence of statements. (Bug #23383)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>IN()</literal> and <literal>CHAR()</literal> can
+          return <literal>NULL</literal>, but did not signal that to the
+          query processor, causing incorrect results for <literal>IS
+            NULL</literal> operations. (Bug #17047)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A trigger that invoked a stored function could cause a server
+          crash when activated by different client connections. (Bug
+          #23651)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>CONCURRENT</literal> did not work correctly for
+          <literal>LOAD DATA INFILE</literal>. (Bug #20637)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Inserting a default or invalid value into a spatial column
+          could fail with <literal>Unknown error</literal> rather than a
+          more appropriate error. (Bug #21790)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The server could send incorrect column count information to
+          the client for queries that produce a larger number of columns
+          than can fit in a two-byte number. (Bug #19216)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Evaluation of subqueries that require the filesort algorithm
+          were allocating and freeing the
+          <literal>sort_buffer_size</literal> buffer many times,
+          resulting in slow performance. Now the buffer is allocated
+          once and reused. (Bug #21727)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          SQL statements close to the size of
+          <literal>max_allowed_packet</literal> could produce binary log
+          events larger than <literal>max_allowed_packet</literal> that
+          could not be read by slave servers. (Bug #19402)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          View columns were always handled as having implicit
+          derivation, leading to <literal>illegal mix of collation
+            errors</literal> for some views in <literal>UNION</literal>
+          operations. Now view column column derivation comes from the
+          original expression given in the view definition. (Bug #21505)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          If elements in a non-top-level <literal>IN</literal> subquery
+          were accessed by an index and the subquery result set included
+          a <literal>NULL</literal> value, the quantified predicate that
+          contained the subquery was evaluated to
+          <literal>NULL</literal> when it should return a
+          non-<literal>NULL</literal> value. (Bug #23478)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Calculation of <literal>COUNT(DISTINCT)</literal>,
+          <literal>AVG(DISTINCT)</literal>, or
+          <literal>SUM(DISTINCT)</literal> when they are referenced more
+          than once in a single query with <literal>GROUP BY</literal>
+          could cause a server crash. (Bug #23184)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          For a cast of a <literal>DATETIME</literal> value containing
+          microseconds to <literal>DECIMAL</literal>, the microseconds
+          part was truncated without generating a warning. Now the
+          microseconds part is preserved. (Bug #19491)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Metadata for columns calculated from scalar subqueries was
+          limited to integer, double, or string, even if the actual type
+          of the column was different. (Bug #11032)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The result for <literal>CAST()</literal> when casting a value
+          to <literal>UNSIGNED</literal> was limited to the maximum
+          signed <literal>BIGINT</literal> value, not the maximum
+          unsigned value. (Bug #8663)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Using <literal>EXPLAIN</literal> caused a server crash for
+          queries that selected from
+          <literal>INFORMATION_SCHEMA</literal> in a subquery in the
+          <literal>FROM</literal> clause. (Bug #22413)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Invalidating the query cache caused a server crash for
+          <literal>INSERT INTO ... SELECT</literal> statements that
+          selected from a view. (Bug #20045)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Slave servers would retry the execution of a SQL statement an
+          infinite number of times, ignoring the value
+          <literal>SLAVE_TRANSACTION_RETRIES</literal> when using the
+          NDB engine. (Bug #16228)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          On slave servers, transactions that exceeded the lock wait
+          timeout failed to roll back properly. (Bug #20697)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Changes to character set variables prior to an action on a
+          replication-ignored table were forgotten by slave servers.
+          (Bug #22877)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          With <literal>lower_case_table_names</literal> set to 1,
+          <literal>SHOW CREATE TABLE</literal> printed incorrect output
+          for table names containing Turkish I (LATIN CAPITAL LETTER I
+          WITH DOT ABOVE). (Bug #20404)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          When applying the <literal>group_concat_max_len</literal>
+          limit, <literal>GROUP_CONCAT()</literal> could truncate
+          multi-byte characters in the middle. (Bug #23451)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          For some problems relating to character set conversion or
+          incorrect string values for <literal>INSERT</literal> or
+          <literal>UPDATE</literal>, the server was reporting truncation
+          or length errors instead. (Bug #18908)
+        </para>
+      </listitem>
+      <!-- From 5.0.32 (end) -->
+      
+      <!-- From 5.0.30 (begin) -->
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Data nodes added while the
+          cluster was running in single user mode were all assigned node
+          ID 0, which could later cause multiple node failures. Adding
+          of nodes in single user mode is no longer possible. (Bug
+          #20395)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Attempting to create an
+          <literal>NDB</literal> table on a MySQL with an existing
+          non-Cluster table with the same name in the same database
+          could result in data loss or corruption. MySQL now issues a
+          warning when a <literal>SHOW TABLES</literal> or other
+          statement causing table discovery finds such a table. (Bug
+          #21378)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (NDB API): Inacivity timeouts
+          for scans were not correctly handled. (Bug #23107)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (NDB API): Attempting to read a
+          nonexistent tuple using <literal>Commit</literal> mode for
+          <literal>NdbTransaction::execute()</literal> caused node
+          failures. (Bug #22672)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (NDB API): Scans closed before
+          being executed were still placed in the send queue. (Bug
+          #21941)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (NDB API): The
+          <literal>NdbOperation::getBlobHandle()</literal> method, when
+          called with the name of a nonexistent column, caused a
+          segmentation fault. (Bug #21036)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: A problem with takeover during
+          a system restart caused ordered indexes to be rebuilt
+          incorrectly. (Bug #15303)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
+          <command>ndb_config</command> utility did not perform host
+          lookups correctly when using the <option>--host</option>
+          option. (Bug #17582)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The
+          <command>ndb_config</command> utility did not perform host
+          lookups correctly when using the <option>--host</option>
+          option (Bug #17582)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The error returned by the
+          cluster when too many nodes were defined did not make clear
+          the nature of the problem. (Bug #19045)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <command>ndb_mgm -e show |
+            head</command> would hang after displaying the first 10 lines
+          of output. (Bug #19047)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: In rare situations with
+          resource shortages, a crash could result from insufficient
+          <literal>IndexScanOperations</literal>. (Bug #19198)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <command>ndb_restore</command>
+          did not always make clear that it had recovered successfully
+          from temporary errors while restoring a cluster backup. (Bug
+          #19651)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Error messages given when
+          trying to make online changes parameters such as
+          <literal>NoOfReplicas</literal> thast can only be changed via
+          a complete shutdown and restart of the cluster did not
+          indicate the true nature of the problem. (Bug #19787)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Following the restart of an
+          MGM node, the Cluster management client did not automatically
+          reconnect. (Bug #19873)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: In some cases where
+          <literal>SELECT COUNT(*)</literal> from an
+          <literal>NDB</literal> table should have yielded an error,
+          <literal>MAX_INT</literal> was returned instead. (Bug #19914)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (NDB API): When multiple
+          processes or threads in parallel performed the same ordered
+          scan with exclusive lock and updating the retrieved records,
+          the scan could skip some records, which were not updated as a
+          result. (Bug #20446)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Using an invalid node ID with
+          the management client <literal>STOP</literal> command could
+          cause <command>ndb_mgm</command> to hang. (Bug #20575)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Under some circumstances,
+          local checkpointing would hang, keeping any unstarted nodes
+          from being started. (Bug #20895)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Condition pushdown did not
+          work correctly with <literal>DATETIME</literal> columns. (Bug
+          #21056)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: When inserting a row into an
+          <literal>NDB</literal> table with a duplicate value for a
+          non-primary unique key, the error issued would reference the
+          wrong key. (Bug #21072)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Cluster logs were not rotated
+          following the first rotation cycle. (Bug #21345)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The <command>ndb_mgm</command>
+          management client did not set the exit status on errors,
+          always returning 0 instead. (Bug #21530)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Partition distribution keys
+          were updated only for the primary and starting replicas during
+          node recovery. This could lead to node failure recovery for
+          clusters having an odd number of replicas. (Bug #21535)
+        </para>
+        
+        <para>
+          <emphasis role="bold">Note</emphasis>: We recommend values for
+          <literal>NumberOfReplicas</literal> that are even powers of 2,
+          for best results.
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The output for the
+          <option>--help</option> option used with
+          <literal>NDB</literal> executable programs
+          (<command>ndbd</command>, <command>ndb_mgm</command>,
+          <command>ndb_restore</command>, <command>ndb_config</command>,
+          and so on) referred to the <filename>Ndb.cfg</filename> file,
+          instead of <filename>my.cnf</filename>. (Bug #21585)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The node recovery algorithm
+          was missing a version check for tables in the
+          <literal>ALTER_TABLE_COMMITTED</literal> state (as opposed to
+          the <literal>TABLE_ADD_COMMITTED</literal> state, which has
+          the version check). This could cause inconsistent schemas
+          across nodes following node recovery. (Bug #21756)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: A scan timeout returned Error
+          4028 (<errortext>Node failure caused abort of
+            transaction</errortext>) instead of Error 4008
+          (<errortext>Node failure caused abort of
+            transaction...</errortext>). (Bug #21799)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The <option>--help</option>
+          output from <literal>NDB</literal> binaries did not include
+          file-related options. (Bug #21994)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Multiple node restarts in
+          rapid succession could cause a system restart to fail (Bug
+          #22892), or induce a race condition (Bug #23210).
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: If a node restart could not be
+          performed from the REDO log, no node takeover took place. This
+          could cause partitions to be left empty during a system
+          restart. (Bug #22893)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <literal>INSERT ... ON
+            DUPLICATE KEY UPDATE</literal> on an <literal>NDB</literal>
+          table could lead to deadlocks and memory leaks. (Bug #23200)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: The management client command
+          <literal>ALL DUMP 1000</literal> would cause the cluster to
+          crash if data nodes were connected to the cluster but not yret
+          fully started. (Bug #23203)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Cluster backups would fail
+          when there were more than 2048 schema objects in the cluster.
+          (Bug #23499)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Restoring a cluster failed if
+          there were any tables with 128 or more columns. (Bug #23502)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The internal SQL interpreter of <literal>InnoDB</literal>
+          placed an unnecessary lock on the supremum record when
+          <literal>innodb_locks_unsafe_for_binlog=1</literal>. This
+          caused an assertion failure when <literal>InnoDB</literal> was
+          built with debugging enabled. (Bug #23769)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          If a table contains an <literal>AUTO_INCREMENT</literal>
+          column, inserting into an insertable view on the table that
+          does not include the <literal>AUTO_INCREMENT</literal> column
+          should not change the value of
+          <literal>LAST_INSERT_ID()</literal>, because the side effects
+          of inserting default values into columns not part of the view
+          should not be visible. MySQL was incorrectly setting
+          <literal>LAST_INSERT_ID()</literal> to zero. (Bug #22584)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal><replaceable>M</replaceable> % 0</literal> returns
+          <literal>NULL</literal>, but
+          (<literal><replaceable>M</replaceable> % 0) IS NULL</literal>
+          evaluated to false. (Bug #23411)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Within a stored routine, a view definition cannot refer to
+          routine parameters or local variables. However, an error did
+          not occur until the routine was called. Now it occurs during
+          parsing of the routine creation statement. (Bug #20953)
+        </para>
+        
+        <para>
+          <emphasis role="bold">Note</emphasis>: A side effect of this
+          fix is that if you have already created such routines, and
+          error will occur if you execute <literal>SHOW CREATE
+            PROCEDURE</literal> or <literal>SHOW CREATE
+            FUNCTION</literal>. You should drop these routines because
+          they are erroneous.
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A client library crash was caused by executing a statement
+          such as <literal>SELECT * FROM t1 PROCEDURE
+            ANALYSE()</literal> using a server side cursor on a table
+          <literal>t1</literal> that does not have the same number of
+          columns as the output from <literal>PROCEDURE
+            ANALYSE()</literal>. (Bug #17039)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <command>mysql</command> did not check for errors when
+          fetching data during result set printing. (Bug #22913)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Adding a day, month, or year interval to a
+          <literal>DATE</literal> value produced a
+          <literal>DATE</literal>, but adding a week interval produced a
+          <literal>DATETIME</literal> value. Now all produce a
+          <literal>DATE</literal> value. (Bug #21811)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The column default value in the output from <literal>SHOW
+            COLUMNS</literal> or <literal>SELECT FROM
+            INFORMATION_SCHEMA.COLUMNS</literal> was truncated to 64
+          characters. (Bug #23037)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          For not-yet-authenticated connections, the
+          <literal>Time</literal> column in <literal>SHOW
+            PROCESSLIST</literal> was a random value rather than
+          <literal>NULL</literal>. (Bug #23379)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <literal>Host</literal> column in <literal>SHOW
+            PROCESSLIST</literal> output was blank when the server was
+          started with the <option>--skip-grant-tables</option> option.
+          (Bug #22728)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <literal>Handler_rollback</literal> status variable
+          sometimes was incremented when no rollback had taken place.
+          (Bug #22728)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Within a prepared statement, <literal>SELECT (COUNT(*) =
+            1)</literal> (or similar use of other aggregate functions) did
+          not return the correct result for statement re-execution. (Bug
+          #21354)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Lack of validation for input and output
+          <literal>TIME</literal> values resulted in several problems:
+          <literal>SEC_TO_TIME()</literal> within subqueries incorrectly
+          clipped large values; <literal>SEC_TO_TIME()</literal> treated
+          <literal>BIGINT UNSIGNED</literal> values as signed; only
+          truncation warnings were produced when both truncation and
+          out-of-range <literal>TIME</literal> values occurred. (Bug
+          #11655, Bug #20927)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Range searches on columns with an index prefix could miss
+          records. (Bug #20732)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          With <literal>SQL_MODE=TRADITIONAL</literal>, MySQL
+          incorrectly aborted on warnings within stored routines and
+          triggers. (Bug #20028)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          In <command>mysql</command>, invoking
+          <literal>connect</literal> or <literal>\r</literal> with very
+          long <replaceable>db_name</replaceable> or
+          <replaceable>host_name</replaceable> parameters caused buffer
+          overflow. (Bug #20894)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <command>mysqldump --xml</command> produced invalid XML for
+          <literal>BLOB</literal> data. (Bug #19745)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          For a debug server, a reference to an undefined user variable
+          in a prepared statment executed with
+          <literal>EXECUTE</literal> caused an assertion failure. (Bug
+          #19356)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Within a trigger for a base table, selecting from a view on
+          that base table failed. (Bug #19111)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>DELETE IGNORE</literal> could hang for foreign key
+          parent deletes. (Bug #18819)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Transient errors in replication from master to slave may
+          trigger multiple <literal>Got fatal error 1236: 'binlog
+            truncated in the middle of event'</literal> errors on the
+          slave. (Bug #4053)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The value of the <literal>warning_count</literal> system
+          variable was not being calculated correctly (also affecting
+          <literal>SHOW COUNT(*) WARNINGS</literal>). (Bug #19024)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>InnoDB</literal> exhibited thread thrashing with more
+          than 50 concurrent connections under an update-intensive
+          workload. (Bug #22868)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>InnoDB</literal> showed substandard performance with
+          multiple queries running concurrently. (Bug #15815)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          There was a race condition in the <literal>InnoDB</literal>
+          <literal>fil_flush_file_spaces()</literal> function. (Bug
+          #24089)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>FROM_UNIXTIME()</literal> did not accept arguments up
+          to <literal>POWER(2,31)-1</literal>, which it had previously.
+          (Bug #9191)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Some yaSSL-related memory leaks detected by Valgrind were
+          fixed. (Bug #23981)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          If <literal>COMPRESS()</literal> returned
+          <literal>NULL</literal>, subsequent invocations of
+          <literal>COMPRESS()</literal> within a result set or within a
+          trigger also returned <literal>NULL</literal>. (Bug #23254)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <command>mysql</command> would lose its connection to the
+          server if its standard output was not writable. (Bug #17583)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <command>mysql-test-run</command> did not work correctly for
+          RPM-based installations. (Bug #17194)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The return value from <literal>my_seek()</literal> was
+          ignored. (Bug #22828)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Use of <literal>PREPARE</literal> with a <literal>CREATE
+            PROCEDURE</literal> statement that contained a syntax error
+          caused a server crash. (Bug #21868)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Use of a DES-encrypted SSL certificate file caused a server
+          crash. (Bug #21868)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Column names were not quoted properly for replicated views.
+          (Bug #19736)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>InnoDB</literal> used table locks (not row locks)
+          within stored functions. (Bug #18077)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Statements such as <literal>DROP PROCEDURE</literal> and
+          <literal>DROP VIEW</literal> were written to the binary log
+          too late due to a race condition. (Bug #14262)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          MySQL would fail to build on the Alpha platform. (Bug #23256)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The optimizer failed to use equality propagation for
+          <literal>BETWEEN</literal> and <literal>IN</literal>
+          predicates with string arguments. (Bug #22753)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The optimizer used the <literal>ref</literal> join type rather
+          than <literal>eq_ref</literal> for a simple join on strings.
+          (Bug #22367)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The <literal>WITH CHECK OPTION</literal> for a view failed to
+          prevent storing invalid column values for
+          <literal>UPDATE</literal> statements. (Bug #16813)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A literal string in a <literal>GROUP BY</literal> clause could
+          be interpreted as a column name. (Bug #14019)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Some queries that used <literal>MAX()</literal> and
+          <literal>GROUP BY</literal> could incorrectly return an empty
+          result. (Bug #22342)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>WITH ROLLUP</literal> could group unequal values.
+          (Bug #20825)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Use of a subquery that invoked a function in the column list
+          of the outer query resulted in a memory leak. (Bug #21798)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>LIKE</literal> searches failed for indexed
+          <literal>utf8</literal> character columns. (Bug #20471)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>FLUSH INSTANCES</literal> in Instance Manager
+          triggered an assertion failure. (Bug #19368)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>ALTER TABLE</literal> was not able to rename a view.
+          (Bug #14959)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Entries in the slow query log could have an incorrect
+          <literal>Rows_examined</literal> value. (Bug #12240)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Insufficient memory
+          (<literal>myisam_sort_buffer_size</literal>) could cause a
+          server crash for several operations on
+          <literal>MyISAM</literal> tables: repair table, create index
+          by sort, repair by sort, parallel repair, bulk insert. (Bug
+          #23175)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>OPTIMIZE TABLE</literal> with
+          <literal>myisam_repair_threads</literal> &gt; 1 could result
+          in <literal>MyISAM</literal> table corruption. (Bug #8283)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Selecting from a <literal>MERGE</literal> table could result
+          in a server crash if the underlying tables had fewer indexes
+          than the <literal>MERGE</literal> table itself. (Bug #22937)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A locking safety check in <literal>InnoDB</literal> reported a
+          spurious error <literal>stored_select_lock_type is 0 inside
+            ::start_stmt()</literal> for <literal>INSERT ...
+            SELECT</literal> statements in
+          <literal>innodb_locks_unsafe_for_binlog</literal> mode. The
+          safety check was removed. (Bug #10746)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          For multiple-table <literal>UPDATE</literal> statements,
+          storage engines were not notified of duplicate-key errors.
+          (Bug #21381)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Incorrect results could be obtained from re-execution of a
+          parametrized prepared statement or a stored routine with a
+          <literal>SELECT</literal> that uses <literal>LEFT
+            JOIN</literal> with a second table having only one row. (Bug
+          #21081)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          An <literal>UPDATE</literal> that referred to a key column in
+          the <literal>WHERE</literal> clause and activated a trigger
+          that modified the column resulted in a loop. (Bug #20670)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Creating a <literal>TEMPORARY</literal> table with the same
+          name as an existing table that was locked by another client
+          could result in a lock conflict for <literal>DROP TEMPORARY
+            TABLE</literal> because the server unnecessarily tried to
+          acquire a name lock. (Bug #21096)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          After <literal>FLUSH TABLES WITH READ LOCK</literal> followed
+          by <literal>UNLOCK TABLES</literal>, attempts to drop or alter
+          a stored routine failed with an error that the routine did not
+          exist, and attempts to execute the routine failed with a lock
+          conflict error. (Bug #21414)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>SHOW VARIABLES</literal> truncated the
+          <literal>Value</literal> field to 256 characters. (Bug #20862)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Instance Manager didn't close the client socket file when
+          starting a new <command>mysqld</command> instance.
+          <command>mysqld</command> inherited the socket, causing
+          clients connected to Instance Manager to hang. (Bug #12751)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Instance Manager had a race condition involving <command>
+            mysqld</command> PID file removal. (Bug #22379)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          It was possible for a stored routine with a
+          non-<literal>latin1</literal> name to cause a stack overrun.
+          (Bug #21311)
+        </para>
+      </listitem>
+      <!-- From 5.0.30 (end) -->
+      
+      <!-- From 5.0.28 (begin) -->
+      <listitem>
+        <para>
+          MySQL 5.0.26 introduced an ABI incompatibility, which this
+          release reverts. Programs compiled against 5.0.26 are not
+          compatible with any other version and must be recompiled. (Bug
+          #23427)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>InnoDB</literal>: Reduced optimization level for
+          Windows 64 builds to handle possible memory overrun. (Bug
+          #19424)
+        </para>
+      </listitem>
+      <!-- From 5.0.28 (end) -->
+
+    </itemizedlist>
+    
+  </section>
+  
   <section id="releasenotes-cs-5-0-27">
 
     <title>Release Notes for MySQL Community Server 5.0.27 (21 October 2006)</title>


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-01-08 22:33:05 UTC (rev 4403)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-01-09 09:13:15 UTC (rev 4404)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 600 bytes

@@ -156,7 +156,7 @@
 
   <section id="releasenotes-es-5-0-32">
 
-    <title>Release Notes for MySQL Enterprise 5.0.32 (Not yet released)</title>
+    <title>Release Notes for MySQL Enterprise 5.0.32 (20 December 2006)</title>
 
     <para role="release-level">
       This is a <emphasis>Service Pack</emphasis> release of the MySQL


Thread
svn commit - mysqldoc@docsrva: r4404 - trunk/refman-5.0stefan9 Jan