Important Change: Partitioning: Security Fix: It was possible, by creating a partitioned table using the DATA DIRECTORY and INDEX DIRECTORY options to gain privileges on other tables having the same name as the partitioned table. As a result of this fix, any table-level DATA DIRECTORY or INDEX DIRECTORY options are now ignored for partitioned tables. (Bug#32091, CVE-2007-5970)

See also Bug#29325, Bug#32111

Incompatible Change: In MySQL 5.1.6, when log tables were implemented, the default log destination for the general query and slow query log was TABLE. This default has been changed to FILE, which is compatible with MySQL 5.0, but incompatible with earlier releases of MySQL 5.1 from 5.1.6 to 5.1.20. If you are upgrading from MySQL 5.0 to this release, no logging option changes should be necessary. However, if you are upgrading from 5.1.6 through 5.1.20 to this release and were using TABLE logging, use the --log-output=TABLE option explicitly to preserve your server's table-logging behavior.

In MySQL 5.1.x, this bug was addressed twice because it turned out that the default was set in two places, only one of which was fixed the first time. (Bug#29993)

Incompatible Change

The parser accepted statements that contained /* ... */ that were not properly closed with */, such as SELECT 1 /* + 2. Statements that contain unclosed /*-comments now are rejected with a syntax error.

This fix has the potential to cause incompatibilities. Because of Bug#26302, which caused the trailing */ to be truncated from comments in views, stored routines, triggers, and events, it is possible that objects of those types may have been stored with definitions that now will be rejected as syntactically invalid. Such objects should be dropped and re-created so that their definitions do not contain truncated comments. (Bug#28779)

MySQL Cluster: The following improvements have been made in the ndb_size.pl utility:

Support for a --socket option was also added.

For more information, see Section 15.9.15, “ndb_size.pl — NDBCluster Size Requirement Estimator”. (Bug#28683, Bug#28253)

MySQL Cluster: Mapping of NDB error codes to MySQL storage engine error codes has been improved. (Bug#28423)

MySQL Cluster: The output from the cluster management client showing the progress of data node starts has been improved. (Bug#23354)

Partitioning: Error messages for partitioning syntax errors have been made more descriptive. (Bug#29368)

Replication: Replication of the following now switches to row-based logging in MIXED mode, and generates a warning in STATEMENT mode:

See Section 5.2.4.3, “Mixed Binary Logging (MBL) Format”, for more information. (Bug#12092, Bug#28086, Bug#30244)

mysqltest now has a change_user command to change the user for the current connection. (It invokes the mysql_change_user() C API function.) (Bug#31608)

mysql-test-run.pl now allows a suite name prefix to be specified in command-line arguments that name test cases. The test name syntax now is [suite_name.]test_name[.suffix]. For example, mysql-test-run.pl binlog.mytest runs the mytest.test test in the binlog test suite. (Bug#31400)

The --event-scheduler option without a value disabled the event scheduler. Now it enables the event scheduler. (Bug#31332)

mysqldump produces a -- Dump completed on DATE comment at the end of the dump if --comments is given. The date causes dump files for identical data take at different times to appear to be different. The new options --dump-date and --skip-dump-date control whether the date is added to the comment. --skip-dump-date suppresses date printing. The default is --dump-date (include the date in the comment). (Bug#31077)

Server parser performance was improved for expression parsing by lowering the number of state transitions and reductions needed. (Bug#30625)

Server parser performance was improved for identifier lists, expression lists, and UDF expression lists. (Bug#30333)

Server parser performance was improved for boolean expressions. (Bug#30237)

The LAST_EXECUTED column of the INFORMATION_SCHEMA.EVENTS table now indicates when the event started executing rather than when it finished executing. As a result, the ENDS column is never less than LAST_EXECUTED. (Bug#29830)

The mysql_odbc_escape_string() C API function has been removed. It has multi-byte character escaping issues, doesn't honor the NO_BACKSLASH_ESCAPES SQL mode and is not needed anymore by Connector/ODBC as of 3.51.17. (Bug#29592)

If a MyISAM table is created with no DATA DIRECTORY option, the .MYD file is created in the database directory. By default, if MyISAM finds an existing .MYD file in this case, it overwrites it. The same applies to .MYI files for tables created with no INDEX DIRECTORY option. To suppress this behavior, start the server with the new --keep_files_on_create option, in which case MyISAM will not overwrite existing files and returns an error instead. (Bug#29325)

The default value of the connect_timeout system variable was increased from 5 to 10 seconds. This might help in cases where clients frequently encounter errors of the form Lost connection to MySQL server at 'XXX', system error: errno. (Bug#28359)

MySQL now can be compiled with gcc 4.2.x. There was a problem involving a conflict with the min() and max() macros in my_global.h. (Bug#28184)

The script is now able to be used with multiple databases; lists of databases and tables can be excluded from analysis.

If selecting from INFORMATION_SCHEMA fails, the script now attempts to fall back to SHOW TABLES.

The report title has been amended to cover cases where more than one database is being analyzed.

A --real_table_name option has been added; this designates a table to handle unique index size calculations.

The database name is now an optional parameter, the exclusion of which causes all databases to be examined.

Schema name information has been added to index table calculations.

Security Fix: Using RENAME TABLE against a table with explicit DATA DIRECTORY and INDEX DIRECTORY options can be used to overwrite system table information by replacing the symbolic link points. the file to which the symlink points.

MySQL will now return an error when the file to which the symlink points already exists. (Bug#32111, CVE-2007-5969)

Security Fix: ALTER VIEW retained the original DEFINER value, even when altered by another user, which could allow that user to gain the access rights of the view. Now ALTER VIEW is allowed only to the original definer or users with the SUPER privilege. (Bug#29908)

Security Fix: When using a FEDERATED table, the local server can be forced to crash if the remote server returns a result with fewer columns than expected. (Bug#29801)

Important Change: Incompatible Change: A number of problems existed in the implementation of MERGE tables that could cause problems. The problems are summarized below:

The fix introduces the following changes in behavior:

(Bug#26377, Bug#26379, Bug#26867, Bug#25038, Bug#25700, Bug#30275, Bug#19627, Bug#27660, Bug#30273)

Incompatible Change: Inserting a row with a NULL value for a DATETIME column results in a CSV file that the storage engine cannot read.

All CSV tables now need to be defined with each column marked as NOT NULL. An error is raised if you try to create a CSV table with columns that are not defined with NOT NULL. (Bug#31473, Bug#32817)

Incompatible Change: SET PASSWORD statements now cause an implicit commit, and thus are prohibited within stored functions and triggers. (Bug#30904)

Incompatible Change: The mysql_install_db script could fail to locate some components (including resolveip) during execution if the --basedir option was specified on the command-line or within the my.cnf file. This was due to a conflict when comparing the compiled-in values and the supplied values.

The --source-install command-line option to the script has been removed and replaced with the --srcdir option. mysql_install_db now locates components either using the compiled-in options, the --basedir option or --srcdir option. (Bug#30759)

Incompatible Change: Within a stored routine, it is no longer allowable to declare a cursor for a SHOW statement. This happened to work in some instances, but is no longer supported. (Bug#29223)

Incompatible Change: GRANT and REVOKE statements now cause an implicit commit, and thus are prohibited within stored functions and triggers. (Bug#21975, Bug#21422, Bug#17244)

Incompatible Change: It was possible for option files to be read twice at program startup, if some of the standard option file locations turned out to be the same directory. Now duplicates are removed from the list of files to be read.

Also, users could not override system-wide settings using ~/.my.cnf because SYSCONFDIR/my.cnf was read last. The latter file now is read earlier so that ~/.my.cnf can override system-wide settings. (Bug#20748)

Important Change: MySQL Cluster: AUTO_INCREMENT columns had the following problems when used in NDB tables:

As part of this fix, the behavior of ndb_autoincrement_prefetch_sz has changed. Setting this to less than 32 no longer has any effect on prefetching within statements (where IDs are now always obtained in batches of 32 or more), but only between statements. The default value for this variable has also changed, and is now 1. (Bug#25176, Bug#31956, Bug#32055)

Partitioning: Important Note: An apostrophe or single quote character (') used in the DATA DIRECTORY, INDEX DIRECTORY, or COMMENT for a PARTITION clause caused the server to crash. When used as part of a CREATE TABLE statement, the crash was immediate. When used in an ALTER TABLE statement, the crash did not occur until trying to perform a SELECT or DML statement on the table. In either case, the server could not be completely restarted until the .FRM file corresponding to the newly created or altered table was deleted.

(Bug#30695)

Important Note: The RENAME DATABASE statement was removed and replaced with ALTER DATABASE db_name UPGRADE DATA DIRECTORY NAME. The RENAME DATABASE statement was intended for upgrading database directory names to the encoding format used in 5.1 for representing identifiers in the filesystem (see Section 7.2.3, “Mapping of Identifiers to Filenames”). However, the statement was found to be dangerous because it could result in loss of database contents. See Section 11.1.18, “RENAME DATABASE Syntax” and Section 11.1.1, “ALTER DATABASE Syntax”. (Bug#17565, Bug#21741, Bug#28360)

Replication: MySQL Cluster: Row-based replication from or to a big-endian machine where the table used the NDB storage engine failed, if the same table on the other machine was either non-NDB or the other machine was little-endian. (Bug#29549, Bug#30790)

See also Bug#24231, Bug#30024, Bug#30133, Bug#30134

MySQL Cluster: An improperly reset internal signal was observed as a hang when using events in the NDB API but could result in various errors. (Bug#33206)

MySQL Cluster: Incorrectly handled parameters could lead to a crash in the Transaction Coordinator during a node failure, causing other data nodes to fail. (Bug#33168)

MySQL Cluster: A memory leak occurred if a subscription start request was received by the subscription manager before the node making the request was fully connected to the cluster. (Bug#32652)

MySQL Cluster: A local checkpoint could sometimes be started before the previous LCP was restorable from a global checkpoint. (Bug#32519)

MySQL Cluster: High numbers of API nodes on a slow or congested network could cause connection negotiation to time out prematurely, leading to the following issues:

(Bug#32359)

MySQL Cluster: The failure of a master node could lead to subsequent failures in local checkpointing. (Bug#32160)

MySQL Cluster: An error with an if statement in sql/ha_ndbcluster.cc could potentially lead to an infinite loop in case of failure when working with AUTO_INCREMENT columns in NDB tables. (Bug#31810)

MySQL Cluster: The NDB storage engine code was not safe for strict-alias optimization in gcc 4.2.1. (Bug#31761)

MySQL Cluster: It was possible in some cases for a node group to be “lost” due to missed local checkpoints following a system restart. (Bug#31525)

MySQL Cluster: A query against a table with TEXT or BLOB columns that would return more than a certain amount of data failed with Got error 4350 'Transaction already aborted' from NDBCLUSTER. (Bug#31482)

This regression was introduced by Bug#29102

MySQL Cluster: NDB tables having names containing non-alphanumeric characters (such as “ $ ”) were not discovered correctly. (Bug#31470)

MySQL Cluster: A node failure during a local checkpoint could lead to a subsequent failure of the cluster during a system restart. (Bug#31257)

MySQL Cluster: When handling BLOB columns, the addition of read locks to the lock queue was not handled correctly. (Bug#30764)

MySQL Cluster: Discovery of NDB tables did not work correctly with INFORMATION_SCHEMA. (Bug#30667)

MySQL Cluster: A filesystem close operation could fail during a node or system restart. (Bug#30646)

MySQL Cluster: Transaction timeouts were not handled well in some circumstances, leading to excessive number of transactions being aborted unnecessarily. (Bug#30379)

MySQL Cluster: Attempting to restore a backup made on a cluster host using one endian to a machine using the other endian could cause the cluster to fail. (Bug#29674)

MySQL Cluster: Log event requests to ndb_mgmd could time out, causing it to fail. (Bug#29621)

MySQL Cluster: In some cases, the cluster managment server logged entries multiple times following a restart of mgmd. (Bug#29565)

MySQL Cluster: ndb_mgm --help did not display any information about the -a option. (Bug#29509)

MySQL Cluster: An interpreted program of sufficient size and complexity could cause all cluster data nodes to shut down due to buffer overruns. (Bug#29390)

MySQL Cluster: ndb_size.pl failed on tables with FLOAT columns whose definitions included commas (for example, FLOAT(6,2)). (Bug#29228)

MySQL Cluster: The error message for NDB error code 275 (Out of transaction records for complete phase) was missing. (Bug#29139)

MySQL Cluster: Reads on BLOB columns were not locked when they needed to be to guarantee consistency. (Bug#29102)

See also Bug#31482

MySQL Cluster: A query using joins between several large tables and requiring unique index lookups failed to complete, eventually returning Uknown Error after a very long period of time. This occurred due to inadequate handling of instances where the Transaction Coordinator ran out of TransactionBufferMemory, when the cluster should have returned NDB error code 4012 (Request ndbd time-out). (Bug#28804)

MySQL Cluster: There was a short interval during the startup process prior to the beginning of heartbeat detection such that, were an API or management node to reboot or a network failure to occur, data nodes could not detect this, with the result that there could be a lingering connection. (Bug#28445)

MySQL Cluster: The description of the --print option provided in the output from ndb_restore --help was incorrect. (Bug#27683)

MySQL Cluster: Restoring a backup made on a cluster host using one endian to a machine using the other endian failed for BLOB and DATETIME columns. (Bug#27543, Bug#30024)

MySQL Cluster: An invalid subselect on an NDB table could cause mysqld to crash. (Bug#27494)

MySQL Cluster: An attempt to perform a SELECT ... FROM INFORMATION_SCHEMA.TABLES whose result included information about NDB tables for which the user had no privileges crashed the MySQL Server on which the query was performed. (Bug#26793)

MySQL Cluster: Performing DELETE operations after a data node had been shut down could lead to inconsistent data following a restart of the node. (Bug#26450)

MySQL Cluster: UPDATE IGNORE could sometimes fail on NDB tables due to the use of unitialized data when checking for duplicate keys to be ignored. (Bug#25817)

MySQL Cluster: The cluster log was formatted inconsistently and contained extraneous newline characters. (Bug#25064)

MySQL Cluster: A restart of the cluster failed when more than 1 REDO phase was in use. (Bug#22696)

MySQL 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.

This improves on an initial fix for this issue made in MySQL 5.1.13. (Bug#21072)

MySQL Cluster: An insufficiently descriptive and potentially misleading Error 4006 (Connect failure - out of connection objects...) was produced when either of the following two conditions occurred:

Separate error messages are now generated for each of these two cases. (Bug#11313)

Partitioning: Replication: Replication of partitioned tables using the InnoDB storage engine failed with binlog-format=ROW or binlog-format=MIXED. (Bug#28430)

Partitioning: It was possible to partition a table to which a foreign key referred. (Bug#32948)

Partitioning: A query of the form SELECT col1 FROM table GROUP BY (SELECT col2 FROM table LIMIT 1); against a partitioned table having a SET column crashed the server. (Bug#32772)

Partitioning: SHOW CREATE TABLE misreported the value of AUTO_INCREMENT for partitioned tables using either of the InnoDB or ARCHIVE storage engines. (Bug#32247)

Partitioning: Selecting from INFORMATION_SCHEMA.PARTITIONS while partition management statements (for example, ALTER TABLE ... ADD PARTITION) were executing caused the server to crash. (Bug#32178)

Partitioning: Repeated updates of a table that was partitioned by KEY on a TIMESTAMP column eventually crashed the server. (Bug#32067)

Partitioning: Changing the storage engine used by a table having subpartitions led to a server crash. (Bug#31893)

Partitioning: ORDER BY ... DESC did not always work correctly when selecting from partitioned tables. (Bug#31890)

See also Bug#31001

Partitioning: Selecting from a table partitioned by KEY on a VARCHAR column whose size was greater than 65530 caused the server to crash. (Bug#31705)

Partitioning: INSERT DELAYED into a partitioned table crashed the server. (Bug#31201)

Partitioning: Using ALTER TABLE to partition an existing table having an AUTO_INCREMENT column could crash the server. (Bug#30878)

This regression was introduced by Bug#27405

Partitioning: ALTER TABLE ... COALESCE PARTITION on a table partitioned by [LINEAR] HASH or [LINEAR] KEY caused the server to crash. (Bug#30822)

Partitioning: LIKE queries on tables partitioned by KEY and using third-party storage engines could return incomplete results. (Bug#30480)

See also Bug#29320, Bug#29493, Bug#30563

Partitioning: It was not possible to insert the greatest possible value for a given data type into a partitioned table. For example, consider a table defined as shown here:

CREATE TABLE t (c BIGINT UNSIGNED)
    PARTITION BY RANGE(c) (
      PARTITION p0 VALUES LESS THAN MAXVALUE
    );

The largest possible value for a BIGINT UNSIGNED column is 18446744073709551615, but the statement INSERT INTO t VALUES (18446744073709551615); would fail, even though the same statement succeeded were t not a partitioned table.

In other words, MAXVALUE was treated as being equal to the greatest possible value, rather than as a least upper bound. (Bug#29258)

Replication: When dropping a database containing a stored procedure while using row-cased replication, the delete of the stored procedure from the mysql.proc table was recorded in the binary log following the DROP DATABASE statement. To correct this issue, DROP DATABASE now uses statement-based replication. (Bug#32435)

Replication: It was possible for the name of the relay log file to exceed the amount of memory reserved for it, possibly leading to a crash of the server. (Bug#31836)

See also Bug#28597

Replication: Corruption of log events caused the server to crash on 64-bit Linux systems having 4 GB of memory or more. (Bug#31793)

Replication: Trying to replicate an update of a row that was missing on the slave led to a failure on the slave. (Bug#31702)

Replication: Table names were displayed as binary “garbage” characters in slave error messages. The issue was observed on 64-bit Windows but may have effected other platforms. (Bug#30854)

Replication: One thread could read uninitialized memory from the stack of another thread. This issue was only known to occur in a mysqld process acting as both a master and a slave. (Bug#30752)

Replication: It was possible to set SQL_SLAVE_SKIP_COUNTER such that the slave would jump into the middle of a transaction. This fix improves on one made for this bug in MySQL 5.1.20; the previous fix insured that the slave could not be made to jump into the middle of an event group, but the slave failed to recognize that BEGIN, COMMIT, and ROLLBACK statements could begin or end an event group. (Bug#28618)

See also Bug#12691

Replication: Due a previous change in how the default name and location of the binlog file were determined, replication failed following some upgrades. (Bug#28597)

See also Bug#31836

This regression was introduced by Bug#20166

Replication: Stored procedures having BIT parameters were not replicated correctly. (Bug#26199)

Replication: Issuing SHOW SLAVE STATUS as mysqld was shutting down could cause a crash. (Bug#26000)

Replication: If a temporary error occured inside an event group on an event that was not the first event of the group, the slave could get caught in an endless loop because the retry counter was reset whenever an event was executed successfully. (Bug#24860)

See also Bug#12691, Bug#23171

Replication: An UPDATE statement using a stored function that modified a non-transactional table was not logged if it failed. This caused the copy of the non-transactional table on the master have a row that the copy on the slave did not. (Bug#23333)

See also Bug#12713

Replication: A replication slave sometimes failed to reconnect because it was unable to run SHOW SLAVE HOSTS. It was not necessary to run this statement on slaves (since the master should track connection IDs), and the execution of this statement by slaves was removed. (Bug#21132)

See also Bug#13963, Bug#21869

Replication: A replication slave sometimes stopped for changes that were idempotent (that is, such changes should have been considered “safe”), even though it should have simply noted that the change was already done, and continued operation. (Bug#19958)

Cluster Replication: Memory was mistakenly freed for NdbBlob objects when adding an index while replicating the cluster, which could cause mysqld to crash. (Bug#33142)

See also Bug#18106

Cluster Replication: Under certain conditions, the slave stopped processing relay logs. This resulted in the logs never being cleared and the slave eventually running out of disk space. (Bug#31958)

Cluster Replication: A node failure during replication could lead to buckets out of order; now active subscribers are checked for, rather than empty buckets. (Bug#31701)

Cluster Replication: When the master mysqld crashed or was restarted, no LOST_EVENTS entry was made in the binlog. (Bug#31484)

See also Bug#21494

Cluster Replication: Incorrect handling of INSERT plus DELETE operations with regard to local checkpoints caused data node failures in multi-master replication setups. (Bug#30914)

Cluster Replication: An issue with the mysql.ndb_apply_status table could cause NDB schema autodiscovery to fail in certain rare circumstances. (Bug#20872)

Cluster API: A call to CHECK_TIMEDOUT_RET() in mgmapi.cpp should have been a call to DBUG_CHECK_TIMEDOUT_RET(). (Bug#30681)

Cluster API: An Ndb object in the NDB API was initialized with insufficient parallellism

The fix for Bug#11230 and Bug#26215 introduced a significant input-parsing slowdown for the mysql client. This has been corrected. (Bug#33057)

SHOW EVENTS and selecting from the INFORMATION_SCHEMA.EVENTS table failed if the current database was INFORMATION_SCHEMA. (Bug#32775)

Use of the cp932 character set with CAST() in an ORDER BY clause could cause a server crash. (Bug#32726)

Specifying a non-existent column for an INSERT DELAYED statement caused a server crash rather than producing an error. (Bug#32676)

Use of CLIENT_MULTI_QUERIES caused libmysqld to crash. (Bug#32624)

The INTERVAL() function incorrectly handled NULL values in the value list. (Bug#32560)

Use of a NULL-returning GROUP BY expression in conjunction with WITH ROLLUP could cause a server crash. (Bug#32558)

ORDER BY UpdateXML(...) caused the server to crash in queries where UpdateXML() returned NULL. (Bug#32557)

For FLUSH TABLES WITH READ LOCK, the server failed to properly detect write-locked tables when running with low-priority updates, resulting in a crash or deadlock. (Bug#32528)

The rules for valid column names were being applied differently for base tables and views. (Bug#32496)

Sending several KILL QUERY statements to target a connection running SELECT SLEEP() could freeze the server. (Bug#32436)

ssl-cipher values in option files were not being read by libmysqlclient. (Bug#32429)

If a global read lock acquired with FLUSH TABLES WITH READ LOCK was in effect, executing ALTER TABLE could cause a server crash. (Bug#32395)

Assigning a 65,536-byte string to a TEXT column (which can hold a maximum of 65,535 bytes) resulted in truncation without a warning. Now a truncation warning is generated. (Bug#32282)

Some uses of user variables in a query could result in a server crash. (Bug#32260)

Various test program cleanups were made: 1) mytest and libmysqltest were removed. 2) bug25714 displays an error message when invoked with incorrect arguments or the --help option. 3) mysql_client_test exits cleanly with a proper error status. (Bug#32221)

The default grant tables on Windows contained information for host production.mysql.com, which should not be there. (Bug#32219)

Under certain conditions, the presence of a GROUP BY clause could cause an ORDER BY clause to be ignored. (Bug#32202)

For comparisons of the form date_col OP datetime_const (where OP is =, <, >, <=, or >=), the comparison is done using DATETIME values, per the fix for Bug#27590. However that fix caused any index on date_col not to be used and compromised performance. Now the index is used again. (Bug#32198)

DATETIME arguments specified in numeric form were treated by DATE_ADD() as DATE values. (Bug#32180)

Killing a statement could lead to a race condition in the server. (Bug#32148)

InnoDB does not support SPATIAL indexes, but could crash when asked to handle one. Now an error is returned. (Bug#32125)

The server crashed on optimizations involving a join of INT and MEDIUMINT columns and a system variable in the WHERE clause. (Bug#32103)

mysql-test-run.pl used the --user option when starting mysqld, which produces warnings if the current user is not root. Now --user is added only for root. (Bug#32078)

mysqlslap was missing from the MySQL 5.1.22 Linux RPM packages. (Bug#32077)

With lower_case_table_names set, CREATE TABLE LIKE was treated differently by libmysqld than by the non-embedded server. (Bug#32063)

Within a subquery, UNION was handled differently than at the top level, which could result in incorrect results or a server crash. (Bug#32036, Bug#32051)

On 64-bit platforms, assignments of values to enumeration-valued storage engine-specific system variables were not validated and could result in unexpected values. (Bug#32034)

A DELETE statement with a subquery in the WHERE clause would sometimes ignore an error during subquery evaluation and proceed with the delete operation. (Bug#32030)

Using dates in the range '0000-00-01' to '0000-00-99' range in the WHERE clause could result in an incorrect result set. (These dates are not in the supported range for DATE, but different results for a given query could occur depending on position of records containing the dates within a table.) (Bug#32021)

User-defined functions are not loaded if the server is started with the --skip-grant-tables option, but the server did not properly handle this case and issued an Out of memory error message instead. (Bug#32020)

If a user-defined function was used in a SELECT statement, and an error occurred during UDF initialization, the error did not terminate execution of the SELECT, but rather was converted to a warning. (Bug#32007)

HOUR(), MINUTE(), and SECOND() could return non-zero values for DATE arguments. (Bug#31990)

Changing the SQL mode to cause dates with “zero” parts to be considered invalid (such as '1000-00-00') could result in indexed and non-indexed searches returning different results for a column that contained such dates. (Bug#31928)

The server used unnecessarily large amounts of memory when user variables were used as an argument to CONCAT() or CONCAT_WS(). (Bug#31898)

In debug builds, testing the result of an IN subquery against NULL caused an assertion failure. (Bug#31884)

SHOW CREATE TRIGGER caused a server crash. (Bug#31866)

The server crashed after insertion of a negative value into an AUTO_INCREMENT column of an InnoDB table. (Bug#31860)

For libmysqld applications, handling of mysql_change_user() calls left some pointers improperly updated, leading to server crashes. (Bug#31850)

Using ORDER BY leads to the wrong result when using the ARCHIVE on a table with a BLOB when the table cache is full. The table may also be reported as crashed after the query has completed, even though the table data was intact. (Bug#31833)

Comparison results for BETWEEN were different from those for operators like < and > for DATETIME-like values with trailing extra characters such as '2007-10-01 00:00:00 GMT-6'. BETWEEN treated the values as DATETIME, whereas the other operators performed a binary-string comparison. Now they all uniformly use a DATETIME comparison, but generate warnings for values with trailing garbage. (Bug#31800)

With ONLY_FULL_GROUP_BY SQL mode enabled, queries such as SELECT a FROM t1 HAVING COUNT(*)>2 were not being rejected as they should have been. (Bug#31794)

The server could crash during filesort for ORDER BY based on expressions with INET_NTOA() or OCT() if those functions returned NULL. (Bug#31758)

For a fatal error during filesort in find_all_keys(), the error was returned without the necessary handler uninitialization, causing an assertion failure. Fixed by uninitializing the handler before returning the error. (Bug#31742)

The examined-rows count was not incremented for const queries. (Bug#31700)

The server crashed if a thread was killed while locking the general_log table at the beginning of statement processing. (Bug#31692)

The mysql_change_user() C API function was subject to buffer overflow. (Bug#31669)

For SELECT ... INTO OUTFILE, if the ENCLOSED BY string is empty and the FIELDS TERMINATED BY string started with a special character (one of n, t, r, b, 0, Z, or N), every occurrence of the character within field values would be duplicated. (Bug#31663)

SHOW COLUMNS and DESCRIBE displayed null as the column type for a view with no valid definer. This caused mysqldump to produce a non-reloadable dump file for the view. (Bug#31662)

The mysqlbug script did not include the correct values of CFLAGS and CXXFLAGS that were used to configure the distribution. (Bug#31644)

Queries that include a comparison of an INFORMATION_SCHEMA table column to NULL caused a server crash. (Bug#31633)

EXPLAIN EXTENDED for SELECT from INFORMATION_SCHEMA tables caused an assertion failure. (Bug#31630)

ucs2 does not work as a client character set, but attempts to use it as such were not rejected. Now character_set_client cannot be set to ucs2. This also affects statements such as SET NAMES and SET CHARACTER SET. (Bug#31615)

A buffer used when setting variables was not dimensioned to accommodate the trailing '\0' byte, so a single-byte buffer overrun was possible. (Bug#31588)

HAVING could treat lettercase of table aliases incorrectly if lower_case_table_names was enabled. (Bug#31562)

Spurious duplicate-key errors could occur for multiple-row inserts into an InnoDB table that activate a trigger. (Bug#31540)

Using ALTER EVENT to rename a disabled event caused it to become enabled. (Bug#31539)

The fix for Bug#24989 introduced a problem such that a NULL thread handler could be used during a rollback operation. This problem is unlikely to be seen in practice. (Bug#31517)

The length of the result from IFNULL() could be calculated incorrectly because the sign of the result was not taken into account. (Bug#31471)

Queries that used the ref access method or index-based subquery execution over indexes that have DECIMAL columns could fail with an error Column col_name cannot be null. (Bug#31450)

InnoDB now tracks locking and use of tables by MySQL only after a table has been successfully locked on behalf of a transaction. Previously, the locked flag was set and the table in-use counter was updated before checking whether the lock on the table succeeded. A subsequent failure in obtaining a lock on the table led to an inconsistent state as the table was neither locked nor in use. (Bug#31444)

SELECT 1 REGEX NULL caused an assertion failure for debug servers. (Bug#31440)

The UpdateXML() function did not check for the validity of all its arguments; in some cases, this could lead to a crash of the server. (Bug#31438)

The mysql_change_user() C API function caused advisory locks (obtained with GET_LOCK()) to malfunction. (Bug#31418)

NDB libraries and include files were missing from some binary tar file distributions. (Bug#31414)

Executing RENAME while tables were open for use with HANDLER statements could cause a server crash. (Bug#31409)

mysql-test-run.pl tried to create files in a directory where it could not be expected to have write permission. mysqltest created .reject files in a directory other than the one where test results go. (Bug#31398)

For a table that had been opened with HANDLER and marked for reopening after being closed with FLUSH TABLES, DROP TABLE did not properly discard the handler. (Bug#31397)

Automatically allocated memory for string options associated with a plugin was not freed if the plugin did not get installed. (Bug#31382)

INFORMATION_SCHEMA.TABLES was returning incorrect information. (Bug#31381)

DROP USER caused an increase in memory usage. (Bug#31347)

For InnoDB tables with READ COMMITTED isolation level, UPDATE statements skipped rows locked by another transaction, rather than waiting for the locks to be released. (Bug#31310)

For an almost-full MyISAM table, an insert that failed could leave the table in a corrupt state. (Bug#31305)

myisamchk --unpack could corrupt a table that when unpacked has static (fixed-length) row format. (Bug#31277)

CONVERT(val, DATETIME) would fail on invalid input, but processing was not aborted for the WHERE clause, leading to a server crash. (Bug#31253)

Allocation of an insufficiently large group-by buffer following creation of a temporary table could lead to a server crash. (Bug#31249)

Use of DECIMAL(n, n) ZEROFILL in GROUP_CONCAT() could cause a server crash. (Bug#31227)

When a TIMESTAMP with a non-zero time part was converted to a DATE value, no warning was generated. This caused index lookups to assume that this is a valid conversion and was returning rows that match a comparison between a TIMESTAMP value and a DATE keypart. Now a warning is generated so that TIMESTAMP with a non-zero time part will not match DATE values. (Bug#31221)

WIth small values of myisam_sort_buffer_size, REPAIR TABLE for MyISAM tables could cause a server crash. (Bug#31174)

Use of the @@hostname system variable in inserts in mysql_system_tables_data.sql did not replicate. The workaround is to select its value into a user variable (which does replicate) and insert that. (Bug#31167)

If MAKETIME() returned NULL when used in an ORDER BY that was evaluated using filesort, a server crash could result. (Bug#31160)

LAST_INSERT_ID() execution could be handled improperly in subqueries. (Bug#31157)

An assertion designed to detect a bug in the ROLLUP implementation would incorrectly be triggered when used in a subquery context with non-cacheable statements. (Bug#31156)

Selecting spatial types in a UNION could cause a server crash. (Bug#31155)

Use of GROUP_CONCAT(DISTINCT bit_column) caused an assertion failure. (Bug#31154)

The server crashed in the parser when running out of memory. Memory handling in the parser has been improved to gracefully return an error when out-of-memory conditions occur in the parser. (Bug#31153)

mysqldump failed to handle databases containing a ‘-’ character in the name. (Bug#31113)

Starting the server using --read-only and with the Event Scheduler enabled caused it to crash.

(Bug#31111)

GROUP BY NULL WITH ROLLUP could cause a server crash. (Bug#31095)

A rule to prefer filesort over an indexed ORDER BY when accessing all rows of a table was being used even if a LIMIT clause was present. (Bug#31094)

REGEXP operations could cause a server crash for character sets such as ucs2. Now the arguments are converted to utf8 if possible, to allow correct results to be produced if the resulting strings contain only 8-bit characters. (Bug#31081)

Expressions of the form WHERE col NOT IN (col, ...), where the same column was named both times, could cause a server crash in the optimizer. (Bug#31075)

Internal conversion routines could fail for several multi-byte character sets (big5, cp932, euckr, gb2312, sjis) for empty strings or during evaluation of SOUNDS LIKE. (Bug#31069, Bug#31070)

Using ORDER BY with ARCHIVE tables caused a server crash. (Bug#31036)

A server crash could occur when a non-DETERMINISTIC stored function was used in a GROUP BY clause. (Bug#31035)

The MOD() function and the % operator crashed the server for a divisor less than 1 with a very long fractional part. (Bug#31019)

Transactions were committed prematurely when LOCK TABLE and SET AUTOCOMMIT=OFF were used together. (Bug#30996)

On Windows, the pthread_mutex_trylock() implementation was incorrect. (Bug#30992)

A character set introducer followed by a hexadecimal or bit-value literal did not check its argument and could return an ill-formed result for invalid input. (Bug#30986)

CHAR(str USING charset) did not check its argument and could return an ill-formed result for invalid input. (Bug#30982)

The result from CHAR(str USING ucs2) did not add a leading 0x00 byte for input strings with an odd number of bytes. (Bug#30981)

A cluster restart could sometimes fail due to an issue with table IDs. (Bug#30975)

The GeomFromText() function could cause a server crash if the first argument was NULL or the empty string. (Bug#30955)

MAKEDATE() incorrectly moved year values in the 100-200 range into the 1970-2069 range. (This is legitimate for 00-99, but three-digit years should be used unchanged.) (Bug#30951)

When invoked with constant arguments, STR_TO_DATE() could use a cached value for the format string and return incorrect results. (Bug#30942)

GROUP_CONCAT() returned ',' rather than an empty string when the argument column contained only empty strings. (Bug#30897)

For MEMORY tables, lookups for NULL values in BTREE indexes could return incorrect results. (Bug#30885)

A server crash could occur if a stored function that contained a DROP TEMPORARY TABLE statement was invoked by a CREATE TEMPORARY TABLE statement that created a table of the same name. (Bug#30882)

Calling NAME_CONST() with non-constant arguments triggered an assertion failure. Non-constant arguments are now disallowed. (Bug#30832)

For a spatial column with a regular (non-SPATIAL) index, queries failed if the optimizer tried to use the index. (Bug#30825)

Values for the --tc-heuristic-recover option incorrectly were treated as values for the --myisam-stats-method option. (Bug#30821)

INFORMATION_SCHEMA.SCHEMATA was returning incorrect information. (Bug#30795)

Improper calculation of CASE expression results could lead to value truncation. (Bug#30782)

On Windows, the pthread_mutex_trylock() implementation was incorrect. One symptom was that invalidating the query cache could cause a server crash. (Bug#30768)

User-supplied names foreign key names might not be set to the right key, leading to foreign keys with no name. (Bug#30747)

Under some circumstances, CREATE TABLE ... SELECT could crash the server or incorrectly report that the table row size was too large. (Bug#30736)

Using the MIN() or MAX() function to select one part of a multi-part key could cause a crash when the function result was NULL. (Bug#30715)

The embedded server did not properly check column-level privileges. (Bug#30710)

INFORMATION_SCHEMA.VIEWS.VIEW_DEFINITION was incorrect for views that were defined to select from other INFORMATION_SCHEMA tables. (Bug#30689)

Issuing an ALTER SERVER statement to update the settings for a FEDERATED server would cause the mysqld to crash. (Bug#30671)

The optimizer could ignore ORDER BY in cases when the result set is ordered by filesort, resulting in rows being returned in incorrect order. (Bug#30666)

A different execution plan was displayed for EXPLAIN than would actually have been used for the SELECT because the test of sort keys for ORDER BY did not consider keys mentioned in IGNORE KEYS FOR ORDER BY. (Bug#30665)

On Windows, LIMIT arguments greater than 2^32 did not work correctly. (Bug#30639)

MyISAM tables could not exceed 4294967295 (2^32 - 1) rows on Windows. (Bug#30638)

A failed HANDLER ... READ operation could leave the table in a locked state. (Bug#30632)

mysql-test-run.pl could not run mysqld with root privileges. (Bug#30630)

The mysqld_safe script contained a syntax error. (Bug#30624)

The optimization that uses a unique index to remove GROUP BY did not ensure that the index was actually used, thus violating the ORDER BY that is implied by GROUP BY. (Bug#30596)

SHOW STATUS LIKE 'Ssl_cipher_list' from a MySQL client connected via SSL returned an empty string rather than a list of available ciphers. (Bug#30593)

For MEMORY tables, DELETE statements that remove rows based on an index read could fail to remove all matching rows. (Bug#30590)

Using GROUP BY on an expression of the form timestamp_col DIV number caused a server crash due to incorrect calculation of number of decimals. (Bug#30587)

Executing a SELECT COUNT(*) query on an InnoDB table partitioned by KEY that used a DOUBLE column as the partitioning key caused the server to crash. (Bug#30583)

The options available to the CHECK TABLE statement were also allowed in OPTIMIZE TABLE and ANALYZE TABLE statements, but caused corruption during their execution. These options were never supported for the these statements, and an error is now raised if you try to apply these options to these statements. (Bug#30495)

A self-referencing trigger on a partitioned table caused the server to crash instead of failing with an error. (Bug#30484)

The mysql_change_user() C API function did not correctly reset the character set variables to the values they had just after initially connecting. (Bug#30472)

When expanding a * in a USING or NATURAL join, the check for table access for both tables in the join was done using only the grant information of the first table. (Bug#30468)

When casting a string value to an integer, cases where the input string contained a decimal point and was long enough to overrun the unsigned long long type were not handled correctly. The position of the decimal point was not taken into account which resulted in miscalculated numbers and incorrect truncation to appropriate SQL data type limits. (Bug#30453)

Versions of mysqldump from MySQL 4.1 or higher tried to use START TRANSACTION WITH CONSISTENT SNAPSHOT if the --single-transaction and --master-data options were given, even with servers older than 4.1 that do not support consistent snapshots. (Bug#30444)

Issuing a DELETE statement having both an ORDER BY clause and a LIMIT clause could cause mysqld to crash. (Bug#30385)

The Last_query_cost status variable value can be computed accurately only for simple “flat” queries, not complex queries such as those with subqueries or UNION. However, the value was not consistently being set to 0 for complex queries. (Bug#30377)

Queries that had a GROUP BY clause and selected COUNT(DISTINCT bit_column) returned incorrect results. (Bug#30324)

Some valid euc-kr characters having the second byte in the ranges [0x41..0x5A] and [0x61..0x7A] were rejected. (Bug#30315)

When loading a dynamic plugin on FreeBSD, the plugin would fail to load. This was due to a build error where the required symbols would be not exported correctly. (Bug#30296)

Setting certain values on a table using a spatial index could cause the server to crash. (Bug#30286)

The query cache does not support retrieval of statements for which column level access control applies, but the server was still caching such statements, thus wasting memory. (Bug#30269)

Using DISTINCT or GROUP BY on a BIT column in a SELECT statement caused the column to be cast internally as an integer, with incorrect results being returned from the query. (Bug#30245)

Multiple-table DELETE statements could delete rows from the wrong table. (Bug#30234)

GROUP BY on BIT columns produced incorrect results. (Bug#30219)

Short-format mysql commands embedded within /*! ... */ comments were parsed incorrectly by mysql, which discarded the rest of the comment including the terminating */ characters. The result was a malformed (unclosed) comment. Now mysql does not discard the */ characters. (Bug#30164)

When mysqldump wrote DROP DATABASE statements within version-specific comments, it included the terminating semicolon in the wrong place, causing following statements to fail when the dump file was reloaded. (Bug#30126)

Some INFORMATION_SCHEMA tables are intended for internal use, but could be accessed by using SHOW statements. (Bug#30079)

On some 64-bit systems, inserting the largest negative value into a BIGINT column resulted in incorrect data. (Bug#30069)

mysqlslap did not properly handle multiple result sets from stored procedures. (Bug#29985)

Specifying the --without-geometry option for configure caused server compilation to fail. (Bug#29972)

Statements within stored procedures ignored the value of the low_priority_updates system variable. (Bug#29963)

See also Bug#26162

With auto-reconnect enabled, row fetching for a prepared statement could crash after reconnect occurred because loss of the statement handler was not accounted for. (Bug#29948)

mysqldump --skip-events --all-databases dumped data from the mysqld.event table, and when restoring from this dump, events were created in spite of the --skip-events option. (Bug#29938)

When mysqlslap was given a query to execute from a file via a --query=file_name option, it executed the query one too many times. (Bug#29803)

configure did not find nss on some Linux platforms. (Bug#29658)

It was possible when creating a partitioned table using CREATE TABLE ... SELECT to refer in the PARTITION BY clause to columns in the table being selected from, which could cause the server to crash. An example of such a statement is:

CREATE TABLE t1 (b INT)   
PARTITION BY RANGE(t2.b) ( 
    PARTITION p1 VALUES LESS THAN (10),
    PARTITION p2 VALUES LESS THAN (20)
)   SELECT * FROM t2;

The fix is to disallow references in PARTITION BY clauses to columns not in the table being created. (Bug#29444)

If a view used a function in its SELECT statement, the columns from the view were not inserted into the INFORMATION_SCHEMA.COLUMNS table. (Bug#29408)

The mysql client program now ignores Unicode byte order mark (BOM) characters at the beginning of input files. Previously, it read them and sent them to the server, resulting in a syntax error.

Presence of a BOM does not cause mysql to change its default character set. To do that, invoke mysql with an option such as --default-character-set=utf8. (Bug#29323)

For transactional tables, an error during a multiple-table DELETE statement did not roll back the statement. (Bug#29136)

The log and log_slow_queries system variables were displayed by SHOW VARIABLES but could not be accessed in expressions as @@log and @@log_slow_queries. Also, attempting to set them with SET produced an incorrect Unknown system variable message. Now these variables are treated as synonyms for general_log and slow_query_log, which means that they can be accessed in expressions and their values can be changed with SET. (Bug#29131)

SHOW VARIABLES did not display the relay_log, relay_log_index, or relay_log_info_file system variables. (Bug#28893)

Killing an SSL connection on platforms where MySQL is compiled with -DSIGNAL_WITH_VIO_CLOSE (Windows, Mac OS X, and some others) could crash the server. (Bug#28812)

SHOW VARIABLES did not correctly display the value of the thread_handling system variable. (Bug#28785)

On Windows, mysql_upgrade created temporary files in C:\ and did not clean them up. (Bug#28774)

Index hints specified in view definitions were ignored when using the view to select from the base table. (Bug#28702)

Views do not have indexes, so index hints do not apply. Use of index hints when selecting from a view is now disallowed. (Bug#28701)

After changing the SQL mode to a restrictive value that would make already-inserted dates in a column be considered invalid, searches returned different results depending on whether the column was indexed. (Bug#28687)

A SELECT in one connection could be blocked by INSERT ... ON DUPLICATE KEY UPDATE in another connection even when low_priority_updates is set. (Bug#28587)

mysql_upgrade could run binaries dynamically linked against incorrect versions of shared libraries. (Bug#28560)

The result from CHAR() was incorrectly assumed in some contexts to return a single-byte result. (Bug#28550)

mysqldump reversed the event name and program name in one of its error messages. (Bug#28535)

If a LIMIT clause was present, the server could fail to consider indexes that could be used for ORDER BY or GROUP BY. (Bug#28404)

The parser confused user-defined function (UDF) and stored function creation for CREATE FUNCTION and required that there be a default database when creating UDFs, although there is no such requirement. (Bug#28318, Bug#29816)

Fast-mutex locking was not thread-safe and optimization-safe on some platforms, which could cause program failures such as out-of-memory errors. (Bug#28284)

The result of a comparison between VARBINARY and BINARY columns differed depending on whether the VARBINARY column was indexed. (Bug#28076)

The metadata in some MYSQL_FIELD members could be incorrect when a temporary table was used to evaluate a query. (Bug#27990)

Partition pruning was not used for queries having <= or >= conditions in the WHERE clause on a table using TO_DAYS() in the partitioning expression. (Bug#27927)

mysqlbinlog produced incorrectly formatted DATETIME and TIMESTAMP values. (Bug#27894)

Failure to log to the general_log or slow_log log tables were not logged to the error log at all or were logged incorrectly. (Bug#27858)

comp_err created files with permissions such that they might be inaccessible during make install operations. (Bug#27789)

SHOW COLUMNS returned NULL instead of the empty string for the Default value of columns that had no default specified. (Bug#27747)

It was possible to create a view having a column whose name consisted of an empty string or space characters only. (Bug#27695)

See also Bug#31202

With recent versions of DBD::mysql, mysqlhotcopy generated table names that were doubly qualified with the database name. (Bug#27694)

The anonymous accounts were not being created during MySQL installation. (Bug#27692)

Some SHOW statements and INFORMATION_SCHEMA queries could expose information not allowed by the user's access privileges. (Bug#27629)

ALTER TABLE tbl_name ROW_FORMAT=format_type did not cause the table to be rebuilt. (Bug#27610)

Some character mappings in the ascii.xml file were incorrect. (Bug#27562)

Some queries using the NAME_CONST() function failed to return either a result or an error to the client, causing it to hang. This was due to the fact that there was no check to insure that both arguments to this function were constant expressions. (Bug#27545, Bug#32559)

With the read_only system variable enabled, CREATE DATABASE and DROP DATABASE were allowed to users who did not have the SUPER privilege. (Bug#27440)

For an event with an ON COMPLETION value of PRESERVE, an ALTER EVENT statement that specified no ON COMPLETION option caused the value to become NOT PRESERVE. (Bug#27407)

MySQL failed to generate or retrieve an AUTO_INCREMENT primary key for InnoDB tables with user-defined partitioning. (Bug#27405)

Changes to the sql_mode system variable were not tracked by INSERT DELAYED. (Bug#27358)

A SELECT with more than 31 nested dependent subqueries returned an incorrect result. (Bug#27352)

The ExtractValue() and UpdateXML() functions performed extremely slowly for large amounts of XML data (greater than 64 KB). These functions now execute approximately 2000 times faster than previously. (Bug#27287)

Several functions and operators returned an incorrect result type (string) when given DATE parameters: COALESCE(), IF(), IFNULL(), LEAST(), GREATEST(), CASE. These now aggregate DATE (or DATETIME) parameters to produce a DATE (or DATETIME result. In addition, the result type of the STR_TO_DATE() function is now DATETIME by default. (Bug#27216)

On WIndows, writes to the debug log were using freopen() instead of fflush(), resulting in slower performance. (Bug#27099)

For a table that used different full-text parsers for different FULLTEXT indexes, SHOW CREATE TABLE displayed the first parser name for all of them. (Bug#27040)

STR_TO_DATE() displayed an error message that referred to STR_TO_TIME(). (Bug#27014)

Symbolic links on Windows could fail to work. (Bug#26811)

mysqld sometimes miscalculated the number of digits required when storing a floating-point number in a CHAR column. This caused the value to be truncated, or (when using a debug build) caused the server to crash. (Bug#26788)

See also Bug#12860

LOAD DATA INFILE ran very slowly when reading large files into partitioned tables. (Bug#26527)

Using HANDLER to open a table having a storage engine not supported by HANDLER properly returned an error, but also improperly prevented the table from being dropped by other connections. (Bug#25856)

For a prepared statement stmt, changing the default database following PREPARE stmt but before EXECUTE stmt caused stmt to be recorded incorrectly in the binary log. (Bug#25843)

CREATE TABLE LIKE did not work when the source table was an INFORMATION_SCHEMA table. (Bug#25629)

Threads that were calculating the estimated number of records for a range scan did not respond to the KILL statement. That is, if a range join type is possible (even if not selected by the optimizer as a join type of choice and thus not shown by EXPLAIN), the query in the statistics state (shown by the SHOW PROCESSLIST) did not respond to the KILL statement. (Bug#25421)

For InnoDB tables, CREATE TABLE a AS SELECT * FROM A would fail. (Bug#25164)

For mysql --show-warnings, warnings were in some cases not displayed. (Bug#25146)

The returns column of the mysql.proc table was CHAR(64), which is not long enough to store long data types such as ENUM types. The column has been changed to LONGBLOB and a warning is generated if truncation occurs when storing a row into the proc table. (Bug#24923)

If the expected precision of an arithmetic expression exceeded the maximum precision supported by MySQL, the precision of the result was reduced by an unpredictable or arbitrary amount, rather than to the maximum precision. In some cases, exceeding the maximum supported precision could also lead to a crash of the server. (Bug#24907)

A CREATE TRIGGER statement could cause a deadlock or server crash if it referred to a table for which a table lock had been acquired with LOCK TABLES. (Bug#23713)

For storage engines that do not redefine handler::index_next_same() and are capable of indexes, statements that include a WHERE clause might select incorrect data. (Bug#22351)

The parser treated the INTERVAL() function incorrectly, leading to situations where syntax errors could result depending on which side of an arithmetic operator the function appeared. (Bug#22312)

Entries in the general query log were truncated at 1000 characters. (Bug#21557)

A memory leak occurred when CREATE TEMPORARY TABLE .. SELECT was invoked from a stored function that in turn was called from CREATE TABLE ... SELECT. (Bug#21136)

It was possible to execute CREATE TABLE t1 ... SELECT ... FROM t2 with the CREATE privilege for t1 and SELECT privilege for t2, even in the absence of the INSERT privilege for t1. (Bug#20901)

Worked around an icc problem with an incorrect machine instruction being generated in the context of software pre-fetching after a subroutine got in-lined. (Upgrading to icc 10.0.026 makes the workaround unnecessary.) (Bug#20803)

If a column selected by a view referred to a stored function, the data type reported for the column in INFORMATION_SCHEMA.COLUMNS could be incorrect. (Bug#20550)

The mysql_change_user() C API function changed the value of the SQL_BIG_SELECTS session variable. (Bug#20023)

Hostnames sometimes were treated as case sensitive in account-management statements (CREATE USER, GRANT, REVOKE, and so forth). (Bug#19828)

Issuing an SQL KILL of the active connection caused an error on Mac OS X. (Bug#19723)

The readline library has been updated to version 5.2. This addresses issues in the mysql client where history and editing within the client would fail to work as expected. (Bug#18431)

The -lmtmalloc library was removed from the output of mysql_config on Solaris, as it caused problems when building DBD::mysql (and possibly other applications) on that platform that tried to use dlopen() to access the client library. (Bug#18322)

The Aborted_clients status variable was incremented twice if a client exited without calling mysql_close(). (Bug#16918)

Clients were ignoring the TCP/IP port number specified as the default port via the --with-tcp-port configuration option. (Bug#15327)

Parameters of type DATETIME or DATE in stored procedures were silently converted to VARBINARY. (Bug#13675)

Values of types REAL ZEROFILL, DOUBLE ZEROFILL, FLOAT ZEROFILL, were not zero-filled when converted to a character representation in the C prepared statement API. (Bug#11589)

Performing a full text search on a table could cause a crash on a 64-bit platforms with certain characteristics. Searches that were known to cause a crash with certain datasets included numerical values and strings where the match string included data enclosed in single or double quotes. (Bug#11392)

mysql stripped comments from statements sent to the server. Now the --comments or --skip-comments option can be used to control whether to retain or strip comments. The default is --skip-comments. (Bug#11230, Bug#26215)

Several buffer-size system variables were either being handled incorrectly for large values (for settings larger than 4GB, they were truncated to values less than 4GB without a warning), or were limited unnecessarily to 4GB even on 64-bit systems. The following changes were made:

In addition, settings for read_buffer_size and read_rnd_buffer_size are limited to 2GB on all platforms. Larger values are truncated to 2GB with a warning. (Bug#5731, Bug#29419, Bug#29446)

Executing DISABLE KEYS and ENABLE KEYS on a non-empty table would cause the size of the index file for the table to grow considerable. This was because the DISABLE KEYS operation would only mark the existing index, without deleting the index blocks. The ENABLE KEYS operation would re-create the index, adding new blocks, while the previous index blocks would remain. Existing indexes are now dropped and recreated when the ENABLE KEYS statement is executed. (Bug#4692)

There were no more transaction records in the transaction coordinator

Replicating from a master table to a slave table where the size of a CHAR or VARCHAR column was a different size would cause mysqld to crash. For more information on replicating with different column definitions, see Section 14.3.1.20, “Replication with Differing Tables on Master and Slave”.

Grant table checks failed in libmysqld. (Bug #XXX)

There is a new innodb_autoinc_lock_mode system variable to configure the locking behavior that InnoDB uses for generating auto-increment values. The default behavior now is slightly different from before, which involves a minor incompatibility for multiple-row inserts that specify an explicit value for the auto-increment column in some but not all rows. See Section 12.5.6.3, “How AUTO_INCREMENT Handling Works in InnoDB”.

MySQL Cluster: Backups of TIMESTAMP columns made with ndb_restore on a MySQL Cluster using data nodes hosts of one endian could not be used to restore the cluster's data to data node hosts of the other endian. (Bug#30134)

MySQL Cluster: (Replication): Multi-master replication setups did not handle --log-slave-updates correctly. (Bug#30017)

Row-based replication from a pre-5.1.22 MySQL Server to a MySQL 5.1.22 was unstable due to an uninitialized variable. (Bug#31076)

For an InnoDB table if a SELECT was ordered by the primary key and also had a WHERE field = value clause on a different field that was indexed, a DESC order instruction would be ignored. (Bug#31001)

mysql_install_db could fail to find its message file. (Bug#30678)

Memory corruption occurred for some queries with a top-level OR operation in the WHERE condition if they contained equality predicates and other sargable predicates in disjunctive parts of the condition. (Bug#30396)

CONNECTION_ID() always returned 0 for the embedded server (libmysqld). (Bug#30389)

The server created temporary tables for filesort operations in the working directory, not in the directory specified by the tmpdir system variable. (Bug#30287)

Using KILL QUERY or KILL CONNECTION to kill a SELECT statement caused a server crash if the query cache was enabled. (Bug#30201)

mysqldump from the MySQL 5.1.21 distribution could not be used to create a dump from a MySQL 5.1.20 or older server. (Bug#30123)

Under some circumstances, a UDF initialization function could be passed incorrect argument lengths. (Bug#29804)

Operations that used the time zone replicated the time zone only for successful operations, but did not replicate the time zone for errors that need to know it. (Bug#29536)

When using a combination of HANDLER... READ and DELETE on a table, MySQL continued to open new copies of the table every time, leading to an exhaustion of file descriptors. (Bug#29474)

This regression was introduced by Bug#21587

The mysql_list_fields() C API function incorrectly set MYSQL_FIELD::decimals for some view columns. (Bug#29306)

Tables using the InnoDB storage engine incremented AUTO_INCREMENT values incorrectly with ON DUPLICATE KEY UPDATE. (Bug#28781)

Non-range queries of the form SELECT ... FROM ... WHERE keypart1=constant, ..., keypartN=constant ORDER BY ... FOR UPDATE sometimes were unnecessarily blocked waiting for a lock if another transaction was using SELECT ... FOR UPDATE on the same table. (Bug#28570)

On Windows, symbols for yaSSL and taocrypt were missing from mysqlclient.lib, resulting in unresolved symbol errors for clients linked against that library. (Bug#27861)

Read lock requests that were blocked by a pending write lock request were not allowed to proceed if the statement requesting the write lock was killed. (Bug#21281)

Incompatible Change: In MySQL 5.1.6, when log tables were implemented, the default log destination for the general query and slow query log was TABLE. This default has been changed to FILE, which is compatible with MySQL 5.0, but incompatible with earlier releases of MySQL 5.1 from 5.1.6 to 5.1.20. If you are upgrading from MySQL 5.0 to this release, no logging option changes should be necessary. However, if you are upgrading from 5.1.6 through 5.1.20 to this release and were using TABLE logging, use the --log-output=TABLE option explicitly to preserve your server's table-logging behavior.

In MySQL 5.1.x, this bug was addressed twice because it turned out that the default was set in two places, only one of which was fixed the first time. (Bug#29993)

Incompatible Change: On Windows only, the mysqld-nt has been removed from this release and all future releases. The mysqld server now includes named-pipe support as standard, and you do not have to use the mysqld-nt version to enable named-pipe support.

Several programs now accept --debug-check and --debug-info options: mysql, mysqladmin, mysqlbinlog, mysqlcheck, mysqldump, mysqlimport, mysqlshow, mysqlslap, mysqltest, mysql_upgrade. (Note: mysql and mysqltest already accepted --debug-info.) --debug-check prints debugging information at program exit. --debug-info is similar but also prints memory and CPU usage statistics. This patch also corrects a problem for mysql that --debug-info did not display statistics at exit time. (Bug#30127)

The --syslog option that was introduced in 5.1.20 for mysqld_safe (to send error output to syslog) did not work correctly: Error output was buffered and not logged immediately. This has been corrected. In addition, some feature changes were made:

(Bug#29992)

Transaction support in the FEDERATED storage engine has been disabled due to issues with multiple active transactions and sessions on the same FEDERATED table. (Bug#29875)

Previously, prepared statements processed using PREPARE and EXECUTE were not subject to caching in the query cache if they contained any ? parameter markers. This limitation has been lifted. (Bug#29318)

It is now possible to set long_query_time in microseconds or to 0. Setting this value to 0 causes all queries to be recorded in the slow query log.

Currently, fractional values can be used only when logging to files. We plan to provide this functionality for logging to tables when time-related data types are enhanced to support microsecond resolution. (Bug#25412)

The SQL thread on a slave now is always allowed to enter InnoDB even if this would exceed the limit imposed by the innodb_thread_concurrency system variable. In cases of high load on the slave server (when innodb_thread_concurrency is reached), this change helps the slave stay more up to date with the master; in the previous behavior, the SQL thread was competing for resources with all client threads active on the slave server. (Bug#25078)

INFORMATION_SCHEMA implementation changes were made that optimize certain types of queries for INFORMATION_SCHEMA tables so that they execute more quickly. Section 6.2.17, “INFORMATION_SCHEMA Optimization”, provides guidelines on how to take advantage of these optimizations by writing queries that minimize the need for the server to access the filesystem to obtain the information contained in INFORMATION_SCHEMA tables. By writing queries that enable the server to avoid directory scans or opening table files, you will obtain better performance. (Bug#19588)

Log table locking was redesigned, eliminating several lock-related problems:

The changes provide better-defined interface characteristics. See Section 5.2.1, “Selecting General Query and Slow Query Log Output Destinations”. (Bug#17876, Bug#23044, Bug#25422, Bug#29129)

Added the --commit, --detach, --post-system, and --pre-system options for mysqlslap.

Replication between master and slaves now supports different column numbers within a table on both master and slave. The rules for replication where the table definitions are different has also changed. This supercedes the functionality for replication from the master table to a slave table with more columns that was added in MySQL 5.1.12. For more information, see Section 14.3.1.20, “Replication with Differing Tables on Master and Slave”.

A new option, --syslog-tag=tag , modifies the default tags written by mysqld_safe and mysqld to syslog to be mysqld_safe-tag and mysqld-tag rather than the default tags of mysqld_safe and mysqld.

Two options relating to slow query logging have been added for mysqld. --log-slow-slave-statements causes slow statements executed by a replication slave to be written to the slow query log; min_examined_row_limit can be used to cause queries which examine fewer than the stated number of rows not to be logged.

Incompatible Change: Several issues were identified for stored programs (stored functions and procedures, triggers, and events) and views containing non-ASCII symbols. These issues involved conversion errors due to incomplete character set information when translating these objects to and from stored format, such as:

The fix for the problems is to store character set information from the object creation context so that this information is available when the object needs to be used later. The context includes the client character set, the connection character set and collation, and the collation of the database with which the object is associated.

As a result of the patch, several tables have new columns:

These columns store the session values of the character_set_client and collation_connection system variables, and the collation of the database with which the object is associated. The values are those in effect at object creation time. (The saved database collation is not the value of the collation_database system variable, which applies to the default database; the database that contains the object is not necessarily the default database.)

Several SHOW statements now display additional columns corresponding to the new table columns. These statements are: SHOW CREATE EVENT, SHOW CREATE FUNCTION, SHOW CREATE PROCEDURE, SHOW CREATE VIEW, SHOW EVENTS, SHOW FUNCTION STATUS, SHOW PROCEDURE STATUS, SHOW TRIGGERS.

A new statement, SHOW CREATE TRIGGER is introduced and is used by mysqldump for producing CREATE TRIGGER statements.

Subsequent to the patch just described, it was discovered that the patch broke mysql_upgrade; this has been corrected.

(Bug#25221, Bug#21249, Bug#30027, Bug#16291, Bug#11986, Bug#25212, Bug#19443, Bug#30029)

MySQL Cluster: DELETE FROM table WHERE primary_key IN (value_list), where the value_list contained more than one value, called from an AFTER DELETE trigger on an NDB table, caused mysqld to crash. (Bug#30337)

MySQL Cluster: When restarting a data node, queries could hang during that node's start phase 5, and continue only after the node had entered phase 6. (Bug#29364)

MySQL Cluster: Replica redo logs were inconsistently handled during a system restart. (Bug#29354)

MySQL Cluster: When a node failed to respond to a COPY_GCI signal as part of a global checkpoint, the master node was killed instead of the node that actually failed. (Bug#29331)

MySQL Cluster: An invalid comparison made during REDO validation that could lead to an Error while reading REDO log condition. (Bug#29118)

MySQL Cluster: The wrong data pages were sometimes invalidated following a global checkpoint. (Bug#29067)

MySQL Cluster: If at least 2 files were involved in REDO invalidation, then file 0 of page 0 was not updated and so pointed to an invalid part of the redo log. (Bug#29057)

MySQL Cluster: If a storage engine has its own logging capability, then any statement using both this engine and some other engine not having its own logging could not be correctly logged, due to the fact that entries from one engine could be logged before entries from the other engine were. This did not generate any error messages when it occurred.

Now, if multiple storage engines are used in a statement and at least one of them has its own logging capability, then an error message is generated and the statement is not executed.

(Bug#28722)

MySQL Cluster: Warnings and errors generated by ndb_config --config-file=file were sent to stdout, rather than to stderr. (Bug#25941)

MySQL Cluster: (Replication): Inconsistencies could occur between the master and the slave when replicating Disk Data tables. (Bug#19259, Bug#19227)

MySQL Cluster: Large file support did not work in AIX server binaries. (Bug#10776)

Disk Data: Performing Disk Data schema operations during a node restart could cause forced shutdowns of other data nodes. (Bug#29501)

Disk Data: When dropping a page, the stack's bottom entry could sometime be left “cold” rather than “hot”, violating the rules for stack pruning. (Bug#29176)

Disk Data: Disk data meta-information that existed in ndbd might not be visible to mysqld. (Bug#28720)

Disk Data: The number of free extents was incorrectly reported for some tablespaces. (Bug#28642)

Cluster Replication: When executing a statement where binlog_format=statement, the result of the statement was logged both as a statement and as rows. (Bug#29222)

Cluster Replication: mysqld would segfault on startup when the NDB storage engine was enabled and the default character set was a strictly multi-byte character set such as UCS2.

This issue does not apply to character sets that can contain single-byte characters in addition to multi-byte characters such as UTF-8.

Additional issues remain with regard to the use of multi-byte character sets in MySQL Cluster Replication; see Section 15.10.3, “Known Issues in MySQL Cluster Replication”, for more information. (Bug#27404)

Prepared statements containing CONNECTION_ID() could be written improperly to the binary log. (Bug#30200)

Use of local variables with non-ASCII names in stored procedures crashed the server. (Bug#30120)

On Windows, client libraries lacked symbols required for linking. (Bug#30118)

--myisam-recover='' (empty option value) did not disable MyISAM recovery. (Bug#30088)

For the SHOW TABLE TYPES statement, the server sent incorrect output to clients, possibly causing them to crash. (Bug#30036)

The IS_UPDATABLE column in the INFORMATION_SCHEMA.VIEWS table was not always set correctly. (Bug#30020)

SHOW statements were being written to the slow query log that should not have been. (Bug#30000)

REPAIR TABLE ... USE_FRM could corrupt tables. (Bug#29980)

For MyISAM tables on Windows, INSERT, DELETE, or UPDATE followed by ALTER TABLE within LOCK TABLES could cause table corruption. (Bug#29957)

LOCK TABLES did not pre-lock tables used in triggers of the locked tables. Unexpected locking behavior and statement failures similar to failed: 1100: Table 'xx' was not locked with LOCK TABLES could result. (Bug#29929)

INSERT ... VALUES(CONNECTION_ID(), ...) statements were written to the binary log in such a way that they could not be properly restored. (Bug#29928)

Adding DISTINCT could cause incorrect rows to appear in a query result. (Bug#29911)

On Windows, the CMake build process did not produce the embedded server library or related binaries. (Bug#29903)

Using the DATE() function in a WHERE clause did not return any records after encountering NULL. However, using TRIM or CAST produced the correct results. (Bug#29898)

SESSION_USER() returned garbage data (rather than the correct value of the empty string) when executed by a slave SQL thread. (Bug#29878)

Very long prepared statements in stored procedures could cause a server crash. (Bug#29856)

If query execution involved a temporary table, GROUP_CONCAT() could return a result with an incorrect character set. (Bug#29850)

If one thread was performing concurrent inserts, other threads reading from the same table using equality key searches could see the index values for new rows before the data values had been written, leading to reports of table corruption. (Bug#29838)

Repeatedly accessing a view in a stored procedure (for example, in a loop) caused a small amount of memory to be allocated per access. Although this memory is deallocated on disconnect, it could be a problem for a long running stored procedures that make repeated access of views. (Bug#29834)

mysqldump produced output that incorrectly discarded the NO_AUTO_VALUE_ON_ZERO value of the SQL_MODE variable after dumping triggers. (Bug#29788)

An assertion failure occurred within yaSSL for very long keys. (Bug#29784)

For MEMORY tables, the index_merge union access method could return incorrect results. (Bug#29740)

Comparison of TIME values using the BETWEEN operator led to string comparison, producing incorrect results in some cases. Now the values are compared as integers. (Bug#29739)

The thread ID was not reset properly after execution of mysql_change_user(), which could cause replication failure when replicating temporary tables. (Bug#29734)

For a table with a DATE column date_col such that selecting rows with WHERE date_col = 'date_val 00:00:00' yielded a non-empty result, adding GROUP BY date_col caused the result to be empty. (Bug#29729)

In some cases, INSERT INTO ... SELECT ... GROUP BY could insert rows even if the SELECT by itself produced an empty result. (Bug#29717)

Single-row inserts could report a row count greater than one. (Bug#29692)

For the embedded server, the mysql_stmt_store_result() C API function caused a memory leak for empty result sets. (Bug#29687)

EXPLAIN produced Impossible where for statements of the form SELECT ... FROM t WHERE c=0, where c was an ENUM column defined as a primary key. (Bug#29661)

On Windows, ALTER TABLE hung if records were locked in share mode by a long-running transaction. (Bug#29644)

mysqld_safe produced error messages and did not create the error log file under some circumstances. (Bug#29634)

On 64-bit platforms, the filesort code (for queries with GROUP BY or ORDER BY) could crash due to an incorrect pointer size. (Bug#29610)

A left join between two views could produce incorrect results. (Bug#29604)

Certain statements with unions, subqueries, and joins could result in huge memory consumption. (Bug#29582)

Clients using SSL could hang the server. (Bug#29579)

A slave running with --log-slave-updates would fail to write INSERT DELAY IGNORE statements to its binary log, resulting in different binary log contents on the master and slave. (Bug#29571)

Storage engine error conditions in row-based replication were not correctly reported to the user. (Bug#29570)

An incorrect result was returned when comparing string values that were converted to TIME values with CAST(). (Bug#29555)

gcov coverage-testing information was not written if the server crashed. (Bug#29543)

Conversion of ASCII DEL (0x7F) to Unicode incorrectly resulted in QUESTION MARK (0x3F) rather than DEL. (Bug#29499)

A field packet with NULL fields caused a libmysqlclient crash. (Bug#29494)

On Windows, the mysql client died if the user entered a statement and Return after entering Control-C. (Bug#29469)

The full-text parser could enter an infinite loop if it encountered an illegal multi-byte sequence or a sequence that has no mapping to Unicode. (Bug#29464)

Failure to consider collation when comparing space characters could lead to incorrect index entry order, making it impossible to find some index values. (Bug#29461)

Searching a FULLTEXT index for a word with the boolean mode truncation operator could cause an infinite loop. (Bug#29445)

Corrupt data resulted from use of SELECT ... INTO OUTFILE 'file_name' FIELDS ENCLOSED BY 'c', where c is a digit or minus sign, followed by LOAD DATA INFILE 'file_name' FIELDS ENCLOSED BY 'c'. (Bug#29442)

Killing an INSERT DELAYED thread caused a server crash. (Bug#29431)

Use of SHOW BINLOG EVENTS for a non-existent log file followed by PURGE MASTER LOGS caused a server crash. (Bug#29420)

Assertion failure could occur for grouping queries that employed DECIMAL user variables with assignments to them. (Bug#29417)

For CAST(expr AS DECIMAL(M,D)), the limits of 65 and 30 on the precision (M) and scale (D) were not enforced. (Bug#29415)

Deleting from a CSV table could corrupt it. (Bug#29411)

Results for a select query that aliases the column names against a view could duplicate one column while omitting another. This bug could occur for a query over a multiple-table view that includes an ORDER BY clause in its definition. (Bug#29392)

mysqldump created a stray file when a given a too-long filename argument. (Bug#29361)

The special “zero” ENUM value was coerced to the normal empty string ENUM value during a column-to-column copy. This affected CREATE ... SELECT statements and SELECT statements with aggregate functions on ENUM columns in the GROUP BY clause. (Bug#29360)

Inserting a negative number into a CSV table could corrupt it. (Bug#29353)

Optimization of queries with DETERMINISTIC stored functions in the WHERE clause was ineffective: A sequential scan was always used. (Bug#29338)

MyISAM corruption could occur with the cp932_japanese_ci collation for the cp932 character set due to incorrect comparison for trailing space. (Bug#29333)

For updates to InnoDB tables, a TIMESTAMP column with the ON UPDATE CURRENT_TIMESTAMP attribute could be updated even when no values actually changed. (Bug#29310)

FULLTEXT indexes could be corrupted by certain gbk characters. (Bug#29299)

SELECT ... INTO OUTFILE followed by LOAD DATA could result in garbled characters when the FIELDS ENCLOSED BY clause named a delimiter of '0', 'b', 'n', 'r', 't', 'N', or 'Z' due to an interaction of character encoding and doubling for data values containing the enclosed-by character. (Bug#29294)

Sort order of the collation wasn't used when comparing trailing spaces. This could lead to incorrect comparison results, incorrectly created indexes, or incorrect result set order for queries that include an ORDER BY clause. (Bug#29261)

CHECK TABLE could erroneously report table corruption for a CSV table if multiple threads were modifying the table at the same time. (Bug#29253)

Many threads accessing a CSV table simultaneously could cause an assertion failure. (Bug#29252)

If an ENUM column contained '' as one of its members (represented with numeric value greater than 0), and the column contained error values (represented as 0 and displayed as ''), using ALTER TABLE to modify the column definition caused the 0 values to be given the numeric value of the non-zero '' member. (Bug#29251)

Calling mysql_options() after mysql_real_connect() could cause clients to crash. (Bug#29247)

CHECK TABLE for ARCHIVE tables could falsely report table corruption or cause a server crash. (Bug#29207)

Mixing binary and utf8 columns in a union caused field lengths to be calculated incorrectly, resulting in truncation. (Bug#29205)

AsText() could fail with a buffer overrun. (Bug#29166)

Under some circumstances, a SELECT ... FROM mysql.event could cause the server to crash. (Bug#29156)

InnoDB refused to start on some versions of FreeBSD with LinuxThreads. This is fixed by enabling file locking on FreeBSD. (Bug#29155)

LOCK TABLES was not atomic when more than one InnoDB tables were locked. (Bug#29154)

INSERT DELAYED statements on a master server are replicated as non-DELAYED inserts on slaves (which is normal, to preserve serialization), but the inserts on the slave did not use concurrent inserts. Now INSERT DELAYED on a slave is converted to a concurrent insert when possible, and to a normal insert otherwise. (Bug#29152)

mysqld failed to exit during shutdown. (Bug#29133)

A network structure was initialized incorrectly, leading to embedded server crashes. (Bug#29117)

An assertion failure occurred if a query contained a conjunctive predicate of the form view_column = constant in the WHERE clause and the GROUP BY clause contained a reference to a different view column. The fix also enables application of an optimization that was being skipped if a query contained a conjunctive predicate of the form view_column = constant in the WHERE clause and the GROUP BY clause contained a reference to the same view column. (Bug#29104)

A maximum of 4TB InnoDB free space was reported by SHOW TABLE STATUS, which is incorrect on systems with more than 4TB space. (Bug#29097)

If an INSERT INTO ... SELECT statement inserted into the same table that the SELECT retrieved from, and the SELECT included ORDER BY and LIMIT clauses, different data was inserted than the data produced by the SELECT executed by itself. (Bug#29095)

Queries that performed a lookup into a BINARY index containing key values ending with spaces caused an assertion failure for debug builds and incorrect results for non-debug builds. (Bug#29087)

The semantics of BIGINT depended on platform-specific characteristics. (Bug#29079)

A byte-order issue in writing a spatial index to disk caused bad index files on some systems. (Bug#29070)

Creation of a legal stored procedure could fail if no default database had been selected. (Bug#29050)

REPLACE, INSERT IGNORE, and UPDATE IGNORE did not work for FEDERATED tables. (Bug#29019)

Inserting into InnoDB tables and executing RESET MASTER in multiple threads cause assertion failure in debug server binaries. (Bug#28983)

Updates to a CSV table could cause a server crash or update the table with incorrect values. (Bug#28971)

For a ucs2 column, GROUP_CONCAT() did not convert separators to the result character set before inserting them, producing a result containing a mixture of two different character sets. (Bug#28925)

Dropping the definer of an active event caused the server to crash. (Bug#28924)

For a join with GROUP BY and/or ORDER BY and a view reference in the FROM list, the query metadata erroneously showed empty table aliases and database names for the view columns. (Bug#28898)

Creating an event using ON SCHEDULE AT CURRENT_TIMESTAMP + INTERVAL ... could in some cases cause mysqld to crash. (Bug#28881)

Coercion of ASCII values to character sets that are a superset of ASCII sometimes was not done, resulting in illegal mix of collations errors. These cases now are resolved using repertoire, a new string expression attribute (see Section 8.1.6, “String Repertoire”). (Bug#28875)

Executing ALTER EVENT on an event whose definer's event creation privileges had been revoked cause the server to crash. (Bug#28873)

ALTER VIEW is not supported as a prepared statement but was not being rejected. ALTER VIEW is now prohibited as a prepared statement or when called within stored routines. (Bug#28846)

In strict SQL mode, errors silently stopped the SQL thread even for errors named using the --slave-skip-errors option. (Bug#28839)

Fast ALTER TABLE (that works without rebuilding the table) acquired duplicate locks in the storage engine. In MyISAM, if ALTER TABLE was issued under LOCK TABLE, it caused all data inserted after LOCK TABLE to disappear. (Bug#28838)

Runtime changes to the log_queries_not_using_indexes system variable were ignored. (Bug#28808)

Selecting a column not present in the selected-from table caused an extra error to be produced by SHOW ERRORS. (Bug#28677)

Creating an event to be executed at a time close to the end of the allowed range (2038-01-19 03:14:07 UTC) would cause the server to crash. (Bug#28641)

For a statement of the form CREATE t1 SELECT integer_constant , the server created the column using the DECIMAL data type for large negative values that are within the range of BIGINT. (Bug#28625)

For InnoDB tables, MySQL unnecessarily sorted records in certain cases when the records were retrieved by InnoDB in the proper order already. (Bug#28591)

mysql_install_db could fail to find script files that it needs. (Bug#28585)

If a stored procedure was created and invoked prior to selecting a default database with USE, a No database selected error occurred. (Bug#28551)

On Mac OS X, shared-library installation pathnames were incorrect. (Bug#28544)

Using the --skip-add-drop-table option with mysqldump generated incorrect SQL if the database included any views. The recreation of views requires the creation and removal of temporary tables. This option suppressed the removal of those temporary tables. The same applied to --compact since this option also invokes --skip-add-drop-table. (Bug#28524)

mysqlbinlog --hexdump generated incorrect output due to omission of the “ # ” comment character for some comment lines. (Bug#28293)

InnoDB could crash if the server was shut down while innodb_table_monitor was running. (Bug#28254)

A race condition in the interaction between MyISAM and the query cache code caused the query cache not to invalidate itself for concurrently inserted data. (Bug#28249)

A duplicate-key error message could display an incorrect key value when not all columns of the key were used to select rows for update. (Bug#28158)

Indexing column prefixes in InnoDB tables could cause table corruption. (Bug#28138)

Index creation could fail due to truncation of key values to the maximum key length rather than to a mulitiple of the maximum character length. (Bug#28125)

Instance Manager had a race condition when it received a shutdown request while a guarded mysqld instance was starting such that it could fail to stop the mysqld instance. (Bug#28030)

SELECT ... FOR UPDATE with partitioned tables could cause a server crash. (Bug#28026)

On Windows, Instance Manager would crash if an instance object failed to initialize during startup. This could happen if an incorrect mysqld path was supplied in the configuration file. (Bug#28012)

The LOCATE() function returned NULL if any of its arguments evaluated to NULL. Likewise, the predicate, LOCATE(str,NULL) IS NULL, erroneously evaluated to FALSE. (Bug#27932)

Dropping a user-defined function could cause a server crash if the function was still in use by another thread. (Bug#27564)

An error that happened inside INSERT, UPDATE, or DELETE statements performed from within a stored function or trigger could cause inconsistency between master and slave servers. (Bug#27417)

For some event-creation problems, the server displayed messages that implied the problems were errors when they were only warnings. (Bug#27406)

Fixed a case of unsafe aliasing in the source that caused a client library crash when compiled with gcc 4 at high optimization levels. (Bug#27383)

Index-based range reads could fail for comparisons that involved contraction characters (such as ch in Czech or ll in Spanish). (Bug#27345)

Aggregations in subqueries that refer to outer query columns were not always correctly referenced to the proper outer query. (Bug#27333)

Error returns from the time() system call were ignored. (Bug#27198)

Phantom reads could occur under InnoDB serializable isolation level. (Bug#27197)

The SUBSTRING() function returned the entire string instead of an empty string when it was called from a stored procedure and when the length parameter was specified by a variable with the value “ 0 ”. (Bug#27130)

Some functions when used in partitioning expressions could cause mysqld to crash. (Bug#27084)

The server acquired a global mutex for temporary tables, although such tables are thread-specific. This affected performance by blocking other threads. (Bug#27062)

FEDERATED tables had an artificially low maximum of key length. (Bug#26909)

Updates to rows in a partitioned table could update the wrong column. (Bug#26827)

Index creation could corrupt the table definition in the .frm file: 1) A table with the maximum number of key segments and maximum length key name would have a corrupted .frm file, due to incorrect calculation of the total key length. 2) MyISAM would reject a table with the maximum number of keys and the maximum number of key segments in all keys. (It would allow one less than this total maximum.) Now MyISAM accepts a table defined with the maximum. (Bug#26642)

The Windows implementation of pthread_join() was incorrect and could cause crashes. (Bug#26564)

After the first read of a TEMPORARY table, CHECK TABLE could report the table as being corrupt. (Bug#26325)

If an operation had an InnoDB table, and two triggers, AFTER UPDATE and AFTER INSERT, competing for different resources (such as two distinct MyISAM tables), the triggers were unable to execute concurrently. In addition, INSERT and UPDATE statements for the InnoDB table were unable to run concurrently. (Bug#26141)

A number of unsupported constructs — including prohibited constructs, the UCASE() function, and nested function calls — were permitted in partitioning expressions. (Bug#26082, Bug#18198, Bug#29308)

ALTER DATABASE did not require at least one option. (Bug#25859)

The index merge union access algorithm could produce incorrect results with InnoDB tables. The problem could also occur for queries that used DISTINCT. (Bug#25798)

When using a FEDERATED table, the value of last_insert_id() would not correctly update the C API interface, which would affect the autogenerated ID returned both through the C API and the MySQL protocol, affecting Connectors that used the protocol and/or C API. (Bug#25714)

The server was blocked from opening other tables while the FEDERATED engine was attempting to open a remote table. Now the server does not check the correctness of a FEDERATED table at CREATE TABLE time, but waits until the table actually is accessed. (Bug#25679)

Under ActiveState Perl, mysql-test-run.pl could kill itself when attempting to kill other processes. (Bug#25657)

Several InnoDB assertion failures were corrected. (Bug#25645)

A query with DISTINCT in the select list to which the loose-scan optimization for grouping queries was applied returned an incorrect result set when the query was used with the SQL_BIG_RESULT option. (Bug#25602)

For a multiple-row insert into a FEDERATED table that refers to a remote transactional table, if the insert failed for a row due to constraint failure, the remote table would contain a partial commit (the rows preceding the failed one) instead of rolling back the statement completely. This occurred because the rows were treated as individual inserts.

Now FEDERATED performs bulk-insert handling such that multiple rows are sent to the remote table in a batch. This provides a performance improvement and enables the remote table to perform statement rollback properly should an error occur. This capability has the following limitations:

(Bug#25513)

The FEDERATED storage engine failed silently for INSERT ... ON DUPLICATE KEY UPDATE if a duplicate key violation occurred. FEDERATED does not support ON DUPLICATE KEY UPDATE, so now it correctly returns an ER_DUP_KEY error if a duplicate key violation occurs. (Bug#25511)

In a stored function or trigger, when InnoDB detected deadlock, it attempted rollback and displayed an incorrect error message (Explicit or implicit commit is not allowed in stored function or trigger). Now InnoDB returns an error under these conditions and does not attempt rollback. Rollback is handled outside of InnoDB above the function/trigger level. (Bug#24989)

Dropping a temporary InnoDB table that had been locked with LOCK TABLES caused a server crash. (Bug#24918)

On Windows, executables did not include Vista manifests. (Bug#24732)

Slave servers could incorrectly interpret an out-of-memory error from the master and reconnect using the wrong binary log position. (Bug#24192)

If MySQL/InnoDB crashed very quickly after starting up, it would not force a checkpoint. In this case, InnoDB would skip crash recovery at next startup, and the database would become corrupt. Fix: If the redo log scan at InnoDB startup goes past the last checkpoint, force crash recovery. (Bug#23710)

Using the READ COMMITTED transaction isolation level caused mixed and statement-based replication to fail. (Bug#23051)

SHOW INNODB STATUS caused an assertion failure under high load. (Bug#22819)

SHOW BINLOG EVENTS displayed incorrect values of End_log_pos for events associated with transactional storage engines. (Bug#22540)

When determining which transaction to kill after deadlock has been detected, InnoDB now adds the number of locks to a transaction's weight, and avoids killing transactions that mave modified non-transactional tables. This should reduce the likelihood of killing long-running transactions containing SELECT ... FOR UPDATE or INSERT/REPLACE INTO ... SELECT statements, and of causing partial updates if the target is a MyISAM table. (Bug#21293)

InnoDB displayed an incorrect error message when a CREATE TABLE statement exceeded the InnoDB maximum allowable row size. (Bug#21101)

Under heavy load with a large query cache, invalidating part of the cache could cause the server to freeze (that is, to be unable to service other operations until the invalidation was complete). (Bug#21074)

mysql-stress-test.pl and mysqld_multi.server.sh were missing from some binary distributions. (Bug#21023, Bug#25486)

On Windows, the server used 10MB of memory for each connection thread, resulting in memory exhaustion. Now each thread uses 1MB. (Bug#20815)

InnoDB produced an unnecessary (and harmless) warning: InnoDB: Error: trying to declare trx to enter InnoDB, but InnoDB: it already is declared. (Bug#20090)

If a slave timed out while registering with the master to which it was connecting, auto-reconnect failed thereafter. (Bug#19328)

If InnoDB reached its limit on the number of concurrent transactions (1023), it wrote a descriptive message to the error log but returned a misleading error message to the client, or an assertion failure occurred. (Bug#18828)

Under ActiveState Perl, mysql-test-run.pl would not run. (Bug#18415)

The server crashed when the size of an ARCHIVE table grew larger than 2GB. (Bug#15787)

SQL_BIG_RESULT had no effect for CREATE TABLE ... SELECT SQL_BIG_RESULT ... statements. (Bug#15130)

On 64-bit Windows systems, the Config Wizard failed to complete the setup because 64-bit Windows does not resolve dynamic linking of the 64-bit libmysql.dll to a 32-bit application like the Config Wizard. (Bug#14649)

mysql_setpermission tried to grant global-only privileges at the database level. (Bug#14618)

For the general query log, logging of prepared statements executed via the C API differed from logging of prepared statements performed with PREPARE and EXECUTE. Logging for the latter was missing the Prepare and Execute lines. (Bug#13326)

The TABLE_COMMENT column for INFORMATION_SCHEMA.TABLES displayed extraneous information for InnoDB tables. (Bug#11379)

The server returned data from SHOW CREATE TABLE statement or a SELECT statement on an INFORMATION_SCHEMA table using the binary character set. (Bug#10491)

Backup software can cause ERROR_SHARING_VIOLATION or ERROR_LOCK_VIOLATION conditions during file operations. InnoDB now retries forever until the condition goes away. (Bug#9709)

Retrieval of object definitions from INFORMATION_SCHEMA tables.

In INFORMATION_SCHEMA, the VIEWS table now has these columns: CHARACTER_SET_CLIENT, COLLATION_CONNECTION. The ROUTINES, TRIGGERS, and EVENT tables now have these columns: CHARACTER_SET_CLIENT, COLLATION_CONNECTION, DATABASE_COLLATION.

In the mysql database, the proc and event tables now have these columns: character_set_client, collation_connection, db_collation, body_utf8.

Displaying the object definition in SHOW statements. This issue also affected mysqldump, which uses SHOW.

Compiling the stored definition into executable form when the object is invoked.

Bulk-insert handling does not occur for INSERT ... ON DUPLICATE KEY UPDATE.

The size of the insert cannot exceed the maximum packet size between servers. If the insert exceeds this size, it is broken into multiple packets and the rollback problem can occur.

Parsing the original object definition so that it can be stored.

Incompatible Change: It is no longer possible to partition the log tables. (Bug#27816)

Incompatible Change: mysqld_safe now supports error logging to syslog on systems that support the logger command. The new --syslog and --skip-syslog options can be used instead of the --log-error option to control logging behavior, as described in Section 4.3.2, “mysqld_safe — MySQL Server Startup Script”. The default is to use syslog, which differs from the previous default behavior of writing an error log file.

Currently, logging to syslog may fail to operate correctly in some cases, so we recommend that you use --skip-syslog or --log-error. To maintain the older behavior if you were using no error-logging option, use --skip-syslog. If you were using --log-error, continue to use it.

Note: In 5.1.21, the default is changed to --skip-syslog, which is compatible with releases prior to 5.1.20. (Bug#4858)

Important Change: MySQL Cluster: The TimeBetweenWatchdogCheckInitial configuration parameter was added to allow setting of a separate watchdog timeout for memory allocation during startup of the data nodes. See Section 15.4.4.5, “Defining Data Nodes”, for more information. (Bug#28899)

MySQL Cluster: The cluster management client now stores command history between sessions. (Bug#29073)

MySQL Cluster: auto_increment_increment and auto_increment_offset are now supported for NDB tables. (Bug#26342)

MySQL Cluster: The server source tree now includes scripts to simplify building MySQL with SCI support. For more information about SCI interconnects and these build scripts, see Section 15.12.1, “Configuring MySQL Cluster to use SCI Sockets”. (Bug#25470)

MySQL Cluster: A new configuration parameter ODirect causes NDB to attempt using O_DIRECT writes for LCP, backups, and redo logs, often lowering CPU usage.

If a MERGE table cannot be opened or used because of a problem with an underlying table, CHECK TABLE now displays information about which table caused the problem. (Bug#26976)

User variables and stored procedure variables are now supported for use in XPath expressions employed as arguments to the ExtractValue() and UpdateXML() functions.

This means that:

See Section 10.10, “XML Functions”, for more information. (Bug#26518)

Binary distributions for some platforms did not include shared libraries; now shared libraries are shipped for all platforms except AIX 5.2 64-bit. Exception: The library for the libmysqld embedded server is not shared except on Windows. (Bug#16520, Bug#26767, Bug#13450)

XPath can now be used to load data from XML files using virtually any format, and so able to import data from most third party software which either has XML export functionality, or uses XML natively as a storage format.

Various complex conditions can be put on rows and columns, so one can filter for desired rows (or skip unwanted rows) when loading XML.

The SQL_MODE, FOREIGN_KEY_CHECKS, UNIQUE_CHECKS, character set/collations, and SQL_AUTO_IS_NULL sesstion variables are written to the binary log and honoured during replication. See Section 5.2.4, “The Binary Log”.

Various types of preprocessing using SQL functions are now possible when loading XML. For example, you can concatenate two XML tag or attribute values into a single column value using CONCAT(), or remove some parts of the data using REPLACE().

Security Fix: A malformed password packet in the connection protocol could cause the server to crash. Thanks for Dormando for reporting this bug, and for providing details and a proof of concept. (Bug#28984, CVE-2007-3780)

Security Fix: CREATE TABLE LIKE did not require any privileges on the source table. Now it requires the SELECT privilege.

In addition, CREATE TABLE LIKE was not isolated from alteration by other connections, which resulted in various errors and incorrect binary log order when trying to execute concurrently a CREATE TABLE LIKE statement and either DDL statements on the source table or DML or DDL statements on the target table. (Bug#23667, Bug#25578, CVE-2007-3781)

Incompatible Change: Some error codes had error numbers in MySQL 5.1 different from the numbers in MySQL 5.0. In MySQL 5.1, error numbers have been changed to match the MySQL 5.0 values: Error codes with value of 1458 or higher have changed in MySQL 5.1 now. Client applications designed to work with MySQL 5.1 with hard-coded error code values (for example, in statements such as if (mysql_errno(mysql) == 1463) { ... }) need to be updated in the source code. All clients designed to work with MySQL 5.1 that test error codes (for example, in statements such as if (mysql_errno(mysql) == ER_VIEW_RECURSIVE) { ... }) should be recompiled. Existing 5.0 clients should now work, without changes or recompilation, against servers for MySQL 5.1.20 or higher. (Bug#29245)

Incompatible Change: When mysqldump was run with the --delete-master-logs option, binary log files were deleted before it was known that the dump had succeeded, not after. (The method for removing log files used RESET MASTER prior to the dump. This also reset the binary log sequence numbering to .000001.) Now mysqldump flushes the logs (which creates a new binary log number with the next sequence number), performs the dump, and then uses PURGE MASTER LOGS to remove the log files older than the new one. This also preserves log numbering because the new log with the next number is generated and only the preceding logs are removed. However, this may affect applications if they rely on the log numbering sequence being reset. (Bug#24733)

Incompatible Change: The use of an ORDER BY or DISTINCT clause with a query containing a call to the GROUP_CONCAT() function caused results from previous queries to be redisplayed in the current result. The fix for this includes replacing a BLOB value used internally for sorting with a VARCHAR. This means that for long results (more than 65,535 bytes), it is possible for truncation to occur; if so, an appropriate warning is issued. (Bug#23856, Bug#28273)

MySQL Cluster: Memory corruption could occur due to a problem in the DBTUP kernel block. (Bug#29229)

MySQL Cluster: A query having a large IN(...) or NOT IN(...) list in the WHERE condition on an NDB table could cause mysqld to crash. (Bug#29185)

MySQL Cluster: In the event that two data nodes in the same node group and participating in a GCP crashed before they had written their respective P0.sysfile files, QMGR could refuse to start, issuing an invalid Insufficient nodes for restart error instead. (Bug#29167)

MySQL Cluster: Attempting to restore a NULL row to a VARBINARY column caused ndb_restore to fail. (Bug#29103)

MySQL Cluster: ndb_error_reporter now preserves timestamps on files. (Bug#29074)

MySQL Cluster: It is now possible to set the maximum size of the allocation unit for table memory using the MaxAllocate configuration parameter. (Bug#29044)

MySQL Cluster: When shutting down mysqld, the NDB binlog process was not shut down before log cleanup began. (Bug#28949)

MySQL Cluster: ndb_mgm could hang when connecting to a nonexistent host. (Bug#28847)

MySQL Cluster: A regression in the heartbeat monitoring code could lead to node failure under high load. This issue affected MySQL 5.1.19 and MySQL 5.1.15-ndb-6.1.10 only. (Bug#28783)

MySQL Cluster: A corrupt schema file could cause a File already open error. (Bug#28770)

MySQL Cluster: Having large amounts of memory locked caused swapping to disk. (Bug#28751)

MySQL Cluster: Setting InitialNoOpenFiles equal to MaxNoOfOpenFiles caused an error. This was due to the fact that the actual value of MaxNoOfOpenFiles as used by the cluster was offset by 1 from the value set in config.ini. (Bug#28749)

MySQL Cluster: LCP files were not removed following an initial system restart. (Bug#28726)

MySQL Cluster: UPDATE IGNORE statements involving the primary keys of multiple tables could result in data corruption. (Bug#28719)

MySQL Cluster: A race condition could result when non-master nodes (in addition to the master node) tried to update active status due to a local checkpoint (that is, between NODE_FAILREP and COPY_GCIREQ events). Now only the master updates the active status. (Bug#28717)

MySQL Cluster: A fast global checkpoint under high load with high usage of the redo buffer caused data nodes to fail. (Bug#28653)

MySQL Cluster: The management client's response to START BACKUP WAIT COMPLETED did not include the backup ID. (Bug#27640)

MySQL Cluster: (Replication): A replicated unique key allowed duplicate key inserts on the slave. (Bug#27044)

Replication: It was possible to set SQL_SLAVE_SKIP_COUNTER such that the slave would jump into the middle of an event group. (Bug#28618)

See also Bug#12691

Disk Data: When loading data into a cluster following a version upgrade, the data nodes could forcibly shut down due to page and buffer management failures (that is, ndbrequire failures in PGMAN). (Bug#28525)

Disk Data: Repeated INSERT and DELETE operations on a Disk Data table having one or more large VARCHAR columns could cause data nodes to fail. (Bug#20612)

Cluster Replication: When replicating MyISAM or InnoDB tables to a MySQL Cluster, it was not possible to determine exactly what had been applied following a shutdown of the slave cluster or mysqld process. (Bug#26783)

Cluster API: The timeout set using the MGM API ndb_mgm_set_timeout() function was incorrectly interpreted as seconds rather than as milliseconds. (Bug#29063)

Cluster API: An invalid error code could be set on transaction objects by BLOB handling code. (Bug#28724)

The TRUNCATE statement was handled differently by the server when row-based logging was in effect, even though the binlogging format in effect does not effect the fact that TRUNCATE is always logged as a statement. (Bug#29130)

If one of the queries in a UNION used the SQL_CACHE option and another query in the UNION contained a nondeterministic function, the result was still cached. For example, this query was incorrectly cached:

          
SELECT NOW() FROM t1 UNION SELECT SQL_CACHE 1 FROM t1;

(Bug#29053)

DROP USER statements that named multiple users, only some of which could be dropped, were replicated incorrectly. (Bug#29030)

Long pathnames for internal temporary tables could cause stack overflows. (Bug#29015)

Using an INTEGER column from a table to ROUND() a number produced different results than using a constant with the same value as the INTEGER column. (Bug#28980)

Using events in replication could cause the slave to crash. (Bug#28953)

If a program binds a given number of parameters to a prepared statement handle and then somehow changes stmt->param_count to a different number, mysql_stmt_execute() could crash the client or server. (Bug#28934)

Queries using UDFs or stored functions were cached. (Bug#28921)

INSERT .. ON DUPLICATE KEY UPDATE could under some circumstances silently update rows when it should not have. (Bug#28904)

Queries that used UUID() were incorrectly allowed into the query cache. (This should not happen because UUID() is non-deterministic.) (Bug#28897)

Using a VIEW created with a non-existing DEFINER could lead to incorrect results under some circumstances. (Bug#28895)

For InnoDB tables that use the utf8 character set, incorrect results could occur for DML statements such as DELETE or UPDATE that use an index on character-based columns. (Bug#28878)

See also Bug#29449, Bug#30485, Bug#31395

This regression was introduced by Bug#13195

Non-utf8 characters could get mangled when stored in CSV tables. (Bug#28862)

On Windows, USE_TLS was not defined for mysqlclient.lib. (Bug#28860)

In MySQL 5.1.15, a new error code ER_DUP_ENTRY_WITH_KEY_NAME (1582) was introduced to replace ER_DUP_ENTRY (1062) so that the key name could be provided instead of the key number. This was unnecessary, so ER_DUP_ENTRY is used again and the key name is printed. The incompatibility introduced in 5.1.15 no longer applies. (Bug#28842)

A subquery with ORDER BY and LIMIT 1 could cause a server crash. (Bug#28811)

Running SHOW TABLE STATUS while performing a high number of inserts on partitioned tables with a great many partitions could cause the server to crash. (Bug#28806)

Using BETWEEN with non-indexed date columns and short formats of the date string could return incorrect results. (Bug#28778)

Selecting GEOMETRY columns in a UNION caused a server crash. (Bug#28763)

When constructing the path to the original .frm file, ALTER .. RENAME was unnecessarily (and incorrectly) lowercasing the entire path when not on a case-insensitive filesystem, causing the statement to fail. (Bug#28754)

The binlog_format system variable value was empty if the server was started with binary logging disabled. Now it is set to MIXED. (Bug#28752)

Searches on indexed and non-indexed ENUM columns could return different results for empty strings. (Bug#28729)

Executing EXPLAIN EXTENDED on a query using a derived table over a grouping subselect could lead to a server crash. This occurred only when materialization of the derived tables required creation of an auxiliary temporary table, an example being when a grouping operation was carried out with usage of a temporary table. (Bug#28728)

The result of evaluation for a view's CHECK OPTION option over an updated record and records of merged tables was arbitrary and dependant on the order of records in the merged tables during the execution of the SELECT statement. (Bug#28716)

The “manager thread” of the LinuxThreads implementation was unintentionally started before mysqld had dropped privileges (to run as an unprivileged user). This caused signaling between threads in mysqld to fail when the privileges were finally dropped. (Bug#28690)

Setting an interval of EVERY 0 SECOND for a scheduled event caused the server to crash. (Bug#28666)

For debug builds, ALTER TABLE could trigger an assertion failure due to occurrence of a deadlock when committing changes. (Bug#28652)

Attempting to create an index on a BIT column failed after modifying the column. (Bug#28631)

After an upgrade, the names of stored routines referenced by views were no longer displayed by SHOW CREATE VIEW. (Bug#28605)

This regression was introduced by Bug#23491

Conversion of U+00A5 YEN SIGN and U+203E OVERLINE from ucs2 to ujis produced incorrect results. (Bug#28600)

Killing from one connection a long-running EXPLAIN QUERY started from another connection caused mysqld to crash. (Bug#28598)

SHOW GLOBAL VARIABLES repeated some variable names. (Bug#28580)

When one thread attempts to lock two (or more) tables and another thread executes a statement that aborts these locks (such as REPAIR TABLE, OPTIMIZE TABLE, or CHECK TABLE), the thread might get a table object with an incorrect lock type in the table cache. The result is table corruption or a server crash. (Bug#28574)

Outer join queries with ON conditions over constant outer tables did not return NULL-complemented rows when conditions were evaluated to FALSE. (Bug#28571)

An update on a multiple-table view with the CHECK OPTION clause and a subquery in the WHERE condition could cause an assertion failure. (Bug#28561)

Calling the UpdateXML() function using invalid XPath syntax caused memory corruption possibly leading to a crash of the server. (Bug#28558)

PURGE MASTER LOGS BEFORE (subquery) caused a server crash. Subqueries are forbidden in the BEFORE clause now. (Bug#28553)

mysqldump calculated the required memory for a hex-blob string incorrectly causing a buffer overrun. This in turn caused mysqldump to crash silently and produce incomplete output. (Bug#28522)

When upgrading from MySQL 5.1.17 to 5.1.18, mysql_upgrade and mysql_fix_privilege_tables did not upgrade the system tables relating to the Event Scheduler correctly. (Bug#28521)

Passing a DECIMAL value as a parameter of a statement prepared with PREPARE resulted in an error. (Bug#28509)

mysql_affected_rows() could return an incorrect result for INSERT ... ON DUPLICATE KEY UPDATE if the CLIENT_FOUND_ROWS flag was set. (Bug#28505)

A query that grouped by the result of an expression returned a different result when the expression was assigned to a user variable. (Bug#28494)

Subselects returning LONG values in MySQL versions later than 5.0.24a returned LONGLONG prior to this. The previous behavior was restored. (Bug#28492)

This regression was introduced by Bug#19714

Performing ALTER TABLE ... ADD PARTITION or ALTER TABLE DROP PARTITION could result in inconsistent data, or cause the server to crash, if done concurrently with other accesses to the table. (Bug#28477, Bug#28488)

Forcing the use of an index on a SELECT query when the index had been disabled would raise an error without running the query. The query now executes, with a warning generated noting that the use of a disabled index has been ignored. (Bug#28476)

The result of executing of a prepared statement created with PREPARE s FROM "SELECT 1 LIMIT ?" was not replicated correctly. (Bug#28464)

The query SELECT '2007-01-01' + INTERVAL column_name DAY FROM table_name caused mysqld to fail. (Bug#28450)

A server crash could happen under rare conditions such that a temporary table outgrew heap memory reserved for it and the remaining disk space was not big enough to store the table as a MyISAM table. (Bug#28449)

Using ALTER TABLE to move columns resulted only in the columns being renamed. The table contents were not changed. (Bug#28427)

The test case for mysqldump failed with bin-log disabled. (Bug#28372)

Attempting to LOAD_FILE from an empty floppy drive under Windows, caused the server to hang. For example, if you opened a connection to the server and then issued the command SELECT LOAD_FILE('a:test');, with no floppy in the drive, the server was inaccessible until the modal pop-up dialog box was dismissed. (Bug#28366)

mysqltest used a too-large stack size on PPC/Debian Linux, causing thread-creation failure for tests that use many threads. (Bug#28333)

When using a MEMORY table on Mac OS X, dropping a table and than creating a table with the same name could cause the information of the deleted table to remain accessible, leading to index errors. (Bug#28309)

The IS_UPDATABLE column in the INFORMATION_SCHEMA.VIEWS table was not always set correctly. (Bug#28266)

For CAST() of a NULL value with type DECIMAL, the return value was incorrectly initialized, producing a runtime error for binaries built using Visual C++ 2005. (Bug#28250)

Recreating a view that already exists on the master would cause a replicating slave to terminate replication with a 'different error message on slave and master' error. (Bug#28244)

When the query cache was fully used, issuing RENAME DATABASE or RENAME SCHEMA could cause the server to hang, with 100% CPU usage. (Bug#28211)

The Bytes_received and Bytes_sent status variables could hold only 32-bit values (not 64-bit values) on some platforms. (Bug#28149)

Some valid identifiers were not parsed correctly. (Bug#28127)

Storing a large number into a FLOAT or DOUBLE column with a fixed length could result in incorrect truncation of the number if the column's length was greater than 31. (Bug#28121)

Sending debugging information from a dump of the Event Scheduler to COM_DEBUG could cause the server to crash. (Bug#28075)

The PARTITION_COMMENT column of the INFORMATION_SCHEMA.PARTITIONS table had the wrong default value. (Bug#28007)

DECIMAL values beginning with nine 9 digits could be incorrectly rounded. (Bug#27984)

For attempts to open a non-existent table, the server should report ER_NO_SUCH_TABLE but sometimes reported ER_TABLE_NOT_LOCKED. (Bug#27907)

Following an invalid call to UpdateXML(), calling the function again (even if valid) crashed the server. (Bug#27898)

A stored program that uses a variable name containing multibyte characters could fail to execute. (Bug#27876)

The server made strong assumptions about the structure of the general_log and slow_log log tables: It supported only the table structure defined in the mysql database creation scripts. The server also allowed limited ALTER TABLE operations on the log tables, but adding an AUTO_INCREMENT column did not properly initialize the column, and subsequent inserts into the table could fail to generate correct sequence numbers. Now an ALTER TABLE statement that adds an AUTO_INCREMENT column populates the column correctly. In addition, when the server writes a log table row, it will set columns not present in the original table structure to their default values. (Bug#27857)

ON conditions from JOIN expressions were ignored when checking the CHECK OPTION clause while updating a multiple-table view that included such a clause. (Bug#27827)

On some systems, udf_example.c returned an incorrect result length. Also on some systems, mysql-test-run.pl could not find the shared object built from udf_example.c. (Bug#27741)

The modification of a table by a partially completed multi-column update was not recorded in the binlog, rather than being marked by an event and a corresponding error code. (Bug#27716)

SHOW ENGINES and queries on INFORMATION_SCHEMA.ENGINES did not use the same values for representing the same storage engine states. (Bug#27684)

HASH indexes on VARCHAR columns with binary collations did not ignore trailing spaces from strings before comparisons. This could result in duplicate records being successfully inserted into a MEMORY table with unique key constraints. A consequence was that internal MEMORY tables used for GROUP BY calculation contained duplicate rows that resulted in duplicate-key errors when converting those temporary tables to MyISAM, and that error was incorrectly reported as a table is full error. (Bug#27643)

An error occurred trying to connect to mysqld-debug.exe. (Bug#27597)

A stack overrun could occur when storing DATETIME values using repeated prepared statements. (Bug#27592)

If a stored function or trigger was killed, it aborted but no error was thrown, allowing the calling statement to continue without noticing the problem. This could lead to incorrect results. (Bug#27563)

When ALTER TABLE was used to add a new DATE column with no explicit default value, '0000-00-00' was used as the default even if the SQL mode included the NO_ZERO_DATE mode to prohibit that value. A similar problem occurred for DATETIME columns. (Bug#27507)

ALTER TABLE ... ENABLE KEYS could cause mysqld to crash when executed on a table containing on a MyISAM table containing billions of rows. (Bug#27029)

Binary logging of prepared statements could produce syntactically incorrect queries in the binary log, replacing some parameters with variable names rather than variable values. This could lead to incorrect results on replication slaves. (Bug#26842, Bug#12826)

Binary content 0x00 in a BLOB column sometimes became 0x5C 0x00 following a dump and reload, which could cause problems with data using multi-byte character sets such as GBK (Chinese). This was due to a problem with SELECT INTO OUTFILE whereby LOAD DATA later incorrectly interpreted 0x5C as the second byte of a multi-byte sequence rather than as the SOLIDUS (“\”) character, used by MySQL as the escape character. (Bug#26711)

Connections from one mysqld server to another failed on Mac OS X, affecting replication and FEDERATED tables. (Bug#26664)

See also Bug#29083

The server crashed when attempting to open a table having a #mysql50# prefix in the database or table name. The server now will not open such tables. (This prefix is reserved by mysql_upgrade for accessing 5.0 tables that have names not yet encoded for 5.1.) (Bug#26402)

A FLUSH TABLES WITH READ LOCK statement followed by a FLUSH LOGS statement caused a deadlock if the general log or the slow query log was enabled. (Bug#26380)

The query SELECT /*2*/ user, host, db, info FROM INFORMATION_SCHEMA.PROCESSLIST WHERE (command!='Daemon' || user='event_scheduler') AND (info IS NULL OR info NOT LIKE '%processlist%') ORDER BY INFO yielded inconsistent results. (Bug#26338)

For a given user variable @v, the statements SELECT @v and CREATE TABLE ... AS SELECT @v did not return the same data type. (Bug#26277)

Statements within triggers ignored the value of the low_priority_updates system variable. (Bug#26162)

See also Bug#29963

The embedded server library displayed error messages at startup if the mysql.plugin table was not present. This no longer occurs. (Bug#25800)

On Windows, an application that called mysql_thread_init() but forgot to call mysql_thread_end() would get this error: Error in my_thread_global_end(). (Bug#25621)

Embedded /* ... */ comments were handled incorrectly within the definitions of stored programs and views, resulting in malformed definitions (the trailing */ was stripped). This also affected binary log contents. (Bug#25411, Bug#26302)

Due to a race condition, executing FLUSH PRIVILEGES in one thread could cause brief table unavailability in other threads. (Bug#24988)

In SHOW SLAVE STATUS output, Last_Errno and Last_Error were not set after master_retry_count errors had occurred. To provide additional information, the statement now displays four additional columns:

Also, Last_Errno and Last_Error now are aliases for Last_SQL_Errno and Last_SQL_Error. (Bug#24954)

A too-long shared-memory-base-name value could cause a buffer overflow and crash the server or clients. (Bug#24924)

On some Linux distributions where LinuxThreads and NPTL glibc versions both are available, statically built binaries can crash because the linker defaults to LinuxThreads when linking statically, but calls to external libraries (such as libnss) are resolved to NPTL versions. This cannot be worked around in the code, so instead if a crash occurs on such a binary/OS combination, print an error message that provides advice about how to fix the problem. (Bug#24611)

A number of SHOW statements caused mysqld to crash on recent versions of Solaris. This issue is believed to be present only in MySQL 5.1.12 and later. (Bug#23810)

The server deducted some bytes from the key_cache_block_size option value and reduced it to the next lower 512 byte boundary. The resulting block size was not a power of two. Setting the key_cache_block_size system variable to a value that is not a power of two resulted in MyISAM table corruption. (Bug#23068, Bug#28478, Bug#25853)

Conversion errors could occur when constructing the condition for an IN predicate. The predicate was treated as if the affected column contains NULL, but if the IN predicate is inside NOT, incorrect results could be returned. (Bug#22855)

When using transactions and replication, shutting down the master in the middle of a transaction would cause all slaves to stop replicating. (Bug#22725)

Linux binaries were unable to dump core after executing a setuid() call. (Bug#21723)

Stack overflow caused server crashes. (Bug#21476)

Using CREATE TABLE LIKE ... would raise an assertion when replicated to a slave. (Bug#18950)

The server was ignoring the return value of the parse() function for full-text parser plugins. (Bug#18839)

Granting access privileges to an individual table where the database or table name contained an underscore would fail. (Bug#18660)

The -lmtmalloc library was removed from the output of mysql_config on Solaris, as it caused problems when building DBD::mysql (and possibly other applications) on that platform that tried to use dlopen() to access the client library. (Bug#18322)

The check-cpu script failed to detect AMD64 Turion processors correctly. (Bug#17707)

When using mysqlbinlog with --read-from-remote-server to load the data direct from a remote MySQL server would cause a core dump when dumping certain binary log events. (Bug#17654)

Trying to shut down the server following a failed LOAD DATA INFILE caused mysqld to crash. (Bug#17233)

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)

Using up-arrow for command-line recall in mysql could cause a segmentation fault. (Bug#10218)

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

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; used ALTER TABLE to change a table's current AUTO_INCREMENT value; created indexes on utf8 columns.

Re-execution of CREATE DATABASE, CREATE TABLE, and ALTER TABLE statements in stored routines or as prepared statements also caused incorrect results or crashes. (Bug#4968, Bug#6895, Bug#19182, Bug#19733, Bug#22060, Bug#24879)

Last_IO_Error: A description of the last error that caused the I/O thread to stop

Last_IO_Errno: The number of the last error that caused the I/O thread to stop

Last_SQL_Error: A description of the last error that caused the SQL thread to stop

Last_SQL_Errno: The number of the last error that caused the SQL thread to stop

Incompatible Change: INSERT DELAYED is now downgraded to a normal INSERT if the statement uses functions that access tables or triggers, or that is called from a function or a trigger.

This was done to resolve the following interrelated issues:

(Bug#21483)

See also Bug#20497, Bug#21714

MySQL Cluster: Formerly, restoring a cluster backup made on a MySQL 5.0 Cluster to a 5.1 cluster using a 5.1 version of ndb_restore did not resize VARCHAR columns as might be expected; now, the default behavior of ndb_restore in such cases is to resize the VARCHAR columns. This changed default behavior can be overridden using the --no-upgrade (or -u) option when invoking ndb_restore. (Bug#22240)

The BLACKHOLE storage engine now supports INSERT DELAYED. Previously, INSERT DELAYED statements for BLACKHOLE tables were not supported, and caused the server to crash. (Bug#27998)

A new status variable, Com_call_procedure, indicates the number of calls to stored procedures. (Bug#27994)

The BLACKHOLE storage engine now supports LOCK TABLES and UNLOCK TABLES. (Bug#26241)

GLOBAL_STATUS

GLOBAL_VARIABLES

SESSION_VARIABLES

The data type used for the VARIABLE_VALUE column of the following INFORMATION_SCHEMA tables has been changed to VARCHAR:

For more information, see Section 22.24, “The INFORMATION_SCHEMA GLOBAL_STATUS and SESSION_STATUS Tables”, Section 22.25, “The INFORMATION_SCHEMA GLOBAL_VARIABLES and SESSION_VARIABLES Tables”.

See also Bug#26994

SESSION_STATUS

Security Fix: UDFs are supposed to be loadable only from the plugin directory, but this restriction was not being enforced. (Bug#28341)

Security Fix: Use of a view could allow a user to gain update privileges for tables in other databases. (Bug#27878, CVE-2007-3782)

MySQL Cluster: When an API node sent more than 1024 signals in a single batch, NDB would process only the first 1024 of these, and then hang. (Bug#28443)

MySQL Cluster: A delay in obtaining AUTO_INCREMENT IDs could lead to excess temporary errors. (Bug#28410)

MySQL Cluster: Local checkpoint files relating to dropped NDB tables were not removed. (Bug#28348)

MySQL Cluster: Multiple operations involving deletes followed by reads were not handled correctly.

(Bug#28276)

MySQL Cluster: Repeated insertion of data generated by mysqldump into NDB tables could eventually lead to failure of the cluster. (Bug#27437)

MySQL Cluster: Restarting a data node caused SQL nodes to log repeatedly and unnecessarily the status of the event buffer.

(This issue was known to occur in MySQL 5.1.16 and later only.) (Bug#27292)

MySQL Cluster: ndb_mgmd failed silently when the cluster configuration file contained invalid [tcp] entries. (Bug#27207)

MySQL Cluster: ndb_connectstring did not appear in the output of SHOW VARIABLES. (Bug#26675)

MySQL Cluster: A failure to release internal resources following an error could lead to problems with single user mode. (Bug#25818)

MySQL Cluster: DDL operations were not supported on a partially started cluster. (Bug#24631)

Disk Data: Extremely large inserts into Disk Data tables could lead to data node failure in some circumstances. (Bug#27942)

Cluster API: In a multi-operation transaction, a delete operation followed by the insertion of an implicit NULL failed to overwrite an existing value. (Bug#20535)

Some ALTER TABLE statements that worked in MySQL 5.0 did not work in 5.1. (Bug#28415)

mysql_upgrade failed if certain SQL modes were set. Now it sets the mode itself to avoid this problem. (Bug#28401)

A query with a NOT IN subquery predicate could cause a crash when the left operand of the predicate evaluated to NULL. (Bug#28375)

A buffer overflow could occur when using DECIMAL columns on Windows operating systems. (Bug#28361)

libmysql.dll could not be dynamically loaded on Windows. (Bug#28358)

Grouping queries with correlated subqueries in WHERE conditions could produce incorrect results. (Bug#28337)

EXPLAIN for a query on an empty table immediately after its creation could result in a server crash. (Bug#28272)

Comparing a DATETIME column value with a user variable yielded incorrect results. (Bug#28261)

Portability problems caused by use of isinf() were corrected. (Bug#28240)

When dumping procedures, mysqldump --compact generated output that restored the session variable SQL_MODE without first capturing it. When dumping routines, mysqldump --compact neither set nor retrieved the value of SQL_MODE. (Bug#28223)

Comparison of the string value of a date showed as unequal to CURTIME(). Similar behavior was exhibited for DATETIME values. (Bug#28208)

For InnoDB, in some rare cases the optimizer preferred a more expensive ref access to a less expensive range access. (Bug#28189)

Comparisons of DATE or DATETIME values for the IN() function could yield incorrect results. (Bug#28133)

It was not possible to use the value –9223372036854775808 (that is, –MAXVALUE + 1) when specifying a LIST partition. (Bug#28005)

The server could hang for INSERT IGNORE ... ON DUPLICATE KEY UPDATE if an update failed. (Bug#28000)

CAST() to DECIMAL did not check for overflow. (Bug#27957)

The second execution of a prepared statement from a UNION query with ORDER BY RAND() caused the server to crash. This problem could also occur when invoking a stored procedure containing such a query. (Bug#27937)

Views ignored precision for CAST() operations. (Bug#27921)

Changes to some system variables should invalidate statements in the query cache, but invalidation did not happen. (Bug#27792)

LOAD DATA did not use CURRENT_TIMESTAMP as the default value for a TIMESTAMP column for which no value was provided. (Bug#27670)

Selecting MIN() on an indexed column that contained only NULL values caused NULL to be returned for other result columns. (Bug#27573)

Using a TEXT local variable in a stored routine in an expression such as SET var = SUBSTRING(var, 3) produced an incorrect result. (Bug#27415)

The error message for error number 137 did not report which database/table combination reported the problem. (Bug#27173)

A large filesort could result in a division by zero error and a server crash. (Bug#27119)

Some InnoDB variables were missing from the output of mysqld --verbose --help. (Bug#26987)

Flow control optimization in stored routines could cause exception handlers to never return or execute incorrect logic. (Bug#26977)

Some test suite files were missing from some MySQL-test packages. (Bug#26609)

Running CHECK TABLE concurrently with a SELECT, INSERT or other statement on Windows could corrupt a MyISAM table. (Bug#25712)

Concurrent execution of CREATE TABLE ... SELECT and other statements involving the target table suffered from various race conditions, some of which might have led to deadlocks. (Bug#24738)

An attempt to execute CREATE TABLE ... SELECT when a temporary table with the same name already existed led to the insertion of data into the temporary table and creation of an empty non-temporary table. (Bug#24508)

A statement of the form CREATE TABLE IF NOT EXISTS t1 SELECT f1() AS i failed with a deadlock error if the stored function f1() referred to a table with the same name as the to-be-created table. Now it correctly produces a message that the table already exists. (Bug#22427)

Quoted labels in stored routines were mishandled, rendering the routines unusable. (Bug#21513)

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)

CREATE TABLE IF NOT EXISTS ... SELECT caused a server crash if the target table already existed and had a BEFORE INSERT trigger. (Bug#20903)

Deadlock occurred for attempts to execute CREATE TABLE IF NOT EXISTS ... SELECT when LOCK TABLES had been used to acquire a read lock on the target table. (Bug#20662, Bug#15522)

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)

Changing the size of a key buffer that is under heavy use could cause a server crash. The fix partially removes the limitation that LOAD INDEX INTO CACHE fails unless all indexes in a table have the same block size. Now the statement fails only if IGNORE LEAVES is specified. (Bug#17332)

Incompatible Change: MySQL Cluster: The internal specifications for columns in NDB tables has changed to allow compatibility with future MySQL Cluster releases that are expected to implement online adding and dropping of columns. This change is not backward compatible with earlier MySQL versions.

See the related note in Section 15.5.2, “Cluster Upgrade and Downgrade Compatibility”, for important information prior to upgrading a MySQL Cluster to MySQL 5.1.18 or later from MySQL 5.1.17 or earlier.

See also Bug#28205

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, “Cluster Upgrade and Downgrade Compatibility” before upgrading for details.

For more information about the changes to mysql.ndb_apply_status see Section 15.10.4, “Cluster Replication Schema and Tables”.

Incompatible Change: The INFORMATION_SCHEMA.EVENTS and mysql.event tables have been changed to facilitate replication of events. When upgrading to MySQL 5.1.18, you must run mysql_upgrade prior to working with events. Until you have done so, any statement relating to the Event Scheduler or these tables (including SHOW EVENTS) will fail with the errors Expected field status at position 12 to have type enum ('ENABLED','SLAVESIDE_DISABLED','DISABLED'), found enum('ENABLED','DISABLED') and Table mysql.event is damaged. Can not open.

These changes were made as part of fixes for the following bugs:

For more information, see Section 14.3.1.5, “Replication of Invoked Features”. (Bug#17857, Bug#16421, Bug#20384, Bug#17671)

MySQL 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”. (Bug#26899, Bug#26900)

MySQL Cluster: The following changes were made in the ndb_size.pl utility:

(Bug#24227, Bug#24228)

Cluster Replication: Some circular replication setups are now supported for MySQL Cluster. See Section 15.10.3, “Known Issues in MySQL Cluster Replication”, for detailed information. (Bug#17095, Bug#25688)

Cluster API: The MGM API now supports explicit setting of network timeouts using the ndb_mgm_set_timeout() function. A utility function ndb_mgm_number_of_mgmd_in_connect_string() is also implemented to facilitate calculation of timeouts based on the number of management servers in the cluster.

For more information, see ndb_mgm_set_timeout(), and ndb_mgm_number_of_mgmd_in_connect_string().

Prior to this release, when DATE values were compared with DATETIME values the time portion of the DATETIME value was ignored. Now a DATE value is coerced to the DATETIME type by adding the time portion as “00:00:00”. To mimic the old behavior use the CAST() function in the following way: SELECT date_field = CAST(NOW() as DATE);. (Bug#28929)

mysqld_multi now understands the --no-defaults, --defaults-file, and --defaults-extra-file options. The --config-file option is deprecated; if given, it is treated like --defaults-extra-file. (Bug#27390)

If a set function S with an outer reference S(outer_ref) cannot be aggregated in the outer query against which the outer reference has been resolved, MySQL interprets S(outer_ref) the same way that it would interpret S(const). However, standard SQL requires throwing an error in this situation. An error now is thrown for such queries if the ANSI SQL mode is enabled. (Bug#27348)

Several additional data types are supported for columns in INFORMATION_SCHEMA tables: DATE, TIME, BLOB, FLOAT, and all integer types. (Bug#27047)

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

If you use SSL for a client connection, you can tell the client not to authenticate the server certificate by specifying neither --ssl-ca nor --ssl-capath. The server still verifies the client according to any applicable requirements established via GRANT statements for the client, and it still uses any --ssl-ca/--ssl-capath values that were passed to server at startup time. (Bug#25309)

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)

Added the --auto-generate-sql-add-auto-increment, --auto-generate-sql-execute-number, --auto-generate-sql-guid-primary, --auto-generate-sql-secondary-indexes, --auto-generate-sql-unique-query-number, --auto-generate-sql-unique-write-number, --post-query,, and --pre-query, options for mysqlslap. Removed the --lock-directory, --slave, and --use-threads options.

See also Bug#28521

Added --write-binlog option for mysqlcheck. This option is enabled by default, but can be given as --skip-write-binlog to cause ANALYZE TABLE, OPTIMIZE TABLE, and REPAIR TABLE statements generated by mysqlcheck not to be written to the binary log. (Bug#26262)

New command-line options: To alleviate ambiguities in variable names, all variables related to plugins can be specified using a plugin part in the name. For example, every time where we used to have innodb in the command-line options, you can now write plugin-innodb:

--skip-plugin-innodb
--plugin-innodb-buffer-pool-size=#

Furthermore, this is the preferred syntax. It helps to avoid ambiguities when a plugin, say, wait, has an option called timeout. --wait-timeout will still set a system variable, but --plugin-wait-timeout will set the plugin variable. Also, there is a new command-line option --plugin-load to install or load plugins at initialization time without using the mysql.plugin table.

The plugin interface and its handling of system variables was changed. Command-line options such as --skip-innodb now cause an error if InnoDB is not built-in or plugin-loaded. You should use --loose-skip-innodb if you do not want any error even if InnoDB is not available. The --loose prefix modifier should be used for all command-line options where you are uncertain whether the plugin exists and when you want the operation to proceed even if the option is necessarily ignored due to the absence of the plugin. (For a desecription of how --loose works, see Section 4.2.2.1, “Using Options on the Command Line”.)

Storage engine plugins may now be uninstalled at run time. However, a plugin is not actually uninstalled until after its reference count drops to zero. The default_storage_engine system variable consumes a reference count, so uninstalling will not complete until said reference is removed.

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.

Security Fix: The requirement of the DROP privilege for RENAME TABLE was not enforced. (Bug#27515, CVE-2007-2691)

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

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, CVE-2007-2693)

MySQL Cluster: The cluster waited 30 seconds instead of 30 milliseconds before reading table statistics. (Bug#28093)

MySQL Cluster: Under certain rare circumstances, ndbd could get caught in an infinite loop when one transaction took a read lock and then a second transaction attempted to obtain a write lock on the same tuple in the lock queue. (Bug#28073)

MySQL Cluster: Under some circumstances, a node restart could fail to update the Global Checkpoint Index (GCI). (Bug#28023)

MySQL Cluster: INSERT IGNORE wrongly ignored NULL values in unique indexes. (Bug#27980)

MySQL Cluster: The name of the month “March” was given incorrectly in the cluster error log. (Bug#27926)

MySQL 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)

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