End of Product Lifecycle. Active development for MySQL Database Server version 5.0 has ended. Oracle offers various support offerings which may be of interest. For details and more information, see the MySQL section of the Lifetime Support Policy for Oracle Technology Products (http://www.oracle.com/us/support/lifetime-support/index.html). Please consider upgrading to a recent version.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server and MySQL Community Server release (5.0.88). 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.
Privileges for stored routines were ignored for mixed-case routine names. (Bug #48872)
References: See also Bug #41049.
Building MySQL on Fedora Core 12 64-bit failed, due to errors in comp_err. (Bug #48864)
DISTINCT was ignored for queries with
GROUP BY WITH ROLLUP and only
const tables. (Bug #48475)
Loose index scan was inappropriately chosen for some
WHERE conditions. (Bug #48472)
A bad typecast could cause query execution to allocate large amounts of memory. (Bug #48458)
mysql_secure_installation did not work on Solaris. (Bug #48086)
When running mysql_secure_installation, the command failed if the
root password contained multiple space,
'#', or quote characters. (Bug #48031)
InnoDB did not disallow creation of an index with the name
GEN_CLUST_INDEX, which is used internally. (Bug #46000)
InnoDB monitoring (
SHOW ENGINE INNODB STATUS or one of the
InnoDB Monitor tables) could cause a server crash due to invalid access to a shared variable in a concurrent environment. (Bug #38883)
Output from mysql --html did not encode the
'&' characters. (Bug #27884)