Appendix聽C.聽MySQL Change History - MySQL 5.0参考手册英文版

The output of mysql --xml and mysqldump --xml now includes a valid XML namespace. (Bug#25946)

The mysql_create_system_tables script was removed because mysql_install_db no longer uses it in MySQL 5.1.

Renamed the old_mode system variable to old.

Added a MASTER_SSL_VERIFY_SERVER_CERT option for the CHANGE MASTER statement, and a Master_SSL_Verify_Server_Cert output column to the SHOW SLAVE STATUS statement. The option value also is written to the master.info file. (Bug#19991)

NDB Cluster: The behavior of the ndb_restore utility has been changed as follows:

For details of these changes, see Section聽15.8.3, 鈥�ndb_restore 鈥� Restore a Cluster Backup鈥�.

NDB Cluster (Replication)/Incompatible Change: The definition of the mysql.ndb_apply_status table has changed such that an online upgrade is not possible from MySQL 5.1.17 or earlier for a replication slave cluster; you must shut down all SQL nodes as part of the upgrade procedure. See Section聽15.5.2, 鈥淐luster Upgrade and Downgrade Compatibility鈥� before upgrading for details.

For more information about the changes to mysql.ndb_apply_status see Section聽15.10.4, 鈥淐luster Replication Schema and Tables鈥�.

NDB Cluster (Replication): Some circular replication setups are now supported for MySQL Cluster. See Section聽15.10.3, 鈥淜nown Issues鈥�, for detailed information. (Bug#25688, Bug#17095)

Security fix: If a stored routine was declared using SQL SECURITY INVOKER, a user who invoked the routine could gain privileges. (Bug#27337)

Security fix: The requirement of the DROP privilege for RENAME TABLE was not being enforced. (Bug#27515)

Security fix: A user with only the ALTER privilege on a partitioned table could obtain information about the table that should require the SELECT privilege. (Bug#23675)

The patches for Bug#19370 and Bug#21789 were reverted.

NDB Cluster (Disk Data): When in single user mode, it was possible to create log file groups and tablespaces from any SQL node connected to the cluster. (Bug#27712)

NDB Cluster (Disk Data): Changing a column specification or issuing a TRUNCATE statement on a Disk Data table caused the table to become an in-memory table. (Bug#24667, Bug#25296)

This fix supersedes an incomplete fix that was made for this issue in MySQL 5.1.15.

NDB Cluster (Replication): Setting SQL_LOG_BIN to zero did not disable binary logging. (Bug#27076)

This issue affected only the NDB storage engine.

NDB Cluster (Replication): It was possible for API nodes to begin interacting with the cluster subscription manager before they were fully connected to the cluster. (Bug#27651)

NDB Cluster (Replication): Under very high loads, checkpoints could be read or written with checkpoint indexes out of order. (Bug#27651)

NDB Cluster: NDB tables having MEDIUMINT AUTO_INCREMENT columns were not restored correctly by ndb_restore, causing spurious duplicate key errors. This issue did not affect TINYINT, INT, or BIGINT columns with AUTO_INCREMENT. (Bug#27775)

NDB Cluster: NDB tables with indexes whose names contained space characters were not restored correctly by ndb_restore (the index names were truncated). (Bug#27758)

NDB Cluster (Disk Data): Changes to a Disk Data table made as part of a transaction could not be seen by the client performing the changes until the transaction had been committed. (Bug#27757)

NDB Cluster: An INSERT followed a delete DELETE on the same NDB table caused a memory leak. (Bug#27756)

(This bug was introduced by the fix for Bug#20612.)

NDB Cluster: Some queries that updated multiple tables were not backed up or replicated correctly. (Bug#27748)

NDB Cluster: Joins on multiple tables containing BLOB columns could cause data nodes run out of memory, and to crash with the error NdbObjectIdMap::expand unable to expand. (Bug#26176)

NDB Cluster: When trying to create an NDB table after the server was started with --ndbcluster but without --ndb-connectstring, mysqld produced a memory allocation error. (Bug#27359)

NDB Cluster (APIs): Using NdbBlob::writeData() to write data in the middle of an existing blob value (that is, updating the value) could overwrite some data past the end of the data to be changed. (Bug#27018)

NDB Cluster (Replication): Trying to replicate a large number of frequent updates with a relatively small relay log (max-relay-log-size set to 1M or less) could cause the slave to crash. (Bug#27529)

NDB Cluster (Replication): An SQL node acting as a replication master server could be a single point of failure; that is, if it failed, the replication slave had no way of knowing this, which could result in a mismatch of data between the master and the slave. (Bug#21494)

NDB Cluster (Disk Data): CREATE TABLE ... LIKE disk_data_table created an in-memory NDB table. (Bug#25875)

NDB Cluster (Disk Data): Creating an excessive number of data files for a single tablespace caused data nodes to crash. (Bug#24521)

NDB Cluster: Under certain rare circumstances, DROP TABLE or TRUNCATE of an NDB table could cause a node failure or forced cluster shutdown. (Bug#27581)

NDB Cluster: Memory usage of a mysqld process grew even while idle. (Bug#27560)

NDB Cluster: Using more than 16GB for DataMemory caused problems with variable-size columns. (Bug#27512)

NDB Cluster: In an NDB table having a TIMESTAMP column using DEFAULT CURRENT_TIMESTAMP, that column would assume a random value when another column in the same row was updated. (Bug#27127)

NDB Cluster: Performing ALTER TABLE ... ENGINE=MERGE on an NDB table caused mysqld to crash. (Bug#26898)

NDB Cluster: The Cluster table handler did not set bits in null bytes correctly. (Bug#26591)

NDB Cluster: In some cases, AFTER UPDATE and AFTER DELETE triggers on NDB tables that referenced subject table did not see the results of operation which caused invocation of the trigger, but rather saw the row as it was prior to the update or delete operation.

This was most noticeable when an update operation used a subquery to obtain the rows to be updated. An example would be UPDATE tbl1 SET col2 = val1 WHERE tbl1.col1 IN (SELECT col3 FROM tbl2 WHERE c4 = val2) where there was an AFTER UPDATE trigger on table tbl1. In such cases, the trigger would fail to execute.

The problem occurred because the actual update or delete operations were deferred to be able to perform them later as one batch. The fix for this bug solves the problem by disabling this optimization for a given update or delete if the table has an AFTER trigger defined for this operation. (Bug#26242)

NDB Cluster: START BACKUP NOWAIT caused a spurious Out of backup record error in the management client (START BACKUP and START BACKUP WAIT STARTED performed normally). (Bug#25446)

NDB Cluster: When trying to create tables on an SQL node not connected to the cluster, a misleading error message Table 'tbl_name' already exists was generated. The error now generated is Could not connect to storage engine. (Bug#18676)

NDB Cluster: A data node failing while another data node was restarting could leave the cluster in an inconsistent state. In certain rare cases, this could lead to a race condition and the eventual forced shutdown of the cluster. (Bug#27466)

NDB Cluster: When using the MemReportFrequency configuration parameter to generate periodic reports of memory usage in the cluster log, DataMemory usage was not always reported for all data nodes. (Bug#27444)

NDB Cluster: Error messages displayed when running in single user mode were inconsistent. (Bug#27021)

NDB Cluster: On Solaris, the value of an NDB table column declared as BIT(33) was always displayed as 0. (Bug#26986)

NDB Cluster (Replication): An UPDATE on the master became a DELETE on slaves. (Bug#27378)

An interaction between SHOW TABLE STATUS and other concurrent statements that modify the table could result in a divide-by-zero error and a server crash. (Bug#27516)

The decimal.h header file was incorrectly omitted from binary distributions. (Bug#27456)

mysqldump could not connect using SSL. (Bug#27669)

yaSSL crashed on pre-Pentium Intel CPUs. (Bug#21765)

The test for the MYSQL_OPT_SSL_VERIFY_SERVER_CERT option for mysql_options() was performed incorrectly. Also changed as a result of this bugfix: The arg option for the mysql_options() C API function was changed from char * to void *. (Bug#24121)

Comparisons using row constructors could fail for rows containing NULL values. (Bug#27704)

Performing a UNION on two views that had had ORDER BY clauses resulted in an Unknown column error. (Bug#27786)

The CRC32() function returns an unsigned integer, but the metadata was signed, which could cause certain queries to return incorrect results. (For example, queries that selected a CRC32() value and used that value in the GROUP BY clause.) (Bug#27530)

A race condition between DROP TABLE and SHOW TABLE STATUS could cause the latter to display incorrect information. (Bug#27499)

mysqldump would not dump a view for which the DEFINER no longer exists. (Bug#26817)

Changing a utf8 column in an InnoDB table to a shorter length did not shorten the data values. (Bug#20095)

The server did not shut down cleanly. (Bug#27310)

Using SET GLOBAL to change the lc_time_names system variable had no effect on new connections. (Bug#22648)

The XML output representing an empty result was an empty string rather than an empty <resultset/> element. (Bug#27608)

The range optimizer could consume a combinatorial amount of memory for certain classes of WHERE clauses. (Bug#26624)

mysqlbinlog produced different output with the -R option than without it. (Bug#27171)

A stored function invocation in the WHERE clause was treated as a constant. (Bug#27354)

mysqldump could not dump the log tables. (Bug#26121)

Implicit conversion of 9912101 to DATE did not match CAST(9912101 AS DATE). (Bug#23093)

CURDATE() is less than NOW(), either when comparing CURDATE() directly (CURDATE() < NOW() is true) or when casting CURDATE() to DATE (CAST(CURDATE() AS DATE) < NOW() is true). However, storing CURDATE() in a DATE column and comparing col_name < NOW() incorrectly yielded false. This is fixed by comparing a DATE column as DATETIME for comparisons to a DATETIME constant. (Bug#21103)

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 DATE_ADD(), DATE_SUB(), + INTERVAL, and - INTERVAL. (For example, DATE_ADD('0050-01-01 00:00:00', INTERVAL 0 SECOND) became '2050-01-01 00:00:00'.) (Bug#18997)

Some equi-joins containing a WHERE clause that included a NOT IN subquery caused a server crash. (Bug#27870)

A memory leak in the event scheduler that was uncovered by Valgrind was fixed. (Bug#27733)

For queries that used ORDER BY with InnoDB tables, if the optimizer chose an index for accessing the table but found a covering index that enabled the ORDER BY to be skipped, no results were returned. (Bug#24778)

Group relay log rotation updated only the log position and not the name, causing the slave to stop. (Bug#27583)

Conversion of DATETIME values in numeric contexts sometimes did not produce a double (YYYYMMDDHHMMSS.uuuuuu) value. (Bug#16546)

Passing nested row expressions with different structures to an IN predicate caused a server crash. (Bug#27484)

SELECT DISTINCT could return incorrect results if the select list contained duplicated columns. (Bug#27659)

A subquery could get incorrect values for references to outer query columns when it contained aggregate functions that were aggregated in outer context. (Bug#27321)

In some cases, the optimizer preferred a range or full index scan access method over lookup access methods when the latter were much cheaper. (Bug#19372)

Duplicates were not properly identified among (potentially) long strings used as arguments for GROUP_CONCAT(DISTINCT). (Bug#26815)

For InnoDB, fixed consistent-read behavior of the first read statement, if the read was served from the query cache, for the READ COMMITTED isolation level. (Bug#21409)

The binary log incompatiblity introduced by the fix for Bug#22583 was corrected. (Bug#27779)

Row-based replication of MyISAM to non-MyISAM tables did not work correctly for BIT columns. This has been corrected, but the fix introduces an incompatibility into the binary log format. (Bug#22583) (The incompatibility is corrected by the fix for Bug#27779.)

Duplicate members in SET definitions were not detected. Now they result in a warning; if strict SQL mode is enabled, an error occurs instead. (Bug#27069)

If the name of a table given to myisamchk -rq was a packed table and the name included the .MYI extension, myisamchk incorrectly created a file with a .MYI.MYI extension. (Bug#26782)

For INSERT INTO ... SELECT where index searches used column prefixes, insert errors could occur when key value type conversion was done. (Bug#26207)

For SHOW ENGINE INNODB STATUS, the LATEST DEADLOCK INFORMATION was not always cleared properly. (Bug#25494)

On Windows, if the server was installed as a service, it did not auto-detect the location of the data directory. (Bug#20376)

The FEDERATED engine did not allow the local and remote tables to have different names. (Bug#26257)

The NO_DIR_IN_CREATE server SQL mode was not enforced for partitioned tables. (Bug#24663)

On Windows, trying to use backslash (\) characters in paths for DATA DIRECTORY and INDEX DIRECTORY when creating partitioned tables caused MySQL to crash. (Bug#26074)

(You must use / characters when specifying paths for these options, regardless of platform. See Section聽16.1, 鈥淥verview of Partitioning in MySQL鈥�, for an example using absolute paths for DATA DIRECTORY and INDEX DIRECTORY when creating a partitioned table on Windows.)

A damaged or missing mysql.event table caused SHOW VARIABLES to fail. (Bug#23631)

Database and table names have a maximum length of 64 characters (even if they contain multi-byte characters), but were being truncated to 64 bytes. (Bug#21432)

If a rotate event occured in the middle of a non-transaction group, the group position would be updated by the rotate event indicating an illegal group start position that was effectively inside a group. This can happen if, for example, a rotate occurs between an Intvar event and the associated Query event, or between the table map events and the rows events when using row-based replication. (Bug#23171)

mysqldump could crash or exhibit incorrect behavior when some options were given very long values, such as --fields-terminated-by="some very long string". The code has been cleaned up to remove a number of fixed-sized buffers and to be more careful about error conditions in memory allocation. (Bug#26346)

Setting a column to NOT NULL with an ON DELETE SET NULL clause foreign key crashes the server. (Bug#25927)

The values displayed for the Innodb_row_lock_time, Innodb_row_lock_time_avg, and Innodb_row_lock_time_max status variables were incorrect. (Bug#23666)

COUNT(decimal_expr) sometimes generated a spurious truncation warning. (Bug#21976)

With NO_AUTO_VALUE_ON_ZERO SQL mode enabled, LOAD DATA operations could assign incorrect AUTO_INCREMENT values. (Bug#27586)

Incorrect results could be returned for some queries that contained a select list expression with IN or BETWEEN together with an ORDER BY or GROUP BY on the same expression using NOT IN or NOT BETWEEN. (Bug#27532)

For the INFORMATION_SCHEMA SESSION_STATUS and GLOBAL_STATUS tables, some status values were incorrectly converted to the data type of the VARIABLE_VALUE column. (Bug#27327)

Queries containing subqueries with COUNT(*) aggregated in an outer context returned incorrect results. This happened only if the subquery did not contain any references to outer columns. (Bug#27257)

Use of an aggregate function from an outer context as an argument to GROUP_CONCAT() caused a server crash. (Bug#27229)

Restoration of the default database after stored routine or trigger execution on a slave could cause replication to stop if the database no longer existed. (Bug#25082)

String truncation upon insertion into an integer or year column did not generate a warning (or an error in strict mode). (Bug#26359, Bug#27176)

In out-of-memory conditions, the server might crash or otherwise not report an error to the Windows event log. (Bug#27490)

The temporary file-creation code was cleaned up on Windows to improve server stability. (Bug#26233)

Out-of-memory errors were not reported. Now they are written to the error log. (Bug#26844)

mysqldump crashed for MERGE tables if the --complete-insert (-c) option was given. (Bug#25993)

Corrupted MyISAM tables that have different definitions in the .frm and .MYI tables might cause a server crash. (Bug#25908)

In certain situations, MATCH ... AGAINST returned false hits for NULL values produced by LEFT JOIN when no full-text index was available. (Bug#25729)

OPTIMIZE TABLE might fail on Windows when it attempts to rename a temporary file to the original name if the original file had been opened, resulting in loss of the .MYD file. (Bug#25521)

GRANT statements were not replicated if the server was started with the --replicate-ignore-table or --replicate-wild-ignore-table option. (Bug#25482)

MBROverlaps() returned incorrect values in some cases. (Bug#24563)

A problem in handling of aggregate functions in subqueries caused predicates containing aggregate functions to be ignored during query execution. (Bug#24484)

Improved out-of-memory detection when sending logs from a master server to slaves, and log a message when allocation fails. (Bug#26837)

MBRDisjoint(), MBRequal(), MBRIntersects(), MBROverlaps(), MBRTouches(), and MBRWithin() were inadvertently omitted from recent versions of MySQL (5.1.14 to 5.1.17). (Bug#24563)

SHOW CREATE VIEW qualified references to stored functions in the view definition with the function's database name, even when the database was the default database. This affected mysqldump (which uses SHOW CREATE VIEW to dump views) because the resulting dump file could not be used to reload the database into a different database. SHOW CREATE VIEW now suppresses the database name for references to functions in the default database. (Bug#23491)

When MySQL logged slow query information to a CSV table, it used an incorrect formula to calculate the query_time and lock_time values. (Bug#27638)

With innodb_file_per_table enabled, attempting to rename an InnoDB table to a non-existent database caused the server to exit. (Bug#27381)

mysql_install_db could terminate with an error after failing to determine that a system table already existed. (Bug#27022)

For InnoDB tables having a clustered index that began with a CHAR or VARCHAR column, deleting a record and then inserting another before the deleted record was purged could result in table corruption. (Bug#26835)

make_win_bin_dist neglected to copy some required MyISAM table files. (Bug#26922)

Fixed a possible buffer overflow in SHOW PROCEDURE CODE. (Bug#26303)

Selecting the result of AVG() within a UNION could produce incorrect values. (Bug#24791)

Access via my_pread() or my_pwrite() to table files larger than 2GB could fail on some systems. (Bug#24566)

An INTO OUTFILE clause is allowed only for the final SELECT of a UNION, but this restriction was not being enforced correctly. (Bug#23345)

Duplicate entries were not assessed correctly in a MEMORY table with a BTREE primary key on a utf8 ENUM column. (Bug#24985)

For MyISAM tables, COUNT(*) could return an incorrect value if the WHERE clause compared an indexed TEXT column to the empty string (''). This happened if the column contained empty strings and also strings starting with control characters such as tab or newline. (Bug#26231)

For DELETE FROM tbl_name ORDER BY col_name (with no WHERE or LIMIT clause), the server did not check whether col_name was a valid column in the table. (Bug#26186)

ALTER VIEW requires the CREATE VIEW and DROP privileges for the view. However, if the view was created by another user, the server erroneously required the SUPER privilege. (Bug#26813)

mysqlbinlog --base64-output produced invalid SQL. (Bug#26194)

In a view, a column that was defined using a GEOMETRY function was treated as having the LONGBLOB data type rather than the GEOMETRY type. (Bug#27300)

Some views could not be created even when the user had the requisite privileges. (Bug#24040)

With the NO_AUTO_VALUE_ON_ZERO SQL mode enabled, LAST_INSERT_ID() could return 0 after INSERT ... ON DUPLICATE KEY UPDATE. Additionally, the next rows inserted (by the same INSERT, or the following INSERT with or without ON DUPLICATE KEY UPDATE), would insert 0 for the auto-generated value if the value for the AUTO_INCREMENT column was NULL or missing. (Bug#23233)

Executing an INSERT ... SELECT ... FROM INFORMATION_SCHEMA.GLOBAL_STATUS statement from within an event caused a server crash. (Bug#26174)

Having the EXECUTE privilege for a routine in a database should make it possible to USE that database, but the server returned an error instead. This has been corrected. As a result of the change, SHOW TABLES for a database in which you have only the EXECUTE privilege returns an empty set rather than an error. (Bug#9504)

When RAND() was called multiple times inside a stored procedure, the server did not write the correct random seed values to the binary log, resulting in incorrect replication. (Bug#25543)

SOUNDEX() returned an invalid string for international characters in multi-byte character sets. (Bug#22638)

Row equalities in WHERE clauses could cause memory corruption. (Bug#27154)

GROUP BY on a ucs2 column caused a server crash when there was at least one empty string in the column. (Bug#27079)

Evaluation of an IN() predicate containing a decimal-valued argument caused a server crash. (Bug#27362)

Storing NULL values in spatial fields caused excessive memory allocation and crashes on some systems. (Bug#27164)

mysql_stmt_fetch() did an invalid memory deallocation when used with the embedded server. (Bug#25492)

For FEDERATED tables, SHOW CREATE TABLE could fail when the table name was longer than the connection name. (Bug#27036)

In a MEMORY table, using a BTREE index to scan for updatable rows could lead to an infinite loop. (Bug#26996)

The range optimizer could cause the server to run out of memory. (Bug#26625)

CREATE SERVER, DROP SERVER, and ALTER SERVER did not require any privileges. Now these statements require the SUPER privilege. (Bug#25671)

Concurrent CREATE SERVER and ALTER SERVER statements could cause a deadlock. (Bug#25721)

Difficult repair or optimization operations could cause an assertion failure, resulting in a server crash. (Bug#25289)

Incompatible change: Scheduled events now use the MySQL server time zone to determine their schedules, rather than UTC as in previous releases. Because of this change, scheduled event metadata now includes time zone information, which can be seen in the TIME_ZONE column of the INFORMATION_SCHEMA.EVENTS table and the Time zone column in the output of the SHOW EVENTS statement. These columns have been added in this release, along with a time_zone column in the mysql.event table. Due to these changes, events created in previous versions of MySQL cannot be created, viewed, or used until mysql.event has been upgraded. (Bug#16420)

Important change: The CREATE EVENT and ALTER EVENT statements now support a DEFINER clause, similar to that used in the CREATE TRIGGER statement. (Bug#16425)

See Section聽20.2.2, 鈥�CREATE EVENT Syntax鈥�, for detailed information.

Important change: The following options for controlling replication master configuration on a slave are now deprecated.

To change the master configuration on a slave you should use the CHANGE MASTER statement. (See also #21490)

Statements that affect mysql database tables now are written to the binary log using the following rules:

For more details, see Section聽6.1.2.4, 鈥淟ogging Format for Changes to mysql Database Tables鈥�. (Bug#25091)

Prepared statements now use the query cache under the conditions described in Section聽5.13.1, 鈥淗ow the Query Cache Operates鈥�. (Bug#735)

Added the --secure-file-priv option for mysql-test-run.pl, which limits the effect of the load_file command for mysqltest and for the LOAD DATA and SELECT ... INTO OUTFILE statements to work with files in a given directory. (Bug#18628)

Added the innodb_stats_on_metadata system variable to enable control over whether InnoDB performs statistics gathering when metadata statements are executed. See Section聽14.5.4, 鈥�InnoDB Startup Options and System Variables鈥�. (Bug#26598)

Added the hostname system variable, which the server sets at startup to the server hostname.

The syntax for index hints has been extended to enable more fine-grained control over the optimizer's selection of an execution plan for various phases of query processing. See Section聽13.2.7.2, 鈥淚ndex Hint Syntax鈥�. (Bug#21174)

Added the old_mode system variable to cause the server to revert to certain behaviors present in older versions. Currently, this variable affects handling of index hints. See Section聽13.2.7.2, 鈥淚ndex Hint Syntax鈥�.

NDB Cluster: Added the --skip-table-check option (short form -s) for ndb_restore, which causes the restoration process to ignore any changes that may have occurred in table schemas after the backup was made. Previously, this was the default behavior. (Bug#24363)

See Section聽15.8.3, 鈥�ndb_restore 鈥� Restore a Cluster Backup鈥�, for more information.

The server now includes a timestamp in error messages that are logged as a result of unhandled signals (such as mysqld got signal 11 messages). (Bug#24878)

Prefix lengths for columns in SPATIAL indexes no longer can be specified. For tables created in older versions of MySQL that have SPATIAL indexes containing prefixed columns, dumping and reloading the table causes the indexes to be created with no prefixes. (The full column width of each column is indexed.) (Bug#26794)

Added a --no-beep option to mysqladmin. It suppresses the warning beep that is emitted by default for errors such as a failure to connect to the server. (Bug#26964)

Incompatible change: INSERT DELAYED statements are not supported for MERGE tables, but the MERGE storage engine was not rejecting such statements, resulting in table corruption. Applications previously using INSERT DELAYED into MERGE table will break when upgrading to versions with this fix. To avoid the problem, remove DELAYED from such statements. (Bug#26464)

Creating a table on one SQL node while in single user mode caused other SQL nodes to crash. (Bug#26997)

NDB Cluster: The output from ndb_restore --print_data was incorrect for a backup made of a database containing tables with TINYINT or SMALLINT columns. (Bug#26740)

NDB Cluster: After putting the cluster in single user mode from one MySQL server, trying to drop an NDB table from a second MySQL server also connected to the cluster would cause the second MySQL server to hang. (Bug#27254)

NDB Cluster (Cluster APIs): You can now use the ndb_mgm_check_connection() function to determine whether a management server is running. See ndb_mgm_check_connection().

NDB Cluster: mysqld could crash shortly after a data node failure following certain DML operations. (Bug#27169)

NDB Cluster: The management client command node_id STATUS displayed the message Node node_id: not connected when node_id was not the node ID of a data node. (Bug#21715)

NDB Cluster (Cluster APIs): NAND and NOR operations with NdbScanFilter did not perform correctly. (Bug#24568)

NDB Cluster (Cluster Replication): The simultaneous failure of a data node and an SQL node could cause replication to fail. (Bug#27005)

NDB Cluster (Disk Data): Under some circumstances, a data node could fail during restart while flushing Disk Data UNDO logs. (Bug#27102)

NDB Cluster (Disk Data): Creating multiple Disk Data tables using different tablespaces could sometimes cause the cluster to fail. (Bug#25992)

NDB Cluster (Disk Data): ALTER TABLE ... ADD COLUMN ... on a Disk Data table moved data for existing non-indexed columns from the tablespace into memory. (Bug#25880)

NDB Cluster (Disk Data): DROP INDEX on a Disk Data table did not always move data from memory into the tablespace. (Bug#25877)

NDB Cluster (Disk Data): When creating a log file group, setting INITIAL_SIZE to less than UNDO_BUFFER_SIZE caused data nodes to crash. (Bug#25743)

NDB Cluster: It was not possible to set LockPagesInMainMemory equal to 0. (Bug#27291)

NDB Cluster: A race condition could sometimes occur if the node acting as master failed while node IDs were still being allocated during startup. (Bug#27286)

NDB Cluster: When a data node was taking over as the master node, a race condition could sometimes occur as the node was assuming responsibility for handling of global checkpoints. (Bug#27283)

NDB Cluster: A delete operation using a scan following by an insert using a scan could cause a data node to fail. (Bug#27203)

NDB Cluster: The same failed request from an API node could be handled by the cluster multiple times, resulting in reduced performance. (Bug#27087)

NDB Cluster: The failure of a data node while restarting could cause other data nodes to hang or crash. (Bug#27003)

NDB Cluster: mysqld processes would sometimes crash under high load. (Bug#26825)

NDB Cluster: When performing an upgrade or downgrade, no specific error information was made available when trying to upgrade data nodes or SQL nodes before upgrading management nodes. (Bug#21296)

NDB Cluster: Some values of MaxNoOfTables caused the error Job buffer congestion to occur. (Bug#19378)

NDB Cluster: An invalid pointer was returned following a FSCLOSECONF signal when accessing the REDO logs during a node restart or system restart. (Bug#26515)

NDB Cluster (Disk Data): A memory overflow could occur with tables having a large amount of data stored on disk, or with queries using a very high degree of parallelism on Disk Data tables. (Bug#26514)

NDB Cluster (Disk Data): Use of a tablespace whose INITIAL_SIZE was greater than 1 GB could cause the cluster to crash. (Bug#26487)

NDB Cluster: Using only the --print_data option (and no other options) with ndb_restore caused ndb_restore to fail. (Bug#26741)

This bug was introduced by the fix for Bug#14612.

NDB Cluster: An infinite loop in an internal logging function could cause trace logs to fill up with Unknown Signal type error messages and thus grow to unreasonable sizes. (Bug#26720)

While preparing prepared statements, the server acquired unnecessary table write locks. (Bug#18326)

For some operations, system tables in the mysql database must be accessed. For example, the HELP statement requires the contents of the server-side help tables, and CONVERT_TZ() might need to read the time zone tables. However, to perform such operations while a LOCK TABLES statement is in effect, the server required you to also lock the requisite system tables explicitly or a lock error occurred:

mysql> LOCK TABLE t1 READ;
Query OK, 0 rows affected (0.02 sec)
mysql> HELP HELP;
ERROR 1100 (HY000) at line 4: Table 'help_topic' was not
locked with LOCK TABLES

Now, the server implicitly locks the system tables for reading as necessary so that you need not lock them explicitly. These tables are treated as just described:

mysql.help_category
mysql.help_keyword
mysql.help_relation
mysql.help_topic
mysql.proc
mysql.time_zone
mysql.time_zone_leap_second
mysql.time_zone_name
mysql.time_zone_transition
mysql.time_zone_transition_type

If you want to explicitly place a WRITE lock on any of those tables with a LOCK TABLES statement, the table must be the only one locked; no other table can be locked with the same statement. (Bug#9953)

For a stored procedure containing a SELECT statement that used a complicated join with an ON expression, the expression could be ignored during re-execution of the procedure, yielding an incorrect result. (Bug#20492)

The parser accepted illegal code in SQL exception handlers, leading to a crash at runtime when executing the code. (Bug#26503)

On Windows, debug builds of mysqld could fail with heap assertions. (Bug#25765)

On Windows, debug builds of mysqlbinlog could fail with a memory error. (Bug#23736)

SELECT ... INTO OUTFILE with a long FIELDS ENCLOSED BY value could crash the server. (Bug#27231)

The server could hang during binary log rotation. (Bug#26079)

Increasing the width of a DECIMAL column could cause column values to be changed. (Bug#24558)

DOUBLE values such as 20070202191048.000000 were being treated as illegal arguments by WEEK(). (Bug#23616)

Replication between master and slave would infinitely retry binary log transmission where the max_allowed_packet on the master was larger than that on the slave if the size of the transfer was between these two values. (Bug#23775)

Setting event_scheduler=1 or event_scheduler=ON caused the server to crash if the server had been started with --skip-grant-tables. Starting the server with --skip-grant-tables now causes event_scheduler to be set to DISABLED automatically, overriding any other value that may have been set. (Bug#26807)

SHOW CREATE EVENT failed to display the STARTS and ENDS clauses for an event defined with STARTS NOW(), ENDS NOW(), or both. (Bug#26429)

Invalid optimization of pushdown conditions for queries where an outer join was guaranteed to read only one row from the outer table led to results with too few rows. (Bug#26963)

For INSERT ... ON DUPLICATE KEY UPDATE statements on tables containing AUTO_INCREMENT columns, LAST_INSERT_ID() was reset to 0 if no rows were successfully inserted or changed. 鈥�Not changed鈥� includes the case where a row was updated to its current values, but in that case, LAST_INSERT_ID() should not be reset to 0. Now LAST_INSERT_ID() is reset to 0 only if no rows were successfully inserted or touched, whether or not touched rows were changed. (Bug#27033)

This bug was introduced by the fix for Bug#19978.

AFTER UPDATE triggers were not activated by the update part of INSERT ... ON DUPLICATE KEY UPDATE statements. (Bug#27006, Bug#27210)

This bug was introduced by the fix for Bug#19978.

For INSERT ... ON DUPLICATE KEY UPDATE statements where some AUTO_INCREMENT values were generated automatically for inserts and some rows were updated, one auto-generated value was lost per updated row, leading to faster exhaustion of the range of the AUTO_INCREMENT column. (Bug#24432)

Because the original problem can affect replication (different values on master and slave), it is recommended that the master and its slaves be upgraded to the current version.

For an INSERT statement that should fail due to a column with no default value not being assigned a value, the statement succeeded with no error if the column was assigned a value in an ON DUPLICATE KEY UPDATE clause, even if that clause was not used. (Bug#26261)

A result set column formed by concatention of string literals was incomplete when the column was produced by a subquery in the FROM clause. (Bug#26738)

When using the result of SEC_TO_TIME() for time value greater than 24 hours in an ORDER BY clause, either directly or through a column alias, the rows were sorted incorrectly as strings. (Bug#26672)

If the server was started with --skip-grant-tables, Selecting from INFORMATION_SCHEMA tables causes a server crash. (Bug#26285)

Adding ORDER BY clause to a query on an InnoDB table could cause the statement to return no result if the optimizer chose a covering index that enabled it to skip the ORDER BY. (Bug#24778)

IN ((subquery)), IN (((subquery))), and so forth, are equivalent to IN (subquery), which is always interpreted as a table subquery (so that it is allowed to return more than one row). MySQL was treating the 鈥�over-parenthesized鈥� subquery as a single-row subquery and rejecting it if it returned more than one row. This bug primarily affected automatically generated code (such as queries generated by Hibernate), because humans rarely write the over-parenthesized forms. (Bug#21904)

For MERGE tables defined on underlying tables that contained a short VARCHAR column (shorter than four characters), using ALTER TABLE on at least one but not all of the underlying tables caused the table definitions to be considered different from that of the MERGE table, even if the ALTER TABLE did not change the definition. (Bug#26881)

If a thread previously serviced a connection that was killed, excessive memory and CPU use by the thread occurred if it later serviced a connection that had to wait for a table lock. (Bug#25966)

CURDATE() is less than NOW(), either when comparing CURDATE() directly (CURDATE() < NOW() is true) or when casting CURDATE() to DATE (CAST(CURDATE() AS DATE) < NOW() is true). However, storing CURDATE() in a DATE column and comparing col_name < NOW() incorrectly yielded false. This is fixed by comparing a DATE column as DATETIME for comparisons to a DATETIME constant. (Bug#21103)

A view on a join is insertable for INSERT statements that store values into only one table of the join. However, inserts were being rejected if the inserted-into table was used in a self-join because MySQL incorrectly was considering the insert to modify multiple tables of the view. (Bug#25122)

Expressions involving SUM(), when used in an ORDER BY clause, could lead to out-of-order results. (Bug#25376)

LOAD DATA INFILE sent an okay to the client before writing the binary log and committing the changes to the table had finished, thus violating ACID requirements. (Bug#26050)

Views that used a scalar correlated subquery returned incorrect results. (Bug#26560)

IF(expr, unsigned_expr, unsigned_expr) was evaluated to a signed result, not unsigned. This has been corrected. The fix also affects constructs of the form IS [NOT] {TRUE|FALSE}, which were transformed internally into IF() expressions that evaluated to a signed result. (Bug#24532)

For existing views that were defined using IS [NOT] {TRUE|FALSE} constructs, there is a related implication. The definitions of such views were stored using the IF() expression, not the original construct. This is manifest in that SHOW CREATE VIEW shows the transformed IF() expression, not the original one. Existing views will evaluate correctly after the fix, but if you want SHOW CREATE VIEW to display the original construct, you must drop the view and re-create it using its original definition. New views will retain the construct in their definition.

BENCHMARK() did not work correctly for expressions that produced a DECIMAL result. (Bug#26093)

For MEMORY tables, extending the length of a VARCHAR column with ALTER TABLE might result in an unusable table. (Bug#26080)

For some values of the position argument, the INSERT() function could insert a NUL byte into the result. (Bug#26281)

Creating a table with latin characters in the name caused the output of SHOW FULL TABLES to have ERROR for the table type. (Bug#25081)

Inserting utf8 data into a TEXT column that used a single-byte character set could result in spurious warnings about truncated data. (Bug#25815)

EXPLAIN EXTENDED did not show WHERE conditions that were optimized away. (Bug#22331)

INSERT DELAYED statements inserted incorrect values into BIT columns. (Bug#26238)

For expr IN(value_list), the result could be incorrect if BIGINT UNSIGNED values were used for expr or in the value list. (Bug#19342)

When a TIME_FORMAT() expression was used as a column in a GROUP BY clause, the expression result was truncated. (Bug#20293)

For SUBSTRING() evaluation using a temporary table, when SUBSTRING() was used on a LONGTEXT column, the max_length metadata value of the result was incorrectly calculated and set to 0. Consequently, an empty string was returned instead of the correct result. (Bug#15757)

Use of a GROUP BY clause that referred to a stored function result together with WITH ROLLUP caused incorrect results. (Bug#25373)

Use of a subquery containing GROUP BY and WITH ROLLUP caused a server crash. (Bug#26830)

Use of a subquery containing a UNION with an invalid ORDER BY clause caused a server crash. (Bug#26661)

In certain cases it could happen that deleting a row corrupted an RTREE index. This affected indexes on spatial columns. (Bug#25673)

SSL connections failed on Windows. (Bug#26678)

Added support for --debugger=dbx for mysql-test-run.pl and fixed support for --debugger=devenv, --debugger=DevEnv, and --debugger=/path/to/devenv. (Bug#26792)

X() IS NULL and Y() IS NULL comparisons failed when X() and Y() returned NULL. (Bug#26038)

UNHEX() IS NULL comparisons failed when UNHEX() returned NULL. (Bug#26537)

The REPEAT() function did not allow a column name as the count parameter. (Bug#25197)

On 64-bit Windows, large timestamp values could be handled incorrectly. (Bug#26536)

In some error messages, inconsistent format specifiers were used for the translations in different languages. comp_err (the error message compiler) now checks for mismatches. (Bug#26571)

On Windows, the server exhibited a file-handle leak after reaching the limit on the number of open file descriptors. (Bug#25222)

A reference to a non-existent column in the ORDER BY clause of an UPDATE ... ORDER BY statement could cause a server crash. (Bug#25126)

mysqlimport used a variable of the wrong type for the --use-threads option, which could cause a crash on some architectures. (Bug#23814)

A multiple-row delayed insert with an auto increment column could cause duplicate entries to be created on the slave in a replication environment. (Bug#25507, Bug#26116)

Using mysqlbinlog on a binary log would crash if there were a large number of row-based events related to a single statement. (Bug#25628)

Duplicating the usage of a user variable in a stored procedure or trigger would not be replicated correctly to the slave. (Bug#25167)

User defined variables used within stored procedures and triggers are not replicated correctly when operating in statement-based replication mode. (Bug#20141, Bug#14914)

Loading data using LOAD DATA INFILE may not replicate correctly (due to character set incompatibilities) if the character_set_database variable is set before the data is loaded. (Bug#15126)

DROP TRIGGER statements would not be filtered on the slave when using the replication-wild-do-table option. (Bug#24478)

SHOW ENGINE MUTEX STATUS failed to produce an Unknown table engine error. (Bug#24392)

See Section聽13.5.4.12, 鈥�SHOW ENGINE Syntax鈥�.

MySQL would not compile when configured using --without-query-cache. (Bug#25075)

When using certain server SQL modes, the mysql.proc table was not created by mysql_install_db. In addition, the creation of this and other MySQL system tables was not checked for by mysql-test-run.pl. (Bug#23669, Bug#20166)

It was not possible to use XPath keywords as tag names for expressions used in the ExtractValue() function. (Bug#24747)

VIEW restrictions were applied to SELECT statements after a CREATE VIEW statement failed, as though the CREATE had succeeded. (Bug#25897)

An INSERT trigger invoking a stored routine that inserted into a table other than the one on which the trigger was defined would fail with a Table '...' doesn't exist referring to the second table when attempting to delete records from the first table. (Bug#21825)

A stored procedure that made use of cursors failed when the procedure was invoked from a stored function. (Bug#25345)

When nesting stored procedures within a trigger on a table, a false dependency error was thrown when one of the nested procedures contained a DROP TABLE statement. (Bug#22580)

When attempting to call a stored procedure creating a table from a trigger on a table tbl in a database db, the trigger failed with ERROR 1146 (42S02): Table 'db.tbl' doesn't exist. However, the actual reason that such a trigger fails is due to the fact that CREATE TABLE causes an implicit COMMIT, and so a trigger cannot invoke a stored routine containing this statement. A trigger which does so now fails with ERROR 1422 (HY000): Explicit or implicit commit is not allowed in stored function or trigger, which makes clear the reason for the trigger's failure. (Bug#18914)

Local variables in stored routines or triggers, when declared as the BIT type, were interpreted as strings. (Bug#12976)

When a stored routine attempted to execute a statement accessing a nonexistent table, the error was not caught by the routine's exception handler. (Bug#8407, Bug#20713)

NOW() returned the wrong value in statements executed at server startup with the --init-file option. (Bug#23240)

Instance Manager did not remove the angel PID file on a clean shutdown. (Bug#22511)

Setting the slow_query_log_file system variable caused log output to go tothe general log, not the slow query log. (Bug#23225)

The server could crash if two or more threads initiated query cache resize operation at moments very close in time. (Bug#23527)

The conditions checked by the optimizer to allow use of indexes in IN predicate calculations were unnecessarily tight and were relaxed. (Bug#20420)

Several deficiencies in resolution of column names for INSERT ... SELECT statements were corrected. (Bug#25831)

Indexes on TEXT columns were ignored when ref accesses were evaluated. (Bug#25971)

The update columns for INSERT ... SELECT ... ON DUPLICATE KEY UPDATE could be assigned incorrect values if a temporary table was used to evaluate the SELECT. (Bug#16630)

A user-defined variable could be assigned an incorrect value if a temporary table was employed in obtaining the result of the query used to determine its value. (Bug#24010)

Queries that used a temporary table for the outer query when evaluating a correlated subquery could return incorrect results. (Bug#23800)

For index reads, the BLACKHOLE engine did not return end-of-file (which it must because BLACKHOLE tables contain no rows), causing some queries to crash. (Bug#19717)

A query of type index_merge, and with a WHERE clause having the form WHERE indexed_column_1=value_1 OR indexed_column_2=value_2 on a partitioned table caused the server to crash. (Bug#26117)

Incompatible change: TRUNCATE TABLE now requires the DROP privilege rather than the DELETE privilege. (Bug#23556).

NDB Cluster (Cluster APIs) / Incompatible change: The AbortOption type is now a member of the NdbOperation class; its values and behavior have also changed. NdbTransaction::AbortOption can no longer be used, and applications written against the NDB API may need to be rewritten and recompiled to accomodate these changes. For more information about this change, see The NdbOperation::AbortOption Type.

This also affects the behavior of the NdbTransaction::execute() method, which now reports failure only if the transaction was actually aborted. See NdbTransaction::execute(), for more information.

NDB Cluster: A new configuration parameter MemReportFrequency allows for additional control of data node memory usage. Previously, only warnings at predetermined percentages of memory allocation were given; setting this parameter allows for that behavior to be overridden. For more information, see Section聽15.4.4.5, 鈥淒efining Data Nodes鈥�.

NDB Cluster (Cluster APIs): A new ndb_mgm_get_clusterlog_loglevel() function was added to the MGM API.

For more information, see ndb_mgm_get_clusterlog_loglevel().

NDB Cluster: Previously, when a data node failed more than 8 times in succession to start, this caused a forced shutdown of the cluster. Now, when a data node fails to start 7 consecutive times, the node will not start again until it is started with the --initial option, and a warning to this effect is written to the error log. (Bug#25984)

NDB Cluster: A number of new and more descriptive error messages covering transporter errors were added. (Bug#22025)

NDB Cluster: In the event that all cluster management and API nodes are configured with ArbitrationRank=0, ndb_mgmd now issues the following warning when starting: Cluster configuration warning: Neither MGM nor API nodes are configured with arbitrator, may cause complete cluster shutdown in case of host failure. (Bug#23546)

The localhost anonymous user account created during MySQL installation on Windows now has no global privileges. Formerly this account had all global privileges. For operations that require global privileges, the root account can be used instead. (Bug#24496)

In the INFORMATION_SCHEMA REFERENTIAL_CONSTRAINTS table, the UNIQUE_CONSTRAINT_NAME column incorrectly named the referenced table. Now it names the referenced constraint, and a new column, REFERENCED_TABLE_NAME, names the referenced table. (Bug#21713)

RAND() now allows non-constant initializers (such as a column name) as its argument. In this case, the seed is initialized with the value for each invocation of RAND(). (One implication of this is that for equal argument values, RAND() will return the same value each time.) (Bug#6172)

The bundled yaSSL library was upgraded to version 1.5.8.

CONNECTION is no longer treated as a reserved word. (Bug#12204)

Security fix: Using an INFORMATION_SCHEMA table with ORDER BY in a subquery could cause a server crash. (CVE-2007-1420, Bug#24630, Bug#26556) We would like to thank Oren Isacson from Flowgate Security Consulting as well as well as Stefan Streichsbier from SEC Consult for informing us about this problem.

NDB Cluster: Condition pushdown did not work with prepared statements. (Bug#26225)

NDB Cluster (APIs): After defining a delete operation using (NdbOperation::deleteTuple()) on a nonexistent primary key of a table having a BLOB or TEXT column, invoking NdbTransaction::execute() caused the calling application to enter an endless loop rather than raising an error. (Bug#24028)

NDB Cluster: An inadvertent use of unaligned data caused ndb_restore to fail on some 64-bit platforms, including Sparc and Itanium-2. (Bug#26739)

NDB Cluster: The InvalidUndoBufferSize error used the same error code (763) as the IncompatibleVersions error. InvalidUndoBufferSize now uses its own error code (779). (Bug#26490)

NDB Cluster: Takeover for local checkpointing due to multiple failures of master nodes was sometimes incorrect handled. (Bug#26457)

NDB Cluster: The LockPagesInMemory parameter was not read until after distributed communication had already started between cluster nodes. When the value of this parameter was 1, this could sometimes result in data node failure due to missed heartbeats. (Bug#26454)

NDB Cluster: Under some circumstances, following the restart of a management, all cluster data nodes would connect to it normally, but some of them subsequently failed to log any events to the management node. (Bug#26293)

NDB Cluster: An error was produced when SHOW TABLE STATUS was used on an NDB table that had no AUTO_INCREMENT column. (Bug#21033)

NDB Cluster: When a node failed due to there being insufficient disk space to perform a local checkpoint, there was no indication that this was the source of the problem. Such a condition now produces an appropriate error message. (Bug#20121)

NDB Cluster (Cluster APIs): libndbclient.so was not versioned. (Bug#13522)

NDB Cluster: The ndb_size.tmpl file (necessary for using the ndb_size.pl script) was missing from binary distributions. (Bug#24191)

NDB Cluster (Cluster APIs / Disk Data): A delete and a read peformed in the same operation could cause one or more of the cluster's data nodes to crash. This could occur when the operation affected more than 5 columns concurrently, or when one or more of the columns was of the VARCHAR type and was stored on disk. (Bug#25794)

NDB Cluster (Replication): The error message Last_Errno: 4294967295, Error in Write_rows event now supplies a valid error code. (Bug#19896)

NDB Cluster (Replication): Under some circumstances, the binlog thread could shut down while the slave SQL thread was still using it. (Bug#26015, Bug#26019)

NDB Cluster: A query with an IN clause against an NDB table employing explicit user-defined partitioning did not always return all matching rows. (Bug#25821)

A memory leak could cause problems during a node or cluster shutdown or failure. (Bug#25997)

NDB Cluster: An appropriate error message was not provided when there was insufficient REDO log file space for the cluster to start. (Bug#25801)

NDB Cluster: An UPDATE using an IN clause on an NDB table on which there was a trigger caused mysqld to crash. (Bug#25522)

NDB Cluster: A memory allocation failure in the cluster Subscription Manager could cause the cluster to crash. (Bug#25239)

NDB Cluster: In the event that cluster backup parameters such as BackupWriteSize were incorrectly set, no appropriate error was issued to indicate that this was the case. (Bug#19146)

OPTIMIZE TABLE caused a race condition in the I/O cache. (Bug#19978)

If the duplicate key value was present in the table, INSERT ... ON DUPLICATE KEY UPDATE reported a row count indicating that a record was updated, even when no record actually changed due to the old and new values being the same. Now it reports a row count of zero. (Bug#19978)

Some UPDATE statements were slower than in previous versions when the search key could not be converted to a valid value for the type of the search column. (Bug#24035)

The WITH CHECK OPTION clause for views was ignored for updates of multiple-table views when the updates could not be performed on fly and the rows to update had to be put into temporary tables first. (Bug#25931)

Using ORDER BY or GROUP BY could yield different results when selecting from a view and selecting from the underlying table. (Bug#26209)

Storing values specified as hexadecimal values 64 or more bits long into BIT(64), BIGINT, or BIGINT UNSIGNED columns did not raise any warning or error if the value was out of range. (Bug#22533)

Inserting DEFAULT into a column with no default value could result in garbage in the column. Now the same result occurs as when inserting NULL into a NOT NULL column. (Bug#20691)

The presence of ORDER BY in a view definition prevented the MERGE algorithm from being used to resolve the view even if nothing else in the definition required the TEMPTABLE algorithm. (Bug#12122)

ISNULL(DATE(NULL)) and ISNULL(CAST(NULL AS DATE)) erroneously returned false. (Bug#23938)

If a slave server closed its relay log (for example, due to an error during log rotation), the I/O thread did not recognize this and still tried to write to the log, causing a server crash. (Bug#10798)

Collation for LEFT JOIN comparisons could be evaluated incorrectly, leading to improper query results. (Bug#26017)

For the IF() and COALESCE() function and CASE expressions, large unsigned integer values could be mishandled and result in warnings. (Bug#22026)

The number of setsockopt() calls performed for reads and writes to the network socket was reduced to decrease system call overhead. (Bug#22943)

A WHERE clause that used BETWEEN for DATETIME values could be treated differently for a SELECT and a view defined as that SELECT. (Bug#26124)

ORDER BY on DOUBLE values could change the set of rows returned by a query. (Bug#19690)

LOAD DATA INFILE did not work with pipes. (Bug#25807)

DISTINCT queries that were executed using a loose scan for an InnoDB table that had been emptied caused a server crash. (Bug#26159)

ALTER TABLE caused loss of CASCADE clauses for InnoDB tables. (Bug#24741)

Type conversion errors during formation of index search conditions were not correctly checked, leading to incorrect query results. (Bug#22344)

Within a stored routine, accessing a declared routine variable with PROCEDURE ANALYSE() caused a server crash. (Bug#23782)

Use of already freed memory caused SSL connections to hang forever. (Bug#19209)

mysql.server stop timed out too quickly (35 seconds) waiting for the server to exit. Now it waits up to 15 minutes, to ensure that the server exits. (Bug#25341)

A yaSSL program named test was installed, causing conflicts with the test system utility. It is no longer installed. (Bug#25417)

perror crashed on some platforms due to failure to handle a NULL pointer. (Bug#25344)

mysql_kill() caused a server crash when used on an SSL connection. (Bug#25203)

The readline library wrote to uninitialized memory, causing mysql to crash. (Bug#19474)

yaSSL was sensitive to the presence of whitespace at the ends of lines in PEM-encoded certificates, causing a server crash. (Bug#25189)

The SEC_TO_TIME() and QUARTER() functions sometimes did not handle NULL values correctly. (Bug#25643)

The optimizer used a filesort rather than a const table read in some cases when the latter was possible. (Bug#16590)

With ONLY_FULL_GROUP_BY enables, the server was too strict: Some expressions involving only aggregate values were rejected as non-aggregate (for example, MAX(a) - MIN(a)). (Bug#23417)

Indexes disabled with ALTER TABLE ... DISABLE KEYS could in some cases be used by specifying FORCE INDEX. (Bug#20604)

The arguments of the ENCODE() and the DECODE() functions were not printed correctly, causing problems in the output of EXPLAIN EXTENDED and in view definitions. (Bug#23409)

An error in the name resolution of nested JOIN ... USING constructs was corrected. (Bug#25575)

A return value of -1 from user-defined handlers was not handled well and could result in conflicts with server code. (Bug#24987)

The server might fail to use an appropriate index for DELETE when ORDER BY, LIMIT, and a non-restricting WHERE are present. (Bug#17711)

Use of ON DUPLICATE KEY UPDATE defeated the usual restriction against inserting into a join-based view unless only one of the underlying tables is used. (Bug#25123)

View definitions that used the ! operator were treated as containing the NOT operator, which has a different precedence and can produce different results. (Bug#25580).

Some queries against INFORMATION_SCHEMA that used subqueries failed. (Bug#23299).

For a UNIQUE index containing many NULL values, the optimizer would prefer the index for col IS NULL conditions over other more selective indexes. (Bug#25407).

GROUP BY and DISTINCT did not group NULL values for columns that have a UNIQUE index. (Bug#25551).

ALTER TABLE ... ENABLE KEYS acquired a global lock, preventing concurrent execution of other statements that use tables. (Bug#25044).

For an InnoDB table with any ON DELETE trigger, TRUNCATE TABLE mapped to DELETE and activated triggers. Now a fast truncation occurs and triggers are not activated. (Bug#23556).

For ALTER TABLE, using ORDER BY expression could cause a server crash. Now the ORDER BY clause allows only column names to be specified as sort criteria (which was the only documented syntax, anyway). (Bug#24562)

readline detection did not work correctly on NetBSD. (Bug#23293)

The --with-readline option for configure does not work for commercial source packages, but no error message was printed to that effect. Now a message is printed. (Bug#25530)

If an ORDER BY or GROUP BY list included a constant expression being optimized away and, at the same time, containing single-row subselects that return more that one row, no error was reported. If a query requires sorting by expressions containing single-row subselects that return more than one row, execution of the query may cause a server crash. (Bug#24653)

To enable installation of MySQL RPMs on Linux systems running RHEL 4 (which includes SE-Linux) additional information was provided to specify some actions that are allowed to the MySQL binaries. (Bug#12676)

Queries that evaluate NULL IN (SELECT ... UNION SELECT ...) could produce an incorrect result (FALSE instead of NULL). (Bug#24085)

Within stored routines or prepared statements, inconsistent results occurred with multiple use of INSERT ... SELECT ... ON DUPLICATE KEY UPDATE when the ON DUPLICATE KEY UPDATE clause erroneously tried to assign a value to a column mentioned only in its SELECT part. (Bug#24491)

Expressions of the form (a, b) IN (SELECT a, MIN(b) FROM t GROUP BY a) could produce incorrect results when column a of table t contained NULL values while column b did not. (Bug#24420)

Expressions of the form (a, b) IN (SELECT c, d ...) could produce incorrect results if a, b, or both were NULL. (Bug#24127)

An AFTER UPDATE trigger on an InnoDB table with a composite primary key caused the server to crash. (Bug#25398)

A query that contained an EXIST subquery with a UNION over correlated and uncorrelated SELECT queries could cause the server to crash. (Bug#25219)

A query with ORDER BY and GROUP BY clauses where the ORDER BY clause had more elements than the GROUP BY clause caused a memory overrun leading to a crash of the server. (Bug#25172)

Certain joins using Range checked for each record in the query execution plan could cause the server to crash. (Bug#24776)

If a prepared statement accessed a view, access to the tables listed in the query after that view was checked in the security context of the view. (Bug#24404)

A nested query on a partitioned table returned fewer records than on the corresponding non-partitioned table, when the subquery affected more than one partition. (Bug#24186)

Passing a NULL value to a user-defined function from within a stored procedure crashes the server. (Bug#25382)

Incompatible change: The following conditions apply to enabling the read_only system variable:

Previously, the attempt to enable read_only would return immediately even if explicit locks or transactions were pending, so some data changes could occur for statements executing in the server at the same time. (Bug#11733, Bug#22009)

Incompatible change: Previously, the DATE_FORMAT() function returned a binary string. Now it returns a string with a character set and collation given by character_set_connection and collation_connection so that it can return month and weekday names containing non-ASCII characters. (Bug#22646)

Important: When using MERGE tables the definition of the MERGE table and the MyISAM tables are checked each time the tables are opened for access (including any SELECT or INSERT statement. Each table is compared for column order, types, sizes and associated. If there is a difference in any one of the tables then the statement will fail.

On Unix, when searching the standard locations for option files, MySQL programs now also look for /etc/mysql/my.cnf after checking for /etc/my.cnf and before checking the remaining locations. (Bug#25104)

Remote servers for use with the FEDERATED storage engine now can be managed with the new CREATE/ALTER/DROP SERVER syntax.

The --skip-thread-priority option now is enabled by default for binary Mac OS X distributions. Use of thread priorities degrades performance on Mac OS X. (Bug#18526)

Added the --disable-grant-options option to configure. If configure is run with this option, the --bootstrap, --skip-grant-tables, and --init-file options for mysqld are disabled and cannot be used. For Windows, the configure.js script recognizes the DISABLE_GRANT_OPTIONS flag, which has the same effect.

Partitioning of tables using the FEDERATED storage engine is no longer permitted. Attempting to create such a table or to modify an existing table so that is uses both partitioning and FEDERATED now fails with an error. (Bug#22451)

In MySQL 5.1, InnoDB rolls back only the last statement on a transaction timeout. A new option, --innodb_rollback_on_timeout, causes InnoDB to abort and roll back the entire transaction if a transaction timeout occurs (the same behavior as in MySQL 4.1). (Bug#24200)

The Com_create_user status variable was added (for counting CREATE USER statements). (Bug#22958)

The --memlock option relies on system calls that are unreliable on some operating systems. If a crash occurs, the server now checks whether --memlock was specified and if so issues some information about possible workarounds. (Bug#22860)

The default value of the max_connections variable has been increased to 151 in order that Websites running on Apache and using MySQL will not have more processes trying to access MySQL than the default number of connections available.

(The maximum number of Apache processes is determined by the Apache MaxClient, which defaults to 256, but is usually set to 150 in the httpd.conf commonly distributed with Apache. For more information about MaxClient, see http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxclients.)

(Bug#23883)

The bundled yaSSL library was upgraded to version 1.5.0.

Calling a non-deterministic stored routine when using statement-based replication now throws an error. Formerly, defining such a stored routine would cause an error to be thrown. (Bug#16456)

The (undocumented) UNIQUE_USERS() and GROUP_UNIQUE_USERS() functions were removed. (Bug#22687)

NDB Cluster: The LockPagesInMainMemory configuration parameter has changed its type and possible values. For more information, see LockPagesInMainMemory. (Bug#25686)

Important: The values true and false are no longer accepted for this parameter. If you were using this parameter and had it set to false in a previous release, you must change it to 0. If you had this parameter set to true, you should instead use 1 to obtain the same behavior as previously, or 2 to take advantage of new functionality introduced with this release described in the section cited above.

Incompatible change: For ENUM columns that had enumeration values containing commas, the commas were mapped to 0xff internally. However, this rendered the commas indistinguishable from true 0xff characters in the values. This no longer occurs. However, the fix requires that you dump and reload any tables that have ENUM columns containing true 0xff in their values: Dump the tables using mysqldump with the current server before upgrading from a version of MySQL 5.1 older than 5.1.15 to version 5.1.15 or newer. (Bug#24660)

mysqld_multi and mysqlaccess looked for option files in /etc even if the --sysconfdir option for configure had been given to specify a different directory. (Bug#24780)

SHOW COLUMNS reported some NOT NULL columns as NULL. (Bug#22377)

Attempts to access a MyISAM table with a corrupt column definition caused a server crash. (Bug#24401)

mysqltest_embedded crashed at startup. (Bug#25890)

Accessing a fixed record format table with a crashed key definition results in server/myisamchk segmentation fault. (Bug#24855)

When opening a corrupted .frm file during a query, the server crashes. (Bug#24358)

If there was insufficient memory to store or update a blob record in a MyISAM table then the table will marked as crashed. (Bug#23196)

When updating a table that used a JOIN of the table itself (for example, when building trees) and the table was modified on one side of the expression, the table would either be reported as crashed or the wrong rows in the table would be updated. (Bug#21310)

When SET PASSWORD was written to the binary log double quotes were included in the statement. If the slave was running in with the sql_mode set to ANSI_QUOTES the event would fail and halt the replication process. (Bug#24158)

Using CREATE TABLE ... SELECT and rolling back the transaction would leave an empty table on the master, but the instructions would not be recorded in the binary log and therefore replicated to the slave. This would result in a difference between the master and slave databases. An implicit commit has been added to ensure consistency. (Bug#22865)

When reading from the standard input on Windows, mysqlbinlog opened the input in text mode rather than binary mode and consequently misinterpreted some characters such as Control-Z. (Bug#23735)

No warning was issued for use of the DATA DIRECTORY or INDEX DIRECTORY table options on a platform that does not support them. (Bug#17498)

When a prepared statement failed during the prepare operation, the error code was not cleared when it was reused, even if the subsequent use was successful. (Bug#15518)

mysql_upgrade failed when called with a basedir pathname containing spaces. (Bug#22801)

Hebrew-to-Unicode conversion failed for some characters. Definitions for the following Hebrew characters (as specified by the ISO/IEC 8859-8:1999) were added: LEFT-TO-RIGHT MARK (LRM), RIGHT-TO-LEFT MARK (RLM) (Bug#24037)

If there was insufficient memory available to mysqld, this could sometimes cause the server to hang during startup. (Bug#24751)

Using row-based replication to replicate to a table having at least one extra BIT column with a default value on the slave as compared to the master could cause the slave to fail. (Bug#24490)

Optimizations that are legal only for subqueries without tables and WHERE conditions were applied for any subquery without tables. (Bug#24670)

A query using WHERE unsigned_column NOT IN ('negative_value') could cause the server to crash. (Bug#24261)

A FETCH statement using a cursor on a table which was not in the table cache could sometimes cause the server to crash. (Bug#24117)

CREATE TABLE ... SELECT statements were not rolled back correctly. As part of the fix, such a statement now causes an implicit commit before and after it is executed. However, it does not cause a commit when used to create a temporary table. (Bug#22864)

SSL connections could hang at connection shutdown. (Bug#24148, Bug#21781)

The STDDEV() function returned a positive value for data sets consisting of a single value. (Bug#22555)

mysqltest incorrectly tried to retrieve result sets for some queries where no result set was available. (Bug#19410)

mysqltest crashed with a stack overflow. (Bug#24498)

The server was built even when configure was run with the --without-server option. (Bug#23973)

mysqld_error.h was not installed when only the client libraries were built. (Bug#21265)

mysql_install_db did not create the mysql.plugin table if strict SQL mode was enabled. (Bug#24270)

The row count for MyISAM tables was not updated properly, causing SHOW TABLE STATUS to report incorrect values. (Bug#23526)

Using a view in combination with a USING clause caused column aliases to be ignored. (Bug#25106)

Using ALTER TABLE to convert a CSV table containing NULL values to MyISAM resulted in warnings. (Bug#21328)

A view was not handled correctly if the SELECT part contained 鈥�\Z鈥�. (Bug#24293)

Inserting a row into a table without specifying a value for a BINARY(N) NOT NULL column caused the column to be set to spaces, not zeroes. (Bug#14171)

An assertion failed incorrectly for prepared statements that contained a single-row non-correlated subquery that was used as an argument of the IS NULL predicate. (Bug#25027)

A table created with the ROW_FORMAT = FIXED table option loses the option if an index is added or dropped with CREATE INDEX or DROP INDEX. (Bug#23404)

Dropping a user-defined function sometimes did not remove the UDF entry from the mysql.proc table. (Bug#15439)

The BUILD/check-cpu script did not recognize Celeron processors. (Bug#20061)

Some problems uncovered by Valgrind were fixed. (Bug#25396)

mysql_fix_privilege_tables did not handle a password containing embedded space or apostrophe characters. (Bug#17700)

On Windows, the SLEEP() function could sleep too long, especially after a change to the system clock. (Bug#14094, Bug#17635, Bug#24686)

In the INFORMATION_SCHEMA.KEY_COLUMN_USAGE table, the value displayed for the REFERENCED_TABLE_NAME column was the table name as encoded for disk storage, not the actual table name. (Bug#25026)

Changing the value of MI_KEY_BLOCK_LENGTH in myisam.h and recompiling MySQL resulted in a myisamchk that saw existing MyISAM tables as corrupt. (Bug#22119)

A stored routine containing semicolon in its body could not be reloaded from a dump of a binary log. (Bug#20396)

For SET, SELECT, and DO statements that invoked a stored function from a database other than the default database, the function invocation could fail to be replicated. (Bug#19725)

SET lc_time_names = value allowed only exact literal values, not expression values. (Bug#22647)

Changes to the lc_time_names system variable were not replicated. (Bug#22645)

SELECT ... FOR UPDATE, SELECT ... LOCK IN SHARE MODE, DELETE, and UPDATE statements executed using a full table scan were not releasing locks on rows that did not satisfy the WHERE condition. (Bug#20390)

A stored procedure, executed from a connection using a binary character set, and which wrote multibyte data, would write incorrectly escaped entries to the binary log. This caused syntax errors, and caused replication to fail. (Bug#23619, Bug#24492)

mysqldump --order-by-primary failed if the primary key name was an identifier that required quoting. (Bug#13926)

Re-execution of CREATE DATABASE, CREATE TABLE, and ALTER TABLE statements in stored routines or as prepared statements caused incorrect results. (Bug#22060)

The internal functions for table preparation, creation, and alteration were not re-execution friendly, causing problems in code that: repeatedly altered a table; repeatedly created and dropped a table; opened and closed a cursor on a table, altered the table, and then reopened the cursor. (Bug#4968, Bug#6895, Bug#19182, Bug#19733)

A workaround was implemented to avoid a race condition in the NPTL pthread_exit() implementation. (Bug#24507)

The Instance Manager DROP INSTANCE command did not work. (Bug#23476)

The Instance Manager STOP INSTANCE command took too much time and caused Instance Manager to be unresponsive. (Bug#23215)

The Instance Manager STOP INSTANCE command could not be applied to instances in the Crashed, Failed, or Abandoned state. (Bug#22306)

Instance Manager could crash during shutdown. (Bug#19044)

A deadlock could occur, with the server hanging on Closing tables, with a sufficient number of concurrent INSERT DELAYED, FLUSH TABLES, and ALTER TABLE operations. (Bug#23312)

A user-defined variable could be assigned an incorrect value if a temporary table was employed in obtaining the result of the query used to determine its value. (Bug#16861)

The optimizer removes expressions from GROUP BY and DISTINCT clauses if they happen to participate in expression = constant predicates of the WHERE clause, the idea being that, if the expression is equal to a constant, then it cannot take on multiple values. However, for predicates where the expression and the constant item are of different result types (for example, when a string column is compared to 0), this is not valid, and can lead to invalid results in such cases. The optimizer now performs an additional check of the result types of the expression and the constant; if their types differ, then the expression is not removed from the GROUP BY list. (Bug#15881)

Referencing an ambiguous column alias in an expression in the ORDER BY clause of a query caused the server to crash. (Bug#25427)

Some CASE statements inside stored routines could lead to excessive resource usage or a crash of the server. (Bug#24854, Bug#19194)

Some joins in which one of the joined tables was a view could return erroneous results or crash the server. (Bug#24345)

OPTIMIZE TABLE tried to sort R-tree indexes such as spatial indexes, although this is not possible (see Section聽13.5.2.5, 鈥�OPTIMIZE TABLE Syntax鈥�). (Bug#23578)

User-defined variables could consume excess memory, leading to a crash caused by the exhaustion of resources available to the MEMORY storage engine, due to the fact that this engine is used by MySQL for variable storage and intermediate results of GROUP BY queries. Where SET had been used, such a condition could instead give rise to the misleading error message You may only use constant expressions with SET, rather than Out of memory (Needed NNNNNN bytes). (Bug#23443)

InnoDB: During a restart of the MySQL Server that followed the creation of a temporary table using the InnoDB storage engine, MySQL failed to clean up in such a way that InnoDB still attempted to find the files associated with such tables. (Bug#20867)

Under some circumstances, a REORGANIZE PARTITION statement could crash mysqld. (Bug#24502)

A multiple-table DELETE QUICK could sometimes cause one of the affected tables to become corrupted. (Bug#25048)

A compressed MyISAM table that became corrupted could crash myisamchk and possibly the MySQL Server. (Bug#23139)

Using INSTALL PLUGIN followed by a restart of the server caused an error due to memory not being properly initialized. (Bug#22694)

A crash of the MySQL Server could occur when unpacking a BLOB column from a row in a corrupted MyISAM table. This could happen when trying to repair a table using either REPAIR TABLE or myisamchk; it could also happen when trying to access such a 鈥�broken鈥� row using statements like SELECT if the table was not marked as crashed. (Bug#22053)

The FEDERATED storage engine did not support the euckr character set. (Bug#21556)

The FEDERATED storage engine did not support the utf8 character set. (Bug#17044)

mysql_upgrade failed if the --password (or -p) option was given. (Bug#24896)

For a nonexistent table, DROP TEMPORARY TABLE failed with an incorrect error message if read_only was enabled. (Bug#22077)

The code for generating USE statements for binary logging of CREATE PROCEDURE statements resulted in confusing output from mysqlbinlog for DROP PROCEDURE statements. (Bug#22043)

The REPEAT() function could return NULL when passed a column for the count argument. (Bug#24947)

Accuracy was improved for comparisons between DECIMAL columns and numbers represented as strings. (Bug#23260)

InnoDB crashed while performing XA recovery of prepared transactions. (Bug#21468)

ROW_COUNT() did not work properly as an argument to a stored procedure. (Bug#23760)

It was possible to use DATETIME values whose year, month, and day parts were all zeroes but whose hour, minute, and second parts contained nonzero values, an example of such an illegal DATETIME being '0000-00-00 11:23:45'. (Bug#21789)

This patch was reverted in MySQL 5.1.18.

It was possible to set the backslash character (鈥� \ 鈥�) as the delimiter character using DELIMITER, but not actually possible to use it as the delimiter. (Bug#21412)

ALTER ENABLE KEYS or ALTER TABLE DISABLE KEYS combined with another ALTER TABLE option other than RENAME TO did nothing. In addition, if ALTER TABLE was used on a table having disabled keys, the keys of the resulting table were enabled. (Bug#24395)

An ALTER TABLE statement that used a RENAME clause in combination with a MODIFY or CHANGE that did not actually change the table (for example, when it changed a column's type from INT to INT). The behavior caused by this bug differed according to whether or not the storage engine used by the table was transactional or non-transactional. For transactional tables (such as those using the InnoDB storage engine), the statement simply failed; for non-transactional tables (such as those using the MyISAM storage engine), the ALTER TABLE statement succeeding renaming the table, but subsequent SELECT statements against the renamed table would fail. (Bug#22369)

Queries of the form SELECT ... WHERE string = ANY(...) failed when the server used a single-byte character set and the client used a multi-byte character set. (Bug#20835)

A partitioned table that used the DATA DIRECTORY option, where the data directory was the same as the directory in which the table definition file resided, became corrupted following ALTER TABLE ENGINE=ARCHIVE. This was actually due to an issue with the ARCHIVE storage engine, and not with partitioned tables in general. (Bug#22634)

NDB Cluster (Cluster APIs): Deletion of an Ndb_cluster_connection object took a very long time. (Bug#25487)

NDB Cluster (Replication): Certain errors in replication setups could lead to subsequent node failures. (Bug#25755)

NDB Cluster (Replication): Connecting a mysqld to a cluster where not all nodes were running, starting the remaining cluster nodes, and then disconnecting from the cluster caused the mysqld process to crash. (Bug#25387)

NDB Cluster (Replication): Connecting an API node to the cluster during a node restart while performing database operations could cause the restarting node to fail. (Bug#25329)

NDB Cluster (Disk Data): Following 3 or more missed local checkpoints by a cluster node, a restart of the node caused incorrect undo information to be used for Disk Data tables. (Bug#25636)

NDB Cluster: It was not possible to create an NDB table with a key on two VARCHAR columns where both columns had a storage length in excess of 256. (Bug#25746)

NDB Cluster: Hosts in clusters with a large number of nodes could experience excessive CPU usage while obtaining configuration data. (Bug#25711)

NDB Cluster: In some circumstances, shutting down the cluster could cause connected mysqld processes to crash. (Bug#25668)

NDB Cluster: Non-32-bit, non-aligned columns were not handled correctly in explicitly partitioned NDB tables. (Bug#25587)

NDB Cluster: Some aggregate queries such as SELECT COUNT(*) performed a table scan on NDB tables rather than checking table statistics, causing such queries to perform much more slowly in MySQL Cluster 5.1 than in 5.0. (Bug#25567)

NDB Cluster: Memory allocations for TEXT columns were calculated incorrectly, resulting in space being wasted and other issues. (Bug#25562)

NDB Cluster: The failure of a master node during a node restart could lead to a resource leak, causing later node failures. (Bug#25554)

NDB Cluster: The failure of a node during a local checkpoint could lead to other node failures. (Bug#25468)

NDB Cluster: A node shutdown occurred if the master failed during a commit. (Bug#25364)

NDB Cluster: Creating a non-unique index with the USING HASH clause silently created an ordered index instead of issuing a warning. (Bug#24820)

NDB Cluster: The management server did not handle logging of node shutdown events correctly in certain cases. (Bug#22013)

NDB Cluster: A potential memory leak in the NDB storage engine's handling of file operations was uncovered. (Bug#21858)

NDB Cluster: When stopping and restarting multiple data nodes, the last node to be restarted would sometimes hang in Phase 100. (Bug#19645)

NDB Cluster (NDB API): Invoking the NdbTransaction::execute() method using execution type Commit and abort option AO_IgnoreError could lead to a crash of the transaction coordinator (DBTC). (Bug#25090)

NDB Cluster (NDB API): A unique index lookup on a non-existent tuple could lead to a data node timeout (error 4012). (Bug#25059)

NDB Cluster (NDB API): Due to an error in the computation of table fragment arrays, some transactions might not be executed from the correct starting point. (Bug#24914)

NDB Cluster (Replication): Following a restart of the master cluster, the latest GCI was set to 0 upon reconnection to the slave. (Bug#21806)

NDB Cluster (Disk Data): A MEDIUMTEXT column of a Disk Data table was stored in memory rather than on disk, even if the column was not indexed. (Bug#25001)

NDB Cluster (Disk Data): Performing a node restart with a newly dropped Disk Data table could lead to failure of the node during the restart. (Bug#24917)

NDB Cluster (Disk Data): When restoring from backup a cluster containing any Disk Data tables with hidden primary keys, a node failure resulted which could lead to a crash of the cluster. (Bug#24166)

NDB Cluster (Disk Data): Repeated CREATE, DROP, or TRUNCATE in various combinations with system restarts between these operations could lead to the eventual failure of a system restart. (Bug#21948)

NDB Cluster (Disk Data): Extents that should have been available for re-use following a DROP TABLE operation were not actually made available again until after the cluster performed a local checkpoint. (Bug#17605)

NDB Cluster: Under certain rare circumstances, local checkpoints were not performed properly, leading to an inability to restart one or more data nodes. (Bug#24664)

NDB Cluster (NDB API): When using the NdbTransaction::execute() method, a very long timeout (greater than 5 minutes) could result if the last data node being polled was disconnected from the cluster. (Bug#24949)

NDB Cluster: When a data node was shut down using the management client STOP command, a connection event (NDB_LE_Connected) was logged instead of a disconnection event (NDB_LE_Disconnected). (Bug#22773)

NDB Cluster: SELECT statements with a BLOB or TEXT column in the selected column list and a WHERE condition including a primary key lookup on a VARCHAR primary key produced empty result sets. (Bug#19956)

NDB Cluster: ndb_config failed when trying to use 2 management servers and node IDs. (Bug#23887)

STR_TO_DATE() returned NULL if the format string contained a space following a non-format character. (Bug#22029)

yaSSL crashed on pre-Pentium Intel CPUs. (Bug#21765)

Selecting into variables sometimes returned incorrect wrong results. (Bug#20836)

mysql_fix_privilege_tables.sql altered the table_privs.table_priv column to contain too few privileges, causing loss of the CREATE VIEW and SHOW VIEW privileges. (Bug#20589)

A server crash occurred when using LOAD DATA to load a table containing a NOT NULL spatial column, when the statement did not load the spatial column. Now a NULL supplied to NOT NULL column error occurs. (Bug#22372)

Unsigned BIGINT values treated as signed values by the MOD() function. (Bug#19955)

Compiling PHP 5.1 with the MySQL static libraries failed on some versions of Linux. (Bug#19817)

The DELIMITER statement did not work correctly when used in an SQL file run using the SOURCE statement. (Bug#19799)

VARBINARY column values inserted on a MySQL 4.1 server had trailing zeroes following upgrade to MySQL 5.0 or later. (Bug#19371)

Subqueries of the form NULL IN (SELECT ...) returned invalid results. (Bug#8804, Bug#23485)

The --extern option for mysql-test-run.pl did not function correctly. (Bug#24354)

ALTER TABLE statements that performed both RENAME TO and {ENABLE|DISABLE} KEYS operations caused a server crash. (Bug#24089)

The MySQL 5.1.12 binaries for Windows were missing the FEDERATED, EXAMPLE, and BLACKHOLE storage engines. (Bug#23900)

myisampack wrote to unallocated memory, causing a crash. (Bug#17951)

Some small double precision numbers (such as 1.00000001e-300) that should have been accepted were truncated to zero. (Bug#22129)

The mysql.server script used the source command, which is less portable than the . command; it now uses . instead. (Bug#24294)

DATE_ADD() requires complete dates with no 鈥�zero鈥� parts, but sometimes did not return NULL when given such a date. (Bug#22229)

Using FLUSH TABLES in one connection while another connection is using HANDLER statements caused a server crash. (Bug#21587)

FLUSH LOGS or mysqladmin flush-logs caused a server crash if the binary log was not open. (Bug#17733)

On HP-UX, mysqltest (non-thread-safe) crashed due to being linked against a thread-safe libmysys library. (Bug#23984)

Incompatible change: Previously, you could create a user-defined function (UDF) or stored function with the same name as a built-in function, but could not invoke the UDF. Now an error occurs if you try to create such a UDF. The server also now generates a warning if you create a stored function with the same name as a built-in function. It is not considered an error to create a stored function with the same name as a built-in function because you can invoke the function using db_name.func_name() syntax. However, the server now generates a warning in this case. (Bug#22619, Bug#18239)

See Section聽9.2.4, 鈥淔unction Name Parsing and Resolution鈥�, for the rules describing how the server interprets references to different kinds of functions.

Incompatible change: The prepared_stmt_count system variable has been converted to the Prepared_stmt_count global status variable (viewable with the SHOW GLOBAL STATUS statement). (Bug#23159)

NDB Cluster: Two major changes have taken place with regard to the MySQL Cluster system tables. These are:

Note: When upgrading from versions of MySQL previous to 5.1.14 to 5.1.14 or later, mysql_fix_privilege_tables merely creates a new mysql.ndb_binlog_index table, but does not remove the existing cluster database (or, if upgrading from MySQL 5.1.7 or earlier, the existing cluster_replication database), nor any of the tables in it.

For more information, see Section聽15.10.4, 鈥淐luster Replication Schema and Tables鈥�.

NDB Cluster: It is now possible to create a unique hashed index on a column that is not defined as NOT NULL. Note that this change applies only to tables using the NDB storage engine.

Unique indexes on columns in NDB tables do not store null values because they are mapped to primary keys in an internal index table (and primary keys cannot contain nulls).

Normally, an additional ordered index is created when one creates unique indexes on NDB table columns; this can be used to search for NULL values. However, if USING HASH is specified when such an index is created, no ordered index is created.

The reason for permitting unique hash indexes with null values is that, in some cases, the user wants to save space if a large number of records are pre-allocated but not fully initialized. This also assumes that the user will not try to search for null values. Since MySQL does not support indexes that are not allowed to be searched in some cases, the NDB storage engine uses a full table scan with pushed conditions for the referenced index columns to return the correct result.

Note that a warning is returned if one creates a unique nullable hash index, since the query optimizer should be provided a hint not to use it with NULL values if this can be avoided.

(Bug#21507)

NDB Cluster: Backup messages are now printed to the Cluster log. (Bug#24544)

NDB Cluster: The error message Management server closed connection, when recorded in the MySQL error log, now includes a timestamp indicating when the error took place. (Bug#21519)

NDB Cluster (Disk Data): The output of mysqldump now includes by default all tablespace and logfile group definitions used by any tables or databases that are dumped. (Bug#20839)

Note: The working of the --all-tablespaces or -Y option for mysqldump remains unaffected by this change.

Direct and indirect usage of stored routines, user-defined functions, and table references is now prohibited in CREATE EVENT and ALTER EVENT statements. (Bug#22830)

See Section聽20.2.2, 鈥�CREATE EVENT Syntax鈥�, and Section聽20.2.1, 鈥�ALTER EVENT Syntax鈥�, for more specific information.

DROP TRIGGER now supports an IF EXISTS clause. (Bug#23703)

All standard XPath comparison operators are now supported for use with the ExtractValue() and UpdateXML() functions. (Bug#22823)

NDB Cluster: If the value set for MaxNoOfAttributes is excessive, a suitable error message is now returned. (Bug#19352)

NDB Cluster: Setting the configuration parameter LockPagesInMainMemory had no effect. (Bug#24461)

NDB Cluster: Multiple occurrences of error conditions were logged with duplicat error messages rather than being reported with a single error message stating that the error was encountered N times. (Bug#22313)

NDB Cluster: Sudden disconnection of an SQL or data node could lead to shutdown of data nodes with the error failed ndbrequire. (Bug#24447)

NDB Cluster: Different error messages were returned for similar cases involving failure to allocate memory for Cluster operations. (Bug#19203)

NDB Cluster: Some values of MaxNoOfTriggers could cause the server to become inaccessible following startup of the data nodes. (Bug#19454)

NDB Cluster (Replication): If errors occurred during purging of the binary logs, extraneous rows could remain left in the binlog_index table. (Bug#15021)

NDB Cluster (Disk Data): ndb_restore could sometimes fail when attempting to restore Disk Data tables due to data node failure caused by accessing unitialized memory. (Bug#24331)

NDB Cluster (Disk Data): Excessive fragmentation of Disk Data files (including log files and data files) could occur during the course of normal use. (Bug#24143)

NDB Cluster (Disk Data): It was possible to execute a statement for creating a Disk Data table that referred to a nonexistent tablespace, in which case the table was an in-memory NDB table. Such a statement instead now fails with an appropriate error message. (Bug#23576)

NDB Cluster (Disk Data): Under some circumstances, a DELETE from a Disk Data table could cause mysqld to crash. (Bug#23542)

NDB Cluster (Cluster APIs): Using BIT values with any of the comparison methods of the NdbScanFilter class caused the cluster's data nodes to fail. (Bug#24503)

NDB Cluster: A value equal to or greater than the allowed maximum for LongMessageBuffer caused all data nodes to crash. (Bug#22547)

NDB Cluster: The failure of a data node failure during a schema operation could lead to additional node failures. (Bug#24752)

NDB Cluster: A committed read could be attempted before a data node had time to connect, causing a timeout error. (Bug#24717)

NDB Cluster: The simultaneous shutdown of mysqld and ndbd processes caused unnecessary locking. (Bug#24655)

NDB Cluster: The failure of the master node in a node group during the allocation of node IDs could cause ndb_mgmd to hang. (Bug#24543)

NDB Cluster: In certain rare cases, a data node could crash due to a typographical error in the MySQL Cluster source code. (Bug#24476)

NDB Cluster: Creating a new tables containing a BLOB column when the server was short of memory could cause the server to crash. (Bug#24470)

NDB Cluster: Any statement following the execution of CREATE TABLE ... LIKE ndb_table (where ndb_table was a table using the NDB storage engine), would cause the mysql client to hang. (Bug#24301)

NDB Cluster: When the management client command ALL RESTART -i was executed while one data node was not running, all data nodes in the cluster were shut down. (Bug#24105)

NDB Cluster: A query using an index scan followed by a delete operation, and then a rollback could cause one or more data nodes to crash. (Bug#24039)

NDB Cluster (Cluster APIs): Some MGM API function calls could yield incorrect return values in certain cases where the cluster was operating under a very high load, or experienced timeouts in inter-node communications. (Bug#24011)

NDB Cluster: It was possible for the sum of the MaxNoOfTables, MaxNoOfOrderedIndexes, and MaxNoOfUniqueHashIndexes configuration parameters, plus the number of system tables to exceed the maximum value for a Uint32 number. In such a case, the cluster's data nodes failed to start, and no reason for this could easily be determined from the error messages provided. (Bug#22548)

NDB Cluster: Given a table mytbl in a database mydb on a MySQL Server acting as an SQL node in a MySQL Cluster, then, following multiple ALTER TABLE mytbl ENGINE=engine statements 鈥� first, to change the storage engine used for a table to NDB, and then again to change the table to use a non-NDB storage engine 鈥� a DROP DATABASE mydb statement executed on any SQL node in the cluster would cause mydb to be dropped on all SQL nodes in the cluster, even if mydb contained non-NDB tables. (Bug#21495)

NDB Cluster: An incorrect error message was displayed in the event that the value of the MaxNoOfOrderedIndexes parameter was set too low. (Bug#20065)

NDB Cluster: An incorrect error message was displayed in the event that the value of the DataMemory parameter was insufficient for the amount of data to be stored by the cluster. (Bug#19808)

NDB Cluster: A unique constraint violation was not ignored by an UPDATE IGNORE statement when the constraint violation occurred on a non-primary key. (Bug#18487, Bug#24303)

The stack size for NetWare binaries was increased to 128KB to prevent problems caused by insufficient stack size. (Bug#23504)

Attempting to use a view containing DEFINER information for a non-existent user resulted in an error message that revealed the definer account. Now the definer is revealed only to superusers. Other users receive only an access denied message. (Bug#17254)

The size of MEMORY tables and internal temporary tables was limited to 4GB on 64-bit Windows systems. (Bug#24052)

For debug builds, mysqladmin shutdown displayed an extraneous skipped 9 bytes from file: socket (3) message. (Bug#21428)

For queries that select from a view, the server was returning MYSQL_FIELD metadata inconsistently for view names and table names. For view columns, the server now returns the view name in the table field and, if the column selects from an underlying table, the table name in the org_table field. (Bug#20191)

CREATE FUNCTION X() and CREATE FUNCTION Y() failed with a syntax error instead of warning the user that these function names are already used (for GIS functions). (Bug#21025)

The loose index scan optimization for GROUP BY with MIN or MAX was not applied within other queries, such as CREATE TABLE ... SELECT ..., INSERT ... SELECT ..., or in the FROM clauses of subqueries. (Bug#24156)

Queries using a column alias in an expression as part of an ORDER BY clause failed, an example of such a query being SELECT mycol + 1 AS mynum FROM mytable ORDER BY 30 - mynum. (Bug#22457)

Trailing spaces were not removed from Unicode CHAR column values when used in indexes. This resulted in excessive usage of storage space, and could affect the results of some ORDER BY queries that made use of such indexes.

Note: When upgrading, it is necessary to re-create any existing indexes on Unicode CHAR columns in order to take advantage of the fix. This can be done by using a REPAIR TABLE statement on each affected table.

(Bug#22052)

Warnings were generated when explicitly casting a character to a number (for example, CAST('x' AS SIGNED)), but not for implicit conversions in simple arithmetic operations (such as 'x' + 0). Now warnings are generated in all cases. (Bug#11927)

BENCHMARK, ENCODE, DECODE, and FORMAT could only accept a constant for some parameters, and could not be used in prepared statements. (Bug#22684)

A query with a subquery that references columns of a view from the outer SELECT could return an incorrect result if used from a prepared statement. (Bug#20327)

Constant expressions and some numeric constants used as input parameters to user-defined functions were not treated as constants. (Bug#18761)

INET_ATON() returned a signed BIGINT value, not an unsigned value. (Bug#21466)

In some cases, the parser failed to distinguish a user-defined function from a stored function. (Bug#21809)

In some cases, a function that should be parsed as a user-defined function was parsed as a stored function. (Bug#24736)

Subqueries for which a pushed-down condition did not produce exactly one key field could cause a server crash. (Bug#24056)

LAST_DAY('0000-00-00') could cause a server crash. (Bug#23653)

Through the C API, the member strings in MYSQL_FIELD for a query that contains expressions may return incorrect results. (Bug#21635)

mysql_affected_rows() could return values different from mysql_stmt_affected_rows() for the same sequence of statements. (Bug#23383)

IN() and CHAR() can return NULL, but did not signal that to the query processor, causing incorrect results for IS NULL operations. (Bug#17047)

Instance Manager option-parsing code caused memory-allocation errors. (Bug#22242)

A trigger that invoked a stored function could cause a server crash when activated by different client connections. (Bug#23651)

CONCURRENT did not work correctly for LOAD DATA INFILE. (Bug#20637)

The server source code had multiple exportable definitions of the field_in_record_is_null() function. These are now all declared static. (Bug#24190)

Inserting a default or invalid value into a spatial column could fail with Unknown error rather than a more appropriate error. (Bug#21790)

The server could send incorrect column count information to the client for queries that produce a larger number of columns than can fit in a two-byte number. (Bug#19216)

Evaluation of subqueries that require the filesort algorithm were allocating and freeing the sort_buffer_size buffer many times, resulting in slow performance. Now the buffer is allocated once and reused. (Bug#21727)

SQL statements close to the size of max_allowed_packet could produce binary log events larger than max_allowed_packet that could not be read by slave servers. (Bug#19402)

View columns were always handled as having implicit derivation, leading to illegal mix of collation errors for some views in UNION operations. Now view column derivation comes from the original expression given in the view definition. (Bug#21505)

If elements in a non-top-level IN subquery were accessed by an index and the subquery result set included a NULL value, the quantified predicate that contained the subquery was evaluated to NULL when it should return a non-NULL value. (Bug#23478)

Calculation of COUNT(DISTINCT), AVG(DISTINCT), or SUM(DISTINCT) when they are referenced more than once in a single query with GROUP BY could cause a server crash. (Bug#23184)

For a cast of a DATETIME value containing microseconds to DECIMAL, the microseconds part was truncated without generating a warning. Now the microseconds part is preserved. (Bug#19491)

Metadata for columns calculated from scalar subqueries was limited to integer, double, or string, even if the actual type of the column was different. (Bug#11032)

The result for CAST() when casting a value to UNSIGNED was limited to the maximum signed BIGINT value, not the maximum unsigned value. (Bug#8663)

Some unnecessary Valgrind warnings were removed from the server. (Bug#24488, Bug#24533).

Using EXPLAIN caused a server crash for queries that selected from INFORMATION_SCHEMA in a subquery in the FROM clause. (Bug#22413)

Invalidating the query cache caused a server crash for INSERT INTO ... SELECT statements that selected from a view. (Bug#20045)

With row-based binary logging, replicated multiple-statement transaction deadlocks did not return the correct error code, causing the slave SQL thread to stop rather than roll back and re-execute. (Bug#23831)

With row-based binary logging, for CREATE TABLE IF NOT EXISTS LIKE temporary_table statements, the IF NOT EXISTS clause was not logged. (Bug#22762)

With row-based binary logging, CREATE TABLE IF NOT EXISTS SELECT statements were not logged properly. (Bug#22027)

On slave servers, transactions that exceeded the lock wait timeout failed to roll back properly. (Bug#20697)

Changes to character set variables prior to an action on a replication-ignored table were forgotten by slave servers. (Bug#22877)

With lower_case_table_names set to 1, SHOW CREATE TABLE printed incorrect output for table names containing Turkish I (LATIN CAPITAL LETTER I WITH DOT ABOVE). (Bug#20404)

When applying the group_concat_max_len limit, GROUP_CONCAT() could truncate multi-byte characters in the middle. (Bug#23451)

For view renaming, the table name to filename encoding was not performed. (Bug#21370)

For some problems relating to character set conversion or incorrect string values for INSERT or UPDATE, the server was reporting truncation or length errors instead. (Bug#18908)

The XPath operators < and >, as implemented in the ExtractValue() function, operated in reverse. (Bug#22823)

Incompatible change: The number of function names affected by IGNORE_SPACE was reduced significantly in MySQL 5.1.13, from about 200 to about 30. (For details about IGNORE_SPACE, see Section聽9.2.4, 鈥淔unction Name Parsing and Resolution鈥�.) This change improves the consistency of parser operation. However, it also introduces the possibility of incompatibility for old SQL code that relies on the following conditions:

For functions that are no longer affected by IGNORE_SPACE as of MySQL 5.1.13, that strategy no longer works. Either of the following approaches can be used if you have code that is subject to the preceding incompatibility:

(Bug#21114)

If the user specified the server options --max-connections=N or --table-open-cache=M, a warning would be given in some cases that some values were recalculated, with the result that --table-open-cache could be assigned greater value.

It should be noted that, in such cases, both the warning and the increase in the --table-open-cache value were completely harmless. Note also that it is not possible for the MySQL Server to predict or to control limitations on the maximum number of open files, since this is determined by the operating system.

The recalculation code has now been fixed to ensure that the value of --table-open-cache is no longer increased automatically, and that a warning is now given only if some values had to be decreased due to operating system limits.

(Bug#21915)

Binary distributions of MySQL 5.1.12 were built without support for partitioning. This has been corrected except for NetWare. (Bug#23949)

A change in the interfaces for the INFORMATION_SCHEMA.FILES table has made the table accessible to storage engines other than NDB. (Bug#23013)

mysqldump --single-transaction now uses START TRANSACTION /*!40100 WITH CONSISTENT SNAPSHOT */ rather than BEGIN to start a transaction, so that a consistent snapshot will be used on those servers that support it. (Bug#19660)

mysql_upgrade now passes all the parameters specified on the command line to both mysqlcheck and mysql using the upgrade_defaults file. (Bug#20100)

For the CALL statement, stored procedures that take no arguments now can be invoked without parentheses. That is, CALL p() and CALL p are equivalent. (Bug#21462)

MySQL 5.0.26 introduced an ABI incompatibility, which this release reverts. Programs compiled against 5.0.26 are not compatible with any other version and must be recompiled. (Bug#23427)

Several string functions could return incorrect results when given very large length arguments. (Bug#10963)

If an init_connect SQL statement produced an error, the connection was silently terminated with no error message. Now the server writes a warning to the error log. (Bug#22158)

If a table contains an AUTO_INCREMENT column, inserting into an insertable view on the table that does not include the AUTO_INCREMENT column should not change the value of LAST_INSERT_ID(), because the side effects of inserting default values into columns not part of the view should not be visible. MySQL was incorrectly setting LAST_INSERT_ID() to zero. (Bug#22584)

M % 0 returns NULL, but (M % 0) IS NULL evaluated to false. (Bug#23411)

Within a stored routine, a view definition cannot refer to routine parameters or local variables. However, an error did not occur until the routine was called. Now it occurs during parsing of the routine creation statement. (Bug#20953)

Note: A side effect of this fix is that if you have already created such routines, and error will occur if you execute SHOW CREATE PROCEDURE or SHOW CREATE FUNCTION. You should drop these routines because they are erroneous.

A client library crash was caused by executing a statement such as SELECT * FROM t1 PROCEDURE ANALYSE() using a server side cursor on a table t1 that does not have the same number of columns as the output from PROCEDURE ANALYSE(). (Bug#17039)

mysql did not check for errors when fetching data during result set printing. (Bug#22913)

Adding a day, month, or year interval to a DATE value produced a DATE, but adding a week interval produced a DATETIME value. Now all produce a DATE value. (Bug#21811)

The column default value in the output from SHOW COLUMNS or SELECT FROM INFORMATION_SCHEMA.COLUMNS was truncated to 64 characters. (Bug#23037)

For not-yet-authenticated connections, the Time column in SHOW PROCESSLIST was a random value rather than NULL. (Bug#23379)

The Host column in SHOW PROCESSLIST output was blank when the server was started with the --skip-grant-tables option. (Bug#22728)

The Handler_rollback status variable sometimes was incremented when no rollback had taken place. (Bug#22728)

Within a prepared statement, SELECT (COUNT(*) = 1) (or similar use of other aggregate functions) did not return the correct result for statement re-execution. (Bug#21354)

Lack of validation for input and output TIME values resulted in several problems: SEC_TO_TIME() within subqueries incorrectly clipped large values; SEC_TO_TIME() treated BIGINT UNSIGNED values as signed; only truncation warnings were produced when both truncation and out-of-range TIME values occurred. (Bug#11655, Bug#20927)

Range searches on columns with an index prefix could miss records. (Bug#20732)

With SQL_MODE=TRADITIONAL, MySQL incorrectly aborted on warnings within stored routines and triggers. (Bug#20028)

In mysql, invoking connect or \r with very long db_name or host_name parameters caused buffer overflow. (Bug#20894)

mysqldump --xml produced invalid XML for BLOB data. (Bug#19745)

For a debug server, a reference to an undefined user variable in a prepared statment executed with EXECUTE caused an assertion failure. (Bug#19356)

Within a trigger for a base table, selecting from a view on that base table failed. (Bug#19111)

DELETE IGNORE could hang for foreign key parent deletes. (Bug#18819)

Transient errors in replication from master to slave may trigger multiple Got fatal error 1236: 'binlog truncated in the middle of event' errors on the slave. (Bug#4053)

The value of the warning_count system variable was not being calculated correctly (also affecting SHOW COUNT(*) WARNINGS). (Bug#19024)

InnoDB showed substandard performance with multiple queries running concurrently. (Bug#15815)

There was a race condition in the InnoDB fil_flush_file_spaces() function. (Bug#24098)

FROM_UNIXTIME() did not accept arguments up to POWER(2,31)-1, which it had previously. (Bug#9191)

Some yaSSL-related memory leaks detected by Valgrind were fixed. (Bug#23981)

If COMPRESS() returned NULL, subsequent invocations of COMPRESS() within a result set or within a trigger also returned NULL. (Bug#23254)

mysql would lose its connection to the server if its standard output was not writable. (Bug#17583)

mysql-test-run did not work correctly for RPM-based installations. (Bug#17194)

The return value from my_seek() was ignored. (Bug#22828)

Use of PREPARE with a CREATE PROCEDURE statement that contained a syntax error caused a server crash. (Bug#21868)

Use of a DES-encrypted SSL certificate file caused a server crash. (Bug#21868)

Column names were not quoted properly for replicated views. (Bug#19736)

InnoDB used table locks (not row locks) within stored functions. (Bug#18077)

InnoDB crashed when trying to display an error message about a foreign key constraint violation when the two tables are in different schemas. (Bug#23368)

Statements such as DROP PROCEDURE and DROP VIEW were written to the binary log too late due to a race condition. (Bug#14262)

At shutdown, Instance Manager told guarded server instances to stop, but did not wait until they actually stopped. (Bug#17486)

It was not possible to do an atomic rename of the log tables without the possibility of losing rows. Now you can do this:

USE mysql;
CREATE TABLE IF NOT EXISTS general_log2 LIKE general_log;
RENAME TABLE general_log TO general_log_backup, general_log2 TO general_log;

(Bug#17544, Bug#21785)

NDB Cluster (Disk Data): In the event of an aborted multiple update, the space in the Disk Data log buffer to be freed as a result was actually freed twice, which could eventually lead to a crash. (Bug#23430)

NDB Cluster: An NDB source file included a memset() call with reversed arguments. (Bug#23169)

NDB Cluster: Under some conditions, the data distribution could become unbalanced in a MySQL Cluster with 2 or more node groups following the creation of a new table. (Bug#21690)

As part of the fix for this bug, two new NDB API methods were added to the NdbDictionary::Object::Table class. See the MySQL Cluster API documentation for details.

Incorrect warnings occurred for use of CREATE TABLE ... LIKE or REPAIR TABLE with the log tables. (Bug#21966)

MySQL failed to build on the Alpha platform. (Bug#23256)

The optimizer failed to use equality propagation for BETWEEN and IN predicates with string arguments. (Bug#22753)

The optimizer used the ref join type rather than eq_ref for a simple join on strings. (Bug#22367)

The WITH CHECK OPTION for a view failed to prevent storing invalid column values for UPDATE statements. (Bug#16813)

A literal string in a GROUP BY clause could be interpreted as a column name. (Bug#14019)

Some queries that used MAX() and GROUP BY could incorrectly return an empty result. (Bug#22342)

WITH ROLLUP could group unequal values. (Bug#20825)

Use of a subquery that invoked a function in the column list of the outer query resulted in a memory leak. (Bug#21798)

LIKE searches failed for indexed utf8 character columns. (Bug#20471)

FLUSH INSTANCES in Instance Manager triggered an assertion failure. (Bug#19368)

ALTER TABLE was not able to rename a view. (Bug#14959)

The optimizer sometimes mishandled R-tree indexes for GEOMETRY data types, resulting in a server crash. (Bug#21888)

An unhandled NULL pointer caused a server crash. (Bug#22138)

Use of SQL_BIG_RESULT did not influence the sort plan for query execution. (Bug#22781)

The server did not allocate sufficient memory for some queries for which a DISTINCT to GROUP BY conversion is possible and an ORDER BY clause is present, resulting in a server crash. (Bug#20503)

The range analysis optimizer did not take into account predicates for which an index could be used after reading const tables. In some cases this resulted in non-optimal execution plans. (Bug#19579)

Entries in the slow query log could have an incorrect Rows_examined value. (Bug#12240)

Insufficient memory (myisam_sort_buffer_size) could cause a server crash for several operations on MyISAM tables: repair table, create index by sort, repair by sort, parallel repair, bulk insert. (Bug#23175)

OPTIMIZE TABLE with myisam_repair_threads > 1 could result in MyISAM table corruption. (Bug#8283)

NDB Cluster: Restoring a cluster failed if there were any tables with 128 or more columns. (Bug#23494, Bug#23502)

NDB Cluster: Cluster backups would fail when there were more than 2048 schema objects in the cluster. (Bug#23499)

NDB Cluster: The management client command ALL DUMP 1000 would cause the cluster to crash if data nodes were connected to the cluster but not yret fully started. (Bug#23203)

NDB Cluster: INSERT ... ON DUPLICATE KEY UPDATE on an NDB table could lead to deadlocks and memory leaks. (Bug#23200)

NDB Cluster: If a node restart could not be performed from the REDO log, no node takeover took place. This could cause partitions to be left empty during a system restart. (Bug#22893)

NDB Cluster: Multiple node restarts in rapid succession could cause a system restart to fail (Bug#22892), or induce a race condition (Bug#23210).

NDB Cluster: Attempting to create a unique constraint with USING HASH on an NDB table caused mysqld to crash. (Bug#21873)

NDB Cluster: When inserting a row into an NDB table with a duplicate value for a non-primary unique key, the error issued would reference the wrong key. (Bug#21072)

NDB Cluster (NDB API): When multiple processes or threads in parallel performed the same ordered scan with exclusive lock and updating the retrieved records, the scan could skip some records, which were not updated as the result. (Bug#20446)

NDB Cluster: Aborting a cluster backup too soon after starting it caused a forced shutdown of the data nodes. (Bug#19148)

Incompatible change: Support for the BerkeleyDB (BDB) engine has been dropped from this release. Any existing tables that are in BDB format will not be readable from within MySQL from 5.1.12 or newer. You should convert your tables to another storage engine before upgrading to 5.1.12.

Because of this change, the SHOW [BDB] LOGS statement has been dropped.

Incompatible change: The namespace for scheduled events has changed, such that events are no longer unique to individual users. This also means that a user with the EVENT privilege on a given database can now view, alter, or drop any events defined on that database.

If you used scheduled events in an earlier MySQL 5.1 release, you should rename any of them having the same name and defined on the same database but belonging to different users 鈥� so that all events in a given database have unique names 鈥� before upgrading to 5.1.12 (or newer).

For additional information, see Section聽20.5, 鈥淭he Event Scheduler and MySQL Privileges鈥�.

Incompatible change: The permitted values for and behaviour of the event_scheduler system variable have changed. Permitted values are now ON, OFF, and DISABLED, with OFF being the default. It is not possible to change its value to or from DISABLED while the server is running.

For details, see Section聽20.1, 鈥淓vent Scheduler Overview鈥�.

Incompatible change: The plugin interface has changed: The st_mysql_plugin structure has a new license member to indicate the license type. (The allowable values are defined in mysql/plugin.h.) This change is not backward compatible, so the API version (MYSQL_PLUGIN_INTERFACE_VERSION) has changed. For additional information, see Section聽26.2.5, 鈥淲riting Plugins鈥�.

Incompatible change: The full-text parser plugin interface has changed in two ways:

These changes are not backward compatible, so the API version (MYSQL_FTPARSER_INTERFACE_VERSION) has changed. For additional information, see Section聽26.2.5, 鈥淲riting Plugins鈥�.

Incompatible change: In the INFORMATION_SCHEMA.EVENTS table, the EVENT_DEFINITION column now contains the SQL executed by a scheduled event.

The EVENT_BODY column now contains the language used for the statement or statements shown in EVENT_DEFINITION. In MySQL 5.1, the value shown in EVENT_BODY is always SQL.

These changes were made to bring this table into line with the INFORMATION_SCHEMA.ROUTINES table, and that table's ROUTINE_BODY and ROUTINE_DEFINITION columns. (Bug#16992)

Incompatible change: MySQL Cluster node and system restarts formerly required that all fragments use the same local checkpoint (LCP); beginning with this version, it is now possible for different fragments to use different LCPs during restarts. This means that data node filesystems must be rebuilt as part of any upgrade to this version by restarting all data nodes with the --initial option. (Bug#21271, Bug#21478)

See Section聽15.5.2, 鈥淐luster Upgrade and Downgrade Compatibility鈥�, and related sections of the Manual before upgrading a MySQL Cluster to version 5.1.12 or later.

Incompatible change: A number of MySQL constructs are now prohibited in partitioning expressions, beginning with this release. These include:

These restrictions were added in part as a result of Bug#18198 and related bug reports.

For more information about these and other restrictions on partitioned tables in MySQL, see Section聽16.5, 鈥淩estrictions and Limitations on Partitioning鈥�.

Binary MySQL distributions no longer include a mysqld-max server. Instead, distributions contain a binary that includes the features previously included in the mysqld-max binary.

The default binary log format (as used during replication) is now Mixed based, automatically using a combination of row-based and statement based log events as appropriate.

The general query log and slow query logs now can be enabled or disabled at runtime with the general_log and slow_query_log system variables, and the name of the log files can be changed by setting the general_log_file and slow_query_log_file system variables. See Section聽5.11.3, 鈥淭he General Query Log鈥�, and Section聽5.11.5, 鈥淭he Slow Query Log鈥�.

The output generated by the server when using the --xml option has changed with regard to null values. It now matches the output from mysqldump --xml. That is, a column containing a NULL value is now reported as

<field name="column_name" xsi:nil="true" />

whereas a column containing the string value 'NULL' is reported as

<field name="column_name">NULL</field>

and a column containing an empty string is reported as

<field name="column_name">>/field>

(Bug#21263)

The following statements now can be executed as prepared statements (using PREPARE plus EXECUTE):

CACHE INDEX
CHANGE MASTER
CHECKSUM {TABLE | TABLES}
{CREATE | RENAME | DROP} DATABASE
{CREATE | RENAME | DROP} USER
FLUSH {TABLE | TABLES | TABLES WITH READ LOCK | HOSTS | PRIVILEGES
  | LOGS | STATUS | MASTER | SLAVE | DES_KEY_FILE | USER_RESOURCES}
GRANT
REVOKE
KILL
LOAD INDEX INTO CACHE
RESET {MASTER | SLAVE | QUERY CACHE}
SHOW BINLOG EVENTS
SHOW CREATE {PROCEDURE | FUNCTION | EVENT | TABLE | VIEW}
SHOW {AUTHORS | CONTRIBUTORS | WARNINGS | ERRORS}
SHOW {MASTER | BINARY} LOGS
SHOW {MASTER | SLAVE} STATUS
SLAVE {START | STOP}
INSTALL PLUGIN
UNINSTALL PLUGIN

(Bug#20665)

The Instance Manager --passwd option has been renamed to --print-password-line. Other options were added to enable management of the IM password file from the command line: --add-user, --drop-user, --edit-user, --list-users, --check-password-file, --clean-password-file, --username, and --password. The --mysql-safe-compatible option was added to cause the Instance Manner to act similarly to mysqld_safe.

On Windows, typing Control-C caused the mysql client to crash. Now it causes mysql to attempt to kill the current statement. If this cannot be done, or Control-C is typed again before the statement is killed, mysql exits. (Bug#17926; see also Bug#1989)

TEXT and BLOB columns do not support DEFAULT values. However, when a default of '' was specified, the specification was silently ignored. This now results in a warning, or an error in strict mode. (Bug#19498)

The mysql client now allows \l in the prompt command argument to insert the current delimiter into the prompt. (Bug#14448)

Log table changes: By default, the log tables use the CSV storage engine, as before. But now the log tables can be altered to use the MyISAM storage engine. You cannot use ALTER TABLE to alter a log table that is in use. The log must be disabled first. No engines other than CSV or MyISAM are legal for the log tables. The use of DROP TABLE for log tables is similarly restricted: It cannot be used to drop a log table that is in use. The log must be disabled first. (These changes also correct a deadlock that occurred for an attempt to drop an in-use log table.) (Bug#18559)

The LEFT() and RIGHT() functions return NULL if any argument is NULL. (Bug#11728)

EXPLAIN EXTENDED now shows a filtered column that is an estimated percentage of the examined rows that will be joined with the previous tables. (Bug#14940)

For mysqlshow, if a database name argument contains wildcard characters (such as 鈥�_鈥�) but matches a single database name exactly, treat the name as a literal name. This allows a command such as mysqlshow information_schema work without having to escape the wildcard character. (Bug#19147)

If a DROP VIEW statement named multiple views, it stopped with an error if a non-existent view was named and did not drop the remaining views. Now it continues on and reports an error at the end, similar to DROP TABLE. (Bug#16614)

SHOW CREATE TABLE now shows constraints for InnoDB tables. (Bug#16614)

Added the --set-charset option to mysqlbinlog to allow the character set to be specified for processing binary log files. (Bug#18351)

NDB Cluster: Backup messages are no longer printed to the Cluster log.

NDB Cluster: The HELP command in the Cluster management client now provides command-specific help. For example, HELP RESTART in ndb_mgm provides detailed information about the START command. (Bug#19620)

NDB Cluster: Inserting into an NDB table failed when the table had no primary key but had a unique key added after table was created on one or more NOT NULL columns. This occurred when the unique key had been adding using either ALTER TABLE or CREATE UNIQUE KEY. (Bug#22838)

NDB Cluster: The ndb_config utility now accepts -c as a short form of the --ndb-connectstring option. (Bug#22295)

NDB Cluster: Added the --bind-address option for ndbd. This allows a data node process to be bound to a specific network interface. (Bug#22195)

NDB Cluster: The Ndb_number_of_storage_nodes system variable was renamed to Ndb_number_of_data_nodes. (Bug#20848)

Added the --ndb-use-copying-alter-table option to mysqld to provide a fallback in case of problems with online ALTER TABLE operations on NDBCluster tables.

Added the SHOW CONTRIBUTORS statement.

It is no longer possible to create partitioned tables using the CSV storage engine.

NDB Cluster: The status variables Ndb_connected_host and Ndb_connected_port were renamed to Ndb_config_from_host and Ndb_config_from_port, respectively.

NDB Cluster: A number of erroneous, misleading, or missing error messages have been corrected. (Bug#17297 & Bug#19543)

NDB Cluster: It is no longer possible to create Cluster tables using any partitioning type other than [LINEAR] KEY. Attempting to do so now raises an error.

The ExtractValue() function now produces an error when passed an XML fragment that is not well-formed. (Bug#18201)

(Previously, the function allowed invalid XML fragments to be used.)

There were several issues regarding how SHOW STATUS affected some status variables and logging which could impact monitoring the MySQL Server. The behavior of this statement has been modified in two ways:

However, SHOW STATUS continues to update global status variables to allow monitoring of what the server is actually doing. This is because SHOW STATUS creates temporary tables that may affect performance if it is called excessively often. (Bug#10210, Bug#19764)

The mysqldumpslow script has been moved from client RPM packages to server RPM packages. This corrects a problem where mysqldumpslow could not be used with a client-only RPM install, because it depends on my_print_defaults which is in the server RPM. (Bug#20216)

The bundled yaSSL library was upgraded to version 1.3.7.

The bundled yaSSL library licensing has added a FLOSS exception similar to MySQL to resolve licensing incompatibilities with MySQL. (See the extra/yassl/FLOSS-EXCEPTIONS file in a MySQL source distribution for details.) (Bug#16755)

mysqlslap threads now try to connect up to 10 times if the initial connect attempt fails. (Bug#21297)

For a successful dump, mysqldump now writes a SQL comment to the end of the dump file in the following format:

-- Dump completed on YYYY-MM-DD hh:mm:ss

(Bug#10877)

The mysqld and mysqlmanager manpages have been reclassified from volume 1 to volume 8. (Bug#21220)

In the INFORMATION_SCHEMA.ROUTINES table the ROUTINE_DEFINITION column now is defined as NULL rather than NOT NULL. Also, NULL rather than the empty string is returned as the column value if the user does not have sufficient privileges to see the routine definition. (Bug#20230)

configure now defines the symbol DBUG_ON in config.h to indicate whether the source tree is configured to be compiled with debugging support. (Bug#19517)

The MySQL distribution now compiles on UnixWare 7.13. (Bug#20190)

The mysql client used the default character set if it automatically reconnected to the server, which is incorrect if the character set had been changed. To enable the character set to remain synchronized on the client and server, the mysql command charset (or \C) that changes the default character set and now also issues a SET NAMES statement. The changed character set is used for reconnects. (Bug#11972)

The STATE column of the INFORMATION_SCHEMA.PROCESSLIST table was increased from 30 to 64 characters to accommodate longer state values. (Bug#21652)

TIMESTAMP columns that are NOT NULL now are reported that way by SHOW COLUMNS and INFORMATION_SCHEMA. (Bug#20910)

INFORMATION_SCHEMA contains new tables, GLOBAL_STATUS, SESSION_STATUS, GLOBAL_VARIABLES, and SESSION_VARIABLES, that correspond to the output from the SHOW {GLOBAL|SESSION} STATUS and SHOW {GLOBAL|SESSION} VARIABLES statements.

The BINARY keyword now is forbidden as a data type attribute in stored routines (for example, DECLARE v1 VARCHAR(25) BINARY), because DECLARE does not support collations, and in this context BINARY specifies the binary collation of the variable's character set. (Bug#20701)

The source distribution has been updated so that the UDF example can be compiled under Windows with CMake. See Section聽26.3.4.5, 鈥淐ompiling and Installing User-Defined Functions鈥�. (Bug#19121)

LOAD DATA INFILE no longer causes an implicit commit for all storage engines. It now causes an implicit commit only for tables using the NDB storage engine. (Bug#11151)

The LOAD DATA FROM MASTER and LOAD TABLE FROM MASTER statements are deprecated. See Section聽13.6.2.2, 鈥�LOAD DATA FROM MASTER Syntax鈥�, for recommended alternatives. (Bug#18822, Bug#9125, Bug#12187, Bug#14399, Bug#15025, Bug#20596)

mysqldump now has a --flush-privileges option. It causes mysqldump to emit a FLUSH PRIVILEGES statement after dumping the mysql database. This option should be used any time the dump contains the mysql database and any other database that depends on the data in the mysql database for proper restoration. (Bug#21424)

The default value of the tmp_table_size system variable was lowered from 32MB to 16MB because it is bounded by the value of max_heap_table_size, which has a default of 16MB. (Bug#18875)

The number of InnoDB threads is no longer limited to 1,000 on Windows. (Bug#22268)

Memory consumption of the InnoDB data dictionary cache was roughly halved by cleaning up the data structures. (Bug#20877)

Using --with-debug to configure MySQL with debugging support enables you to use the --debug="d,parser_debug" option when you start the server. This causes the Bison parser that is used to process SQL statements to dump a parser trace to the server's standard error output. Typically, this output is written to the error log.

A new system variable, lc_time_names, specifies the locale that controls the language used to display day and month names and abbreviations. This variable affects the output from the DATE_FORMAT(), DAYNAME() and MONTHNAME() functions. See Section聽5.10.9, 鈥淢ySQL Server Locale Support鈥�.

Security fix: On Linux, and possibly other platforms using case-sensitive filesystems, it was possible for a user granted rights on a database to create or access a database whose name differed only from that of the first by the case of one or more letters. (CVE-2006-4226, Bug#17647)

Security fix: If a user has access to MyISAM table t, that user can create a MERGE table m that accesses t. However, if the user's privileges on t are subsequently revoked, the user can continue to access t by doing so through m. If this behavior is undesirable, you can start the server with the new --skip-merge option to disable the MERGE storage engine. (Bug#15195)

Security fix: A stored routine created by one user and then made accessible to a different user using GRANT EXECUTE could be executed by that user with the privileges of the routine's definer. (CVE-2006-4227, Bug#18630)

Incompatible change: For utf8 columns, the full-text parser incorrectly considered several non-word punctuation and whitespace characters as word characters, causing some searches to return incorrect results. (Bug#19580)

The fix involves a change to the full-text parser, so any tables that have FULLTEXT indexes on utf8 columns must be repaired with REPAIR TABLE:

REPAIR TABLE tbl_name QUICK;

An invalid GRANT statement for which Ok was returned on a replication master caused an error on the slave and replication to fail. (Bug#6774)

InnoDB locking was improved by removing a gap lock for the case that you try to delete the same row twice within a transaction. (Bug#13544)

Deleting entries from a large MyISAM index 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. (Bug#22384)

Setting myisam_repair_threads caused any repair operation on a MyISAM table to fail to update the cardinality of indexes, instead making them always equal to 1. (Bug#18874)

ALTER EVENT statements including only a COMMENT clause failed with a syntax error on two platforms: Linux for S/390, and OS X 10.4 for 64-bit PPC. (Bug#23423)

For row-based replication, log rotation could occur at an improper time. (Bug#21474)

For row-based replication, the BINLOG command did not lock tables properly, causing a crash for some table types. (Bug#19459)

The parser rejected queries that selected from a table twice using a UNION within a subquery. The parser now supports arbitrary subquery, join, and parenthesis operations within EXISTS subqueries. A limitation still exists for scalar subqueries: If the subquery contains UNION, the first SELECT of the UNION cannot be within parentheses. For example, SELECT (SELECT a FROM t1 UNION SELECT b FROM t2) will work, but SELECT ((SELECT a FROM t1) UNION (SELECT b FROM t2)) will not. (Bug#14654)

Incorrect type aggregation for IN and CASE expressions could lead to an incorrect result. (Bug#18360)

When using row based replication, a CREATE TABLE...SELECT statement would be replicated, even if the table creation failed on the master (for example, due to a duplicate key failure). (Bug#20265)

The optimizer did not take advantage of indexes on columns used for the second or third arguments of BETWEEN. (Bug#18165)

Subqueries with aggregate functions but no FROM clause could return incorrect results. (Bug#21540)

The CSV storage engine failed to detect some table corruption. (Bug#22080)

For multiple-table UPDATE statements, storage engines were not notified of duplicate-key errors. (Bug#21381)

Successive invocations of a COUNT(*) query containing a join on two MyISAM tables and a WHERE clause of the form WHERE (table1.column1 = table2.column2) OR table2.column2 IS NULL yielded different results. (Bug#21019)

It was possible to provide the ExtractValue() function with input containing 鈥�tags鈥� that were not valid XML; for example, it was possible to use tag names beginning with a digit, which are disallowed by the W3C's XML 1.0 specification. Such cases caused the function to return 鈥�junk鈥� output rather than an error message signalling the user as to the true nature of the problem. (Bug#20854)

The presence of a subquery in the ON clause of a join in a view definition prevented the MERGE algorithm from being used for the view in cases where it should be allowed. (Bug#21646)

BIT columns were not replicated properly under row-based replication. (Bug#22550)

Conversion of values inserted into a BIT column could affect adjacent columns. (Bug#22271)

The URL into the online manual that is printed in the stack trace message by the server was out of date. (Bug#21449)

Incorrect results could be obtained from re-execution of a parametrized prepared statement or a stored routine with a SELECT that uses LEFT JOIN with a second table having only one row. (Bug#21081)

PROCEDURE ANALYSE() returned incorrect values of M FLOAT(M, D) and DOUBLE(M, D). (Bug#20305)

Join conditions using index prefixes on utf8 columns of InnoDB tables incorrectly ignored rows where the length of the actual value was greater than the length of the index prefix. (Bug#19960)

On an INSERT into an updatable but non-insertable view, an error message was issued stating that the view was not updatable. Now the message says the view is not insertable-into. (Bug#5505)

INSERT DELAYED did not honor SET INSERT_ID or the auto_increment_* system variables. (Bug#20627, Bug#20830)

For character sets having a mbmaxlen value of 2, any ALTER TABLE statement changed TEXT columns to MEDIUMTEXT. (Bug#21620)

A query that used GROUP BY and an ALL or ANY quantified subquery in a HAVING clause could trigger an assertion failure. (Bug#21853)

For an ENUM column that used the ucs2 character set, using ALTER TABLE to modify the column definition caused the default value to be lost. (Bug#20108)

An UPDATE that referred to a key column in the WHERE clause and activated a trigger that modified the column resulted in a loop. (Bug#20670)

A loaded storage engine plugin did not load after a server restart. (Bug#21610)

Creating a TEMPORARY table with the same name as an existing table that was locked by another client could result in a lock conflict for DROP TEMPORARY TABLE because the server unnecessarily tried to acquire a name lock. (Bug#21096)

After FLUSH TABLES WITH READ LOCK followed by UNLOCK TABLES, attempts to drop or alter a stored routine failed with an error that the routine did not exist, and attempts to execute the routine failed with a lock conflict error. (Bug#21414)

mysql_com.h unnecessarily referred to the ulong type. (Bug#22227)

Incorporated some portability fixes into the definition of __attribute__ in my_global.h. (Bug#2717)

Linking the pthreads library to single-threaded MySQL libraries caused dlopen() to fail at runtime on HP-UX. (Bug#18267)

Loading a plugin caused any an existing plugin with the same name to be lost. (Bug#20615)

In the package of pre-built time zone tables that is available for download at http://dev.mysql.com/downloads/timezones.html, the tables now explicitly use the utf8 character set so that they work the same way regardless of the system character set value. (Bug#21208)

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. (Bug#18888)

mysql_ftdump produced bad counts for common words. (Bug#22326)

The optimizer could make an incorrect index choice for indexes with a skewed key distribution. (Bug#22393)

When records are merged from the insert buffer and the page needs to be reorganized, InnoDB used 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. (Bug#21638)

Instance Manager didn't close the client socket file when starting a new mysqld instance. mysqld inherited the socket, causing clients connected to Instance Manager to hang. (Bug#12751)

Using GROUP_CONCAT() on the result of a subquery in the FROM clause that itself used GROUP_CONCAT() could cause a server crash. (Bug#22015)

Instance Manager had a race condition involving mysqld PID file removal. (Bug#22379)

Execution of a prepared statement that uses an IN subquery with aggregate functions in the HAVING clause could cause a server crash. (Bug#22085)

Selecting from a MERGE table could result in a server crash if the underlying tables had fewer indexes than the MERGE table itself. (Bug#21617, Bug#22937)

A locking safety check in InnoDB reported a spurious error stored_select_lock_type is 0 inside ::start_stmt() for INSERT ... SELECT statements in innodb_locks_unsafe_for_binlog mode. The safety check was removed. (Bug#10746)

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)

The source distribution would not build on Windows due to a spurious dependency on ib_config.h. (Bug#22224)

It was possible for a stored routine with a non-latin1 name to cause a stack overrun. (Bug#21311)

The server returns a more informative error message when it attempts to open a MERGE table that has been defined to use non-MyISAM tables. (Bug#10974)

Within stored routines, some error messages were printed incorrectly. A non-null-terminated string was passed to a message-printing routine that expected a null-terminated string. (Bug#20778)

SUBSTR() results sometimes were stored improperly into a temporary table when multi-byte character sets were used. (Bug#20204)

Certain malformed INSERT statements could crash the mysql client. (Bug#21142)

EXPLAIN EXTENDED now shows a filtered column that is an estimated percentage of the examined rows that will be joined with the previous tables. This was added while dealing with a problem of MySQL choosing the wrong index for some queries. (Bug#14940)

On Mac OS X, zero-byte read() or write() calls to an SMB-mounted filesystem could return a non-standard return value, leading to data corruption. Now such calls are avoided. (Bug#12620)

With 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. (Bug#6147)

The source distribution failed to compile when configured with the --without-geometry option. (Bug#12991)

The source distribution failed to compile when configured with the --with-libwrap option. (Bug#18246)

The feature of being able to recover a temporary table named #sql_id in InnoDB by creating a table named rsql_id_recover_innodb_tmp_table was broken by the introduction of the new identifier encoding in MySQL 5.1.6 (Bug#21313)

ALTER EVENT in the body of a stored procedure led to a crash when the procedure was called. This affected only those ALTER EVENT statements which changed the interval of the event. (Bug#22397)

A DATE can be represented as an integer (such as 20060101) or as a string (such as '2006.01.01'). When a DATE (or TIME) column is compared in one SELECT against both representations, constant propagation by the optimizer led to comparison of DATE as a string against DATE as an integer. This could result in integer comparisons such as 2006 against 20060101, erroneously producing a false result. (Bug#21475)

When a statement used a stored function that inserted into an AUTO_INCREMENT column, the generated AUTO_INCREMENT value was not written into the binary log, so a different value could in some cases be inserted on the slave. (Bug#20341)

A stored procedure that used LAST_INSERT_ID() did not replicate properly using statement-based binary logging. (Bug#20339)

Use of the --no-pager option caused mysql to crash. (Bug#19363)

For INSERT ... ON DUPLICATE KEY UPDATE, use of VALUES(col_name) within the UPDATE clause sometimes was handled incorrectly. (Bug#21555)

When event_scheduler was set to DISABLED, its value was not displayed correctly by SHOW VARIABLES or SELECT @@global.event_scheduler. (Bug#22662)

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. (Bug#16081)

If the binary logging format was changed between the times when a locked table was modified and when it was unlocked, the binary log contents were incorrect. (Bug#20863)

Column names supplied for a view created on a master server could be lost on a slave server. (Bug#19419)

For a MyISAM table locked with LOCK TABLES ...WRITE, queries optimized using the index_merge method did not show rows inserted with the lock in place. (Bug#20256)

Table aliases in multiple-table DELETE statements sometimes were not resolved. (Bug#21392)

A query result could be sorted improperly when using ORDER BY for the second table in a join. (Bug#21302)

The --collation-server server option was being ignored. With the fix for this problem, if you choose a non-default character set with --character-set-server, you should also use --collation-server to specify the collation. (Bug#15276)

A function result in a comparison was replaced with a constant by the optimizer under some circumstances when this optimization was invalid. (Bug#21698)

A subquery that uses an index for both the WHERE and ORDER BY clauses produced an empty result. (Bug#21180)

If the auto_increment_offset 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. (Bug#20573)

Queries containing a subquery that used aggregate functions could return incorrect results. (Bug#16792)

Row-based replication failed when the query cache was enabled on the slave. (Bug#17620)

The index_merge/Intersection optimizer could have a memory overrrun when the number of table columns covered by an index is sufficiently large, possibly resulting in a server crash. (Bug#16201)

The MD5(), SHA1(), and ENCRYPT() functions should return a binary string, but the result sometimes was converted to the character set of the argument. MAKE_SET() and EXPORT_SET() now use the correct character set for their default separators, resulting in consistent result strings which can be coerced according to normal character set rules. (Bug#20536)

EXPLAIN sometimes returned an incorrect select_type for a SELECT from a view, compared to the select_type for the equivalent SELECT from the base table. (Bug#5500)

An InnoDB mutex was not aquired and released under the same condition, leading to deadlock in some rare situations involving XA transactions. (Bug#21833)

With row-based replication, replicating a statement to a slave where the table had additional columns relative to the master table did not work. (Bug#19069)

For a MyISAM table with a FULLTEXT index, compression with myisampack or a check with myisamchk after compression resulted in table corruption. (Bug#19702)

With max_sp_recursion set to 0, a stored procedure that executed a SHOW CREATE PROCEDURE statement for itself triggered a recursion limit exceeded error, though the statement involves no recursion. (Bug#21416)

mysqldump did not add version-specific comments around WITH PARSER and TABLESPACE ... STORAGE DISK clauses for CREATE TABLE statements, causing the dump file to fail when loaded into older servers. (Bug#20841)

BIN(), OCT(), and CONV() did not work with BIT values. (Bug#15583)

The optimizer could produce an incorrect result after AND with collations such as latin1_german2_ci, utf8_czech_ci, and utf8_lithianian_ci. (Bug#9509)

The server could crash for the second execution of a function containing a SELECT statement that uses an aggregating IN subquery. (Bug#21493)

UPGRADE was treated as a reserved word, although it is not. (Bug#21772)

Database and table names have a maximum length of 64 characters (even if they contain multi-byte characters), but were being truncated to 64 bytes. (Bug#21432) An additional fix was made in MySQL 5.1.18.

Usernames have a maximum length of 16 characters (even if they contain multi-byte characters), but were being truncated to 16 bytes. (Bug#20393)

A query could produce different results with and without and index, if the WHERE clause contained a range condition that used an invalid DATETIME constant. (Bug#16249)

COUNT(*) queries with ORDER BY and LIMIT could return the wrong result. (Bug#21787)

Note: This problem was introduced by the fix for Bug#9676, which limited the rows stored in a temporary table to the LIMIT clause. This optimization is not applicable to non-group queries with aggregate functions. The current fix disables the optimization in such cases.

Memory overruns could occur for certain kinds of subqueries. (Bug#21477)

Adding ORDER BY to a SELECT DISTINCT(expr) query could produce incorrect results. (Bug#21456)

Memory used by scheduled events was not freed when the events were dropped. (Bug#18683)

A scheduled event that took longer to execute than the length of time scheduled between successive executions could 鈥�skip鈥� executions. For example, an event defined with EVERY 1 SECOND 鈥� but which required longer than 1 second to complete 鈥� might be executed only once every 2 seconds. (Bug#16417)

When used in the DO clause of a CREATE EVENT statement, the statements CREATE EVENT, CREATE FUNCTION, and CREATE PROCEDURE caused the server to crash. (These statements are not permitted inside CREATE EVENT.) (Bug#16409, Bug#18896)

A subselect used in the ON SCHEDULE clause of a CREATE EVENT or ALTER EVENT statement caused the server to crash, rather than producing an error as expected. (Bug#16394)

mysql displayed an empty string for NULL values. (Bug#21618)

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. (Bug#21011)

mysql_config --libmysqld-libs did not produce any SSL options necessary for linking libmysqld with SSL support enabled. (Bug#21239)

yaSSL had a conflicting definition for socklen_t on hurd-i386 systems. (Bug#22326)

On Windows, inserting into a MERGE table after renaming an underlying MyISAM table caused a server crash. (Bug#20789)

character_set_results can be NULL to signify 鈥�no conversion,鈥� but some code did not check for NULL, resulting in a server crash. (Bug#21913)

If a partitioned InnoDB table contained an AUTO_INCREMENT column, a SHOW statement could cause an assertion failure with more than one connection. (Bug#20493)

Running InnoDB with many concurrent threads could cause memory corruption and a seg fault due to a bug introduced in MySQL 5.1.11. (Bug#20213)

Using DROP TABLE with concurrent queries causes mysqld to crash. (Bug#21784)

The ExtractValue() function did not accept XML tag names containing a period (.) character. (Bug#20795)

For table-format output, mysql did not always calculate columns widths correctly for columns containing multi-byte characters in the column name or contents. (Bug#17939)

Identifiers with embedded escape characters were not handled correctly by some SHOW statements due to some old code that was doing some extra unescaping. (Bug#19874)

InnoDB was slow with more than 100,000 .idb files. (Bug#21112)

SHOW INNODB STATUS contained some duplicate output. (Bug#21113)

After an INSERT ... ON DUPLICATE KEY UPDATE statement that updated an existing row, LAST_INSERT_ID() could return a value not in the table. (Bug#11460)

Selecting from INFORMATION_SCHEMA.FILES could crash the server. (Bug#21676)

Using cursors with READ COMMITTED isolation level could cause InnoDB to crash. (Bug#19834)

A server or network failure with an open client connection would cause the client to hang even though the server was no longer available. (Bug#9678)

Using ALTER TABLE ... REORGANIZE PARTITIONS to reduce the number of subpartitions to 1 caused the server to crash. (Bug#21210)

NDB Cluster: Data nodes added while the cluster was running in single user mode were all assigned node ID 0, which could later cause multiple node failures. Adding of nodes in single user mode is no longer possible. (Bug#20395)

NDB Cluster: Attempting to create an NDB table on a MySQL with an existing non-Cluster table with the same name in the same database could result in data loss or corruption. Now, if such a table is encountered during autodiscovery, a warning is written to the error log of the affected mysqld, and the local table is overwritten. (Bug#21378)

NDB Cluster (NDB API): Inacivity timeouts for scans were not correctly handled. (Bug#23107)

NDB Cluster (NDB API): Attempting to read a nonexistent tuple using Commit mode for NdbTransaction::execute() caused node failures. (Bug#22672)

NDB Cluster (NDB API): The inclusion of my_config.h in NdbApi.h required anyone wishing to write NDB API applications against MySQL 5.1 to have a complete copy of the 5.1 sources. (Bug#21253)

NDB Cluster (NDB API): The NdbOperation::getBlobHandle() method, when called with the name of a nonexistent column, caused a segmentation fault. (Bug#21036)

NDB Cluster: The --help output from NDB binaries did not include file-related options. (Bug#21994)

NDB Cluster: The node recovery algorithm was missing a version check for tables in the ALTER_TABLE_COMMITTED state (as opposed to the TABLE_ADD_COMMITTED state, which has the version check). This could cause inconsistent schemas across nodes following node recovery. (Bug#21756)

NDB Cluster: The output for the --help option used with NDB executable programs (ndbd, ndb_mgm, ndb_restore, ndb_config, and so on) referred to the Ndb.cfg file, instead of my.cnf. (Bug#21585)

NDB Cluster: Partition distribution keys were updated only for the primary and starting replicas during node recovery. This could lead to node failure recovery for clusters having an odd number of replicas. (Bug#21535)

Note: We recommend values for NumberOfReplicas that are even powers of 2, for best results.

NDB Cluster: The ndb_mgm management client did not set the exit status on errors, always returning 0 instead. (Bug#21530)

NDB Cluster: Cluster logs were not rotated following the first rotation cycle. (Bug#21345)

NDB Cluster: Condition pushdown did not work correctly with DATETIME columns. (Bug#21056)

NDB Cluster: Under some circumstances, local checkpointing would hang, keeping any unstarted nodes from being started. (Bug#20895)

NDB Cluster: Using an invalid node ID with the management client STOP command could cause ndb_mgm to hang. (Bug#20575)

NDB Cluster: In some cases where SELECT COUNT(*) from an NDB table should have yielded an error, MAX_INT was returned instead. (Bug#19914)

NDB Cluster: Following the restart of an MGM node, the Cluster management client did not automatically reconnect. (Bug#19873)

NDB Cluster: Error messages given when trying to make online changes parameters such as NoOfReplicas thast can only be changed via a complete shutdown and restart of the cluster did not indicate the true nature of the problem. (Bug#19787)

NDB Cluster: ndb_restore did not always make clear that it had recovered successfully from temporary errors while restoring a cluster backup. (Bug#19651)

NDB Cluster: In rare situations with resource shortages, a crash could result from insufficient IndexScanOperations. (Bug#19198)

NDB Cluster: ndb_mgm -e show | head would hang after displaying the first 10 lines of output. (Bug#19047)

NDB Cluster: The error returned by the cluster when too many nodes were defined did not make clear the nature of the problem. (Bug#19045)

NDB Cluster: A problem with takeover during a system restart caused ordered indexes to be rebuilt incorrectly. This also adversely affected Cluster Replication. (Bug#15303)

NDB Cluster: Some queries involving joins on very large NDB tables could crash the MySQL server. (Bug#21059)

NDB Cluster (Disk Data): mysqldump did not back up tablespace or log file group information for Disk Data tables correctly. (Specifically, UNDO_BUFFER_SIZE and INITIAL_SIZE values were misreported.) Trying to restore from such a backup would produce error 1296 (Got error 1504 'Out of logbuffer memory' from NDB). (Bug#20809)

NDB Cluster (Disk Data): The INFORMATION_SCHEMA.FILES table showed incorrect values in the EXTENT_SIZE, FREE_EXTENTS, and TOTAL_EXTENTS columns for UNDO log files. (Bug#20073)

NDB Cluster (Disk Data): Deletes from Disk Data tables used a non-optimal scan to find the rows to be deleted, resulting in poor performance. The fix causes disk order rather than memory order to be used, and can improve performance of Disk Data deletes by up to ~300% in some cases. (Bug#17929)

NDB Cluster: A scan timeout returned Error 4028 (Node failure caused abort of transaction) instead of Error 4008 (Node failure caused abort of transaction...). (Bug#21799)

NDB Cluster: The message Error 0 in readAutoIncrementValue(): no Error was written to the error log whenever SHOW TABLE STATUS was performed on a Cluster table that did not have an AUTO_INCREMENT column. (Bug#21033)

NDB Cluster (Direct APIs): The storage/ndb directory was missing from the server binary distribution, making it impossible to compile NDB API and MGM API applications. This directory can be found as /usr/include/storage/ndb after installing that distribution. (Bug#21955)

NDB Cluster: ndb_size.pl and ndb_error_reporter were missing from RPM packages. (Bug#20426)

The ndb_mgm program was included in both the MySQL-ndb-tools and MySQL-ndb-management RPM packages, resulting in a conflict if both were installed. Now ndb_mgm is included only in MySQL-ndb-tools. (Bug#21058)

libmysqld produced some warnings to stderr which could not be silenced. These warnings now are suppressed. (Bug#13717)

If a column definition contained a character set declaration, but a DEFAULT value began with an introducer, the introducer character set was used as the column character set. (Bug#20695)

If a query had a condition of the form tableX.key = tableY.key, which participated in equality propagation and also was used for ref access, then early ref-access NULL filtering was not peformed for the condition. This could make query execution slower. (Bug#19649)

The optimizer sometimes produced an incorrect row-count estimate after elimination of const tables. This resulted in choosing extremely inefficient execution plans in same cases when distribution of data in joins were skewed. (Bug#21390)

Query results could be incorrect if the WHERE clause contained t.key_part NOT IN (val_list), where val_list is a list of more than 1000 constants. (Bug#21282)

STR_TO_DATE() sometimes would return NULL if the %D format specifier was not the last specifier in the format string. (Bug#20987)

On Windows, a definition for mysql_set_server_option() was missing from the C client library. (Bug#16513)

The myisam_stats_method variable was mishandled when set from an option file or on the command line. (Bug#21054)

The optimizer assumed that if (a=x AND b=x) is true, (a=x AND b=x) AND a=b is also true. But that is not always so if a and b have different data types. (Bug#21159)

InnoDB did not honor IGNORE INDEX, which prevented using IGNORE INDEX in cases where an index sort would be slower than a filesort. (Bug#21174)

For connections that required a SUBJECT value, a check was performed to verify that the value was correct, but the connection was not refused if not. (Bug#20411)

Some Linux-x86_64-icc packages (of previous releases) mistakenly contained 32-bit binaries. Only ICC builds are affected, not gcc builds. Solaris and FreeBSD x86_64 builds are not affected. (Bug#22238)

INSERT ... SELECT sometimes generated a spurious Column count doesn't match value count error. (Bug#21774)

Some user-level errors were being written to the server's error log, which is for server errors. (Bug#20402)

to the client could have an empty column name. When using tables created under MySQL 4.1 with a 5.0 server, if the tables contained VARCHAR columns, for some queries the metadata sent to the client could have an empty column name. (Bug#14897)

On 64-bit systems, use of the cp1250 character set with a primary key column in a LIKE clause caused a server crash for patterns having letters in the range 128..255. (Bug#19741)

ORDER BY RAND() LIMIT 1 always set a user variable to the last possible value from the table. (Bug#16861)

N'xxx' and _utf8'xxx' were not treated as equivalent because N'xxx' failed to unescape backslashes (\) and doubled apostrophe/single quote characters (''). (Bug#17313)

A subquery in the WHERE clause of the outer query and using IN and GROUP BY returned an incorrect result. (Bug#16255)

When NOW() was used in a BETWEEN clause of the definition for a view, it was replaced with a constant in the view. (Bug#15950)

A stored procedure with a CONTINUE handler that encountered an error continued to execute a statement that caused an error, rather with the next statement following the one that caused the error. (Bug#8153)

libmysqlclient defined a symbol BN_bin2bn which belongs to OpenSSL. This could break applications that also linked against OpenSSL's libcrypto library. The fix required correcting an error in a build script that was failing to add rename macros for some functions. (Bug#21930)

Queries that used the index_merge and sort_union methods to access an InnoDB table could produce inaccurate results. This issue was introduced in MySQL 5.1.10 when a new handler and bitmap interface was implemented. (Bug#21277)

The SELECT privilege was required for an insert on a view, instead of the INSERT privilege. (Bug#21261)

Note: This fixes a regression that was introduced by the fix for Bug#20989.

Running SHOW MASTER LOGS at the same time as binary log files were being switched would cause mysqld to hang. (Bug#21965)

Building mysql on Windows with CMake 2.4 would fail to create libmysqld correctly. (Bug#20907)

The server's handling of the number of partitions or subpartitions specified in a PARTITIONS or SUBPARTITIONS clause was changed. Beginning with this release, the number of partitions must:

Also beginning with this version, no attempt is made to convert, truncate, or evaluate a PARTITIONS or SUBPARTITIONS value; instead, the CREATE TABLE or ALTER TABLE statement containing the PARTITIONS or SUBPARTITIONS clause now fails with an appropriate error message. (Bug#15890)

A misleading error message was displayed when attempting to define a unique key that was not valid for a partitioned table. (Bug#21862)

Errors could be generated during the execution of certain prepared statements that ran queries on partitioned tables. (Bug#21658)

Using relative paths for DATA DIRECTORY or INDEX DIRECTORY with a partitioned table generated a warning rather than an error, and caused 鈥�junk鈥� files to be created in the server's data directory. (Bug#21350)

Using EXPLAIN PARTITIONS with a query on a table whose partitioning expression was based on the value of a DATE column could sometimes cause the server to crash. (Bug#21339)

Running SHOW TABLE STATUS on any InnoDB table having at least one record could crash the server. Note that this was not due to any issue in the InnoDB storage engine, but rather with AUTO_INCREMENT handling in the partitioning code 鈥� however, the table did not have to have an AUTO_INCREMENT column for the bug to manifest. (Bug#21173)

Some ALTER TABLE statements affecting a table's subpartitioning could hang. (Bug#21143)

Scheduled events that invoked stored procedures executing DDL operations on partitioned tables could crash the server. (Bug#20548)

The yaSSL library bundled with libmysqlclient had some conflicts with OpenSSL. Now macros are used to rename the conflicting symbols to have a prefix of ya. (Bug#19810)

It is possible to create MERGE tables into which data cannot be inserted (by not specifying a UNION clause. However, when an insert was attempted, the error message was confusing. Now an error occurs indicating that the table is read-only. (Bug#17766)

User-created tables having a name beginning with #sql were not visible to SHOW TABLES and could collide with internal temporary table names. Now they are not hidden and do not collide. (Bug#1405)

A NUL byte within a prepared statement string caused the rest of the string not to be written to the query log, allowing logging to be bypassed. (Bug#21813)

mysql_upgrade created temporary files in a possibly insecure way. (Bug#21224)

Some prepared statements caused a server crash when executed a second time. (Bug#21166)

With query_cache_type set to 0, RESET QUERY CACHE was very slow and other threads were blocked during the operation. Now a cache reset is faster and non-blocking. (Bug#21051)

When DROP DATABASE or SHOW OPEN TABLES was issued while concurrently issuing DROP TABLE (or RENAME TABLE, CREATE TABLE LIKE or any other statement that required a name lock) in another connection, the server crashed. (Bug#19403, Bug#21216)

Use of zero-length variable names caused a server crash. (Bug#20908)

Prepared statements caused general log and server memory corruption. (Bug#14346)

mysqldump incorrectly tried to use LOCK TABLES for tables in the INFORMATION_SCHEMA database. (Bug#21527)

Use of the --prompt option or prompt command caused mysql to be unable to connect to the Instance Manager. (Bug#17485)

The server crashed if it tried to access a CSV table for which the data file had been removed. (Bug#15205)

CREATE USER did not respect the 16-character username limit. (Bug#10668)

Creating a partitioned table that used the InnoDB storage engine and then restarting mysqld with --skip-innodb caused MySQL to crash. (Bug#20871)

In mixed-format binary logging mode, stored functions, triggers, and views that use functions in their body that require row-based logging did not replicate reliably because the logging did not switch from statement-based to row-based format. For example, INSERT INTO t SELECT FROM v, where v is a view that selects UUID() could cause problems. This limitation has been removed. (Bug#20930)

For user-defined functions created with CREATE FUNCTION, the DEFINER clause is not legal, but no error was generated. (Bug#21269)

mysqld --flush failed to flush MyISAM table changes to disk following an UPDATE statement for which no updated column had an index. (Bug#20060)

In mixed-format binary logging mode, stored functions, triggers, and views that use functions in their body that require row-based logging did not replicate reliably because the logging did not switch from statement-based to row-based format. For example, INSERT INTO t SELECT FROM v, where v is a view that selects UUID() could cause problems. This limitation has been removed. (Bug#20930)

When not running in strict mode, the server failed to convert the invalid years portion of a DATE or DATETIME value to '0000' when inserting it into a table. (Bug#19370)

This patch was reverted in MySQL 5.1.18.

The dropping of a temporary table whose name contained a backtick ('`') character was not correctly written to the binary log, which also caused it not to be replicated correctly. (Bug#19188)

Intermediate tables created during the execution of an ALTER TABLE statement were visible in the output of SHOW TABLES. (Bug#18775)

When setting a column to its implicit default value as the result of inserting a NULL into a NOT NULL column as part of a multi-row insert or LOAD DATA operation, the server returned a misleading warning message. (Bug#14770)

The --with-collation option was not honored for client connections. (Bug#7192)

Users who had the SHOW VIEW privilege for a view and privileges on one of the view's base table could not see records in INFORMATION_SCHEMA tables relating to the base table. (Bug#20543)

An issue with yaSSL prevented Connector/J clients from connecting to the server using a certificate. (Bug#19705)

Some server errors were not reported to the client, causing both to try to read from the connection until a hang or crash resulted. (Bug#16581)

FEDERATED tables raised invalid duplicate key errors when attempting on one server to insert rows having the same primary key values as rows that had been deleted from the linked table on the other server. (Bug#18764)

The C API failed to return a status message when invoking a stored procedure. (Bug#15752)

AUTHORS and CONTRIBUTORS were not treated as reserved words. (Bug#19939)

Stored procedures did not use the character set defined for the database in which they were created. (Bug#16676)

CREATE PROCEDURE, CREATE FUNTION, CREATE TRIGGER, and CREATE VIEW statements containing multi-line comments (/* ... */) could not be replicated. (Bug#20438)

The final parenthesis of a CREATE INDEX statement occurring in a stored procedure was omitted from the binary log when the stored procedure was called. (Bug#19207)

Attempting to insert a string of greater than 4096 bytes into a FEDERATED table resulted in the error ERROR 1296 (HY000) at line 2: Got error 10000 'Error on remote system: 1054: Unknown column 'string-value' from FEDERATED. This error was raised regardless of the type of column involved (VARCHAR, TEXT, and so on.) (Bug#17608)

Performance during an import on a table with a trigger that called a stored procedure was severely degraded. (Bug#21013)

Repeated DROP TABLE statements in a stored procedure could sometimes cause the server to crash. (Bug#19399)

On 64-bit Windows, a missing table generated error 1017, not the correct value of 1146. (Bug#21396)

The same trigger error message was produced under two conditions: The trigger duplicated an existing trigger name, or the trigger duplicated an existing combination of action and event. Now different messages are produced for the two conditions so as to be more informative. (Bug#10946)

The value returned by a stored function returning a string value was not of the declared character set. (Bug#16211)

FLUSH TABLES followed by a LOCK TABLES statement to lock a log table and a non-log table caused an infinite loop and high CPU use. Now FLUSH TABLES ignores log tables. To flush the log tables, use FLUSH LOGS instead. (Bug#20139)

If a filename was specified for the --log or --log-slow_queries options but the server was logging to tables and not files, the server produced no error message. (Bug#17599)

mysqlcheck tried to check views instead of ignoring them. (Bug#16502)

Long multiple-row INSERT statements could take a very long time for some multi-byte character sets. (Bug#15811)

For mysql, escaping with backslash sometimes did not work. (Bug#20103)

Under certain circumstances, AVG(key_val) returned a value but MAX(key_val) returned an empty set due to incorrect application of MIN()/MAX() optimization. (Bug#20954)

Using aggregate functions in subqueries yielded incorrect results under certain circumstances due to incorrect application of MIN()/MAX() optimization. (Bug#20792)

A query using WHERE column = constant OR column IS NULL did not return consistent results on successive invocations. The column in each part of the WHERE clause could be either the same column, or two different columns, for the effect to be observed. (Bug#21019)

The PASSWORD() function returned invalid results when used in some UNION queries. (Bug#16881)

USE did not refresh database privileges when employed to re-select the current database. (Bug#10979)

A query using WHERE NOT (column < ANY (subquery)) yielded a different result from the same query using the same column and subquery with WHERE (column > ANY (subquery)). (Bug#20975)

A user variable set to a value selected from an unsigned column was stored as a signed value. (Bug#7498)

SELECT statements using GROUP BY against a view could have missing columns in the output when there was a trigger defined on one of the base tables for the view. (Bug#20466)

A SELECT with a subquery that was bound to the outer query over multiple columns returned different results when a constant was used instead of one of the dependant columns. (Bug#18925)

InnoDB: Quoted Unicode identifiers were not handled correctly. This included names of tables, columns, and foreign keys. (Bug#18800)

A stored procedure that created and invoked a prepared statement was not executed when called in a mysqld init-file. (Bug#17843)

Using the extended syntax for TRIM() 鈥� that is, TRIM(... FROM ...) 鈥� in a SELECT statement defining a view caused an invalid syntax error when selecting from the view. (Bug#17526)

Assignments of values to variables of type TEXT were handled incorrectly in stored routines. (Bug#17225)

When performing a GROUP_CONCAT(), the server transformed BLOB columns VARCHAR columns, which could cause erroneous results when using Connector/J and possibly other MySQL APIs. (Bug#16712)

The type of the value returned by the VARIANCE() function varied according to the type of the input value. The function should always return a DOUBLE value. (Bug#10966)

Performing an INSERT on a view that was defined using a SELECT that specified a collation and a column alias caused the server to crash (Bug#21086).

A query of the form shown here caused the server to crash:

SELECT * FROM t1 NATURAL JOIN (
    t2 JOIN (
        t3 NATURAL JOIN t4,
        t5 NATURAL JOIN t6
    )
    ON (t3.id3 = t2.id3 AND t5.id5 = t2.id5)
  );

(Bug#21007)

myisam_ftdump would fail when trying to open a MyISAM index file that you did not have write permissions to access, even though the command would only be reading from the file. (Bug#17122)

REPLACE ... SELECT for a view required the INSERT privilege for tables other than the table being modified. (Bug#20989)

mysqldump sometimes did not select the correct database before trying to dump views from it, resulting in an empty result set that caused mysqldump to die with a segmentation fault. (Bug#21014)

With mixed-format binary logging, INSERT DELAYED statements were logged using statement-based logging, and they did not replicate properly for statements that used values such as UUID(), RAND(), or user-defined variables that require row-based logging. To correct this, the DELAYED handler thread how switches to row-based logging if the logging format is mixed. (Bug#20633, Bug#20649)

Using EXPLAIN PARTITIONS with a UNION query could crash the server. This could occur whether or not the query actually used any partitioned tables. (Bug#20484)

Partition pruning could cause incorrect results from queries, such missing rows, when the partitioning expression relied on a BIGINT UNSIGNED column. (Bug#20257)

The implementation for UNCOMPRESS() did not indicate that it could return NULL, causing the optimizer to do the wrong thing. (Bug#18539)

TIMESTAMPDIFF() examined only the date and ignored the time when the requested difference unit was months or quarters. (Bug#16226)

perror did not properly report NDB error codes. (Bug#16561)

mysqlimport sends a set @@character_set_database=binary statement to the server, but this is not understood by pre-4.1 servers. Now mysqlimport encloses the statement within a /*!40101 ... */ comment so that old servers will ignore it. (Bug#15690)

The character set was not being properly initialized for CAST() with a type like CHAR(2) BINARY, which resulted in incorrect results or even a server crash. (Bug#17903)

For ODBC compatibility, MySQL supports use of WHERE col_name IS NULL for DATE or DATETIME columns that are NOT NULL, to allow column values of '0000-00-00' or '0000-00-00 00:00:00' to be selected. However, this was not working for WHERE clauses in DELETE statements. (Bug#8143)

The --master-data option for mysqldump requires certain privileges, but mysqldump generated a truncated dump file without producing an appropriate error message or exit status if the invoking user did not have those privileges. (Bug#21215)

ALTER VIEW did not retain existing values of attributes that had been originally specified but were not changed in the ALTER VIEW statement. (Bug#21080)

mysql crashed for very long arguments to the connect command. (Bug#21042)

perror crashed on Solaris due to NULL return value of strerror() system call. (Bug#20145)

The query command for mysqltest did not work. (Bug#19890)

For certain queries, the server incorrectly resolved a reference to an aggregate function and crashed. (Bug#20868)

When executing a SELECT with ORDER BY on a view that is constructed from a SELECT statement containing a stored function, the stored function was evaluated too many times. (Bug#19862)

A SELECT that used a subquery in the FROM clause that did not select from a table failed when the subquery was used in a join. (Bug#21002)

Subqueries on INFORMATION_SCHEMA tables could erroneously return an empty result. (Bug#21231)

Issuing a SHOW CREATE FUNCTION or SHOW CREATE PROCEDURE statement without sufficient privileges could crash the mysql client. (Bug#20664)

In a view defined with SQL SECURITY DEFINER, the CURRENT_USER() function returned the invoker, not the definer. (Bug#20570)

DATE_ADD() and DATE_SUB() returned NULL when the result date was on the day '9999-12-31'. (Bug#12356)

For a DATE parameter sent via a MYSQL_TIME data structure, mysql_stmt_execute() zeroed the hour, minute, and second members of the structure rather than treating them as read-only. (Bug#20152)

The DATA DIRECTORY table option did not work for TEMPORARY tables. (Bug#8706)

If the files for an open table were removed at the OS level (external to the server), the server exited with an assertion failure. (Bug#16532)

Some memory leaks in the libmysqld embedded server were corrected. (Bug#16017)

With the auto_increment_increment system variable set larger than 1, if the next generated AUTO_INCREMENT value would be larger than the column's maximum value, the value would be clipped down to that maximum value and inserted, even if the resulting value would not be in the generated sequence. This could cause problems for master-master replication. Now the server clips the value down to the previous value in the sequence, which correctly produces a duplicate-key error if that value already exists in the column. (Bug#20524)

If a table on a slave server had a higher AUTO_INCREMENT counter than the corresponding master table (even though all rows of the two tables were identical), in some cases REPLACE or INSERT ... ON DUPLICATE KEY UPDATE would not replicate properly using statement-based logging. (Different values would be inserted on the master and slave.) (Bug#20188)

mysqlslap did not enable the CLIENT_MULTI_RESULTS flag when connecting, which is necessary for executing stored procedures. (Bug#20365)

When creating a table using CREATE...SELECT and a stored procedure, there would be a mismatch between the binary log and transaction cache which would cause a server crash. (Bug#21039)

When run with the --use-threads option, mysqlimport returned a random exit code. (Bug#21188)

The effect of a stored function or trigger that caused AUTO_INCREMENT values to be generated for multiple tables was not logged properly if statement-based logging was used. Only the first table's value was logged, causing replication to fail. Under mixed logging format, this is dealt with by switching to row-based logging for the function or trigger. For statement-based logging, this remains a problem. (Bug#19630)

Changing the definition of a DECIMAL column with ALTER TABLE caused loss of column values. (Bug#18014)

Under heavy load (executing more than 1024 simultaneous complex queries), a problem in the code that handles internal temporary tables could lead to writing beyond allocated space and memory corruption. Use of more than 1024 simultaneous cursors server wide also could lead to memory corruption. (This applies both to stored procedure and C API cursors.) (Bug#21206)

A race condition during slave server shutdown caused an assert failure. (Bug#20850)

mysqldump produced a malformed dump file when dumping multiple databases that contained views. (Bug#20221)

Partitions were represented internally as the wrong data type, which led in some cases to failures of queries such as SELECT COUNT(*) FROM INFORMATION_SCHEMA.PARTITIONS WHERE PARTITION_NAME = 'partition_name'. (Bug#20340)

Searches against a ZEROFILL column of a partitioned table could fail when the ZEROFILL column was part of the table's partitioning key. (Bug#20733)

In mixed binary logging mode, a temporary switch from statement-based logging to row-based logging occurs when storing a row that uses a function such as UUID() into a temporary table. However, temporary table changes are not written to the binary log under row-based logging, so the row does not exist on the slave. A subsequent select from the temporary table to a non-temporary table using statement-based logging works correctly on the master, but not on the slave where the row does not exist. The fix for this is that replication does not switch back from row-based logging to statement-based logging until there are no temporary tables for the session. (Bug#20499)

Re-executing a stored procedure with a complex stored procedure cursor query could lead to a server crash. (Bug#15217)

Views created from prepared statements inside of stored procedures were created with a definition that included both SQL_CACHE and SQL_NO_CACHE. (Bug#17203)

Updating a column of a FEDERATED table to NULL sometimes failed. (Bug#16494)

Performing INSERT ... SELECT ... JOIN ... USING without qualifying the column names caused ERROR 1052 "column 'x' in field list is ambiguous" even in cases where the column references were unambiguous. (Bug#18080)

Closing of temporary tables failed if binary logging was not enabled. (Bug#20919)

For statements that have a DEFINER clause such as CREATE TRIGGER or CREATE VIEW, long usernames or hostnames could cause a buffer overflow. (Bug#16899)

mysqldump would not dump views that had become invalid because a table named in the view definition had been dropped. Instead, it quit with an error message. Now you can specify the --force option to cause mysqldump to keep going and write a SQL comment containing the view definition to the dump output. (Bug#17371)

InnoDB (Partitioning): Updating an InnoDB table using HASH partitioning with a composite primary key would cause the server to hang. (Bug#20852)

Old partition and subpartition files were not always removed following ALTER TABLE ... REORGANIZE PARTITION statements. (Bug#20770)

Merging multiple partitions having subpartitions into a single partition with subpartitions, or splitting a single partition having subpartitions into multiple partitions with subpartitions, could sometimes crash the server. These issues were associated with a failure reported in the partition_range test. (Bug#20766, Bug#20767, Bug#20893, Bug#21357)

Some queries using ORDER BY ... DESC on subpartitioned tables could crash the server. (Bug#20389)

Referring to a stored function qualified with the name of one database and tables in another database caused a 鈥�table doesn't exist鈥� error. (Bug#18444)

For NDB and possibly InnoDB tables, a BEFORE UPDATE trigger could insert incorrect values. (Bug#18437)

For multiple INSERT DELAYED statements executed in a batch by the delayed-insert handler thread, not all rows were written to the binary log. (Bug#20821)

Triggers on tables in the mysql database caused a server crash. Triggers for tables in this database now are disallowed. (Bug#18005, Bug#18361)

The length of the pattern string prefix for LIKE operations was calculated incorrectly for multi-byte character sets. As a result, the scanned range was wider than necessary if the prefix contained any multi-byte characters, and rows could be missing from the result set. (Bug#16674, Bug#18359)

Very complex SELECT statements could create temporary tables that were too big, but for which the temporary files did not get removed, causing subsequent queries to fail. (Bug#11824)

Multiple-table updates with FEDERATED tables could cause a server crash. (Bug#19773)

On Windows, terminating mysqld with Control-C could result in a crash during shutdown. (Bug#18235)

Renaming a database to itself caused a server crash. (Bug#19392)

For spatial data types, the server formerly returned these as VARSTRING values with a binary collation. Now the server returns spatial values as BLOB values. (Bug#10166)

Using tables from MySQL 4.x in MySQL 5.x, in particular those with VARCHAR fields and using INSERT DELAYED to update data in the table would result in either data corruption or a server crash. (Bug#16611, Bug#16218, Bug#17294)

Using SELECT and a table join while running a concurrent INSERT operation would join incorrect rows. (Bug#14400)

Using SELECT on a corrupt MyISAM table using the dynamic record format could cause a server crash. (Bug#19835)

Checking a MyISAM table (using CHECK TABLE) having a spatial index and only one row would wrongly indicate that the table was corrupted. (Bug#17877)

A Table ... doesn't exist error could occur for statements that called a function defined in another database. (Bug#17199)

SHOW GRANTS FOR CURRENT_USER did not return definer grants when executed in DEFINER context (such as within a stored prodedure defined with SQL SECURITY DEFINER), it returned the invoker grants. (Bug#15298)

Portions of statements related to partitioning were not surrounded by version-specific comments by mysqldump, breaking backwards compatibility for dump files. (Bug#19488)

A DELETE FROM table with no WHERE clause (deleting all rows) running concurrently with INSERT statements on a storage engine with row-level locking (such as NDB) could produce inconsistent results when using statement-based replication. (Bug#19066)

Concatenating the results of multiple constant subselects produced incorrect results. (Bug#16716)

The use of MIN() and MAX() on columns with an index prefix produced incorrect results in some queries. (Bug#18206)

The WITH CHECK OPTION was not enforced when a REPLACE statement was executed against a view. (Bug#19789)

For SELECT ... FOR UPDATE statements that used DISTINCT or GROUP BY over all key parts of a unique index (or primary key), the optimizer unnecessarily created a temporary table, thus losing the linkage to the underlying unique index values. This caused a Result set not updatable error. (The temporary table is unnecessary because under these circumstances the distinct or grouped columns must also be unique.) (Bug#16458)

A buffer overwrite error in Instance Manager caused a crash. (Bug#20622)

Re-execution of a prepared multiple-table DELETE statement that involves a trigger or stored function can result in a server crash. (Bug#19634)

On Windows, corrected a crash stemming from differences in Visual C runtime library routines from POSIX behavior regarding invalid file descriptors. (Bug#18275)

Creation of a view as a join of views or tables could fail if the views or tables are in different databases. (Bug#20482)

Use of MIN() or MAX() with GROUP BY on a ucs2 column could cause a server crash. (Bug#20076)

INSERT INTO ... SELECT ... LIMIT 1 could be slow because the LIMIT was ignored when selecting candidate rows. (Bug#9676)

Queries on tables that were partitioned by KEY and had a VARCHAR column as the partitioning key produced an empty result set. (Bug#20086)

The omission of leading zeros in dates could lead to erroneous results when these were compared with the output of certain date and time functions. (Bug#16377)

An invalid comparison between keys with index prefixes over multi-byte character fields could lead to incorrect result sets if the selected query execution plan used a range scan by an index prefix over a UTF8 character field. This also caused incorrect results under similar circumstances with many other character sets. (Bug#14896)

A prepared statement that altered partitioned table within a stored procedure failed with the error Unknown prepared statement handler. (Bug#17138)

A query selecting records from a single partition of a partitioned table and using ORDER BY ic DESC (where ic represents an indexed column) could cause errors or crash the server. (Bug#20583)

NDB Cluster (Disk Data): On some platforms, ndbd compiled with gcc 4 would crash when attempting to run CREATE LOGFILE GROUP. (Bug#21981)

NDB Cluster: Setting TransactionDeadlockDetectionTimeout to a value greater than 12000 would cause scans to deadlock, time out, fail to release scan records, until the cluster ran out of scan records and stopped processing. (Bug#21800)

NDB Cluster: Data was stored unevenly between partitions due to all BLOB data being placed in partition 0. (Bug#21690)

NDB Cluster: The server provided a non-descriptive error message when encountering a fatally corrupted REDO log. (Bug#21615)

NDB Cluster: A partial rollback could lead to node restart failures. (Bug#21536)

NDB Cluster: The failure of a unique index read due to an invalid schema version could be handled incorrectly in some cases, leading to unpredictable results. (Bug#21384)

NDB Cluster: In a cluster with more than 2 replicas, a manual restart of one of the data nodes could fail and cause the other nodes in its nodegroup to shut down. (Bug#21213)

NDB Cluster: When the redo buffer ran out of space, a Pointer too large error was raised and the cluster could become unusable until restarted with --initial. (Bug#20892)

NDB Cluster: In some situations with a high disk-load, writing of the redo log could hang, causing a crash with the error message GCP STOP detected. (Bug#20904)

NDB Cluster: A vague error message was returned when reading of both schema files occurred during a restart of the cluster. (Bug#20860)

NDB Cluster: The server did not honor the value set for ndb_cache_check_time in the my.cnf file. (Bug#20708)

NDB Cluster: The server failed with a non-descriptive error message when out of data memory. (Bug#18475)

NDB Cluster (Direct APIss): Invoking the MGM API function ndb_mgm_listen_event() caused a memory leak. (Bug#21671)

NDB Cluster: The management client ALL STATUS command could sometimes report the status of some data nodes incorrectly. (Bug#13985)

NDB Cluster (Disk Data): Trying to create a Disk Data table using a nonexistent tablespace or trying to drop a nonexistent data file from a tablespace produced an uninformative error message. (Bug#21751)

NDB Cluster (Disk Data): Errors could occur when dropping a data file during a node local checkpoint. (Bug#21710)

NDB Cluster (Disk Data): Creating a tablespace and log file group, then attempting to restart the cluster without using the --initial option and without having created any Disk Data tables could cause a forced shutdown of the cluster and raise a configuration error. (Bug#21172)

NDB Cluster: Responses to the ALL DUMP 1000 management client command were printed multiple times in the cluster log for each cluster node. (Bug#21044)

A memory leak was found when running ndb_mgm -e "SHOW". (Bug#21670)

NDB Cluster (Direct APIs): The MGM API function ndb_logevent_get_fd() was not actually implemented. (Bug#21129)

NDB Cluster: Restarting a data node while DDL operations were in progress on the cluster could cause other data nodes to fail. This could also lead to mysqld hanging or crashing under some circumstances. (Bug#21017, Bug#21050)

NDB Cluster: A cluster data node could crash when an ordered index became full before the table containing the index was full. (Bug#14935)

NDB Cluster: The repeated creating and dropping of a table would eventually lead to NDB Error 826, Too many tables and attributes ... Insufficient space. (Bug#20847)

NDB Cluster: REPLACE statements did not work correctly on an NDB table having both a primary key and a unique key. In such cases, proper values were not set for columns which were not explicitly referenced in the statement. (Bug#20728)

NDB Cluster: Trying to create or drop a table while a node was restarting caused the node to crash. This is now handled by raising an error. (Bug#18781)

NDB Cluster: A race condition could in some cirumstances following a DROP TABLE. (Bug#20897)

NDB Cluster: Running ndbd --nowait-nodes=id where id was the node ID of a node that was already running would fail with an invalid error message. (Bug#20419)

NDB Cluster: When stopping and restarting multiple data nodes, the last node to be restarted would sometimes hang in Phase 100. (Bug#19645)

NDB Cluster: The DATA_LENGTH and AVG_ROW_LENGTH columns of the INFORMATION_SCHEMA.TABLES table did not report the size of variable-width column values correctly. (Bug#18413)

See Section聽22.2, 鈥淭he INFORMATION_SCHEMA TABLES Table鈥�, for more information.

NDB Cluster: When attempting to restart the cluster following a data import, the cluster would fail during Phase 4 of the restart with Error 2334: Job buffer congestion. (Bug#20774)

NDB Cluster: A node failure during a scan could sometime cause the node to crash when restarting too quickly following the failure. (Bug#20197)

NDB Cluster: It was possible to use port numbers greater than 65535 for ServerPort in the config.ini file. (Bug#19164)

NDB Cluster (Replication): In some cases, a large number of MySQL servers sending requests to the cluster simultaneously could cause the cluster to crash. This could also be triggered by many NDB API clients making simultaneous event subscriptions or unsubscriptions. (Bug#20683)

NDB Cluster (Direct APIs): NdbScanOperation::readTuples() and NdbIndexScanOperation::readTuples() ignored the batch parameter. (Bug#20252)

NDB Cluster: Cluster system status variables were not updated. (Bug#11459)

NDB Cluster (Disk Data): Trying to create Disk Data tables when running the cluster in diskless mode would crash the cluster's data nodes. (Bug#20008)

Note: Disk Data tables are now disabled when running in diskless mode.

NDB Cluster (Disk Data): A data file created on one tablespace could be dropped using ALTER TABLESPACE ... DROP DATAFILE on a different tablespace. (Bug#20053)

NDB Cluster: Truncating a table on one mysqld caused other mysqld processes in the cluster to return ERROR 1412 (HY000): Table definition has changed, please retry transaction on subsequent queries. (Bug#20705)

NDB Cluster: The cluster's data nodes would fail while trying to load data when NoOfFrangmentLogFiles was equal to 1. (Bug#19894)

NDB Cluster: A problem with error handling when ndb_use_exact_count was enabled could lead to incorrect values returned from queries using COUNT(). A warning is now returned in such cases. (Bug#19202)

NDB Cluster: Restarting a failed node could crash the cluster. (Bug#18782)

NDB Cluster (Disk Data): The failure of a CREATE TABLESPACE or CREATE LOGFILE GROUP statement did not revert all changes made prior to the point of failure. (Bug#16341)

NDB Cluster: Creating tables with variable-size columns caused DataMemory to be used but not freed when the tables were dropped. (Bug#20007)

NDB Cluster: Restoring a backup made using ndb_restore failed when the backup had been taken from a cluster whose data memory was full. (Bug#19852)

NDB Cluster: An excessive number of ALTER TABLE operations could cause the cluster to fail with NDB error code 773 (Out of string memory, please modify StringMemory). (Bug#19275)

NDB Cluster: TEXT columns in Cluster tables having both an explicit primary key and a unique key were not correctly updated by REPLACE statements. (Bug#19906)

NDB Cluster: Running out of DataMemory could sometimes crash ndbd and mysqld processes. (Bug#19185)

NDB Cluster (Replication): A node failure could send duplicate events, causing a mysqld replicating tables containing BLOBs to crash.

NDB Cluster (Disk Data): INFORMATION_SCHEMA.FILES records for UNDO files showed incorrect values in the EXTENT_SIZE, FREE_EXTENTS, and TOTAL_EXTENTS columns. (Bug#20073)

NDB Cluster: An internal formatting error caused some management client error messages to be unreadable. (Bug#20016)

NDB Cluster: Running management client commands while mgmd was in the process of disconnecting could cause the management server to fail. (Bug#19932)

NDB Cluster (NDBAPI): Update operations on blobs were not checked for illegal operations.

Note: Read locks with blob update operations are now upgraded from read committed to read shared.

NDB Cluster: The management client ALL STOP command shut down mgmd processes (as well as ndbd processes). (Bug#18966)

NDB Cluster: Renaming of table columns was not supported as fast a ALTER TABLE for NDB tables. (Bug#20456)

NDB Cluster: Under some circumstances, repeated DDL operations on one mysqld could cause failure of a second mysqld attached to the same cluster. (Bug#19770)

NDB Cluster (Replication): One or more of the mysqld processes could fail when subjecting a Cluster replication setup with multiple mysqld processes on both the master and slave clusters to high loads. (Bug#19768)

NDB Cluster: LOAD DATA LOCAL failed to ignore duplicate keys in Cluster tables. (Bug#19496)

NDB Cluster: Repeated CREATE - INSERT - DROP operations tables could in some circumstances cause the MySQL table definition cache to become corrupt, so that some mysqld processes could access table information but others could not. (Bug#18595)

NDB Cluster (Disk Data): Running a large nbumber of scans on Disk Data could cause subsequent scans to perform poorly. (Bug#20334)

NDB Cluster (Disk Data): An issue with disk allocation could sometimes cause a forced shutdown of the cluster when running a mix of memory and Disk Data tables. (Bug#18780)

NDB Cluster: The mgm client command ALL CLUSTERLOG STATISTICS=15; had no effect. (Bug#20336)

NDB Cluster: Under certain conditions, a starting node could miss transactions, leading to inconsistencies between the primary and backup replicas. (Bug#19929)

NDB Cluster: An uncommitted row could sometimes be checkpointed and thus incorrectly included in a backup. (Bug#19928)

NDB Cluster: A DELETE of many rows immediately followed by an INSERT on the same table could cause the ndbd process on the backup replica to crash. (Bug#19293)

NDB Cluster: TRUNCATE TABLE failed to reset the AUTO_INCREMENT counter. (Bug#18864)

NDB Cluster: SELECT ... FOR UPDATE failed to lock the selected rows. (Bug#18184)

NDB Cluster: New mysqld processes were allowed to connect without a restart of the cluster, causing the cluster to crash. (Bug#13266)

NDB Cluster: The failure of a data node when preparing to commit a transaction (that is, while the node's status was CS_PREPARE_TO_COMMIT) could cause the failure of other cluster data nodes. (Bug#20185)

NDB Cluster: Renaming a table in such a way as to move it to a different database failed to move the table's indexes. (Bug#19967)

NDB Cluster: SHOW ENGINE NDB STATUS could sometimes return an incorrect value of 0 for the latest epoch, which could cause problems with synchronising the binlog. (Bug#20142)

NDB Cluster: A CREATE TABLE statement involving foreign key constraints raised an error rather than being silently ignored (see Section聽13.1.8, 鈥�CREATE TABLE Syntax鈥�). (Bug#18483)

This bug affected Cluster in MySQL 5.1 only.

NDB Cluster (Replication): Data definition and data manipulation statements on different tables were not serialised correctly in the binlog. For example, there was no guarantee that a CREATE TABLE statement and an update on a different table would occur in the same order in the binlog as they did on the cluster being replicated. (Bug#18947)

NDB Cluster: Resources for unique indexes on Cluster table columns were incorrectly allocated, so that only one-fourth as many unique indexes as indicated by the value of UniqueHashIndexes could be created. (Bug#19623)

A cast problem caused incorrect results for prepared statements that returned float values when MySQL was compiled with gcc 4.0. (Bug#19694)

Some queries that used ORDER BY and LIMIT performed quickly in MySQL 3.23, but slowly in MySQL 4.x/5.x due to an optimizer problem. (Bug#4981)

mysql_upgrade was missing from binary MySQL distributions. (Bug#18516, Bug#20403, Bug#20556)

It was possible using ALTER EVENT ... RENAME ... to move an event to a database on which the user did not have the EVENT privilege. (Bug#18897)

A number of dependency issues in the RPM bench and test packages caused installation of these packages to fail. (Bug#20078)

Queries using an indexed column as the argument for the MIN() and MAX() functions following an ALTER TABLE .. DISABLE KEYS statement returned Got error 124 from storage engine until ALTER TABLE ... ENABLE KEYS was run on the table. (Bug#20357)

A redundant table map event could be generated in the binary log when there were no actual changes to a table being replicated. In addition, a slave failed to stop when attempting to replicate a table that did not exist on the slave. (Bug#18948)

Multiple calls to a stored procedure that altered a partitioned MyISAM table would cause the server to crash. (Bug#19309)

Adding an index to a partitioned table that had been created using AUTO_INCREMENT = value caused the AUTO_INCREMENT value to be reset. (Bug#19281)

A CREATE TABLE that produced a The PARTITION function returns the wrong type error also caused an Incorrect information in file to be printed to STDERR, and a junk file to be left in the database directory. (Bug#16000)

Nested natural joins worked executed correctly when executed as a non-prepared statement could fail with an Unknown column 'col_name' in 'field list' error when executed as a prepared statement, due to a name resolution problem. (Bug#15355)

The max_length metadata value for columns created from CONCAT() could be incorrect when the collation of an argument differed from the collation of the CONCAT() itself. In some contexts such as UNION, this could lead to truncation of the column contents. (Bug#15962)

The MD5() and SHA() functions treat their arguments as case-sensitive strings. But when they are compared, their arguments were compared as case-insensitive strings, which leads to two function calls with different arguments (and thus different results) compared as being identical. This can lead to a wrong decision made in the range optimizer and thus to an incorrect result set. (Bug#15351)

For BOOLEAN mode full-text searches on non-indexed columns, NULL rows generated by a LEFT JOIN caused incorrect query results. (Bug#14708)

If the general log table reached a large enough file size (27GB), SELECT COUNT(*) on the table caused a server crash. (Bug#17589)

Identifiers could not contain bytes with a value of 255, though that should be allowed as of the identifier-encoding changes made in MySQL 5.1.6. (Bug#12982)

BIT columns in a table could cause joins that use the table to fail. (Bug#18895)

A UNION over more than 128 SELECT statements that use an aggregate function failed. (Bug#18175)

InnoDB unlocked its data directory before committing a transaction, potentially resulting in non-recoverable tables if a server crash occurred before the commit. (Bug#19727)

Multiple-table DELETE statements containing a subquery that selected from one of the tables being modified caused a server crash. (Bug#19225)

With settings of read_buffer_size >= 2G and read_rnd_buffer_size >=2G, LOAD DATA INFILE failed with no error message or caused a server crash for files larger than 2GB. (Bug#12982)

REPLACE statements caused activation of UPDATE triggers, not DELETE and INSERT triggers. (Bug#13479)

The thread for INSERT DELAYED rows was maintaining a separate AUTO_INCREMENT counter, resulting in incorrect values being assigned if DELAYED and non-DELAYED inserts were mixed. (Bug#20195)

mysqldump wrote an extra pair of DROP DATABASE and CREATE DATABASE statements if run with the --add-drop-database option and the database contained views. (Bug#17201)

Shutting down a slave in a replication scenario where temporary tables are in use would cause the slave to produce a core dump. (Bug#19881)

When a statement is executed that does not generate any rows, an extra table map event and associated binrows event would be generated and written to the binary log. (Bug#19995)

File size specifications for InnoDB data files were case sensitive. (Bug#19609)

Compilation on Windows would fail if row based replication was disabled using --without-row-based-replication. (Bug#16837)

InnoDB did not increment the handler_read_prev counter. (Bug#19542)

In the INFORMATION_SCHEMA.FILES table, the INITIAL_SIZE, MAXIMUM_SIZE, and AUTOEXTEND_SIZE columns incorrectly were being stored as VARCHAR rather than BIGINT. (Bug#19544).

For mysqld, Valgrind revealed problems that were corrected: Possible uninitialized data in a string comparison (Bug#20783); memory corruption in replication slaves when switching databases (Bug#19022); syscall write parameter pointing to uninitialized byte (Bug#20579); uninitialized doublewrite memory in InnoDB (Bug#20791).

For ndb_mgmd, Valgrind revealed problems that were corrected: A memory leak (Bug#19318); a dependency on an uninitialized variable (Bug#20333).

An update that used a join of a table to itself and modified the table on both sides of the join reported the table as crashed. (Bug#18036)

SSL connections using yaSSL on OpenBSD could fail. (Bug#19191)

Following a failed attempt to add an index to an ARCHIVE table, it was no longer possible to drop the database in which the table had been created. (Bug#17310)

Using ALTER TABLE ... ENGINE = x, where x was not a storage engine supported by the server, would cause mysqld to crash. (Bug#20397)

Defining a table partitioned by LIST with a single PARTITION ... VALUES IN (NULL) clause could lead to server crashes, particularly with queries having WHERE conditions comparing the partitioning key with a constant. (Bug#19801 / Bug#20268)

Values greater than 2 gigabytes used in the VALUES LESS THAN clause of a table partitioned by RANGE were treated as negative numbers. (Bug#16002)

The fill_help_tables.sql file did not load properly if the ANSI_QUOTES SQL mode was enabled. (Bug#20542)

The fill_help_tables.sql file did not contain a SET NAMES 'utf8' statement to indicate its encoding. This caused problems for some settings of the MySQL character set such as big5. (Bug#20551)

The --default-storage-engine server option did not work. (Bug#20168)

The MySQL server startup script /etc/init.d/mysql (created from mysql.server) is now marked to ensure that the system services ypbind, nscd, ldap, and NTP are started first (if these are configured on the machine). (Bug#18810)

For a reference to a non-existent index in FORCE INDEX, the error message referred to a column, not an index. (Bug#17873)

The EGNINE clause was displayed in the output of SHOW CREATE TABLE for partitioned tables when the SQL mode included no_table_options. (Bug#19695)

ALTER TABLE ... COALESCE PARTITION did not delete the files associated with the partitions that were removed. (Bug#19305)

ALTER TABLE ... REBUILD PARTITION could cause the server to hang or crash. (Bug#19122)

Some yaSSL public function names conflicted with those from OpenSSL, causing conflicts for applications that linked against both OpenSSL and a version of libmysqlclient that was built with yaSSL support. The yaSSL public functions now are renamed to avoid this conflict. (Bug#19575)

CHECK TABLE on a MyISAM table briefly cleared its AUTO_INCREMENT value, while holding only a read lock. Concurrent inserts to that table could use the wrong AUTO_INCREMENT value. CHECK TABLE no longer modifies the AUTO_INCREMENT value. (Bug#19604)

If there is a global read lock, CREATE DATABASE, RENAME DATABASE, and DROP DATABASE could deadlock. (Bug#19815)

EXPLAIN PARTITIONS would produce illegible output in the partitions column if the length of text to be displayed in that column was too long. This could occur when very many partitions were defined for the table, partitions were given very long names, or due to a combination of the two. (Bug#19684)

Trying to execute a query having a WHERE clause using int_col = "string_value" OR int_col IS NULL on a partitioned table whose partitioning or subpartitioning function used the integer column int_col would crash the server. (Bug#19055)

On Linux, libmysqlclient when compiled with yaSSL using the icc compiler had a spurious dependency on C++ libraries. (Bug#20119)

In MySQL 5.1.11, the --with-openssl and --with-yassl options were replaced by --with-ssl. But no message was issued if the old options were given. Now configure produces a message indicating that the new option should be used and exits. (Bug#20002)

Grant table modifications sometimes did not refresh the in-memory tables if the hostname was '' or not specified. (Bug#16297)

Invalid escape sequences in option files caused MySQL programs that read them to abort. (Bug#15328)

Using ALTER TABLE on a subpartitioned table caused the server to crash. (Bug#19067)

For a table having LINEAR HASH subpartitions, the LINEAR keyword did not appear in the SUBPARTITION_METHOD column of the INFORMATION_SCHEMA.PARTITIONS table. (Bug#20161)

Race conditions on certain platforms could cause the Instance Manager to fail to initialize. (Bug#19391)

ALTER TABLE on a table created prior to 5.0.3 would cause table corruption if the ALTER TABLE did one of the following:

(Bug#17001)

An ALTER TABLE operation that does not need to copy data, when executed on a table created prior to MySQL 4.0.25, could result in a server crash for subsequent accesses to the table. (Bug#19192)

The binary log lacked character set information for table name when dropping temporary tables. (Bug#14157)

A B-TREE index on a MEMORY table erroneously reported duplicate entry error for multiple NULL values. (Bug#12873)

Race conditions on certain platforms could cause the Instance Manager to try to restart the same instance multiple times. (Bug#18023)

OPTIMIZE TABLE and REPAIR TABLE yielded incorrect messages or warnings when used on partitioned tables. (Bug#17455)

Selecting data from a MEMORY table with a VARCHAR column and a HASH index over it returned only the first row matched. (Bug#18233)

RPM packages had spurious dependencies on Perl modules and other programs. (Bug#13634)

Incompatible change: The Event Scheduler can now be in one of three states (on, off, or the new suspended state). In addition, due to the fact that SET GLOBAL event_scheduler; now acts in a synchronous rather than asynchronous manner, the Event Scheduler thread can be no longer be activated or deactivated at run time. (Bug#17619)

For more information regarding these changes, see Section聽20.1, 鈥淓vent Scheduler Overview鈥�.

Previously, to build MySQL from source with SSL support enabled, you would invoke configure with either the --with-openssl or --with-yassl option. Those options both have been replaced by the --with-ssl option. By default, --with-ssl causes the bundled yaSSL library to be used. To select OpenSSL instead, give the option as --with-ssl=path, where path is the directory where the OpenSSL header files and libraries are located.

Added the --ssl-verify-server-cert option to MySQL client programs. This option causes the server's Common Name value in its certificate to be verified against the hostname used when connecting to the server, and the connection is rejected if there is a mismatch. Added MYSQL_OPT_SSL_VERIFY_SERVER_CERT option for the mysql_options() C API function to enable this verification. This feature can be used to prevent man-in-the-middle attacks. Verification is disabled by default. (Bug#17208)

Added the ssl_ca, ssl_capath, ssl_cert, ssl_cipher, and ssl_key system variables, which display the values given via the corresponding command options. See Section聽5.8.7.3, 鈥淪SL Command Options鈥�. (Bug#19606)

NDB Cluster: The limit of 2048 ordered indexes per cluster has been lifted. There is now no upper limit on the number of ordered indexes (including AUTO_INCREMENT columns) that may be used. (Bug#14509)

Added the log_queries_not_using_indexes system variable. (Bug#19616)

Added the --angel-pid-file option to mysqlmanager for specifying the file in which the angel process records its process ID when mysqlmanager runs in daemon mode. (Bug#14106)

The ENABLE KEYS and DISABLE KEYS clauses for the ALTER TABLE statement are now supported for partitioned tables. (Bug#19502)

It is now possible to use NEW.var_name values within triggers as INOUT parameters to stored procedures. (Bug#14635)

The default for the innodb_thread_concurrency system variable was changed to 8. (Bug#15868)

mysql_explain_log (a third-party program) is no longer included in MySQL distributions.

Security fix: An SQL-injection security hole has been found in multi-byte encoding processing. The bug was in the server, incorrectly parsing the string escaped with the mysql_real_escape_string() C API function. (CVE-2006-2753, Bug#8378)

This vulnerability was discovered and reported by Josh Berkus <josh@postgresql.org> and Tom Lane <tgl@sss.pgh.pa.us> as part of the inter-project security collaboration of the OSDB consortium. For more information about SQL injection, please see the following text.

Discussion: An SQL-injection security hole has been found in multi-byte encoding processing. An SQL-injection security hole can include a situation whereby when a user supplied data to be inserted into a database, the user might inject SQL statements into the data that the server will execute. With regards to this vulnerability, when character set unaware-escaping is used (for example, addslashes() in PHP), it is possible to bypass the escaping in some multi-byte character sets (for example, SJIS, BIG5 and GBK). As a result, a function such as addslashes() is not able to prevent SQL-injection attacks. It is impossible to fix this on the server side. The best solution is for applications to use character set-aware escaping offered by a function such mysql_real_escape_string().

However, a bug was detected in how the MySQL server parses the output of mysql_real_escape_string(). As a result, even when the character set-aware function mysql_real_escape_string() was used, SQL injection was possible. This bug has been fixed.

Workarounds: If you are unable to upgrade MySQL to a version that includes the fix for the bug in mysql_real_escape_string() parsing, but run MySQL 5.0.1 or higher, you can use the NO_BACKSLASH_ESCAPES SQL mode as a workaround. (This mode was introduced in MySQL 5.0.1.) NO_BACKSLASH_ESCAPES enables an SQL standard compatibility mode, where backslash is not considered a special character. The result will be that queries will fail.

To set this mode for the current connection, enter the following SQL statement:

SET sql_mode='NO_BACKSLASH_ESCAPES';

You can also set the mode globally for all clients:

SET GLOBAL sql_mode='NO_BACKSLASH_ESCAPES';

This SQL mode also can be enabled automatically when the server starts by using the command-line option --sql-mode=NO_BACKSLASH_ESCAPES or by setting sql-mode=NO_BACKSLASH_ESCAPES in the server option file (for example, my.cnf or my.ini, depending on your system).

The patch for Bug#8303 broke the fix for Bug#8378 and was undone. (In string literals with an escape character (\) followed by a multi-byte character that has a second byte of (\), the literal was not interpreted correctly. The next byte now is escaped, not the entire multi-byte character. This means it a strict reverse of the mysql_real_escape_string() function.)

The client libraries had not been compiled for position-indpendent code on Solaris-SPARC and AMD x86_64 platforms. (Bug#13159, Bug#14202, Bug#18091)

Altering a VARCHAR column in a MyISAM table to make it longer could cause corruption of the following column. (Bug#19386)

A CREATE TABLE statement that created a table from a materialized view did not inherit default values from the underlying table. (Bug#19089)

NDB Cluster: A Cluster whose storage nodes were installed from the MySQL-ndb-storage-* RPMs could not perform CREATE or ALTER operations that made use of non-default character sets or collations. (Bug#14918)

NDB Cluster: mysqld processes did not always detect cluster shutdown, leading to issues with CLuster replication and schema distribution. (Bug#19395)

NDB Cluster: SELECT MIN(unique_column) from a Cluster table with user-defined partitioning crashed the server. (Bug#18730)

Premature optimization of nested subqueries in the FROM clause that refer to aggregate functions could lead to incorrect results. (Bug#19077)

For dates with 4-digit year parts less than 200, an implicit conversion to add a century was applied for date arithmetic performed with DATE_ADD(), DATE_SUB(), + INTERVAL, and - INTERVAL. (For example, DATE_ADD('0050-01-01 00:00:00', INTERVAL 0 SECOND) became '2050-01-01 00:00:00'.) Now these operations return NULL rather than an incorrect non-NULL value. (Bug#18997)

BLOB or TEXT arguments to or values returned from stored functions were not copied properly if too long and could become garbled. (Bug#18587)

Simultaneous scheduled events whose actions conflicted with one another could crash the server. (Bug#16428)

In was not possible to invoke a stored routine containing dynamic SQL from a scheduled event. (Bug#19264)

NDB Cluster: Running ALL START in the NDB management client or restarting multiple nodes simultaneously could under some circumstances cause the cluster to crash. (Bug#19930)

The result from CONV() is a string, but was not always treated the same way as a string when converted to a real value for an arithmetic operation. (Bug#13975)

CREATE TABLE ... SELECT ... statements that used a stored function explicitly or implicitly (through a view) resulted in a Table not locked error. (Bug#12472, Bug#15137)

Within a trigger, SET used the SQL mode of the invoking statement, not the mode in effect at trigger creation time. (Bug#6951)

The server no longer uses a signal handler for signal 0 because it could cause a crash on some platforms. (Bug#15869)

The embedded server crashed with row-based replication enabled. (Bug#18518)

Display better error message for ALTER TABLE operations that will result in duplicate keys due to AUTO_INCREMENT resequencing. (Bug#14573)

The Data_free column in the output of SHOW TABLE STATUS always displayed 0 for partitioned tables. (Bug#19501)

Adding an index to a table created using partitioning by KEY and the MEMORY storage engine caused the server to crash. (Bug#19140)

When creating a table using CREATE TABLE ... PARTITION BY ... SELECT ..., the partitioning clause was ignored. (Bug#19062)

ALTER TABLE ENGINE=... failed when used to change a MySQL Cluster table having no explicit primary key to use a different storage engine. (Bug#19010)

Note: As a consequence of this fix, SHOW CREATE TABLE no longer displays auto-partitioning information for NDBCluster tables.

NDB Cluster (NDBAPI): On big-endian platforms, NdbOperation::write_attr() did not update 32-bit fields correctly. (Bug#19537)

NDB Cluster: Using 鈥�stale鈥� mysqld .FRM files could cause a newly-restored cluster to fail. This situation could arise when restarting a MySQL Cluster using the --intial option while leaving connected mysqld processes running. (Bug#16875)

NDB Cluster (Replication): Memory was not freed after some ALTER TABLE operations, which could cause mysqld processes to crash. (Bug#19885)

NDB Cluster (NDBAPI): The Ndb::dropEventOperation() method failed to clean up all objects used, which could cause memory leaks to occur. (Bug#17610)

NDB Cluster: Data node failures could cause excessive CPU usage by ndb_mgmd. (Bug#13987)

NDB Cluster: TRUNCATE failed on tables having BLOB or TEXT columns with the error Lock wait timeout exceeded. This affected both in-memory and Disk Data tables. (Bug#19201)

Revised memory allocation for local objects within stored functions and triggers to avoid memory leak for repeated function or trigger invocation. (Bug#17260)

EXPLAIN ... SELECT INTO caused the client to hang. (Bug#15463)

Symlinking .mysql_history to /dev/null to suppress statement history saving by mysql did not work. (mysql deleted the symlink and recreated .mysql_history as a regular file, and then wrote history to it.) (Bug#16803)

The basedir and tmpdir system variables could not be accessed via @@var_name syntax. (Bug#1039)

Corrected several problems with the treatment of the --log-error option by mysqld_safe. These problems were manifest as differences from mysqld in error log handling.

In addition, some argument quoting problems were corrected. (Bug#6061)

Returning the value of a system variable from a stored function caused a server crash. (Bug#18037)

Use of uninitialized user variables in a subquery in the FROM clause resulted in bad entries in the binary log. (Bug#19136)

IS_USED_LOCK() could return an incorrect connection identifier. (Bug#16501)

Concurrent reading and writing of privilege structures could crash the server. (Bug#16372)

Security enhancement: Added the global max_prepared_stmt_count system variable to limit the total number of prepared statements in the server. This limits the potential for denial-of-service attacks based on running the server out of memory by preparing huge numbers of statements. The current number of prepared statements is available through the prepared_stmt_count system variable. (Bug#16365)