Released on 30 Mar 2008
MySQL 5.0.56sp1 Changelog

This is a Service Pack release of the MySQL Enterprise Server 5.0.

This section documents all changes and bugfixes that have been applied in MySQL 5.0.56sp1 since the previous MySQL Enterprise Server Quarterly Service Pack release (5.0.50sp1a). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see

  • Functionality Added or Changed

  • Bugs Fixed

Functionality Added or Changed

  • 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)

  • The mysql_odbc_escape_string() C API function has been removed. It has multibyte 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)

    References: See also Bug #41728.

  • 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)

  • The argument for the --do-test and --skip-test options is now interpreted as a Perl regular expression if there is a pattern metacharacter in the argument value. This enables more flexible specification of which tests to perform or skip.

  • The use of InnoDB hash indexes now can be controlled by setting the new innodb_adaptive_hash_index system variable at server startup. By default, this variable is enabled. See Adaptive Hash Indexes.

Bugs Fixed

  • 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 enable that user to gain the access rights of the view. Now ALTER VIEW is permitted only to the original definer or users with the SUPER privilege. (Bug #29908)

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

  • Security Enhancement: It was possible to force an error message of excessive length which could lead to a buffer overflow. This has been made no longer possible as a security precaution. (Bug #32707)

  • Performance: InnoDB had a race condition for an adaptive hash rw-lock waiting for an X-lock. This fix may also provide significant speed improvements on systems experiencing problems with contention for the adaptive hash index. (Bug #29560)

  • Incompatible Change: 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.

    This fix results in the following behavior:

    • There is a check against mixing group and nongroup columns only when ONLY_FULL_GROUP_BY is enabled.

    • This check is done both for the select list and for the HAVING clause if there is one.

    This behavior differs from previous versions as follows:

    • Previously, the HAVING clause was not checked when ONLY_FULL_GROUP_BY was enabled; now it is checked.

    • Previously, the select list was checked even when ONLY_FULL_GROUP_BY was not enabled; now it is checked only when ONLY_FULL_GROUP_BY is enabled.

    (Bug #31794)

  • Incompatible Change: The MySQL 5.0.50 patch for this bug was reverted because it changed the behavior of a General Availability MySQL release. (Bug #30234)

    References: See also Bug #27525.

  • Incompatible Change: It was possible to create a view having a column whose name consisted of an empty string or space characters only.

    One result of this bug fix is that aliases for columns in the view SELECT statement are checked to ensure that they are legal column names. In particular, the length must be within the maximum column length of 64 characters, not the maximum alias length of 256 characters. This can cause problems for replication or loading dump files. For additional information and workarounds, see Restrictions on Views. (Bug #27695)

    References: See also Bug #31202.

  • Incompatible Change: Several type-preserving functions and operators returned an incorrect result type that does not match their argument types: COALESCE(), IF(), IFNULL(), LEAST(), GREATEST(), CASE. These now aggregate using the precise SQL types of their arguments rather than the internal type. In addition, the result type of the STR_TO_DATE() function is now DATETIME by default. (Bug #27216)

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

    The fix for this problem had a side effect such that on Unix, MySQL programs looked for options in ~/my.cnf rather than the standard location of ~/.my.cnf. That problem is addressed in Bug #38180. (Bug #20748)

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

    • The AUTO_INCREMENT counter was not updated correctly when such a column was updated.

    • AUTO_INCREMENT values were not prefetched beyond statement boundaries.

    • AUTO_INCREMENT values were not handled correctly with INSERT IGNORE statements.

    • After being set, ndb_autoincrement_prefetch_sz showed a value of 1, regardless of the value it had actually been set to.

    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)

  • Important Change; Replication: When the master crashed during an update on a transactional table while in autocommit mode, the slave failed. This fix causes every transaction (including autocommit transactions) to be recorded in the binary log as starting with a BEGIN and ending with a COMMIT or ROLLBACK.


    The current fix does not cause nontransactional changes to be wrapped in BEGIN ... COMMIT or BEGIN ... ROLLBACK when written to the binary log. For this purpose, any statements affecting tables using a nontransactional storage engine such as MyISAM are regarded as nontransactional, even when autocommit is enabled.

    (Bug #26395)

    References: See also Bug #29288, Bug #49522.

  • Important Note; Replication: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet. If you experience reliability issues and see many You have an error in your SQL syntax errors on replication slaves, we strongly recommend that you upgrade to a MySQL version which includes this fix. (Bug #26489)

  • 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: The failure of a master node could lead to subsequent failures in local checkpointing. (Bug #32160)

  • MySQL Cluster: An uninitialized variable in the NDB storage engine code led to AUTO_INCREMENT failures when the server was compiled with gcc 4.2.1. (Bug #31848)

    References: This bug was introduced by Bug #27437.

  • MySQL Cluster: An error with an if statement in sql/ 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: Primary keys on variable-length columns (such as VARCHAR) did not work correctly. (Bug #31635)

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

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

  • 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: 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: When inserting a row into an NDB table with a duplicate value for a nonprimary unique key, the error issued would reference the wrong key.

    This improves on an initial fix for this issue made in MySQL 5.0.30 and MySQL 5.0.33 (Bug #21072)

  • Replication: A CREATE USER, DROP USER, or RENAME USER statement that fails on the master, or that is a duplicate of any of these statements, is no longer written to the binary log; previously, either of these occurrences could cause the slave to fail. (Bug #33862)

    References: See also Bug #29749.

  • Replication: SHOW BINLOG EVENTS could fail when the binary log contained one or more events whose size was close to the value of max_allowed_packet. (Bug #33413)

  • Replication: SQL statements containing comments using -- syntax were not replayable by mysqlbinlog, even though such statements replicated correctly. (Bug #32205)

  • 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)

    References: See also Bug #28597.

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

  • Replication: 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)

  • Replication: Issuing a DROP VIEW statement caused replication to fail if the view did not actually exist. (Bug #30998)

  • 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: Replication of LOAD DATA INFILE could fail when read_buffer_size was larger than max_allowed_packet. (Bug #30435)

  • Replication: Setting server_id did not update its value for the current session. (Bug #28908)

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

    References: See also Bug #31836. This bug 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: An UPDATE statement using a stored function that modified a nontransactional table was not logged if it failed. This caused the copy of the nontransactional table on the master have a row that the copy on the slave did not.

    In addition, when an INSERT ... ON DUPLICATE KEY UPDATE statement encountered a duplicate key constraint, but the UPDATE did not actually change any data, the statement was not logged. As a result of this fix, such statements are now treated the same for logging purposes as other UPDATE statements, and so are written to the binary log. (Bug #23333)

    References: 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)

    References: See also Bug #13963, Bug #21869.

  • The server crashed when executing a query that had a subquery containing an equality X=Y where Y referred to a named select list expression from the parent select. The server crashed when trying to use the X=Y equality for ref-based access. (Bug #33794)

  • Use of uninitialized memory for filesort in a subquery caused a server crash. (Bug #33675)

  • The server could crash when REPEAT or another control instruction was used in conjunction with labels and a LEAVE instruction. (Bug #33618)

  • The parser permitted control structures in compound statements to have mismatched beginning and ending labels. (Bug #33618)

  • SET GLOBAL myisam_max_sort_file_size=DEFAULT set myisam_max_sort_file_size to an incorrect value. (Bug #33382)

    References: See also Bug #31177.

  • CREATE TABLE ... SELECT created tables that for date columns used the obsolete Field_date type instead of Field_newdate. (Bug #33256)

  • For DECIMAL columns used with the ROUND(X,D) or TRUNCATE(X,D) function with a nonconstant value of D, adding an ORDER BY for the function result produced misordered output. (Bug #33143)

    References: See also Bug #33402, Bug #30617.

  • Some valid SELECT statements could not be used as views due to incorrect column reference resolution. (Bug #33133)

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

  • UNION constructs cannot contain SELECT ... INTO except in the final SELECT. However, if a UNION was used in a subquery and an INTO clause appeared in the top-level query, the parser interpreted it as having appeared in the UNION and raised an error. (Bug #32858)

  • The correct data type for a NULL column resulting from a UNION could be determined incorrectly in some cases: 1) Not correctly inferred as NULL depending on the number of selects; 2) Not inferred correctly as NULL if one select used a subquery. (Bug #32848)

  • An ORDER BY query using IS NULL in the WHERE clause did not return correct results. (Bug #32815)

  • For queries containing GROUP_CONCAT(DISTINCT col_list ORDER BY col_list), there was a limitation that the DISTINCT columns had to be the same as ORDER BY columns. Incorrect results could be returned if this was not true. (Bug #32798)

  • The LAST_DAY() function returns a DATE value, but internally the value did not have the time fields zeroed and calculations involving the value could return incorrect results. (Bug #32770)

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

  • A subquery using an IS NULL check of a column defined as NOT NULL in a table used in the FROM clause of the outer query produced an invalid result. (Bug #32694)

  • Specifying a nonexistent 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)

    References: See also Bug #31095.

  • A SELECT ... GROUP BY bit_column query failed with an assertion if the length of the BIT column used for the GROUP BY was not an integer multiple of 8. (Bug #32556)

  • Using SELECT INTO OUTFILE with 8-bit ENCLOSED BY characters led to corrupted data when the data was reloaded using LOAD DATA INFILE. This was because SELECT INTO OUTFILE failed to escape the 8-bit characters. (Bug #32533)

  • 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)

  • A build problem introduced in MySQL 5.0.52 was resolved: The x86 32-bit Intel icc-compiled server binary had unwanted dependences on Intel icc runtime libraries. (Bug #32514)

  • 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)

  • Repeated execution of a query containing a CASE expression and numerous AND and OR relations could crash the server. The root cause of the issue was determined to be that the internal SEL_ARG structure was not properly initialized when created. (Bug #32403)

  • Referencing within a subquery an alias used in the SELECT list of the outer query was incorrectly permitted. (Bug #32400)

  • An ORDER BY query on a view created using a FEDERATED table as a base table caused the server to crash. (Bug #32374)

  • Comparison of a BIGINT NOT NULL column with a constant arithmetic expression that evaluated to NULL mistakenly caused the error Column '...' cannot be null (error 1048). (Bug #32335)

  • 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)

  • MIN() and MAX() could return incorrect results when an index was present if a loose index scan was used. (Bug #32268)

  • Memory corruption could occur due to large index map in Range checked for each record status reported by EXPLAIN SELECT. The problem was based in an incorrectly calculated length of the buffer used to store a hexadecimal representation of an index map, which could result in buffer overrun and stack corruption under some circumstances. (Bug #32241)

  • 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, 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)

  • 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)

  • With lower_case_table_names set, CREATE TABLE LIKE was treated differently by libmysqld than by the nonembedded 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)

  • 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)

  • HOUR(), MINUTE(), and SECOND() could return nonzero values for DATE arguments. (Bug #31990)

  • A column with malformed multibyte characters could cause the full-text parser to go into an infinite loop. (Bug #31950)

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

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

  • sometimes set up test scenarios in which the same port number was passed to multiple servers, causing one of them to be unable to start. (Bug #31880)

  • 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)

  • Name resolution for correlated subqueries and HAVING clauses failed to distinguish which of two was being performed when there was a reference to an outer aliased field. This could result in error messages about a HAVING clause for queries that had no such clause. (Bug #31797)

  • 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 a filesort in find_all_keys(), the error was returned without the necessary handler uninitialization, causing an assertion failure. (Bug #31742)

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

  • 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 nonreloadable 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)

  • 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)

  • 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)

  • Killing a CREATE TABLE ... LIKE statement that was waiting for a name lock caused a server crash. When the statement was killed, the server attempted to release locks that were not held. (Bug #31479)

  • 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)

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

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

  • 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)

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

  • 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) failed 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)

  • Server variables could not be set to their current values on Linux platforms. (Bug #31177)

    References: See also Bug #6958.

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

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

  • Full-text searches on ucs2 columns caused a server crash. (FULLTEXT indexes on ucs2 columns cannot be used, but it should be possible to perform IN BOOLEAN MODE searches on ucs2 columns without a crash.) (Bug #31159)

  • Data in BLOB or GEOMETRY columns could be cropped when performing a UNION query. (Bug #31158)

  • An assertion designed to detect a bug in the ROLLUP implementation would incorrectly be triggered when used in a subquery context with noncacheable 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)

  • MySQL declares a UNIQUE key as a PRIMARY key if it doesn't have NULL columns and is not a partial key, and the PRIMARY key must alway be the first key. However, in some cases, a nonfirst key could be reported as PRIMARY, leading to an assert failure by InnoDB. This is fixed by correcting the key sort order. (Bug #31137)

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

    References: See also Bug #32558.

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

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

  • Many nested subqueries in a single query could led to excessive memory consumption and possibly a crash of the server. (Bug #31048)

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

  • 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)

  • 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 to 200 range into the 1970 to 2069 range. (This is legitimate for 00 to 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)

  • ROUND(X,D) or TRUNCATE(X,D) for nonconstant values of D could crash the server if these functions were used in an ORDER BY that was resolved using filesort. (Bug #30889)

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

  • Calling NAME_CONST() with nonconstant arguments triggered an assertion failure. Nonconstant arguments are no longer permitted. (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)

  • The optimizer incorrectly optimized conditions out of the WHERE clause in some queries involving subqueries and indexed columns. (Bug #30788)

  • 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)

  • A multiple-table UPDATE involving transactional and nontransactional tables caused an assertion failure. (Bug #30763)

  • 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 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)

  • MyISAM tables could not exceed 4294967295 (232 - 1) rows on Windows. (Bug #30638)

  • could not run mysqld with root privileges. (Bug #30630)

  • 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)

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

  • 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)

  • For CREATE ... SELECT ... FROM, where the resulting table contained indexes, adding SQL_BUFFER_RESULT to the SELECT part caused index corruption in the table. (Bug #30384)

  • The optimizer made incorrect assumptions about the value of the is_member value for user-defined functions, sometimes resulting in incorrect ordering of UDF results. (Bug #30355)

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

  • Simultaneous ALTER TABLE statements for BLACKHOLE tables caused 100% CPU use due to locking problems. (Bug #30294)

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

  • Tables with a GEOMETRY column could be marked as corrupt if you added a non-SPATIAL index on a GEOMETRY column. (Bug #30284)

  • 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)

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

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

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

  • Views were treated as insertable even if some base table columns with no default value were omitted from the view definition. (This is contrary to the condition for insertability that a view must contain all columns in the base table that do not have a default value.) (Bug #29477)

  • 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 can be accessed in expressions and attempting to set their values produces an error message that the variable is read only. (Bug #29131)

  • Denormalized double-precision numbers cannot be handled properly by old MIPS processors. For IRIX, this is now handled by enabling a mode to use a software workaround. (Bug #29085)

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

  • When doing a DELETE on a table that involved a JOIN with MyISAM or MERGE tables and the JOIN referred to the same table, the operation could fail reporting ERROR 1030 (HY000): Got error 134 from storage engine. This was because scans on the table contents would change because of rows that had already been deleted. (Bug #28837)

  • 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 no longer permitted. (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)

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

  • 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)

  • 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)

  • An ORDER BY at the end of a UNION affected individual SELECT statements rather than the overall query result. (Bug #27848)

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

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

  • A race condition between killing a statement and the thread executing the statement could lead to a situation such that the binary log contained an event indicating that the statement was killed, whereas the statement actually executed to completion. (Bug #27571)

  • 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 permitted to users who did not have the SUPER privilege. (Bug #27440)

  • resolveip failed to produce correct results for host names that begin with a digit. (Bug #27427)

  • 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)

    References: See also Bug #12860.

  • mysqlcheck -A -r did not correctly identify all tables that needed repairing. (Bug #25347)

  • 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)

  • For Windows Vista, MySQLInstanceConfig.exe did not include a proper manifest enabling it to run with administrative privileges. (Bug #22563)

    References: See also Bug #24732.

  • mysqldumpslow returned a confusing error message when no configuration file was found. (Bug #20455)

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

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

  • 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 using the --with-tcp-port configuration option. (Bug #15327)

  • Zero-padding of exponent values was not the same across platforms. (Bug #12860)

  • 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)

  • 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)

  • If an INSERT ... SELECT statement is executed, and no automatically generated value is successfully inserted, then mysql_insert_id() returns the ID of the last inserted row.

    If no automatically generated value is successfully inserted, then mysql_insert_id() returns 0. (Bug #9481)

  • 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:

    • For key_buffer_size, values larger than 4GB are permitted on 64-bit platforms (except Windows, for which large values are truncated to 4GB with a warning).

    • For join_buffer_size, sort_buffer_size, and myisam_sort_buffer_size, values are limited to 4GB on all platforms. Larger values are truncated to 4GB with a warning.

    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 nonempty 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)