New features of MySQL6.0

New features of MySQL6.0: bitsCN.com

Original article:

New features of MySQL 6.0

New features of MySQL 6.0
Note:

Because MySQL 6.0 is still in its early stages, the content here will change.

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

* The 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, that is, those beyond the base of a basic multilingual language ).

* The backup database and RESTORE statements are added for BACKUP and restoration. for details, see section 6.3 "using MySQL BACKUP ".

* The INFORMATION_SCHEMA database is improved and the INFORMATION_SCHEMA.PARAMETERS table is added. INFORMATION_SCHEMA.ROUTINES adds a new column (see INFORMATION_SCHEMA in section 19.27 ".

PARAMETERS table ", and 19.14", INFORMATION_SCHEMA ROUTINES table ").

* The subquery 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. In lock tables... in share mode or lock tables... in exclusive mode, you can use

You can also ensure that the lock tables statement can continuously obtain multiple transaction locks and add additional TABLES to the LOCK set without unlocking the previously locked TABLES. When lock tables with in share is used

MODE or exclusive mode, the table-level lock is 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 submission", lists

Statements that may cause implicit submission.

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

* The enhanced XML function includes a new load xml syntax (see section 12.2.7, "load xml syntax ").

* Supports extended annotations, including tables, columns, and indexes.

The following structure is outdated and has been deleted in MySQL 6.0. The application should be new and use them in another way.

* Table_type system variable (storage_engine ).

* The TYPE parameter used for TABLE creation in 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

BitsCN.com