- 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:
-
Cluster API: Incompatible Change: The
AbortOptiontype is now a member of theNdbOperationclass; its values and behavior have also changed.NdbTransaction::AbortOptioncan no longer be used, and applications written against the NDB API may need to be rewritten and recompiled to accomodate these changes. For more information about this change, see TheNdbOperation::AbortOptionType.This also affects the behavior of the
NdbTransaction::execute()method, which now reports failure only if the transaction was actually aborted. SeeNdbTransaction::execute(), for more information.
Bugs fixed:
-
Security Fix: Using an
INFORMATION_SCHEMAtable withORDER BYin a subquery could cause a server crash.We would like to thank Oren Isacson of Flowgate Security Consulting and Stefan Streichsbier of SEC Consult for informing us of this problem. (Bug#24630, Bug#26556, CVE-2007-1420)
