This is a bugfix release for the current production release family.
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
Important Change; MySQL Cluster:
INFILE no longer causes an implicit commit for all
storage engines. It now causes an implicit commit only for
tables using the
LOAD DATA FROM MASTER and
TABLE FROM MASTER statements are deprecated. See
LOAD DATA FROM MASTER Syntax, for recommended
(Bug #9125, Bug #20596, Bug #14399, Bug #12187, Bug #15025, Bug #18822)
The source distribution has been updated so that the UDF example can be compiled under Windows with CMake. See Compiling and Installing User-Defined Functions. (Bug #19121)
For mysqldump, the output generated by the
server when using the
option has changed with regard to null values. It now matches
the output from mysqldump
--xml. That is, a column
NULL value is now reported as
column_name" xsi:nil="true" />
whereas a column containing the string value
'NULL' is reported as
and a column containing an empty string is reported as
mysqldump now has a
--flush-privileges option. It
causes mysqldump to emit a
PRIVILEGES statement after dumping the
mysql database. This option should be used
any time the dump contains the
and any other database that depends on the data in the
mysql database for proper restoration.
The number of
InnoDB threads is no longer
limited to 1,000 on Windows.
Replication: Column names supplied for a view created on a master server could be lost on a slave server. (Bug #19419)
The source distribution would not build on Windows due to a
spurious dependency on
SUBSTRING() results sometimes
were stored improperly into a temporary table when multibyte
character sets were used.
User names have a maximum length of 16 characters (even if they contain multibyte characters), but were being truncated to 16 bytes. (Bug #20393)
When records are merged from the insert buffer and the page
needs to be reorganized,
incorrect column length information when interpreting the
records of the page. This caused a server crash due to apparent
corruption of secondary indexes in
ROW_FORMAT=COMPACT that contain prefix
indexes of fixed-length columns. Data files should not be
corrupted, but the crash was likely to repeat every time the
server was restarted.
PROCEDURE ANALYSE() returned incorrect values
MyISAM table with a
FULLTEXT index, compression with
myisampack or a check with
myisamchk after compression resulted in table
yaSSL had a conflicting definition for
socklen_t on hurd-i386 systems.
A subquery that uses an index for both the
ORDER BY clauses
produced an empty result.
The value of
not always updated correctly within stored routines.
INSERT DELAYED did not honor
SET INSERT_ID or the
auto_increment_* system variables.
(Bug #20627, Bug #20830)
A query that used
GROUP BY and an
subquery in a
HAVING clause could trigger an
setting causes MySQL to generate a value larger than the
column's maximum possible value, the
INSERT statement is accepted in
strict SQL mode, whereas but should fail with an error.
UPGRADE was treated as a reserved word,
although it is not.
mysql_com.h unnecessarily referred to the
mysqld was linked against a
zlib library compiled
without large-file support, it would likely exit with a
SIGXFSZ (file size exceeded) signal if an
ARCHIVE table reached 2GB. The server now
checks for space before writing.
The server could crash for the second execution of a function
that uses an aggregating
Subqueries with aggregate functions but no
FROM clause could return incorrect results.
Incorporated portability fixes into the definition of
pthreads library to
single-threaded MySQL libraries caused
dlopen() to fail at runtime on HP-UX.
On Mac OS X, zero-byte
write() calls to an SMB-mounted file system
could return a nonstandard return value, leading to data
corruption. Now such calls are avoided.
TRADITIONAL SQL mode,
assignment of out-of-bound values and rounding of assigned
values was done correctly, but assignment of the same numbers
represented as strings sometimes was handled differently.
mysql_config --libmysqld-libs did not produce
any SSL options necessary for linking
libmysqld with SSL support enabled.
Within stored routines, some error messages were printed incorrectly. A nonnull-terminated string was passed to a message-printing routine that expected a null-terminated string. (Bug #20778)
Execution of a prepared statement that uses an
IN subquery with aggregate functions in the
HAVING clause could cause a server crash.
The source distribution failed to compile when configured with
On Windows, inserting into a
after renaming an underlying
caused a server crash.
myisam_ftdump produced bad counts for common words. (Bug #21459)
Conversion of values inserted into a
BIT column could affect adjacent
The parser rejected queries that selected from a table twice
UNION within a subquery.
The parser now supports arbitrary subquery, join, and
parenthesis operations within
subqueries. A limitation still exists for scalar subqueries: If
the subquery contains
SELECT of the
UNION cannot be within
parentheses. For example,
SELECT (SELECT a FROM t1
UNION SELECT b FROM t2) will work, but
((SELECT a FROM t1) UNION (SELECT b FROM t2)) will
Join conditions using index prefixes on
InnoDB tables incorrectly ignored
rows where the length of the actual value was greater than the
length of the index prefix.
MyISAM table locked with
TABLES ...WRITE, queries optimized using the
index_merge method did not
show rows inserted with the lock in place.
Deleting entries from a large
could cause index corruption when it needed to shrink. Deletes
from an index can happen when a record is deleted, when a key
changes and must be moved, and when a key must be un-inserted
because of a duplicate key. This can also happen in
REPAIR TABLE when a duplicate key
is found and in myisamchk when sorting the
records by an index.
Row equalities (such as
WHERE (a,b) = (c,d)
were not taken into account by the optimizer, resulting in slow
query execution. Now they are treated as conjunctions of
equalities between row elements.
INSERT into an updatable
but noninsertable view, an error message was issued stating that
the view was not updatable. Now the message says the view is not
The server returns a more informative error message when it
attempts to open a
MERGE table that has been
defined to use non-
mysql_upgrade produced a malformed
upgrade_defaults file by overwriting the
[client] group header with a
password option. This prevented
mysqlcheck from running successfully when
invoked by mysql_upgrade.
Table aliases in multiple-table
DELETE statements sometimes were
The build process incorrectly tried to overwrite
sql/lex_hash.h. This caused the build to
fail when using a shadow link tree pointing to original sources
that were owned by another account.
The presence of a subquery in the
of a join in a view definition prevented the
MERGE algorithm from being used for the view
in cases where it should be permitted.
make install tried to build files that should already have been built by make all, causing a failure if installation was performed using a different account than the one used for the initial build. (Bug #19738)
A function result in a comparison was replaced with a constant by the optimizer under some circumstances when this optimization was invalid. (Bug #21698)
In the package of pre-built time zone tables that is available
for download at
the tables now explicitly use the
character set so that they work the same way regardless of the
system character set value.
Queries containing a subquery that used aggregate functions could return incorrect results. (Bug #16792)
The URL into the online manual that is printed in the stack trace message by the server was out of date. (Bug #21449)
mysql displayed an empty string for