Skip navigation links

Additional languages
MySQL 6.0 Reference Manual :: C MySQL Change History :: C.2 Changes in release 5.2.x (Development) :: C.2.1 Changes in MySQL 5.2.5 (08 August 2007: Alpha)
C.2.2 Changes in MySQL 5.2.4 (Not released) »
Section Navigation      [Toggle]

C.2.1. Changes in MySQL 5.2.5 (08 August 2007: Alpha)

This is a new Alpha development release, fixing recently discovered bugs.

Note

This Alpha release, as any other pre-production release, should not be installed on production level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has worked very hard to ensure a high level of quality, protect your data by making a backup as you would for any software beta release. Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Network (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.

Functionality added or changed:

  • Incompatible Change: The obsolete constructs in the following table have been removed. Use the equivalents shown in the table's second column instead. Existing applications that depend on the obsolete constructs should be converted to make use of the current equivalents as soon as possible.

    Obsolete: Current:
    @@table_type @@storage_engine
    @@log_bin_trust_routine_creators @@log_bin_trust_function_creators
    TIMESTAMP(N) See Section 11.6, “Date and Time Functions”.
    TYPE= ENGINE=
    BACKUP TABLE mysqldump, mysqlhotcopy, or MySQL Administrator
    RESTORE TABLE, LOAD TABLE FROM MASTER mysqldump, mysql, or MySQL Administrator
    SHOW TABLE TYPES SHOW [STORAGE] ENGINES
    SHOW INNODB STATUS SHOW ENGINE INNODB STATUS
    SHOW MUTEX STATUS SHOW ENGINE INNODB MUTEX
    --master-xxx options to set replication parameters: --master-host, --master-user, --master-password , --master-port, --master-connect-retry, --master-ssl, --master-ssl-ca, --master-ssl-capath, --master-ssl-cert, --master-ssl-cipher, --master-ssl-key CHANGE MASTER

  • MySQL Cluster: It is now possible to control whether fixed-width or variable-width storage is used for a given column of an NDB table by means of the COLUMN_FORMAT specifier as part of the column's definition in a CREATE TABLE or ALTER TABLE statement.

    It is also possible to control whether a given column of an NDB table is stored in memory or on disk, using the STORAGE specifier as part of the column's definition in a CREATE TABLE or ALTER TABLE statement.

    For permitted values and other information about COLUMN_FORMAT and STORAGE, see Section 12.1.13, “CREATE TABLE Syntax”.

  • The INFORMATION_SCHEMA.COLUMNS table now has STORAGE and FORMAT columns. For NDB tables, STORAGE indicates whether a column is stored on disk or memory, and FORMAT indicates the column storage format (FIXED, DYNAMIC, or DEFAULT).

  • The INFORMATION_SCHEMA.STATISTICS table now has an INDEX_COMMENT column to indicate any comment string provided for the column. The SHOW INDEX statement now displays an Index_comment column that provides the same information.

  • The LOAD XML INFILE statement was added. This statement makes it possible to read data directly from XML files into database tables. For more information, see Section 12.2.7, “LOAD XML Syntax”.

Bugs fixed:

  • Use of the latin2_czech_cs collation caused a server crash. (Bug#29459)