This is a new Beta development release, fixing recently discovered bugs.
This Beta release, as any other pre-production release, should not be installed on production level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has worked very hard to ensure a high level of quality, protect your data by making a backup as you would for any software beta release. Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details, please see http://www.mysql.com/products/enterprise.
Functionality added or changed:
This was done to resolve the following interrelated issues:
The server could abort or deadlock for
INSERT DELAYED statements for
which another insert was performed implicitly (for example,
via a stored function that inserted a row).
A trigger using an
DELAYED caused the error INSERT DELAYED
can't be used with table ... because it is locked with LOCK
TABLES although the target table was not
INSERT DELAYED into a table
BEFORE INSERT or
INSERT trigger gave an incorrect
NEW pseudocolumn value and caused the
server to deadlock or abort.
Formerly, restoring a cluster backup made on a MySQL 5.0 Cluster
to a 5.1 cluster using a 5.1 version of
ndb_restore did not resize
VARCHAR columns as might be
expected; now, the default behavior of
ndb_restore in such cases is to resize the
VARCHAR columns. This changed
default behavior can be overridden using the
when invoking ndb_restore.
A new status variable,
indicates the number of calls to stored procedures.
The data type used for the
column of the following
tables has been changed to
See also Bug#26994.
Security Fix: UDFs are supposed to be loadable only from the plugin directory, but this restriction was not being enforced. (Bug#28341)
When an API node sent more than 1024 signals in a single batch,
NDB would process only the first
1024 of these, and then hang.
A delay in obtaining
AUTO_INCREMENT IDs could
lead to excess temporary errors.
Local checkpoint files relating to dropped
NDB tables were not removed.
MySQL Cluster: Multiple operations involving deletes followed by reads were not handled correctly.
This issue could also affect MySQL Cluster Replication.
MySQL Cluster: Restarting a data node caused SQL nodes to log repeatedly and unnecessarily the status of the event buffer, causing a memory leak of approximately 4 MB for each mysqld process each time this occurred.
(This issue was known to occur in MySQL 5.1.16 and later only.) (Bug#27292)
ndb_mgmd failed silently when the cluster
configuration file contained invalid
MySQL Cluster: A failure to release internal resources following an error could lead to problems with single user mode. (Bug#25818)
MySQL Cluster: DDL operations were not supported on a partially started cluster. (Bug#24631)
Disk Data: Extremely large inserts into Disk Data tables could lead to data node failure in some circumstances. (Bug#27942)
In a multi-operation transaction, a delete operation followed by
the insertion of an implicit
NULL failed to
overwrite an existing value.
A query with a
NOT IN subquery predicate
could cause a crash when the left operand of the predicate
libmysql.dll could not be dynamically loaded
Grouping queries with correlated subqueries in
WHERE conditions could produce incorrect
Portability problems caused by use of
When dumping procedures, mysqldump
output that restored the session variable
sql_mode without first
capturing it. When dumping routines, mysqldump
set nor retrieved the value of
It was not possible to use the value
–9223372036854775808 (that is,
–MAXVALUE + 1) when specifying a
The server could hang for
INSERT IGNORE ... ON
DUPLICATE KEY UPDATE if an update failed.
The second execution of a prepared statement from a
UNION query with
BY RAND() caused the server to crash. This problem
could also occur when invoking a stored procedure containing
such a query.
Changes to some system variables should invalidate statements in the query cache, but invalidation did not happen. (Bug#27792)
The error message for error number
not report which database/table combination reported the
A large filesort could result in a division by zero error and a server crash. (Bug#27119)
Flow control optimization in stored routines could cause exception handlers to never return or execute incorrect logic. (Bug#26977)
Some test suite files were missing from some MySQL-test packages. (Bug#26609)
An attempt to execute
CREATE TABLE ...
SELECT when a temporary table with the same name
already existed led to the insertion of data into the temporary
table and creation of an empty nontemporary table.
A statement of the form
CREATE TABLE IF NOT EXISTS t1
SELECT f1() AS i failed with a deadlock error if the
f1() referred to a table with
the same name as the to-be-created table. Now it correctly
produces a message that the table already exists.
Quoted labels in stored routines were mishandled, rendering the routines unusable. (Bug#21513)
CURDATE() is less than
NOW(), either when comparing
CURDATE() < NOW() is true) or when
DATE) < NOW() is true). However, storing
CURDATE() in a
DATE column and comparing
DATE column as
DATETIME for comparisons to a
CREATE TABLE IF NOT EXISTS ... SELECT caused
a server crash if the target table already existed and had a
BEFORE INSERT trigger.
For dates with 4-digit year parts less than 200, an incorrect
implicit conversion to add a century was applied for date
arithmetic performed with
- INTERVAL. (For
INTERVAL 0 SECOND) became
Changing the size of a key buffer that is under heavy use could
cause a server crash. The fix partially removes the limitation
LOAD INDEX INTO
CACHE fails unless all indexes in a table have the
same block size. Now the statement fails only if
LEAVES is specified.