Appendix E. MySQL Enterprise Release Notes
Prev |  | Next

## Appendix E. MySQL Enterprise Release Notes

This appendix lists the changes from version to version in MySQL Enterprise, including MySQL Enterprise Server. Releases in MySQL Enterprise Server are divided into the following release packs:

- Rapid Update Service Packs are issued once a month and incorporate all the bug fixes and security updates introduced since the previous MySQL Enterprise Server release. A single Service Pack can be used to update MySQL Enterprise Server; it is not necessary to install intervening service packs to bring your system up to date.

- Quarterly Service Packs are issued each quarter and incorporate all the bug fixes and security updates introduced since the previous MySQL Enterprise Server release. A single Service Pack can be used to update MySQL Enterprise Server; it is not necessary to install intervening service packs to bring your system up to date.

- Hot-fix releases incorporate fixes for bugs that caused significant issues that are not released as part of a Service Pack.

The Release Notes are updated as bugs are fixed and features are incorporated, so that everybody can follow the development process.

Note that we tend to update the manual at the same time we make changes to MySQL. If you find a recent version of MySQL listed here that you can't find on our download page (http://dev.mysql.com/downloads/), it means that the version has not yet been released (and will normally be marked so in the appropriate Release Note section).

The date mentioned with a release version is the date of the last change done internally at MySQL AB (the BitKeeper ChangeSet) on which the release was based, not the date when the packages were made available. The binaries are usually made available a few days after the date of the tagged ChangeSet, because building and testing all packages takes some time.

For information on how to determine your current version and release type, see Section 2.2, “Determining your current MySQL version”.

## E.1. MySQL Enterprise 5.0 Release Notes

This section documents all changes and bug fixes as of the first MySQL Enterprise Server release (5.0.28) that are made available through hot-fixes, and through service packs.

For a full list of changes, please refer to the changelog sections for each individual 5.0.x release.

### E.1.1. Release Notes for MySQL Enterprise 5.0.36 (Not yet released)

This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.

This section documents all changes and bug fixes that have been applied since the last MySQL Enterprise Server release (5.0.34).

Functionality added or changed:

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

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

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

Bugs fixed:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### E.1.2. Release Notes for MySQL Enterprise 5.0.34 (17 January 2007)

This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.

This section documents all changes and bug fixes that have been applied since the last MySQL Enterprise Server release (5.0.32).

Functionality added or changed:

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

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

Bugs fixed:

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

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

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

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

- A view was not handled correctly if the `SELECT` part contained ‘`\Z`’. (Bug#24293)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### E.1.3. Release Notes for MySQL Enterprise 5.0.32 (20 December 2006)

This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.

This section documents all changes and bug fixes that have been applied since the last MySQL Enterprise Server release (5.0.30).

Functionality added or changed:

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

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

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

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

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

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

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

  (Bug#21507)

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

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

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

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

- The bundled yaSSL library was upgraded to version 1.5.0.

Bugs fixed:

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

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

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

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

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

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

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

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

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

- Foreign key identifiers for `InnoDB` tables could not contain certain characters. (Bug#24299)

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

- With `innodb_file_per_table` enabled, `InnoDB` displayed incorrect file times in the output from `SHOW TABLE STATUS`. (Bug#24712)

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

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

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

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

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

- The `InnoDB` mutex structure was simplified to reduce memory load. (Bug#24386)

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

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

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

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

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

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

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

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

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

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

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

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

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

  (Bug#22052)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- Slave servers would retry the execution of a SQL statement an infinite number of times, ignoring the value `SLAVE_TRANSACTION_RETRIES` when using the NDB engine. (Bug#16228)

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

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

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

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

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

### E.1.4. Release Notes for MySQL Enterprise 5.0.30sp1 (19 January 2007)

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

This section documents all changes and bug fixes that have been applied since the last MySQL Enterprise Server release (5.0.30).

Functionality added or changed:

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

Bugs fixed:

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

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

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

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

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

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

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

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

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

### E.1.5. Release Notes for MySQL Enterprise 5.0.30 (14 November 2006)

This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.

This section documents all changes and bug fixes that have been applied since the last MySQL Enterprise Server release (5.0.28).

Functionality added or changed:

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

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

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

  (Bug#21915)

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

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

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

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

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

- `SHOW STATUS` is no longer logged to the slow query log. (Bug#19764)

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

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

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

Bugs fixed:

- `NDB Cluster`: Data nodes added while the cluster was running in single user mode were all assigned node ID 0, which could later cause multiple node failures. Adding of nodes in single user mode is no longer possible. (Bug#20395)

- `NDB Cluster`: Attempting to create an `NDB` table on a MySQL with an existing non-Cluster table with the same name in the same database could result in data loss or corruption. MySQL now issues a warning when a `SHOW TABLES` or other statement causing table discovery finds such a table. (Bug#21378)

- `NDB Cluster` (NDB API): Inacivity timeouts for scans were not correctly handled. (Bug#23107)

- `NDB Cluster` (NDB API): Attempting to read a nonexistent tuple using `Commit` mode for `NdbTransaction::execute()` caused node failures. (Bug#22672)

- `NDB Cluster` (NDB API): Scans closed before being executed were still placed in the send queue. (Bug#21941)

- `NDB Cluster` (NDB API): The `NdbOperation::getBlobHandle()` method, when called with the name of a nonexistent column, caused a segmentation fault. (Bug#21036)

- `NDB Cluster`: A problem with takeover during a system restart caused ordered indexes to be rebuilt incorrectly. (Bug#15303)

- `NDB Cluster`: The ndb_config utility did not perform host lookups correctly when using the `--host` option. (Bug#17582)

- `NDB Cluster`: The ndb_config utility did not perform host lookups correctly when using the `--host` option (Bug#17582)

- `NDB Cluster`: The error returned by the cluster when too many nodes were defined did not make clear the nature of the problem. (Bug#19045)

- `NDB Cluster`: ndb_mgm -e show | head would hang after displaying the first 10 lines of output. (Bug#19047)

- `NDB Cluster`: In rare situations with resource shortages, a crash could result from insufficient `IndexScanOperations`. (Bug#19198)

- `NDB Cluster`: ndb_restore did not always make clear that it had recovered successfully from temporary errors while restoring a cluster backup. (Bug#19651)

- `NDB Cluster`: Error messages given when trying to make online changes parameters such as `NoOfReplicas` thast can only be changed via a complete shutdown and restart of the cluster did not indicate the true nature of the problem. (Bug#19787)

- `NDB Cluster`: Following the restart of an MGM node, the Cluster management client did not automatically reconnect. (Bug#19873)

- `NDB Cluster`: In some cases where `SELECT COUNT(*)` from an `NDB` table should have yielded an error, `MAX_INT` was returned instead. (Bug#19914)

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

- `NDB Cluster`: Using an invalid node ID with the management client `STOP` command could cause ndb_mgm to hang. (Bug#20575)

- `NDB Cluster`: Under some circumstances, local checkpointing would hang, keeping any unstarted nodes from being started. (Bug#20895)

- `NDB Cluster`: Condition pushdown did not work correctly with `DATETIME` columns. (Bug#21056)

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

- `NDB Cluster`: Cluster logs were not rotated following the first rotation cycle. (Bug#21345)

- `NDB Cluster`: The ndb_mgm management client did not set the exit status on errors, always returning 0 instead. (Bug#21530)

- `NDB Cluster`: Partition distribution keys were updated only for the primary and starting replicas during node recovery. This could lead to node failure recovery for clusters having an odd number of replicas. (Bug#21535)

  Note: We recommend values for `NumberOfReplicas` that are even powers of 2, for best results.

- `NDB Cluster`: The output for the `--help` option used with `NDB` executable programs (ndbd, ndb_mgm, ndb_restore, ndb_config, and so on) referred to the `Ndb.cfg` file, instead of `my.cnf`. (Bug#21585)

- `NDB Cluster`: The node recovery algorithm was missing a version check for tables in the `ALTER_TABLE_COMMITTED` state (as opposed to the `TABLE_ADD_COMMITTED` state, which has the version check). This could cause inconsistent schemas across nodes following node recovery. (Bug#21756)

- `NDB Cluster`: A scan timeout returned Error 4028 (Node failure caused abort of transaction) instead of Error 4008 (Node failure caused abort of transaction...). (Bug#21799)

- `NDB Cluster`: The `--help` output from `NDB` binaries did not include file-related options. (Bug#21994)

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

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

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

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

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

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

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

- The internal SQL interpreter of `InnoDB` placed an unnecessary lock on the supremum record when `innodb_locks_unsafe_for_binlog=1`. This caused an assertion failure when `InnoDB` was built with debugging enabled. (Bug#23769)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- `InnoDB` exhibited thread thrashing with more than 50 concurrent connections under an update-intensive workload. (Bug#22868)

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

- There was a race condition in the `InnoDB` `fil_flush_file_spaces()` function. (Bug#24089)

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

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

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

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

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

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

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

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

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

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

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

- MySQL would fail to build on the Alpha platform. (Bug#23256)

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

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

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

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

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

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

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

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

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

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

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

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

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

- Selecting from a `MERGE` table could result in a server crash if the underlying tables had fewer indexes than the `MERGE` table itself. (Bug#22937)

- A locking safety check in `InnoDB` reported a spurious error `stored_select_lock_type is 0 inside ::start_stmt()` for `INSERT ... SELECT` statements in `innodb_locks_unsafe_for_binlog` mode. The safety check was removed. (Bug#10746)

- For multiple-table `UPDATE` statements, storage engines were not notified of duplicate-key errors. (Bug#21381)

- Incorrect results could be obtained from re-execution of a parametrized prepared statement or a stored routine with a `SELECT` that uses `LEFT JOIN` with a second table having only one row. (Bug#21081)

- An `UPDATE` that referred to a key column in the `WHERE` clause and activated a trigger that modified the column resulted in a loop. (Bug#20670)

- Creating a `TEMPORARY` table with the same name as an existing table that was locked by another client could result in a lock conflict for `DROP TEMPORARY TABLE` because the server unnecessarily tried to acquire a name lock. (Bug#21096)

- After `FLUSH TABLES WITH READ LOCK` followed by `UNLOCK TABLES`, attempts to drop or alter a stored routine failed with an error that the routine did not exist, and attempts to execute the routine failed with a lock conflict error. (Bug#21414)

- `SHOW VARIABLES` truncated the `Value` field to 256 characters. (Bug#20862)

- Instance Manager didn't close the client socket file when starting a new mysqld instance. mysqld inherited the socket, causing clients connected to Instance Manager to hang. (Bug#12751)

- Instance Manager had a race condition involving mysqld PID file removal. (Bug#22379)

- It was possible for a stored routine with a non-`latin1` name to cause a stack overrun. (Bug#21311)

### E.1.6. Release Notes for MySQL Enterprise 5.0.28 (24 October 2006)

This is the first MySQL Enterprise Server release, following the last Community Server release (5.0.27).

Bugs fixed:

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

- `InnoDB`: Reduced optimization level for Windows 64 builds to handle possible memory overrun. (Bug#19424)

Prev |  | Next
Appendix D. Credits | Home | Appendix F. MySQL Community Server Enhancements and Release Notes