Skip navigation links
MySQL 5.0 Reference Manual :: C MySQL Change History
C.1 Changes in Release 5.0.x (Production) »
Section Navigation      [Toggle]

Appendix C. MySQL Change History

Table of Contents     [+/-]

C.1. Changes in Release 5.0.x (Production)     [+/-]
C.2. Changes in MySQL Cluster     [+/-]
C.3. MySQL Enterprise Monitor Change History     [+/-]
C.4. MySQL Connector/ODBC (MyODBC) Change History     [+/-]
C.5. MySQL Connector/NET Change History     [+/-]
C.6. MySQL Visual Studio Plugin Change History     [+/-]
C.7. MySQL Connector/J Change History     [+/-]
C.8. MySQL Connector/MXJ Change History     [+/-]
C.9. MySQL Proxy Change History     [+/-]

This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 5.0, which is currently MySQL 5.0.91. We offer a version of the Manual for each series of MySQL releases (5.0, 5.1, and so forth). For information about changes in another release series of the MySQL database software, see the corresponding version of this Manual.

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

We update this section as we add new features in the 5.0 series, so that everybody can follow the development process.

This section documents all enhancements, changes, and bug fixes made to MySQL Enterprise Server and MySQL Community Server.

Releases in MySQL Enterprise Server are divided into the following release packs:

  • Rapid Update Service Packs are issued once a month and incorporate all the bug fixes and security updates introduced since the previous MySQL Enterprise Server release. A single Service Pack can be used to update MySQL Enterprise Server; it is not necessary to install intervening service packs to bring your system up to date.

  • Quarterly Service Packs are issued each quarter and incorporate all the bug fixes and security updates introduced up to the Rapid Update that the QSP it is based on, and possibly some critical bug fixes and security updates from later releases. A single Service Pack can be used to update MySQL Enterprise Server; it is not necessary to install intervening service packs to bring your system up to date.

  • Hot-fix releases incorporate fixes for bugs that caused significant issues that are not released as part of a Service Pack.

Note that we tend to update the manual at the same time we make changes to MySQL. If you find a recent version of MySQL listed here that you can't find on our download page (http://dev.mysql.com/downloads/), it means that the version has not yet been released (and will normally be marked so in the appropriate Release Note section).

The date mentioned with a release version is the date of the last Bazaar commit on which the release was based, not the date when the packages were made available. The binaries are usually made available a few days after the date of the tagged ChangeSet, because building and testing all packages takes some time.

For information on how to determine your current version and release type, see Section 2.2, “Determining your current MySQL version”.

The manual included in the source and binary distributions may not be fully accurate when it comes to the release changelog entries, because the integration of the manual happens at build time. For the most up-to-date release changelog, please refer to the online version instead.