- 5.2 Key changes in MySQL 5.1 releases
- 5.2.1 Changes in MySQL 5.1.43 (15 January 2010)
- 5.2.2 Changes in MySQL 5.1.41 (05 November 2009)
- 5.2.3 Changes in MySQL 5.1.40 (06 October 2009)
- 5.2.4 Changes in MySQL 5.1.37 (13 July 2009)
- 5.2.5 Changes in MySQL 5.1.36 (16 June 2009)
- 5.2.6 Changes in MySQL 5.1.32 (14 February 2009)
- 5.2.7 Changes in MySQL 5.1.31sp1 [QSP] (19 March 2009)
- 5.2.8 Changes in MySQL 5.1.29 (11 October 2008)
- 5.2.9 Changes in MySQL 5.1.28 (28 August 2008)
- 5.2.10 Changes in MySQL 5.1.23 (29 January 2008)
- 5.2.11 Changes in MySQL 5.1.21 (16 August 2007)
- 5.2.12 Changes in MySQL 5.1.20 (25 June 2007)
- 5.2.13 Changes in MySQL 5.1.19 (25 May 2007)
- 5.2.14 Changes in MySQL 5.1.18 (08 May 2007)
- 5.2.15 Changes in MySQL 5.1.17 (04 April 2007)
- 5.2.16 Changes in MySQL 5.1.16 (26 February 2007)
- 5.2.17 Changes in MySQL 5.1.15 (25 January 2007)
- 5.2.18 Changes in MySQL 5.1.14 (05 December 2006)
- 5.2.19 Changes in MySQL 5.1.13 (Not released)
- 5.2.20 Changes in MySQL 5.1.12 (24 October 2006)
Functionality added or changed:
-
Incompatible Change: MySQL Cluster: The
LockPagesInMainMemoryconfiguration parameter has changed its type and possible values. For more information, seeLockPagesInMainMemory.Important
The values
trueandfalseare no longer accepted for this parameter. If you were using this parameter and had it set tofalsein a previous release, you must change it to0. If you had this parameter set totrue, you should instead use1to obtain the same behavior as previously, or2to take advantage of new functionality introduced with this release, as described in the section cited above. Incompatible Change:
InnoDBrolls back only the last statement on a transaction timeout. A new option,--innodb_rollback_on_timeout, causesInnoDBto abort and roll back the entire transaction if a transaction timeout occurs (the same behavior as in MySQL 5.0.13 and earlier). (Bug#24200)Incompatible Change: Previously, the
DATE_FORMAT()function returned a binary string. Now it returns a string with a character set and collation given bycharacter_set_connectionandcollation_connectionso that it can return month and weekday names containing non-ASCII characters. (Bug#22646)-
Incompatible Change: The following conditions apply to enabling the
read_onlysystem variable:If you attempt to enable
read_onlywhile you have any explicit locks (acquired withLOCK TABLESor have a pending transaction, an error will occur.If other clients hold explicit table locks or have pending transactions, the attempt to enable
read_onlyblocks until the locks are released and the transactions end. While the attempt to enableread_onlyis pending, requests by other clients for table locks or to begin transactions also block untilread_onlyhas been set.read_onlycan be enabled while you hold a global read lock (acquired withFLUSH TABLES WITH READ LOCK) because that does not involve table locks.
Previously, the attempt to enable
read_onlywould return immediately even if explicit locks or transactions were pending, so some data changes could occur for statements executing in the server at the same time. (Bug#22009, Bug#11733) Incompatible Change: Previously, the
ARCHIVEstorage engine created a metadata file with an extension of.ARMfor each table. The engine no longer creates this file.
Bugs fixed:
Incompatible Change: For
ENUMcolumns that had enumeration values containing commas, the commas were mapped to0xffinternally. However, this rendered the commas indistinguishable from true0xffcharacters in the values. This no longer occurs. However, the fix requires that you dump and reload any tables that haveENUMcolumns containing any true0xffvalues. Dump the tables using mysqldump with the current server before upgrading from a version of MySQL 5.1 older than 5.1.15 to version 5.1.15 or newer. (Bug#24660)
