Skip navigation links

Additional languages
1.5 MySQL Information Sources »
Section Navigation      [Toggle]

1.4.2. What's Planned for MySQL 6.0

Note

This section remains subject to change as long as MySQL 6.0 development is in its early stages.

The following features are expected to be added to, or change in MySQL 6.0:

  • A new transactional storage engine (Falcon).

  • Support for additional Unicode character sets: utf16, utf32, and 4-byte utf8. These character sets support supplementary Unicode characters; that is, characters outside the Basic Multilingual Plane (BMP).

  • BACKUP DATABASE and RESTORE statements for backup and restore operations.

  • Improvements in the INFORMATION_SCHEMA database, with the addition of the INFORMATION_SCHEMA.PARAMETERS table, and new columns added to INFORMATION_SCHEMA.ROUTINES.

  • Optimizer enhancements for faster subqueries and joins, including batched index access of table rows for sequences of disjoint ranges by the MyISAM and InnoDB storage engines.

  • RESET SLAVE no longer changes replication connection parameters. Previously, it reset them to the values specified on the command line.

  • The syntax for the LOCK TABLES statement is extended to support transactional table locks that do not commit transactions automatically. Following LOCK TABLES ... IN SHARE MODE or LOCK TABLES ... IN EXCLUSIVE MODE, you can access tables not mentioned in the LOCK TABLES statement. You can now also issue these extended LOCK TABLES statements many times in succession, adding additional tables to the locked set, and without unlocking any tables that were locked previously. When using LOCK TABLES with IN SHARE MODE or IN EXCLUSIVE MODE, tables are not unlocked until the transaction ends.

    The behavior of LOCK TABLES when not using IN SHARE MODE or IN EXCLUSIVE MODE remains unchanged.

  • Further enhancements to XML functionality, including a new LOAD XML statement.

  • Support for extended comments for tables, columns, and indexes.

The following constructs are deprecated and have been removed for MySQL 6.0 (they were actually removed in 5.2.5). Where alternatives are shown, applications should be updated to use them.

  • The table_type system variable (use storage_engine).

    The TYPE table option to specify the storage engine for CREATE TABLE or ALTER TABLE (use ENGINE).

    The SHOW TABLE TYPES SQL statement (use SHOW ENGINES).

  • The log_bin_trust_routine_creators variable (use log_bin_trust_function_creators).

  • TIMESTAMP(N): The ability to specify a display width of N (use without N).

  • The SHOW INNODB STATUS and SHOW MUTEX STATUS SQL statements (use SHOW ENGINE INNODB STATUS for both of these).

  • The LOAD TABLE ... FROM MASTER and LOAD DATA FROM MASTER SQL statements.

  • The SHOW PLUGIN SQL statement (use SHOW PLUGINS).

  • The RESTORE TABLE SQL statement.

  • The BACKUP TABLE SQL statement.

  • The --master-xxx server options to set replication parameters (use the CHANGE MASTER TO statement).