MySQL 5.7 Release Notes - Download - MySQL

MySQL 5.7 Release Notes• Valgrind errors were produced during row comparator setup. (Bug #17755540)• In some cases, UNIX_TIMESTAMP() could return NULL when it should return 0. (Bug #17728371)• An assertion could be raised if a filesort failed to resize its main buffer when record propertieschanged. (Bug #17757914)• The resetconnection command for mysql did not report proper errors if the server was down orthe user password had expired. (Bug #17772561)• Compilation failed if MySQL was configured using -DWITH_LIBWRAP=1. (Bug #17738805)• Contraction information in a collation could be mishandled, resulting in incorrect decisions aboutwhether a character is part of a contraction, and miscalculation of contraction weights. (Bug#17760379)• The cache used for the Index Merge access method was freed only after successful retrieval of allrows. Interruption or failure of the operation led to a file descriptor leak. (Bug #17708621)• The optimizer calculated the cost for joined buffer scans incorrectly, evaluating rows filtered out byattached conditions not once, but once per join buffer. (Bug #17694707)• Incorrect reference counting in the range optimizer module resulted in potential for missing orduplicate rows in the query result set. (Bug #17619119)• Using the mysqldump --set-gtid-purged option with no value caused mysqldump to crash.(Bug #17650245)• A race condition between Performance Schema statement event threads led to a server exit. (Bug#17637970)• For debug builds, an aggregate function in a subquery join condition could raise an assertion. (Bug#17602807)• If SAFE_MUTEX was enabled (true only for debug builds), THR_LOCK_mutex was used before beinginitialized. (Bug #17641055, Bug #70639)• After the fix for Bug #16409270, it was not possible to #include following #include. (Bug #17514554)• An addressing error in accessing the join buffer could produce invalid results or a server exit. (Bug#17513341)• The parser permitted some queries with multiple ORDER BY clauses, which then failed duringexecution and caused a server exit. (Bug #17473479)• For debug builds, the server could exit for statements that inserted into a BLOB column declared asNOT NULL using a subquery that retrieved from a BLOB column and included GROUP BY NULL.(Bug #17458917)• Insufficient cleanup after removal of a SELECT_LEX structure caused dereferencing of a NULLpointer and a server exit. (Bug #17458169)• Within a CASE expression, use of a subquery referencing the VALUES() function could cause aserver exit. (Bug #17458914)References: This bug is a regression of Bug #14789787.• mysql_config incorrectly included some flags to generate compiler warning output. (Bug#17400967)• The parser silently accepted duplicate ORDER BY clauses and/or LIMIT clauses before ORDER BYclauses in subqueries. These caused failures during query execution. Fixing this problem results insome changes in parser behavior. The parser no longer accepts:33