In the latin5_turkish_ci collation, the order of the characters A WITH CIRCUMFLEX, I WITH CIRCUMLEX, and U WITH CIRCUMFLEX was changed. If you have used these characters in any indexed columns, you should rebuild those indexes. (Bug#13421)

Support files for compiling with Visual Studio 6 have been removed. (Bug#15094)

Internal sha1_result function renamed to mysql_sha1_result to prevent conflicts with other projects. (Bug#13944)

CAST(... AS TIME) operations returned different results when using versus not using prepared-statement protocol. (Bug#15805)

Performing a RENAME TABLE on an InnoDB table when the server is started with the --innodb-file-per-table option and the data directory is a symlink caused a server crash. (Bug#15991)

Characters in the gb2312 and euckr character sets which did not have Unicode mappings were truncated. (Bug#15377)

Piping the fill_help_tables.sql file into mysqld resulted in a syntax error. (Bug#15965)

NDBCluster: Upon the completion of a scan where a key request remained outstanding on the primary replica and a starting node died, the scan did not terminate. This caused incompleted error handling of the failed node. (Bug#15908)

Using CAST() to convert values with long fractional and/or exponent parts to TIME returned wrong results. (Bug#12440)

An INSERT ... SELECT statement between tables in a MERGE set can return errors when statement involves insert into child table from merge table or vice-versa. (Bug#5390)

Certain permission management statements could create a NULL hostname for a user, resulting in a server crash. (Bug#15598)

For InnoDB tables, using a column prefix for a utf8 column in a primary key caused Cannot find record errors when attempting to locate records. (Bug#14056)

Certain CREATE TABLE ... AS ... statements involving ENUM columns could cause server crash. (Bug#12913)

Using an aggregate function as the argument for a HAVING clause would result in the aggregate function always returning FALSE. (Bug#14274)

The COALESCE() function truncated data in a TINYTEXT column. (Bug#15581)

InnoDB: Comparison of indexed VARCHAR CHARACTER SET ucs2 COLLATE ucs2_bin columns using LIKE could fail. (Bug#14583)

Issuing a DROP USER command could cause some users to encounter a hostname is not allowed to connect to this MySQL server error. (Bug#15775)

Access Denied error could be erroneously returned with specific grant combinations under high load. (Bug#7209)

Symbolic links did not function properly on Windows platforms. (Bug#14960, Bug#14310)

BDB: A DELETE, INSERT, or UPDATE of a BDB table could cause the server to crash where the query contained a subquery using an index read. (Bug#15536)

DELETE could report full-text index corruption (Invalid key for table ...) if the index was built with repair-by-sort, the data in the full-text index used UCA collation, and some word appeared in the data terminated by a 0xC2A0 character as well as by other non-letter characters. (Bug#11336)

A race condition when creating temporary files caused a deadlock on Windows with threads in Opening tables or Waiting for table states. (Bug#12071)

InnoDB: If FOREIGN_KEY_CHECKS was 0, InnoDB allowed inconsistent foreign keys to be created. (Bug#13778)

NDB Cluster: A memory leak occurred when performing ordered index scans using indexes a columns larger than 32 bytes, which would eventually lead to the forced shutdown of all mysqld server processes used with the cluster. (Bug#13078)

NDB Cluster: Under some circumstances, it was possible for a restarting node to undergo a forced shutdown. (Bug#15632)

NDB Cluster: If an abort by the Transaction Coordinator timed out, the abort condition was incorrectly handled, causing the transacviton record to be released prematurely. (Bug#15685)

NDB Cluster: A node which failed during cluster startup was sometimes not removed from the internal list of active nodes. (Bug#15587)

NDB Cluster: There was a small window for a node failure to occur during a backup without an error being reported. (Bug#15425)

Multiple-table update operations were counting updates and not updated rows. As a result, if a row had several updates it was counted several times for the “rows matched” value but updated only once. (Bug#15028)

SELECT queries that began with an opening parenthesis were not being placed in the query cache. (Bug#14652)