Appendix D. MySQL Change History

Table of Contents

D.1. Changes in release 5.1.x (Development)
D.1.1. Changes in release 5.1.2 (Not yet released)
D.1.2. Changes in release 5.1.1 (Not yet released)
D.2. Changes in MyODBC
D.2.1. Changes in MyODBC 3.51.12
D.2.2. Changes in MyODBC 3.51.11

This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 5.1, which is currently MySQL 5.1.2-alpha. Starting with MySQL 5.0, we began offering a new version of the Manual for each new series of MySQL releases (5.0, 5.1, and so on). For information about changes in previous release series of the MySQL database software, see the corresponding version of this Manual. For information about legacy versions of the MySQL sofware through the 4.1 series, see MySQL 4.1 Reference Manual.

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

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.

The date mentioned with a release version is the date of the last BitKeeper ChangeSet 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.

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.

D.1. Changes in release 5.1.x (Development)

The following changelog shows what has been done in the 5.1 tree:

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

D.1.1. Changes in release 5.1.2 (Not yet released)

Functionality added or changed:

Bugs fixed:

  • Foreign keys were not properly enforced in TEMPORARY tables. Foreign keys now are disallowed in TEMPORARY tables. (Bug #12084)

D.1.2. Changes in release 5.1.1 (Not yet released)

Functionality added or changed:

Bugs fixed:

  • Performing a CREATE TABLE statement with a PARTITION BY clause in a prepared statement could crash a server running in debug mode. (Bug #12097)

  • NDB: Specifying the wrong nodegroup in a CREATE TABLE using partitioning would lead to the table name being locked after the CREATE TABLE statement failed (that is, the table name could not be re-used). (Bug #12114)

  • Using ORDER BY in a query with a partitioned table on a 64-bit operating system could crash the server. (Bug #12116)

  • When two threads compete for the same table, a deadlock could occur if one thread has also a lock on another table through LOCK TABLES and the thread is attempting to remove the table in some manner and the other thread want locks on both tables. (Bug #10600)

D.2. Changes in MyODBC

D.2.1. Changes in MyODBC 3.51.12

Functionality added or changed:

  • N/A

Bugs fixed:

  • SQLColumns() returned no information for tables that had a column named using a reserved word. (Bug #9539)

D.2.2. Changes in MyODBC 3.51.11

Functionality added or changed: No changes.

Bugs fixed:

  • mysql_list_dbcolumns() and insert_fields() were retrieving all rows from a table. Fixed the queries generated by these functions to return no rows. (Bug #8198)

  • SQLGetTypoInfo() returned tinyblob for SQL_VARBINARY and nothing for SQL_BINARY. Fixed to return varbinary for SQL_VARBINARY, binary for SQL_BINARY, and longblob for SQL_LONGVARBINARY. (Bug #8138)