Go to the first, previous, next, last section, table of contents.


D MySQL Change History

This appendix lists the changes from version to version in the MySQL source code.

We are now working actively on MySQL 4.1 & 5.0 and will only provide critical bug fixes for MySQL 4.0 and MySQL 3.23. We update this section as we add new features, so that everybody can follow the development.

Our TODO section contains what further plans we have for 4.1 & 5.0. See section 1.9 MySQL and The Future (The TODO).

Note that we tend to update the manual at the same time we make changes to MySQL. If you find a version listed here that you can't find on the MySQL download page (http://www.mysql.com/downloads/), this means that the version has not yet been released!

D.1 Changes in release 5.0.0 (Development)

Version 5.0 is for the moment only available on for MySQL developers. It will be publicly available as soon we are confident that the base for stored procedures is sound and working.

The following changelog shows what is already done in the 5.0 tree:

D.2 Changes in release 4.1.x (Alpha)

Version 4.1 of the MySQL server includes many enhancements and new features: This version is available from our public BitKeeper tree (sources) and will be available as a binary shortly.

For a full list of changes, please refer to the changelog sections for each individual 4.1.x release.

D.2.1 Changes in release 4.1.0

D.3 Changes in release 4.0.x (Production)

Version 4.0 of the MySQL server includes many enhancements and new features:

For a full list of changes, please refer to the changelog sections for each individual 4.0.x release.

D.3.1 Changes in release 4.0.13 (not released yet)

Functionality added or changed:

Bugs fixed:

D.3.2 Changes in release 4.0.12 (15 Mar 2003: Production)

Functionality added or changed:

Bugs fixed:

D.3.3 Changes in release 4.0.11 (20 Feb 2003)

Functionality added or changed:

Bugs fixed:

D.3.4 Changes in release 4.0.10 (29 Jan 2003)

Functionality added or changed:

Bugs fixed:

D.3.5 Changes in release 4.0.9 (09 Jan 2003)

Functionality added or changed:

Bugs fixed:

D.3.6 Changes in release 4.0.8 (07 Jan 2003)

Functionality added or changed:

Bugs fixed:

D.3.7 Changes in release 4.0.7 (20 Dec 2002)

Functionality added or changed:

Bugs fixed:

D.3.8 Changes in release 4.0.6 (14 Dec 2002: Gamma)

Functionality added or changed:

Bugs fixed:

D.3.9 Changes in release 4.0.5 (13 Nov 2002)

Functionality added or changed:

Bugs fixed:

D.3.10 Changes in release 4.0.4 (29 Sep 2002)

D.3.11 Changes in release 4.0.3 (26 Aug 2002: Beta)

D.3.12 Changes in release 4.0.2 (01 Jul 2002)

D.3.13 Changes in release 4.0.1 (23 Dec 2001)

D.3.14 Changes in release 4.0.0 (Oct 2001: Alpha)

D.4 Changes in release 3.23.x (Recent; still supported)

Please note that since release 4.0 is now production level, only critical fixes are done in the 3.23 release series. You are recommended to upgrade when possible, to take advantage of all speed and feature improvements in 4.0. See section 2.5.3 Upgrading From Version 3.23 to 4.0.

The 3.23 release has several major features that are not present in previous versions. We have added three new table types:

MyISAM
A new ISAM library which is tuned for SQL and supports large files.
InnoDB
A transaction-safe storage engine that supports row level locking, and many Oracle-like features.
BerkeleyDB or BDB
Uses the Berkeley DB library from Sleepycat Software to implement transaction-safe tables.

Note that only MyISAM is available in the standard binary distribution.

The 3.23 release also includes support for database replication between a master and many slaves, full-text indexing, and much more.

All new features are being developed in the 4.x version. Only bug fixes and minor enhancements to existing features will be added to 3.23.

The replication code and BerkeleyDB code is still not as tested and as the rest of the code, so we will probably need to do a couple of future releases of 3.23 with small fixes for this part of the code. As long as you don't use these features, you should be quite safe with MySQL 3.23!

Note that the above doesn't mean that replication or Berkeley DB don't work. We have done a lot of testing of all code, including replication and BDB without finding any problems. It only means that not as many users use this code as the rest of the code and because of this we are not yet 100% confident in this code.

D.4.1 Changes in release 3.23.57 (not released yet)

D.4.2 Changes in release 3.23.56 (13 Mar 2003)

D.4.3 Changes in release 3.23.55 (23 Jan 2003)

D.4.4 Changes in release 3.23.54 (05 Dec 2002)

D.4.5 Changes in release 3.23.53 (09 Oct 2002)

D.4.6 Changes in release 3.23.52 (14 Aug 2002)

D.4.7 Changes in release 3.23.51 (31 May 2002)

D.4.8 Changes in release 3.23.50 (21 Apr 2002)

D.4.9 Changes in release 3.23.49

D.4.10 Changes in release 3.23.48 (07 Feb 2002)

D.4.11 Changes in release 3.23.47 (27 Dec 2001)

D.4.12 Changes in release 3.23.46 (29 Nov 2001)

D.4.13 Changes in release 3.23.45 (22 Nov 2001)

D.4.14 Changes in release 3.23.44 (31 Oct 2001)

The following changes are for InnoDB tables:

D.4.15 Changes in release 3.23.43 (04 Oct 2001)

D.4.16 Changes in release 3.23.42 (08 Sep 2001)

D.4.17 Changes in release 3.23.41 (11 Aug 2001)

D.4.18 Changes in release 3.23.40

D.4.19 Changes in release 3.23.39 (12 Jun 2001)

D.4.20 Changes in release 3.23.38 (09 May 2001)

D.4.21 Changes in release 3.23.37 (17 Apr 2001)

D.4.22 Changes in release 3.23.36 (27 Mar 2001)

D.4.23 Changes in release 3.23.35 (15 Mar 2001)

D.4.24 Changes in release 3.23.34a

D.4.25 Changes in release 3.23.34 (10 Mar 2001)

D.4.26 Changes in release 3.23.33 (09 Feb 2001)

D.4.27 Changes in release 3.23.32 (22 Jan 2001: Production)

D.4.28 Changes in release 3.23.31 (17 Jan 2001)

D.4.29 Changes in release 3.23.30 (04 Jan 2001)