New Features of MySQL 6.0: Prospect of multiple enhancements

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:

◆ For details about the new Falcon transaction storage engine, refer to "Falcon storage engine" 13.8 ");

◆ Supports more Unicode character sets: utf16, utf32, and 4-byte utf8. These additional Unicode character sets are supported );

◆ Added backup database and RESTORE statements for BACKUP and restoration. For details, see section 6.3, "using MySQL BACKUP ");

◆ Improve the INFORMATION_SCHEMA database and add the INFORMATION_SCHEMA.PARAMETERS table. For the INFORMATION_SCHEMA.ROUTINES table, see section 19.27, "INFORMATION_SCHEMA PARAMETERS table", "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 parameter of the replication connection. In the past, it RESET them to the value specified in the command line, see 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, which can be found in 12.2.7 and "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;

◆ Use storage_engine for table_type system variables );

◆ TABLE is used to use ENGINE in the TYPE parameter of CREATE TABEl or alter table );

◆ Show table types syntax uses show engines );

◆ The log_bin_trust_routine_creators variable uses log_bin_trust_function_creators );

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

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

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

◆ Use show plugins in the show plugin syntax );

◆ Backup table and restore table syntax;

◆ The -- master-xxx indicates that The server parameter of The copied parameter is replaced by 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

1. MySQL database getting started and proficient tutorial
2. Establish routine maintenance specifications for MySQL Databases
3. How to lock MySQL database tables
4. How to maintain MySQL Database Log Files