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)
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
The MySQL Instance Configuration Wizard failed to start correctly on Windows Vista. (Bug #42386)
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 failed.
USE INDEX hints could cause
EXPLAIN EXTENDED to crash.
mysqldump included views that were excluded
strings/CHARSET_INFO.txt file was not
included in source distributions.
help command output displayed by
mysql, the description for the
clear) command was
An attempt by a user who did not have the
SUPER privilege to kill a system
thread could cause a server crash.
mysql crashed if a request for the current
database name returned an empty result, such as after the client
has executed a preceding
Passing an unknown time zone specification to
CONVERT_TZ() resulted in a memory
The use of
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)
The mysql client could misinterpret its input if a line was longer than an internal buffer. (Bug #41486)
Time column for
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 =
or the thread is
executing on a slave and processing events from a master that
has its clock set ahead of the slave.
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).