Skip navigation links

Additional languages
MySQL 3.23, 4.0, 4.1 Reference Manual :: B MySQL Change History :: B.2 Changes in release 4.0.x :: B.2.1 Changes in release 4.0.31 (Not yet released)
B.2.2 Changes in release 4.0.30 (12 February 2007) »
Section Navigation      [Toggle]

B.2.1. Changes in release 4.0.31 (Not yet released)

End of Product Lifecycle. Active development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.0 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. 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.

Bugs fixed:

  • Security Fix: Using RENAME TABLE against a table with explicit DATA DIRECTORY and INDEX DIRECTORY options can be used to overwrite system table information by replacing the symbolic link points. the file to which the symlink points.

    MySQL will now return an error when the file to which the symlink points already exists. (Bug#321111, CVE-2007-5969)

  • Error returns from the time() system call were ignored. (Bug#27198)