MySQL 6.0.5-alpha Released
Join the DZone community and get the full member experience.Join For Free
MySQL 6.0.5-alpha, a new version of the MySQL database system including the Falcon transactional storage engine, has been released. The main page for MySQL 6.0 release is at: http://www.mysql.com/mysql60/
If you are new to the Falcon storage engine and need more information, please read the Falcon Evaluation Guide at:
http://www.mysql.com/why-mysql/white-papers/falcon-getting-started.php and the whitepaper at:
Functionality that has been added or changed in this version
- Incompatible Change: In MySQL 5.1.6, when log tables were
implemented, the default log destination for the general query
and slow query log was TABLE. This default has been changed to
FILE, which is compatible with MySQL 5.0, but incompatible
with earlier releases of MySQL 5.1 from 5.1.6 to 5.1.20. If
you are upgrading from MySQL 5.0 to this release, no logging
option changes should be necessary. However, if you are
upgrading from 5.1.6 through 5.1.20 to this release and were
using TABLE logging, use the --log-output=TABLE option
explicitly to preserve your server's table-logging behavior.
- Incompatible Change: Incompatible Change: The server now includes dtoa, a library for conversion between strings and numbers by David M. Gay. In MySQL, this library provides the basis for improved conversion between string or DECIMAL values and approximate-value (FLOAT/DOUBLE) numbers. See also:
- Important Change: MySQL Cluster: Packaging: Beginning with
this release, standard MySQL 6.0 binaries are no longer built
with support for the NDBCLUSTER storage engine, and the
NDBCLUSTER code included in 6.0 mainline sources is no longer
guaranteed to be maintained or supported.
- Cluster API: Important Change: Because
NDB_LE_MemoryUsage.page_size_kb shows memory page sizes in
bytes rather than kilobytes, it has been renamed to
page_size_bytes. The name page_size_kb is now deprecated and
thus subject to removal in a future release, although it
currently remains supported for reasons of backward
- Important Change: Added a ROUTINE_TYPE column to the
INFORMATION_SCHEMA.PARAMETERS table, to make it possible to
distinguish like-named parameters of stored routines and
stored functions having the same names.
- Important Change: Security Fix: It was possible to circumvent privileges through the creation of MyISAM tables employing the DATA DIRECTORY and INDEX DIRECTORY options to overwrite existing table files in the MySQL data directory. Use of the MySQL data directory in DATA DIRECTORY and INDEX DIRECTORY is now disallowed.
- Important Change: Security Enhancement: On Windows Vista and Windows Server 2008, a user without administrative privileges does not have write permissions to the Program Files directory where MySQL and the associated data files are normally installed. Using data files located in the standard Program Files installation directory could therefore cause MySQL to fail, or lead to potential security issues in an installed instance. To address the problem, on Windows XP, Windows Vista and Windows Server 2008, the datafiles and data file configuration are now set to the Microsoft recommended AppData folder.
- Important Change: MySQL Cluster: AUTO_INCREMENT columns had
the following problems when used in NDB tables:
- The AUTO_INCREMENT counter was not updated correctly when such a column was updated.
- AUTO_INCREMENT values were not prefetched beyond statement boundaries.
- AUTO_INCREMENT values were not handled correctly with INSERT IGNORE statements.
- After being set, ndb_autoincrement_prefetch_sz showed a value of 1, regardless of the value it had actually been set to.
- Important Change: Replication: When the master crashed during an update on a transactional table while in AUTOCOMMIT mode, the slave failed. This fix causes every transaction (including AUTOCOMMIT transactions) to be recorded in the binlog as starting with a BEGIN and ending with a COMMIT or ROLLBACK.
- Disk Data: Important Change: It is no longer possible on 32-bit systems to issue statements appearing to create Disk Data log files or data files greater than 4 GB in size.
- Important Change: It was possible to use FRAC_SECOND as a synonym for MICROSECOND with DATE_ADD(), DATE_SUB(), and INTERVAL; now, using FRAC_SECOND with anything other than TIMESTAMPADD() or TIMESTAMPDIFF() produces a syntax error.
- Important Change: InnoDB free space information is now shown in the Data_free column of SHOW TABLE STATUS and in the DATA_FREE column of the INFORMATION_SCHEMA.TABLES table.
- Important Change: The server handled truncation of values having excess trailing spaces into CHAR, VARCHAR, and TEXT columns in different ways. This behavior has now been made consistent for columns of all three of these types, and now follows the existing behavior of VARCHAR columns in this regard; that is, a Note is always issued whenever such truncation occurs.
- Important Change: An AFTER UPDATE trigger was not invoked when the UPDATE did not make any changes to the table for which the trigger was defined. Now AFTER UPDATE triggers behave the same in this regard as do BEFORE UPDATE triggers, which are invoked whether the UPDATE makes any changes in the table or not.
- Replication: Important Note: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet.
To read all the details of this release head over to the official release notice at the MySQL AB website.
Opinions expressed by DZone contributors are their own.