New Features of MySQL6.0: Prospect of multiple enhancements

New Features of MySQL6.0 (Note: The content here will change as MySQL6.0 is still in its early stages) the following features have been or will be added to MySQL6.0: ◆ new Falcon transaction storage engine (see 13.8, "Falcon storage engine"); ◆ supports more Unicode character sets: utf16, utf32, and 4-byte utf8 (

New Features of MySQL 6.0 (Note: The content here will change as MySQL 6.0 is still in its early stages) the following features have been or will be added to MySQL 6.0: ◆ new Falcon transaction storage engine (see 13.8, "Falcon storage engine"); ◆ supports more Unicode character sets: utf16, utf32, and 4-byte utf8 (

New Features of MySQL 6.0

(Note: The content here will change because MySQL 6.0 is still in its early stages)

The following functions have been or are to be added to MySQL 6.0:

◆ New Falcon transaction storage engine (see "Falcon storage engine" in "13.8 ");

◆ Supports more Unicode character sets: utf16, utf32, and 4-byte utf8 (these character sets support these additional Unicode character sets );

◆ Added backup database and RESTORE statements for BACKUP and restoration (see section 6.3 "using MySQL BACKUP ");

◆ Improve the INFORMATION_SCHEMA database and add the INFORMATION_SCHEMA.PARAMETERS table. INFORMATION_SCHEMA.ROUTINES adds new columns (see section 19.27, "INFORMATION_SCHEMA PARAMETERS table" and "INFORMATION_SCHEMA ROUTINES table ");

◆ Subqueries and Join operations are optimized, including Batch index access in the scattered regions of MyISAD and InnoB storage engines;

◆ Reset slave no longer changes the replication connection parameters. Previously, it RESET them to the value specified by the command line (see section 12.6.2.3, "reset slave Syntax ");

◆ The lock tables syntax has been extended and supports transaction table locks that are not automatically committed by transactions. Lock tables... in share mode or lock tables... in exclusive mode you can use a table-Level LOCK that is not mentioned. You can also ensure that the lock tables statement can continuously obtain multiple transaction locks and add additional TABLES to the LOCK set, instead of unlocking a previously locked table. When lock tables with in share mode or exclusive mode is used, table-level locks are not unlocked before the transaction ends.

The transaction LOCK obtained using the lock table is released at the end of the transaction, including the displayed commit or rollback, implicit commit caused by the statement, or closed due to the link. 12.4.3, "statements that cause implicit commit", lists the statements that cause implicit commit.

The lock tables action remains unchanged IN the READ and WRITE locks (that is, when the in share mode or in exclusive mode is not used );

◆ Enhanced XML functions, including a new load xml syntax (see section 12.2.7, "load xml Syntax ");

◆ Supports extended comments, including tables, columns, and indexes.

The following structure is outdated and has been deleted in MySQL 6.0

Applications should be updated to use them in another way;

◆ Table_type system variable (storage_engine );

◆ The TYPE parameter used by the TABLE in CREATE TABEl or alter table (using ENGINE );

◆ Show table types syntax (use show engines );

◆ The log_bin_trust_routine_creators variable (use log_bin_trust_function_creators );

◆ TIMESTAMP (N): to specify the display width as N (N is not used );

◆ Show innodb status and show mutex status syntax (use show engine innodb status );

◆ The load table... from master and load data from master syntax;

◆ Show plugin syntax (use show plugins );

◆ Backup table and restore table syntax;

◆ The -- master-xxx specifies The server parameter of The copied parameter (replace it with change master to statement ):

--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