Skip navigation links

Additional languages
MySQL 5.0 Reference Manual :: E MySQL Change History :: E.1 Changes in release 5.0.x (Production)
E.1.1 Changes for release 5.0.27 and up »
Section Navigation      [Toggle]

E.1. Changes in release 5.0.x (Production)

[+/-]

E.1.1. Changes for release 5.0.27 and up
E.1.2. Changes in MySQL 5.0.26 (03 October 2006)
E.1.3. Changes in MySQL 5.0.25 (15 September 2006)
E.1.4. Changes in MySQL 5.0.24a (25 August 2006)
E.1.5. Changes in MySQL 5.0.24 (27 July 2006)
E.1.6. Changes in MySQL 5.0.23 (Not released)
E.1.7. Changes in MySQL 5.0.22 (24 May 2006)
E.1.8. Changes in MySQL 5.0.21 (02 May 2006)
E.1.9. Changes in MySQL 5.0.20a (18 April 2006)
E.1.10. Changes in MySQL 5.0.20 (31 March 2006)
E.1.11. Changes in MySQL 5.0.19 (04 March 2006)
E.1.12. Changes in MySQL 5.0.18 (21 December 2005)
E.1.13. Changes in MySQL 5.0.17 (14 December 2005)
E.1.14. Changes in MySQL 5.0.16 (10 November 2005)
E.1.15. Changes in MySQL 5.0.15 (19 October 2005: Production)
E.1.16. Changes in MySQL 5.0.14 (Not released)
E.1.17. Changes in MySQL 5.0.13 (22 September 2005: Release Candidate)
E.1.18. Changes in MySQL 5.0.12 (02 September 2005)
E.1.19. Changes in MySQL 5.0.11 (06 August 2005)
E.1.20. Changes in MySQL 5.0.10 (27 July 2005)
E.1.21. Changes in MySQL 5.0.9 (15 July 2005)
E.1.22. Changes in MySQL 5.0.8 (Not released)
E.1.23. Changes in MySQL 5.0.7 (10 June 2005)
E.1.24. Changes in MySQL 5.0.6 (26 May 2005)
E.1.25. Changes in MySQL 5.0.5 (Not released)
E.1.26. Changes in MySQL 5.0.4 (16 April 2005)
E.1.27. Changes in MySQL 5.0.3 (23 March 2005: Beta)
E.1.28. Changes in MySQL 5.0.2 (01 December 2004)
E.1.29. Changes in MySQL 5.0.1 (27 July 2004)
E.1.30. Changes in MySQL 5.0.0 (22 December 2003: Alpha)

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

  • Basic support for read-only server side cursors. For information about using cursors within stored routines, see Section 12.8.5, “Cursors”. For information about using cursors from within the C API, see Section 19.7.7.3, “mysql_stmt_attr_set()”.

  • Basic support for (updatable) views. See, for example, Section 12.1.11, “CREATE VIEW Syntax”.

  • Basic support for stored procedures and functions (SQL:2003 style). See Section 17.2, “Using Stored Routines (Procedures and Functions)”.

  • Initial support for rudimentary triggers.

  • Added SELECT INTO list_of_vars, which can be of mixed (that is, global and local) types. See Section 12.8.3.3, “SELECT ... INTO Statement”.

  • Removed the update log. It is fully replaced by the binary log. If the MySQL server is started with --log-update, it is translated to --log-bin (or ignored if the server is explicitly started with --log-bin), and a warning message is written to the error log. Setting SQL_LOG_UPDATE silently sets SQL_LOG_BIN instead (or do nothing if the server is explicitly started with --log-bin).

  • Support for the ISAM storage engine has been removed. If you have ISAM tables, you should convert them before upgrading. See Section 2.18.2, “Upgrading from MySQL 4.1 to 5.0”.

  • Support for RAID options in MyISAM tables has been removed. If you have tables that use these options, you should convert them before upgrading. See Section 2.18.2, “Upgrading from MySQL 4.1 to 5.0”.

  • User variable names are now case insensitive: If you do SET @a=10; then SELECT @A; now returns 10. Case sensitivity of a variable's value depends on the collation of the value.

  • Strict mode, which in essence means that you get an error instead of a warning when inserting an incorrect value into a column. See Section 5.1.7, “SQL Modes”.

  • VARCHAR and VARBINARY columns remember end space. A VARCHAR() or VARBINARY column can contain up to 65,535 characters or bytes, respectively.

  • MEMORY (HEAP) tables can have VARCHAR columns.

  • When using a constant string or a function that generates a string result in CREATE ... SELECT, MySQL creates the result column based on the maximum length of the string or expression:

    Maximum Length Data type
    = 0 CHAR(0)
    < 512 VARCHAR(max_length)
    >= 512 TEXT

  • A fixed-point math library is introduced that supports precision math, resulting in more accurate results when working with the DECIMAL and NUMERIC data types. For details, see Section 11.13, “Precision Math”.

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