Skip navigation links
MySQL 5.0 Reference Manual :: C MySQL Change History :: C.1 Changes in Release 5.0.x (Production) :: C.1.14 Release Notes for MySQL Enterprise 5.0.80 [MRU] (01 May 2009)
C.1.15 Release Notes for MySQL Enterprise 5.0.79 [MRU] (09 March 2009) »
Section Navigation      [Toggle]

C.1.14. Release Notes for MySQL Enterprise 5.0.80 [MRU] (01 May 2009)

This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.

This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.79). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.

Support Ending for AIX 5.2: Per the http://www.mysql.com/about/legal/lifecycle/ regarding ending support for OS versions that have reached vendor end of life, we plan to discontinue building or supporting MySQL binaries for AIX 5.2 as of April 30, 2009. This release of MySQL 5.0 (5.0.80) is the last MySQL 5.0 release with support for AIX 5.2. For more information, see the March 24, 2009 note at MySQL Product Support EOL Announcements.

Functionality added or changed:

  • The MD5 algorithm now uses the Xfree implementation. (Bug#42434)

Bugs fixed:

  • Replication: An INSERT DELAYED into a TIMESTAMP column issued concurrently with an insert on the same column not using DELAYED, but applied after the other insert, was logged using the same timestamp as generated by the other (non-DELAYED) insert. (Bug#41719)

  • An attempt by a user who did not have the SUPER privilege to kill a system thread could cause a server crash. (Bug#43748)

  • Use of USE INDEX hints could cause EXPLAIN EXTENDED to crash. (Bug#43354)

  • mysql crashed if a request for the current database name returned an empty result, such as after the client has executed a preceding SET sql_select_limit=0 statement. (Bug#43254)

  • The strings/CHARSET_INFO.txt file was not included in source distributions. (Bug#42937)

  • mysqldump included views that were excluded with the --ignore-table option. (Bug#42635)

  • Passing an unknown time zone specification to CONVERT_TZ() resulted in a memory leak. (Bug#42502)

  • The MySQL Instance Configuration Wizard would fail to start correctly on Windows Vista. (Bug#42386)

  • With more than two arguments, LEAST(), GREATEST(), and CASE could unnecessarily return Illegal mix of collations errors. (Bug#41627)

  • The mysql client could misinterpret its input if a line was longer than an internal buffer. (Bug#41486)

  • In the help command output displayed by mysql, the description for the \c (clear) command was misleading. (Bug#41268)

  • When running the MySQL Instance Configuration Wizard in command-line only mode, the service name would be ignored (effectively creating all instances with the default MySQL service name), irrespective of the name specified on the command line. However, the wizard would attempt to start the service with the specified name, and would fail. (Bug#38379)

  • The use of NAME_CONST() can result in a problem for CREATE TABLE ... SELECT statements when the source column expressions refer to local variables. Converting these references to NAME_CONST() expressions can result in column names that are different on the master and slave servers, or names that are too long to be legal column identifiers. A workaround is to supply aliases for columns that refer to local variables.

    Now a warning is issued in such cases that indicate possible problems. (Bug#35383)

  • CHECK TABLE, REPAIR TABLE, ANALYZE TABLE, and OPTIMIZE TABLE erroneously reported a table to be corrupt if the table did not exist or the statement was terminated with KILL. (Bug#29458)

  • The Time column for SHOW PROCESSLIST output now can have negative values. Previously, the column was unsigned and negative values were displayed incorrectly as large positive values. Negative values can occur if a thread alters the time into the future with SET TIMESTAMP = value or the thread is executing on a slave and processing events from a master that has its clock set ahead of the slave. (Bug#22047)

  • Restoring a mysqldump dump file containing FEDERATED tables failed because the file contained the data for the table. Now only the table definition is dumped (because the data is located elsewhere). (Bug#21360)