Appendix B. MySQL Change History
Prev |  | Next

## Appendix B. MySQL Change History

This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 4.1.

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

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.

The date mentioned with a release version is the date of the last 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.

The manual included in the source and binary distributions may not be fully accurate when it comes to the release changelog entries, because the integration of the manual happens at build time. For the most up-to-date release changelog, please refer to the online version instead.

## B.1. Changes in release 4.1.x (Production)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Version 4.1 of the MySQL server includes many enhancements and new features. Binaries for this version are available for download at http://dev.mysql.com/downloads/mysql-4.1.html.

- The `SUBSTRING()` function can now take a negative value for the `pos` (position) argument. See Section 11.4, “String Functions”.

- Subqueries and derived tables (unnamed views). See Section 12.2.8, “Subquery Syntax”.

- `INSERT ... ON DUPLICATE KEY UPDATE ...` syntax. This allows you to `UPDATE` an existing row if the insert would cause a duplicate value in a `PRIMARY` or `UNIQUE` key. (`REPLACE` allows you to overwrite an existing row, which is something entirely different.) See Section 12.2.4, “`INSERT` Syntax”.

- A newly designed `GROUP_CONCAT()` aggregate function. See Section 11.11, “Functions and Modifiers for Use with `GROUP BY` Clauses”.

- Extensive Unicode (UTF8) support.

- Table names and column names now are stored in `UTF8`. This makes MySQL more flexible, but might cause some problems upgrading if you have table or column names that use characters outside of the standard 7-bit US-ASCII range. See Section 2.11.1, “Upgrading from MySQL 4.0 to 4.1”.

- Character sets can be defined per column, table, and database.

- New key cache for `MyISAM` tables with many tunable parameters. You can have multiple key caches, preload index into caches for batches...

- `BTREE` index on `HEAP` tables.

- Support for OpenGIS spatial types (geographical data). See Chapter 15, Spatial Extensions.

- `SHOW WARNINGS` shows warnings for the last command. See Section 12.5.4.21, “`SHOW WARNINGS` Syntax”.

- Faster binary protocol with prepared statements and parameter binding. See Section 16.2.4, “C API Prepared Statements”.

- You can now issue multiple statements with a single C API call and then read the results in one go. See Section 16.2.9, “C API Handling of Multiple Statement Execution”.

- Create Table: `CREATE [TEMPORARY] TABLE [IF NOT EXISTS] table2 LIKE table1`.

- Server based `HELP` command that can be used in the mysql command-line client (and other clients) to get help for SQL statements.

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

### B.1.1. Changes in MySQL 4.1.24 (Not yet released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.1 release family.

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

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

- Replication: Connections from one mysqld server to another failed on Mac OS X, affecting replication and `FEDERATED` tables. (Bug#29083)

  See also Bug#26664

- 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 non-embedded server. (Bug#32063)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  This regression was introduced by Bug#13195

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

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

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

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

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

- Format strings in English error messages were insufficiently wide for pathnames printed in those messages by the embedded server. (Bug#16635)

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

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

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

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

### B.1.2. Changes in MySQL 4.1.23 (12 June 2007)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.1 release family.

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)

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

- `INSERT DELAYED` statements on `BLACKHOLE` tables are now rejected, due to the fact that the `BLACKHOLE` storage engine does not support them. (Bug#27998)

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

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

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

- A dependency on the Intel runtime libraries existed in the `shared-`xxx`` RPMs for the IA-64 CPU of some versions of MySQL 4.1 (4.1.16, 4.1.20, and 4.1.22). This has been resolved. (Bug#18776)

- ### Important

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

Bugs fixed:

- Security Fix: The requirement of the `DROP` privilege for `RENAME TABLE` was not enforced. (Bug#27515, CVE-2007-2691)

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

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

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

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

- MySQL Cluster: The management client command ``node_id` STATUS` displayed the message `Node `node_id`: not connected` when `node_id` was not the node ID of a data node.

  ### Note

  The `ALL STATUS` command in the cluster management client still displays status information for data nodes only. This is by design. See Section 14.6.2, “Commands in the MySQL Cluster Management Client”, for more information.

  (Bug#21715)

- Replication: Some queries that updated multiple tables were not backed up correctly. (Bug#27748)

- Cluster API: `libndbclient.so` was not versioned. (Bug#13522)

- The `mysqlserver.lib` library on Windows had many missing symbols. (Bug#29007)

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

- The second execution of a prepared statement from a `UNION` query with `ORDER BY RAND()` caused the server to crash. (Bug#27937)

- Changes to some system variables should invalidate statements in the query cache, but invalidation did not happen. (Bug#27792)

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

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

- The fix for Bug#17212 provided correct sort order for misordered output of certain queries, but caused significant overall query performance degradation. (Results were correct (good), but returned much more slowly (bad).) The fix also affected performance of queries for which results were correct. The performance degradation has been addressed. (Bug#27531)

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

- The error message for error number `137` did not report which database/table combination reported the problem. (Bug#27173)

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

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

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

  In addition, when the underlying tables contained a `TINYINT` or `CHAR(1)` column, the `MERGE` storage engine incorrectly reported that they differed from the `MERGE` table in certain cases. (Bug#26881)

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

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

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

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

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

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

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

- Index hints (`USE INDEX`, `IGNORE INDEX`, `FORCE INDEX`) cannot be used with `FULLTEXT` indexes, but were not being ignored. (Bug#25951)

- Running `CHECK TABLE` concurrently with a `SELECT`, `INSERT` or other statement on Windows could corrupt a MyISAM table. (Bug#25712)

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

- The `InnoDB` parser sometimes did not account for null bytes, causing spurious failure of some queries. (Bug#25596)

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

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

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

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

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

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

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

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

- The result set of a query that used `WITH ROLLUP` and `DISTINCT` could lack some rollup rows (rows with `NULL` values for grouping attributes) if the `GROUP BY` list contained constant expressions. (Bug#24856)

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

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

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

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

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

- 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 returned more that one row, no error was reported. If a query required sorting by expressions containing single-row subselects that returned more than one row, execution of the query could cause a server crash. (Bug#24653)

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

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

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

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

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

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

- The `MERGE` storage engine could return incorrect results when several index values that compare equality were present in an index (for example, `'gross'` and `'gross '`, which are considered equal but have different lengths). (Bug#24342)

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

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

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

  This regression was introduced by Bug#15653

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

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

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

- Using `CAST()` to convert `DATETIME` values to numeric values did not work. (Bug#23656)

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

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

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

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

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

- For ODBC compatibility, MySQL supports use of `WHERE `col_name` IS NULL` for `DATE` or `DATETIME` columns that are `NOT NULL`, to allow column values of `'0000-00-00'` or `'0000-00-00 00:00:00'` to be selected. However, this was not working for `WHERE` clauses in `DELETE` statements. (Bug#23412)

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

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

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

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

- MySQL failed to build on Linux/Alpha. (Bug#23256)

  This regression was introduced by Bug#21250

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- 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'`.

  ### Note

  This fix was reverted in MySQL 4.1.24.

  (Bug#21789)

  See also Bug#25301

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

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

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

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

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

- Some long error messages were printed incorrectly. (Bug#20710)

- The creation of MySQL system tables was not checked for by mysql-test-run.pl. (Bug#20166)

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

- `ORDER BY` values of the `DOUBLE` or `DECIMAL` types could change the result returned by a query. (Bug#19690)

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

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

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

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

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

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

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

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

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

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

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

- For `BOOLEAN` mode full-text searches on non-indexed columns, `NULL` rows generated by a `LEFT JOIN` caused incorrect query results. (Bug#14708, Bug#25637)

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

- `INSERT...ON DUPLICATE KEY UPDATE` could cause `Error 1032: Can't find record in ...` for inserts into an `InnoDB` table unique index using key column prefixes with an underlying `utf8` string column. (Bug#13191)

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

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

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

- The internal functions for table preparation, creation, and alteration were not re-execution friendly, causing problems in code that: repeatedly altered a table; repeatedly created and dropped a table; opened and closed a cursor on a table, altered the table, and then reopened the cursor; used `ALTER TABLE` to change a table's current `AUTO_INCREMENT` value; created indexes on `utf8` columns.

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

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

### B.1.3. Changes in MySQL 4.1.22 (02 November 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.1 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. 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 http://www.mysql.com/products/enterprise.

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)

- MySQL now can do stack dumps on `x86_64` and `i386/NPTL` systems. (Bug#21250)

- The mysqld manpage has been reclassified from volume 1 to volume 8. (Bug#21220)

- A warning now is issued if the client attempts to set the `SQL_LOG_OFF` variable without the `SUPER` privilege. (Bug#16180)

- The `LOAD DATA FROM MASTER` and `LOAD TABLE FROM MASTER` statements are deprecated. See Section 12.6.2.2, “`LOAD DATA FROM MASTER` Syntax”, for recommended alternatives. (Bug#9125, Bug#20596, Bug#14399, Bug#12187, Bug#15025, Bug#18822)

Bugs fixed:

- MySQL Cluster: Packaging: The ndb_mgm program was included in both the `MySQL-ndb-tools` and `MySQL-ndb-management` RPM packages, resulting in a conflict if both were installed. Now ndb_mgm is included only in `MySQL-ndb-tools`. (Bug#21058)

- MySQL Cluster: Backup of a cluster failed if there were any tables with 128 or more columns. (Bug#23502)

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

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

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

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

- MySQL Cluster: Setting `TransactionDeadlockDetectionTimeout` to a value greater than 12000 would cause scans to deadlock, time out, fail to release scan records, until the cluster ran out of scan records and stopped processing. (Bug#21800)

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

- MySQL Cluster: The server provided a non-descriptive error message when encountering a fatally corrupted REDO log. (Bug#21615)

- MySQL Cluster: The output for the `--help` option used with `NDB` executable programs (such as ndbd, ndb_mgm, ndb_restore, ndb_config, and others mentioned in Section 14.8, “Cluster Utility Programs”) referred to the `Ndb.cfg` file, instead of to `my.cnf`. (Bug#21585)

- MySQL Cluster: A partial rollback could lead to node restart failures. (Bug#21536)

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

- MySQL Cluster: The failure of a unique index read due to an invalid schema version could be handled incorrectly in some cases, leading to unpredictable results. (Bug#21384)

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

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

- MySQL Cluster: In a cluster with more than 2 replicas, a manual restart of one of the data nodes could fail and cause the other nodes in the same node group to shut down. (Bug#21213)

- MySQL Cluster: The ndb_size.pl script did not account for `TEXT` and `BLOB` column values correctly. (Bug#21204)

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

- MySQL Cluster: Some queries involving joins on very large `NDB` tables could crash the MySQL server. (Bug#21059)

- MySQL Cluster: In some situations with a high disk-load, writing of the redo log could hang, causing a crash with the error message GCP STOP detected. (Bug#20904)

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

- MySQL Cluster: When the redo buffer ran out of space, a Pointer too large error was raised and the cluster could become unusable until restarted with `--initial`. (Bug#20892)

- MySQL Cluster: ndb_size.pl and ndb_error_reporter were missing from RPM packages. (Bug#20426)

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

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

- MySQL Cluster: The server failed with a non-descriptive error message when out of data memory. (Bug#18475)

- MySQL Cluster: `SELECT ... FOR UPDATE` failed to lock the selected rows. (Bug#18184)

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

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

- `REPAIR TABLE ... USE_FRM` could cause a server crash or hang when used for a `MyISAM` table in a database other than the default database. (Bug#22562)

- Deleting entries from a large `MyISAM` index could cause index corruption when it needed to shrink. Deletes from an index can happen when a record is deleted, when a key changes and must be moved, and when a key must be un-inserted because of a duplicate key. This can also happen in `REPAIR TABLE` when a duplicate key is found and in myisamchk when sorting the records by an index. (Bug#22384)

- Some Linux-x86_64-icc packages (of previous releases) mistakenly contained 32-bit binaries. Only ICC builds are affected, not gcc builds. Solaris and FreeBSD x86_64 builds are not affected. (Bug#22238)

- Execution of a prepared statement that uses an `IN` subquery with aggregate functions in the `HAVING` clause could cause a server crash. (Bug#22085)

- Running `SHOW MASTER LOGS` at the same time as binary log files were being switched would cause `mysqld` to hang. (Bug#21965)

- `character_set_results` can be `NULL` to signify “no conversion,” but some code did not check for `NULL`, resulting in a server crash. (Bug#21913)

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

- A query that used `GROUP BY` and an `ALL` or `ANY` quantified subquery in a `HAVING` clause could trigger an assertion failure. (Bug#21853)

- `COUNT(*)` queries with `ORDER BY` and `LIMIT` could return the wrong result.

  ### Note

  This problem was introduced by the fix for Bug#9676, which limited the rows stored in a temporary table to the `LIMIT` clause. This optimization is not applicable to non-group queries with aggregate functions. The current fix disables the optimization in such cases.

  (Bug#21787)

- Redundant binary log `LAST_INSERT_ID` events could be generated; `LAST_INSERT_ID(`expr`)` did not return the value of `expr`; `LAST_INSERT_ID()` could return the value generated by the current statement if the call occurred after value generation, as in:

      CREATE TABLE t1 (i INT AUTO_INCREMENT PRIMARY KEY, j INT);
      INSERT INTO t1 VALUES (NULL, 0), (NULL, LAST_INSERT_ID());

  (Bug#21726)

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

- For `INSERT ... ON DUPLICATE KEY UPDATE`, use of `VALUES(`col_name`)` within the `UPDATE` clause sometimes was handled incorrectly. (Bug#21555)

- `EXPORT_SET()` did not accept arguments with coercible character sets. (Bug#21531)

- Adding `ORDER BY` to a `SELECT DISTINCT(`expr`)` query could produce incorrect results. (Bug#21456)

- Table aliases in multiple-table `DELETE` statements sometimes were not resolved. (Bug#21392)

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

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

- In the package of pre-built time zone tables that is available for download at timezones.html, the tables now explicitly use the `utf8` character set so that they work the same way regardless of the system character set value. (Bug#21208)

- Under heavy load (executing more than 1024 simultaneous complex queries), a problem in the code that handles internal temporary tables could lead to writing beyond allocated space and memory corruption. (Bug#21206)

- A subquery that uses an index for both the `WHERE` and `ORDER BY` clauses produced an empty result. (Bug#21180)

- Certain malformed `INSERT` statements could crash the mysql client. (Bug#21142)

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

- For `InnoDB` tables, the server could crash when executing `NOT IN(...)` subqueries. (Bug#21077)

- The `myisam_stats_method` variable was mishandled when set from an option file or on the command line. (Bug#21054)

- A query using `WHERE `column` = `constant` OR `column` IS NULL` did not return consistent results on successive invocations. The `column` in each part of the `WHERE` clause could be either the same column, or two different columns, for the effect to be observed. (Bug#21019)

- A query using `WHERE NOT (`column` < ANY (`subquery`))` yielded a different result from the same query using the same `column` and `subquery` with `WHERE (`column` > ANY (`subquery`))`. (Bug#20975)

- Under certain circumstances, `AVG(`key_val`)` returned a value but `MAX(`key_val`)` returned an empty set due to incorrect application of `MIN()/MAX()` optimization. (Bug#20954)

- Using `ALTER TABLE` to add an `ENUM` column with an enumeration value containing `0xFF` caused the name of the first table column to be lost. (Bug#20922)

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

- Using aggregate functions in subqueries yielded incorrect results under certain circumstances due to incorrect application of `MIN()`/`MAX()` optimization. (Bug#20792)

- mysql_install_db incorrectly had a blank first line. (Bug#20721)

- Character set collation was ignored in `GROUP BY` clauses. (Bug#20709)

- If a column definition contained a character set declaration, but a `DEFAULT` value began with an introducer, the introducer character set was used as the column character set. (Bug#20695)

- The `MD5()`, `SHA1()`, and `ENCRYPT()` functions should return a binary string, but the result sometimes was converted to the character set of the argument. `MAKE_SET()` and `EXPORT_SET()` now use the correct character set for their default separators, resulting in consistent result strings which can be coerced according to normal character set rules. (Bug#20536)

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

- User names have a maximum length of 16 characters (even if they contain multi-byte characters), but were being truncated to 16 bytes. (Bug#20393)

- `PROCEDURE ANALYSE()` returned incorrect values of `M` `FLOAT(`M`, `D`)` and `DOUBLE(`M`, `D`)`. (Bug#20305)

- `SUBSTRING()` results sometimes were stored improperly into a temporary table when multi-byte character sets were used. (Bug#20204)

- For an `ENUM` column that used the `ucs2` character set, using `ALTER TABLE` to modify the column definition caused the default value to be lost. (Bug#20108)

- mysqld --flush failed to flush `MyISAM` table changes to disk following an `UPDATE` statement for which no updated column had an index. (Bug#20060)

- libmysqld returned `TEXT` columns to the client as number of bytes, not number of characters (which can be different for multi-byte character sets). (Bug#19983)

- For `TIME_FORMAT()`, the `%H` and `%k` format specifiers can return values larger than two digits (if the hour is greater than 99), but for some query results that contained three-character hours, column values were truncated. (Bug#19844)

- On 64-bit systems, use of the `cp1250` character set with a primary key column in a `LIKE` clause caused a server crash for patterns having letters in the range 128..255. (Bug#19741)

- For a `MyISAM` table with a `FULLTEXT` index, compression with myisampack or a check with myisamchk after compression resulted in table corruption. (Bug#19702)

- The build process incorrectly tried to overwrite `sql/lex_hash.h`. This caused the build to fail when using a shadow link tree pointing to original sources that were owned by another account. (Bug#18888)

- Setting `myisam_repair_threads` caused any repair operation on a `MyISAM` table to fail to update the cardinality of indexes, instead making them always equal to 1. (Bug#18874)

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

- Using `> ALL` with subqueries that return no rows yielded incorrect results under certain circumstances due to incorrect application of `MIN()`/`MAX()` optimization. (Bug#18503)

- Multiple invocations of the `REVERSE()` function could return different results. (Bug#18243)

- For table-format output, mysql did not always calculate columns widths correctly for columns containing multi-byte characters in the column name or contents. (Bug#17939)

- Views could not be updated within a stored function or trigger. (Bug#17591)

- Using the extended syntax for `TRIM()` — that is, `TRIM(... FROM ...)` — in a `SELECT` statement defining a view caused an invalid syntax error when selecting from the view. (Bug#17526)

- Use of the join cache in favor of an index for `ORDER BY` operations could cause incorrect result sorting. (Bug#17212)

- Queries containing a subquery that used aggregate functions could return incorrect results. (Bug#16792)

- Conversion of `TIMESTAMP` values between UTC and the local time zone resulted in some values having the year 2069 rather than 1969. (Bug#16327)

- Using `ANY` with “non-table” subqueries such as `SELECT 1` yielded incorrect results under certain circumstances due to incorrect application of `MIN()`/`MAX()` optimization. (Bug#16302)

- Parallel builds occasionally failed on Solaris. (Bug#16282)

- A subquery in the `WHERE` clause of the outer query and using `IN` and `GROUP BY` returned an incorrect result. (Bug#16255)

- The `--collation-server` server option was being ignored. With the fix for this problem, if you choose a non-default character set with `--character-set-server`, you should also use `--collation-server` to specify the collation. (Bug#15276)

- When using tables containing `VARCHAR` columns created under MySQL 4.1 with a 5.0 or later server, for some queries the metadata sent to the client could have an empty column name. (Bug#14897)

- The use of `WHERE `col_name` IS NULL` in `SELECT` statements reset the value of `LAST_INSERT_ID()` to zero. (Bug#14553)

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

- `libmysqld` produced some warnings to `stderr` which could not be silenced. These warnings now are suppressed. (Bug#13717)

- The source distribution failed to compile when configured with the `--without-geometry` option. (Bug#12991)

- On Mac OS X, zero-byte `read()` or `write()` calls to an SMB-mounted filesystem could return a non-standard return value, leading to data corruption. Now such calls are avoided. (Bug#12620)

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

- The server returns a more informative error message when it attempts to open a `MERGE` table that has been defined to use non-`MyISAM` tables. (Bug#10974)

- `DELETE` with `WHERE` condition on a `BTREE`-indexed column for a `MEMORY` table deleted only the first matched row. (Bug#9719)

- A server or network failure with an open client connection would cause the client to hang even though the server was no longer available.

  As a result of this change, the `MYSQL_OPT_READ_TIMEOUT` and `MYSQL_OPT_WRITE_TIMEOUT` options for `mysql_options()` now apply to TCP/IP connections on all platforms. Previously, they applied only to Windows. (Bug#9678)

- The optimizer could produce an incorrect result after `AND` with collations such as `latin1_german2_ci`, `utf8_czech_ci`, and `utf8_lithianian_ci`. (Bug#9509)

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

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

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

- For cross-database multiple-table `UPDATE` statements, a user with all privileges for the default database could update tables in another database for which the user did not have `UPDATE` privileges. (Bug#7391)

- The `--with-collation` option was not honored for client connections. (Bug#7192)

- Incorporated some portability fixes into the definition of `__attribute__` in `my_global.h`. (Bug#2717)

- A patch fixing the omission of leading zeros in dates in MySQL 4.1.21 was reverted.

  The patch for the following bugs was reverted: Bug#16377.

### B.1.4. Changes in MySQL 4.1.21 (19 July 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.1 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. 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 http://www.mysql.com/products/enterprise.

Functionality added or changed:

- For spatial data types, the server formerly returned these as `VARSTRING` values with a binary collation. Now the server returns spatial values as `BLOB` values. (Bug#10166)

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

- For a table with an `AUTO_INCREMENT` column, `SHOW CREATE TABLE` now shows the next `AUTO_INCREMENT` value to be generated. (Bug#19025)

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

- A new system variable, `lc_time_names`, specifies the locale that controls the language used to display day and month names and abbreviations. This variable affects the output from the `DATE_FORMAT()`, `DAYNAME()` and `MONTHNAME()` functions. See Section 9.10, “MySQL Server Locale Support”.

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)

- MySQL now can do stack dumps on `x86_64` and `i386/NPTL` systems. (Bug#21250)

- The mysqld manpage has been reclassified from volume 1 to volume 8. (Bug#21220)

- A warning now is issued if the client attempts to set the `SQL_LOG_OFF` variable without the `SUPER` privilege. (Bug#16180)

- The `LOAD DATA FROM MASTER` and `LOAD TABLE FROM MASTER` statements are deprecated. See Section 12.6.2.2, “`LOAD DATA FROM MASTER` Syntax”, for recommended alternatives. (Bug#9125, Bug#20596, Bug#14399, Bug#12187, Bug#15025, Bug#18822)

Bugs fixed:

- MySQL Cluster: Packaging: The ndb_mgm program was included in both the `MySQL-ndb-tools` and `MySQL-ndb-management` RPM packages, resulting in a conflict if both were installed. Now ndb_mgm is included only in `MySQL-ndb-tools`. (Bug#21058)

- MySQL Cluster: Backup of a cluster failed if there were any tables with 128 or more columns. (Bug#23502)

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

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

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

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

- MySQL Cluster: Setting `TransactionDeadlockDetectionTimeout` to a value greater than 12000 would cause scans to deadlock, time out, fail to release scan records, until the cluster ran out of scan records and stopped processing. (Bug#21800)

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

- MySQL Cluster: The server provided a non-descriptive error message when encountering a fatally corrupted REDO log. (Bug#21615)

- MySQL Cluster: The output for the `--help` option used with `NDB` executable programs (such as ndbd, ndb_mgm, ndb_restore, ndb_config, and others mentioned in Section 14.8, “Cluster Utility Programs”) referred to the `Ndb.cfg` file, instead of to `my.cnf`. (Bug#21585)

- MySQL Cluster: A partial rollback could lead to node restart failures. (Bug#21536)

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

- MySQL Cluster: The failure of a unique index read due to an invalid schema version could be handled incorrectly in some cases, leading to unpredictable results. (Bug#21384)

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

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

- MySQL Cluster: In a cluster with more than 2 replicas, a manual restart of one of the data nodes could fail and cause the other nodes in the same node group to shut down. (Bug#21213)

- MySQL Cluster: The ndb_size.pl script did not account for `TEXT` and `BLOB` column values correctly. (Bug#21204)

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

- MySQL Cluster: Some queries involving joins on very large `NDB` tables could crash the MySQL server. (Bug#21059)

- MySQL Cluster: In some situations with a high disk-load, writing of the redo log could hang, causing a crash with the error message GCP STOP detected. (Bug#20904)

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

- MySQL Cluster: When the redo buffer ran out of space, a Pointer too large error was raised and the cluster could become unusable until restarted with `--initial`. (Bug#20892)

- MySQL Cluster: ndb_size.pl and ndb_error_reporter were missing from RPM packages. (Bug#20426)

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

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

- MySQL Cluster: The server failed with a non-descriptive error message when out of data memory. (Bug#18475)

- MySQL Cluster: `SELECT ... FOR UPDATE` failed to lock the selected rows. (Bug#18184)

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

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

- `REPAIR TABLE ... USE_FRM` could cause a server crash or hang when used for a `MyISAM` table in a database other than the default database. (Bug#22562)

- Deleting entries from a large `MyISAM` index could cause index corruption when it needed to shrink. Deletes from an index can happen when a record is deleted, when a key changes and must be moved, and when a key must be un-inserted because of a duplicate key. This can also happen in `REPAIR TABLE` when a duplicate key is found and in myisamchk when sorting the records by an index. (Bug#22384)

- Some Linux-x86_64-icc packages (of previous releases) mistakenly contained 32-bit binaries. Only ICC builds are affected, not gcc builds. Solaris and FreeBSD x86_64 builds are not affected. (Bug#22238)

- Execution of a prepared statement that uses an `IN` subquery with aggregate functions in the `HAVING` clause could cause a server crash. (Bug#22085)

- Running `SHOW MASTER LOGS` at the same time as binary log files were being switched would cause `mysqld` to hang. (Bug#21965)

- `character_set_results` can be `NULL` to signify “no conversion,” but some code did not check for `NULL`, resulting in a server crash. (Bug#21913)

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

- A query that used `GROUP BY` and an `ALL` or `ANY` quantified subquery in a `HAVING` clause could trigger an assertion failure. (Bug#21853)

- `COUNT(*)` queries with `ORDER BY` and `LIMIT` could return the wrong result.

  ### Note

  This problem was introduced by the fix for Bug#9676, which limited the rows stored in a temporary table to the `LIMIT` clause. This optimization is not applicable to non-group queries with aggregate functions. The current fix disables the optimization in such cases.

  (Bug#21787)

- Redundant binary log `LAST_INSERT_ID` events could be generated; `LAST_INSERT_ID(`expr`)` did not return the value of `expr`; `LAST_INSERT_ID()` could return the value generated by the current statement if the call occurred after value generation, as in:

      CREATE TABLE t1 (i INT AUTO_INCREMENT PRIMARY KEY, j INT);
      INSERT INTO t1 VALUES (NULL, 0), (NULL, LAST_INSERT_ID());

  (Bug#21726)

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

- For `INSERT ... ON DUPLICATE KEY UPDATE`, use of `VALUES(`col_name`)` within the `UPDATE` clause sometimes was handled incorrectly. (Bug#21555)

- `EXPORT_SET()` did not accept arguments with coercible character sets. (Bug#21531)

- Adding `ORDER BY` to a `SELECT DISTINCT(`expr`)` query could produce incorrect results. (Bug#21456)

- Table aliases in multiple-table `DELETE` statements sometimes were not resolved. (Bug#21392)

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

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

- In the package of pre-built time zone tables that is available for download at timezones.html, the tables now explicitly use the `utf8` character set so that they work the same way regardless of the system character set value. (Bug#21208)

- Under heavy load (executing more than 1024 simultaneous complex queries), a problem in the code that handles internal temporary tables could lead to writing beyond allocated space and memory corruption. (Bug#21206)

- A subquery that uses an index for both the `WHERE` and `ORDER BY` clauses produced an empty result. (Bug#21180)

- Certain malformed `INSERT` statements could crash the mysql client. (Bug#21142)

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

- For `InnoDB` tables, the server could crash when executing `NOT IN(...)` subqueries. (Bug#21077)

- The `myisam_stats_method` variable was mishandled when set from an option file or on the command line. (Bug#21054)

- A query using `WHERE `column` = `constant` OR `column` IS NULL` did not return consistent results on successive invocations. The `column` in each part of the `WHERE` clause could be either the same column, or two different columns, for the effect to be observed. (Bug#21019)

- A query using `WHERE NOT (`column` < ANY (`subquery`))` yielded a different result from the same query using the same `column` and `subquery` with `WHERE (`column` > ANY (`subquery`))`. (Bug#20975)

- Under certain circumstances, `AVG(`key_val`)` returned a value but `MAX(`key_val`)` returned an empty set due to incorrect application of `MIN()/MAX()` optimization. (Bug#20954)

- Using `ALTER TABLE` to add an `ENUM` column with an enumeration value containing `0xFF` caused the name of the first table column to be lost. (Bug#20922)

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

- Using aggregate functions in subqueries yielded incorrect results under certain circumstances due to incorrect application of `MIN()`/`MAX()` optimization. (Bug#20792)

- mysql_install_db incorrectly had a blank first line. (Bug#20721)

- Character set collation was ignored in `GROUP BY` clauses. (Bug#20709)

- If a column definition contained a character set declaration, but a `DEFAULT` value began with an introducer, the introducer character set was used as the column character set. (Bug#20695)

- The `MD5()`, `SHA1()`, and `ENCRYPT()` functions should return a binary string, but the result sometimes was converted to the character set of the argument. `MAKE_SET()` and `EXPORT_SET()` now use the correct character set for their default separators, resulting in consistent result strings which can be coerced according to normal character set rules. (Bug#20536)

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

- User names have a maximum length of 16 characters (even if they contain multi-byte characters), but were being truncated to 16 bytes. (Bug#20393)

- `PROCEDURE ANALYSE()` returned incorrect values of `M` `FLOAT(`M`, `D`)` and `DOUBLE(`M`, `D`)`. (Bug#20305)

- `SUBSTRING()` results sometimes were stored improperly into a temporary table when multi-byte character sets were used. (Bug#20204)

- For an `ENUM` column that used the `ucs2` character set, using `ALTER TABLE` to modify the column definition caused the default value to be lost. (Bug#20108)

- mysqld --flush failed to flush `MyISAM` table changes to disk following an `UPDATE` statement for which no updated column had an index. (Bug#20060)

- libmysqld returned `TEXT` columns to the client as number of bytes, not number of characters (which can be different for multi-byte character sets). (Bug#19983)

- For `TIME_FORMAT()`, the `%H` and `%k` format specifiers can return values larger than two digits (if the hour is greater than 99), but for some query results that contained three-character hours, column values were truncated. (Bug#19844)

- On 64-bit systems, use of the `cp1250` character set with a primary key column in a `LIKE` clause caused a server crash for patterns having letters in the range 128..255. (Bug#19741)

- For a `MyISAM` table with a `FULLTEXT` index, compression with myisampack or a check with myisamchk after compression resulted in table corruption. (Bug#19702)

- The build process incorrectly tried to overwrite `sql/lex_hash.h`. This caused the build to fail when using a shadow link tree pointing to original sources that were owned by another account. (Bug#18888)

- Setting `myisam_repair_threads` caused any repair operation on a `MyISAM` table to fail to update the cardinality of indexes, instead making them always equal to 1. (Bug#18874)

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

- Using `> ALL` with subqueries that return no rows yielded incorrect results under certain circumstances due to incorrect application of `MIN()`/`MAX()` optimization. (Bug#18503)

- Multiple invocations of the `REVERSE()` function could return different results. (Bug#18243)

- For table-format output, mysql did not always calculate columns widths correctly for columns containing multi-byte characters in the column name or contents. (Bug#17939)

- Views could not be updated within a stored function or trigger. (Bug#17591)

- Using the extended syntax for `TRIM()` — that is, `TRIM(... FROM ...)` — in a `SELECT` statement defining a view caused an invalid syntax error when selecting from the view. (Bug#17526)

- Use of the join cache in favor of an index for `ORDER BY` operations could cause incorrect result sorting. (Bug#17212)

- Queries containing a subquery that used aggregate functions could return incorrect results. (Bug#16792)

- Conversion of `TIMESTAMP` values between UTC and the local time zone resulted in some values having the year 2069 rather than 1969. (Bug#16327)

- Using `ANY` with “non-table” subqueries such as `SELECT 1` yielded incorrect results under certain circumstances due to incorrect application of `MIN()`/`MAX()` optimization. (Bug#16302)

- Parallel builds occasionally failed on Solaris. (Bug#16282)

- A subquery in the `WHERE` clause of the outer query and using `IN` and `GROUP BY` returned an incorrect result. (Bug#16255)

- The `--collation-server` server option was being ignored. With the fix for this problem, if you choose a non-default character set with `--character-set-server`, you should also use `--collation-server` to specify the collation. (Bug#15276)

- When using tables containing `VARCHAR` columns created under MySQL 4.1 with a 5.0 or later server, for some queries the metadata sent to the client could have an empty column name. (Bug#14897)

- The use of `WHERE `col_name` IS NULL` in `SELECT` statements reset the value of `LAST_INSERT_ID()` to zero. (Bug#14553)

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

- `libmysqld` produced some warnings to `stderr` which could not be silenced. These warnings now are suppressed. (Bug#13717)

- The source distribution failed to compile when configured with the `--without-geometry` option. (Bug#12991)

- On Mac OS X, zero-byte `read()` or `write()` calls to an SMB-mounted filesystem could return a non-standard return value, leading to data corruption. Now such calls are avoided. (Bug#12620)

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

- The server returns a more informative error message when it attempts to open a `MERGE` table that has been defined to use non-`MyISAM` tables. (Bug#10974)

- `DELETE` with `WHERE` condition on a `BTREE`-indexed column for a `MEMORY` table deleted only the first matched row. (Bug#9719)

- A server or network failure with an open client connection would cause the client to hang even though the server was no longer available.

  As a result of this change, the `MYSQL_OPT_READ_TIMEOUT` and `MYSQL_OPT_WRITE_TIMEOUT` options for `mysql_options()` now apply to TCP/IP connections on all platforms. Previously, they applied only to Windows. (Bug#9678)

- The optimizer could produce an incorrect result after `AND` with collations such as `latin1_german2_ci`, `utf8_czech_ci`, and `utf8_lithianian_ci`. (Bug#9509)

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

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

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

- For cross-database multiple-table `UPDATE` statements, a user with all privileges for the default database could update tables in another database for which the user did not have `UPDATE` privileges. (Bug#7391)

- The `--with-collation` option was not honored for client connections. (Bug#7192)

- Incorporated some portability fixes into the definition of `__attribute__` in `my_global.h`. (Bug#2717)

- A patch fixing the omission of leading zeros in dates in MySQL 4.1.21 was reverted.

  The patch for the following bugs was reverted: Bug#16377.

### B.1.5. Changes in MySQL 4.1.20 (24 May 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a security fix release for the MySQL 4.1 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. 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 http://www.mysql.com/products/enterprise.

Bugs fixed:

- Security Fix: An SQL-injection security hole has been found in multi-byte encoding processing. The bug was in the server, incorrectly parsing the string escaped with the `mysql_real_escape_string()` C API function.

  This vulnerability was discovered and reported by Josh Berkus `<josh@postgresql.org>` and Tom Lane `<tgl@sss.pgh.pa.us>` as part of the inter-project security collaboration of the OSDB consortium. For more information about SQL injection, please see the following text.

  Discussion. An SQL injection security hole has been found in multi-byte encoding processing. An SQL injection security hole can include a situation whereby when a user supplied data to be inserted into a database, the user might inject SQL statements into the data that the server will execute. With regards to this vulnerability, when character set-unaware escaping is used (for example, `addslashes()` in PHP), it is possible to bypass the escaping in some multi-byte character sets (for example, SJIS, BIG5 and GBK). As a result, a function such as `addslashes()` is not able to prevent SQL-injection attacks. It is impossible to fix this on the server side. The best solution is for applications to use character set-aware escaping offered by a function such `mysql_real_escape_string()`.

  However, a bug was detected in how the MySQL server parses the output of `mysql_real_escape_string()`. As a result, even when the character set-aware function `mysql_real_escape_string()` was used, SQL injection was possible. This bug has been fixed.

  Workarounds. If you are unable to upgrade MySQL to a version that includes the fix for the bug in `mysql_real_escape_string()` parsing, but run MySQL 5.0.1 or higher, you can use the `NO_BACKSLASH_ESCAPES` SQL mode as a workaround. (This mode was introduced in MySQL 5.0.1.) `NO_BACKSLASH_ESCAPES` enables an SQL standard compatibility mode, where backslash is not considered a special character. The result will be that queries will fail.

  To set this mode for the current connection, enter the following SQL statement:

      SET sql_mode='NO_BACKSLASH_ESCAPES';

  You can also set the mode globally for all clients:

      SET GLOBAL sql_mode='NO_BACKSLASH_ESCAPES';

  This SQL mode also can be enabled automatically when the server starts by using the command-line option `--sql-mode=NO_BACKSLASH_ESCAPES` or by setting `sql-mode=NO_BACKSLASH_ESCAPES` in the server option file (for example, `my.cnf` or `my.ini`, depending on your system). (Bug#8378, CVE-2006-2753)

  See also Bug#8303

- The dropping of a temporary table whose name contained a backtick ('```') character was not correctly written to the binary log, which also caused it not to be replicated correctly. (Bug#19188)

- The client libraries were not compiled for position-independent code on Solaris-SPARC and AMD x86_64 platforms. (Bug#18091, Bug#13159, Bug#14202)

- RPM packages had spurious dependencies on Perl modules and other programs. (Bug#13634)

- Running myisampack followed by myisamchk with the `--unpack` option would corrupt the `auto_increment` key. (Bug#12633)

- The patch for Bug#8303 broke the fix for Bug#8378 and was undone. (In string literals with an escape character (`\`) followed by a multi-byte character that has a second byte of (`\`), the literal was not interpreted correctly. The next byte now is escaped, not the entire multi-byte character. This means it a strict reverse of the `mysql_real_escape_string()` function.)

### B.1.6. Changes in MySQL 4.1.19 (29 April 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This release includes the patches for recently reported security vulnerabilites in the MySQL client-server protocol. We would like to thank Stefano Di Paola `<stefano.dipaola@wisec.it>` for finding and reporting these to us.

Functionality added or changed:

- Security Enhancement: Added the global `max_prepared_stmt_count` system variable to limit the total number of prepared statements in the server. This limits the potential for denial-of-service attacks based on running the server out of memory by preparing huge numbers of statements. The current number of prepared statements is available through the `prepared_stmt_count` system variable. (Bug#16365)

- Packaging: The `MySQL-shared-compat-4.1.`X`-.i386.rpm` shared compatibility RPMs no longer contain libraries for MySQL 5.0 and up. They now contain libraries for MySQL 3.23, 4.0, and 4.1.1 only. (Bug#19288)

- New `charset` command added to mysql command-line client. By typing `charset `name`` or `\C `name`` (such as `\C UTF8`), the client character set can be changed without reconnecting. (Bug#16217)

- `InnoDB` now caches a list of unflushed files instead of scanning for unflushed files during a table flush operation. This improves performance when `--innodb_file_per_table` is set on a system with a large number of `InnoDB` tables. (Bug#15653)

- When using the `GROUP_CONCAT()` function where the `group_concat_max_len` system variable was greater than 512, the type of the result was `BLOB` only if the query included an `ORDER BY` clause; otherwise the result was a `VARCHAR`.

  The result type of the `GROUP_CONCAT()` function is now `VARCHAR` only if the value of the `group_concat_max_len` system variable is less than or equal to 512. Otherwise, this function returns a `BLOB`. (Bug#14169)

- Large file support was re-enabled for the MySQL server binary for the AIX 5.2 platform. (Bug#13571)

Bugs fixed:

- Security Fix: A malicious client, using specially crafted invalid login or `COM_TABLE_DUMP` packets was able to read uninitialized memory, which potentially, though unlikely in MySQL, could have led to an information disclosure. (, ) Thanks to Stefano Di Paola `<stefano.dipaola@wisec.it>` for finding and reporting this bug. (CVE-2006-1516, CVE-2006-1517)

- MySQL Cluster: A simultaneous `DROP TABLE` and table update operation utilising a table scan could trigger a node failure. (Bug#18597)

- MySQL Cluster: A timeout in the handling of an `ABORT` condition with more that 32 operations could yield a node failure. (Bug#18414)

- MySQL Cluster: A node restart immediately following a `CREATE TABLE` would fail.

  ### Important

  This fix supports 2-node Clusters only.

  (Bug#18385)

- MySQL Cluster: In event of a node failure during a rollback, a “false” lock could be established on the backup for that node, which lock could not be removed without restarting the node. (Bug#18352)

- MySQL Cluster: The cluster created a crashed replica of a table having an ordered index — or when logging was not enabled, of a table having a table or unique index — leading to a crash of the cluster following 8 successive restarts. (Bug#18298)

- MySQL Cluster: When replacing a failed master node, the replacement node could cause the cluster to crash from a buffer overflow if it had an excessively large amount of data to write to the cluster log. (Bug#18118)

- MySQL Cluster: Backups could fail for large clusters with many tables, where the number of tables approached `MaxNoOfTables`. (Bug#17607)

- MySQL Cluster: The `REDO` log would become corrupted (and thus unreadable) in some circumstances, due to a failure in the query handler. (Bug#17295)

- MySQL Cluster: An `UPDATE` with an inner join failed to match any records if both tables in the join did not have a primary key. (Bug#17257)

- MySQL Cluster: A `DELETE` with a join in the `WHERE` clause failed to retrieve any records if both tables in the join did not have a primary key. (Bug#17249)

- MySQL Cluster: In some cases, `LOAD DATA INFILE` did not load all data into `NDB` tables. (Bug#17081)

- MySQL Cluster: Restarting nodes were allowed to start and join the cluster too early. (Bug#16772)

- MySQL Cluster: ndb_delete_all ran out of memory when processing tables containing `BLOB` columns. (Bug#16693)

- MySQL Cluster: In a 2-node cluster with a node failure, restarting the node with a low value for `StartPartialTimeout` could cause the cluster to come up partitioned (“split-brain” issue).

  A similar issue could occur when the cluster was first started with a sufficiently low value for this parameter. (Bug#16447, Bug#18612)

- MySQL Cluster: On systems with multiple network interfaces, data nodes would get “stuck” in startup phase 2 if the interface connecting them to the management server was working on node startup while the interface interconnecting the data nodes experienced a temporary outage. (Bug#15695)

- MySQL Cluster: Inserting and deleting `BLOB` column values while a backup was in process could cause data nodes to shut down. (Bug#14028)

- MySQL Cluster: No error message was generated for setting `NoOfFragmentLogFiles` too low. (Bug#13966)

- MySQL Cluster: No error message was generated for setting `MaxNoOfAttributes` too low. (Bug#13965)

- MySQL Cluster: The server would not compile with `NDB` support on AIX 5.2. (Bug#10776)

- Attempting to set the default value of an `ENUM` or `SET` column to `NULL` caused a server crash. (Bug#19145)

- Index prefixes for `utf8` `VARCHAR` columns did not work for `UPDATE` statements. (Bug#19080)

- Index corruption could occur in cases when `key_cache_block_size` was not a multiple of `myisam_block_size` (for example, with `key_cache_block_size=1536` and `myisam_block_size=1024`). (Bug#19079)

- Creating a table in an `InnoDB` database with a column name that matched the name of an internal `InnoDB` column (including `DB_ROW_ID`, `DB_TRX_ID`, `DB_ROLL_PTR` and `DB_MIX_ID`) would cause a crash. MySQL now returns Error 1005 Cannot create table with `errno` set to -1. (Bug#18934)

- MySQL would not compile on Linux distributions that use the `tinfo` library. (Bug#18912)

- `mysql_reconnect()` sent a `SET NAMES` statement to the server, even for pre-4.1 servers that do not understand the statement. (Bug#18830)

- For single-`SELECT` union constructs of the form (SELECT ... ORDER BY `order_list1` [LIMIT `n`]) ORDER BY `order_list2`, the `ORDER BY` lists were concatenated and the `LIMIT` clause was ignored. (Bug#18767)

- Conversion of a number to a `CHAR UNICODE` string returned an invalid result. (Bug#18691)

- `UNCOMPRESS(NULL)` could cause subsequent `UNCOMPRESS()` calls to return `NULL` for legal non-`NULL` arguments. (Bug#18643)

- A `LOCK TABLES` statement that failed could cause `MyISAM` not to update table statistics properly, causing a subsequent `CHECK TABLE` to report table corruption. (Bug#18544)

- The `IN`-to-`EXISTS` transformation was making a reference to a parse tree fragment that was left out of the parse tree. This caused problems with prepared statements. (Bug#18492)

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

- The euro sign (`€`) was not stored correctly in columns using the `latin1_german1_ci` or `latin1_general_ci` collation. (Bug#18321)

- If `InnoDB` encountered a `HA_ERR_LOCK_TABLE_FULL` error and rolled back a transaction, the transaction was still written to the binary log. (Bug#18283)

- Connecting to a server with a UCS2 default character set with a client using a non-UCS2 character set crashed the server. (Bug#18004)

- Executing `SELECT` on a large table that had been compressed within myisampack could cause a crash. (Bug#17917)

- A call to `MIN()` with a `CASE` expression as its argument could return a non-minimum value. (Bug#17896)

- `MyISAM`: Keys for which the first part of the key was a `CHAR` or `VARCHAR` column using the UTF-8 character set and longer than 254 bytes could become corrupted. (Bug#17705)

- `SELECT ... WHERE `column` LIKE 'A%'`, when `column` had a key and used the `latin2_czech_cs` collation, caused the wrong number of rows to be returned. (Bug#17374)

- Use of `TRUNCATE TABLE` for a `TEMPORARY` table on a master server was propagated to slaves properly, but slaves did not decrement the `Slave_open_temp_tables` counter properly. (Bug#17137)

- A `FULLTEXT` query in a `UNION` could result in unexpected behavior. (Bug#16893)

- IA-64 RPM packages for Red Hat and SuSE Linux that were built with the icc compiler incorrectly depended on icc runtime libraries. (Bug#16662)

- A race condition could occur when dropping the adaptive hash index for a B-tree page in `InnoDB`. (Bug#16582)

- `MySQL-shared-compat-4.1.15-0.i386.rpm`, `MySQL-shared-compat-4.1.16-0.i386.rpm`, and `MySQL-shared-compat-4.1.18-0.i386.rpm` incorrectly depended on `glibc` 2.3 and could not be installed on a `glibc` 2.2 system. (Bug#16539)

- mysqldump tried to dump data from a view. (In MySQL 4.1, this applies when connecting to a server from MySQL 5.0 or higher.) (Bug#16389)

- Dropping `InnoDB` constraints named ``tbl_name`_ibfk_0` could crash the server. (Bug#16387)

- A query using WHERE (`column_1`, `column_2`) IN ((`value_1`, `value_2`)[, (..., ...), ...]) would return incorrect results. (Bug#16248)

- Character set conversion of string constants for `UNION` of constant and table column was not done when it was safe to do so. (Bug#15949)

- The `mysql_close()` C API function leaked handles for shared-memory connections on Windows. (Bug#15846)

- Security improvement: In grant table comparisons, improper use of a `latin1` collation caused some hostname matches to be true that should have been false. Thanks to Deomid Ryabkov for finding this bug and proposing a solution. (Bug#15756)

- Binary distributions for Solaris contained files with group ownership set to the non-existing `wheel` group. Now the `bin` group is used. (Bug#15562)

- When running a query that contained a `GROUP_CONCAT(SELECT GROUP_CONCAT(...) )`, the result was `NULL` except in the `ROLLUP` part of the result, if there was one. (Bug#15560)

- During conversion from one character set to `ucs2`, multi-byte characters with no `ucs2` equivalent were converted to multiple characters, rather than to `0x003F QUESTION MARK`. (Bug#15375)

- `SET` value definitions containing commas were not rejected. Now a definition such as `SET('a,b','c,d')` results in an error. (Bug#15316)

- `LOAD DATA FROM MASTER` produced invalid warnings and Packet out of order errors when the database already existed on the slave. (Bug#15302)

- `CAST(`double` AS SIGNED INT)` for large `double` values outside the signed integer range truncated the result to be within range, but the result sometimes had the wrong sign, and no warning was generated. (Bug#15098)

- `SELECT COUNT(*)` for a `MyISAM` table could return different results depending on whether an index was used. (Bug#14980)

- Killing a long-running query containing a subquery could cause a server crash. (Bug#14851)

- A `FULLTEXT` query in a prepared statement could result in unexpected behavior. (Bug#14496)

- Security Improvement: GRANTs to users with wildcards in their host information could be erroneously applied to similar users with the same username and similar wildcards. For example, a privilege granted to `foo@%` are also applied to user `foo@192.%`. (Bug#14385)

- Avoid trying to include `<asm/atomic.h>` when it doesn't work in C++ code. (Bug#13621)

- mysql_config returned incorrect libraries on `x86_64` systems. (Bug#13158)

- A key on a `MEMORY` table would sometimes fail to match a row. (Bug#12796)

- `MYSQL_STMT` objects were not preserved following a connection reset. Attempting to operate on them afterwards caused the server to crash. (Bug#12744)

- The server was always built as though `--with-extra-charsets=complex` had been specified. (Bug#12076)

- Setting the `myisam_repair_threads` system variable to a value larger than 1 could cause corruption of large `MyISAM` tables. (Bug#11527)

- Repeated invocation of `my_init()` and `my_end()` caused corruption of character set data and connection failure. (Bug#6536)

### B.1.7. Changes in MySQL 4.1.18 (27 January 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- MySQL Cluster: More descriptive warnings are now issued when inappropriate logging parameters are set in `config.ini`. (Formerly, the warning issued was simply Could not add logfile destination.) (Bug#11331)

- `libmysqlclient` now uses versioned symbols with GNU ld. (Bug#3074)

Bugs fixed:

- `UPDATE` statement crashed multi-byte character set `FULLTEXT` index if update value was almost identical to initial value only differing in some spaces being changed to &nbsp;. (Bug#16489)

- The `--replicate-do` and `--replicate-ignore` options were not being enforced on multiple-table statements. (Bug#16487, Bug#15699)

- Single table `UPDATE` statements without `ORDER BY` clauses which updated the same indexed column that was being filtered on were optimized with a full index scan instead of a more appropriate index range scan. (Bug#15935)

- `STR_TO_DATE(1,NULL)` caused a server crash. (Bug#15828, CVE-2006-3081)

- Test suite `func_math` test returned warnings when server not compiled with InnoDB support. (Bug#15429)

- RPM packages had an incorrect `zlib` dependency. (Bug#15223)

- Running out of diskspace in the location specified by the `tmpdir` option resulted in incorrect error message. (Bug#14634)

- The `MBROverlaps` GIS function returned incorrect results. (Bug#14320)

- The length of a `VARCHAR()` column that used the `utf8` character set would increase each time the table was re-created in a stored procedure or prepared statement, eventually causing the `CREATE TABLE` statement to fail. (Bug#13134)

- A prepared statement created from a `SELECT ... LIKE` query (such as `PREPARE stmt1 FROM 'SELECT col_1 FROM tedd_test WHERE col_1 LIKE ?';`) would begin to produce erratic results after being executed repeatedly numerous (thousands) of times. (Bug#12734)

- A `CREATE TABLE ... SELECT ...` on an equation involving `DOUBLE` values could result in the table being created with columns too small to hold the equation result. (Bug#9855)

### B.1.8. Changes in MySQL 4.1.17 (Not released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Support files for compiling with Visual Studio 6 have been removed. (Bug#15094)

- Internal `sha1_result` function renamed to `mysql_sha1_result` to prevent conflicts with other projects. (Bug#13944)

- In the `latin5_turkish_ci` collation, the order of the characters `A WITH CIRCUMFLEX`, `I WITH CIRCUMLEX`, and `U WITH CIRCUMFLEX` was changed. If you have used these characters in any indexed columns, you should rebuild those indexes. (Bug#13421)

Bugs fixed:

- MySQL Cluster: If an abort by the Transaction Coordinator timed out, the abort condition was incorrectly handled, causing the transaction record to be released prematurely. (Bug#15685)

- MySQL Cluster: Under some circumstances, it was possible for a restarting node to undergo a forced shutdown. (Bug#15632)

- MySQL Cluster: A node which failed during cluster startup was sometimes not removed from the internal list of active nodes. (Bug#15587)

- MySQL Cluster: There was a small window for a node failure to occur during a backup without an error being reported. (Bug#15425)

- MySQL Cluster: A memory leak occurred when performing ordered index scans using indexes on columns larger than 32 bytes. This would eventually lead to the forced shutdown of all mysqld server processes used with the cluster. (Bug#13078)

- Cluster API: Upon the completion of a scan where a key request remained outstanding on the primary replica and a starting node died, the scan did not terminate. This caused incomplete error handling for the failed node. (Bug#15908)

- Performing a `RENAME TABLE` on an `InnoDB` table when the server was started with the `--innodb_file_per_table` option and the data directory was a symlink caused a server crash. (Bug#15991)

- Piping the `fill_help_tables.sql` file into mysqld resulted in a syntax error. (Bug#15965)

- `CAST(... AS TIME)` operations returned different results when using versus not using prepared-statement protocol. (Bug#15805)

- Issuing a `DROP USER` command could cause some users to encounter a ``hostname` is not allowed to connect to this MySQL server` error. (Bug#15775)

- Certain permission management statements could create a `NULL` hostname for a user, resulting in a server crash. (Bug#15598)

- The `COALESCE()` function truncated data in a `TINYTEXT` column. (Bug#15581)

- `BDB`: A `DELETE`, `INSERT`, or `UPDATE` of a `BDB` table could cause the server to crash where the query contained a subquery using an index read. (Bug#15536)

- Characters in the `gb2312` and `euckr` character sets which did not have Unicode mappings were truncated. (Bug#15377)

- Multiple-table update operations were counting updates and not updated rows. As a result, if a row had several updates it was counted several times for the “rows matched” value but updated only once. (Bug#15028)

- Symbolic links did not function properly on Windows platforms. (Bug#14960, Bug#14310)

- `SELECT` queries that began with an opening parenthesis were not being placed in the query cache. (Bug#14652)

- `InnoDB`: Comparison of indexed `VARCHAR CHARACTER SET ucs2 COLLATE ucs2_bin` columns using `LIKE` could fail. (Bug#14583)

- Using an aggregate function as the argument for a `HAVING` clause resulted in the aggregate function always returning `FALSE`. (Bug#14274)

- For `InnoDB` tables, using a column prefix for a `utf8` column in a primary key caused `Cannot find record` errors when attempting to locate records. (Bug#14056)

- `InnoDB`: If `FOREIGN_KEY_CHECKS` was 0, `InnoDB` allowed inconsistent foreign keys to be created. (Bug#13778)

- Certain `CREATE TABLE ... AS ...` statements involving `ENUM` columns could cause server crash. (Bug#12913)

- Using `CAST()` to convert values with long fractional and/or exponent parts to TIME returned wrong results. (Bug#12440)

- A race condition when creating temporary files caused a deadlock on Windows with threads in `Opening tables` or `Waiting for table` states. (Bug#12071)

- `DELETE` could report full-text index corruption (`Invalid key for table ...`) if the index was built with repair-by-sort, the data in the full-text index used UCA collation, and some word appeared in the data terminated by a 0xC2A0 character as well as by other non-letter characters. (Bug#11336)

- `Access Denied` error could be erroneously returned with specific grant combinations under high load. (Bug#7209)

- An `INSERT ... SELECT` statement between tables in a `MERGE` set can return errors when statement involves insert into child table from merge table or vice-versa. (Bug#5390)

### B.1.9. Changes in MySQL 4.1.16 (29 November 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- When a date column is set `NOT NULL` and contains `0000-00-00`, it will be updated for UPDATE statements that contains ``columnname` IS NULL` in the WHERE clause. (Bug#14186)

- When executing single-table `UPDATE` or `DELETE` queries containing an `ORDER BY ... LIMIT `N`` clause, but not having any `WHERE` clause, MySQL can now take advantage of an index to read the first `N` rows in the ordering specified in the query. If an index is used, only the first `N` records will be read, as opposed to scanning the entire table. (Bug#12915)

- The `MySQL-server` RPM now explicitly assigns the `mysql` system user to the `mysql` user group during the postinstallation process. This corrects an issue with upgrading the server on some Linux distributions whereby a previously existing `mysql` user was not changed to the `mysql` group, resulting in wrong groups for files created following the installation. (Bug#12823)

- MySQL 4.1 now supports character set conversion for seven additional `cp950` characters into the `big5` character set: `0xF9D6`, `0xF9D7`, `0xF9D8`, `0xF9D9`, `0xF9DA`, `0xF9DB`, and `0xF9DC`.

  ### Note

  If you move data containing these additional characters to an older MySQL installation which does not support them, you may encounter errors.

  (Bug#12476)

- The `CHAR()` function now takes an optional `USING `charset`` clause that may be used to produce a result in a specific character set rather than in the connection character set.

Bugs fixed:

- MySQL Cluster: Creating a table with packed keys failed silently. `NDB` now supports the `PACK_KEYS` option to `CREATE TABLE` correctly. (Bug#14514)

- MySQL Cluster: Repeated transactions using unique index lookups could cause a memory leak leading to error 288, `Out of index operations in transaction coordinator`. (Bug#14199)

- MySQL Cluster: `REPLACE` failed when attempting to update a primary key value in a Cluster table. (Bug#14007)

- MySQL Cluster: The perror utility included with the `MySQL-Server` RPM did not provide support for the `--ndb` option. It now supports this option, and so can be used to obtain error message text for MySQL Cluster error codes. (Bug#13740)

- MySQL Cluster: Placing multiple `[tcp default]` sections in the cluster's `config.ini` file crashed ndb_mgmd. (The process now exits gracefully in such cases, with an appropriate error message.) (Bug#13611)

- Closed a memory leak in the SSL code. (Bug#14780)

- Deletes from a `CSV` table could cause table corruption. (Bug#14672)

- A `LIMIT`-related optimization failed to take into account that `MyISAM` table indexes can be disabled, causing Error 124 when it tried to use such an index. (Bug#14616)

- Selecting from a table in both an outer query and a subquery could cause a server crash. (Bug#14482)

- `CREATE TABLE `tbl_name` (...) SELECT ...` could crash the server and write invalid data into the `.frm` file if the `CREATE TABLE` and `SELECT` both contained a column with the same name. Also, if a default value is specified in the column definition, it is now actually used. (Bug#14480)

- `mysql_fix_privilege_tables.sql` contained an erroneous comment that resulted in an error when the file contents were processed. (Bug#14469)

- Creating a table containing an `ENUM` or `SET` column from within a stored procedure or prepared statement caused a server crash later when executing the procedure or statement. (Bug#14410)

- Non-`latin1` object names were written with wrong character set to grant tables. (Bug#14406)

- For a table that had been opened with `HANDLER OPEN`, issuing `OPTIMIZE TABLE`, `ALTER TABLE`, or `REPAIR TABLE` caused a server crash. (Bug#14397)

- Portability fixes to support OpenSSL 0.9.8a. (Bug#14221)

- A `UNION` of `DECIMAL` columns could produce incorrect results. (Bug#14216)

- Statements of the form `CREATE TABLE ... SELECT ...` that created a column with a multi-byte character set could incorrectly calculate the maximum length of the column, resulting in a `Specified key was too long` error. (Bug#14139)

- Use of `WITH ROLLUP PROCEDURE ANALYSE()` could hang the server. (Bug#14138)

- When the `DATE_FORMAT()` function appeared in both the `SELECT` and `ORDER BY` clauses of a query but with arguments that differ by case (i.e. %m and %M), incorrect sorting may have occurred. (Bug#14016)

- `TIMEDIFF()`, `ADDTIME()`, and `STR_TO_DATE()` were not reporting that they could return `NULL`, so functions that invoked them might misinterpret their results. (Bug#14009)

- An update of a `CSV` table could cause a server crash. (Bug#13894)

- For `MyISAM` tables, incorrect query results or incorrect updates could occur under these conditions: There is a multiple-column index that includes a `BLOB` column that is not the last column in the index, and the statement performs a lookup on the index using key column values that have `NULL` for the `BLOB` column and that provide values for all columns up to the `BLOB` column and at least the next column in the index. (Bug#13814)

- The example configuration files supplied with MySQL distributions listed the `thread_cache_size` variable as `thread_cache`. (Bug#13811)

- mysqld_safe did not correctly start the `-max` version of the server (if it was present) if the `--ledir` option was given. (Bug#13774)

- Character set conversion was not being done for `FIND_IN_SET()`. (Bug#13751)

- On BSD systems, the system `crypt()` call could return an error for some salt values. The error was not handled, resulting in a server crash. (Bug#13619)

- Given a column `col_name` defined as `NOT NULL`, a `SELECT ... FROM ... WHERE `col_name` IS NULL` query following `SHOW TABLE STATUS` would erroneously return a non-empty result. (Bug#13535)

- Specifying `--default-character-set=cp-932` for mysqld would cause SQL scripts containing comments written using that character set to fail with a syntax error. (Bug#13487)

- Use of ``col_name` = VALUES(`col_name`)` in the `ON DUPLICATE KEY UPDATE` clause of an `INSERT` statement failed with an `Column '`col_name`' in field list is ambiguous` error. (Bug#13392)

- `LIKE` operations did not work reliably for the `cp1250` character set. (Bug#13347)

- `CAST(1E+300 TO SIGNED INT)` produced an incorrect result on little-endian machines. (Bug#13344)

- The default value of `query_prealloc_size` was set to 8192, lower than its minimum of 16384. The minimum has been lowered to 8192. (Bug#13334)

- mysqladmin and mysqldump would hang on SCO OpenServer. (Bug#13238)

- Multiple update queries using any type of subquery would be ignored by a replication slave when a condition such as `--replicate-ignore-table` like condition was used. (Bug#13236)

- `SELECT DISTINCT CHAR(`col_name`)` returned incorrect results after `SET NAMES utf8`. (Bug#13233)

- The server did not take character set into account in checking the width of the `mysql.user.Password` column. As a result, it could incorrectly generate long password hashes even if the column was not long enough to hold them. (Bug#13064)

- With `--log-slave-updates` `Exec_master_log_pos` of SQL thread lagged IO (Bug#13023)

- Maximum values were handled incorrectly for command-line options of type `GET_LL`. (Bug#12925)

- The endian byte in for spatial values in WKB format was not consistently respected. (Bug#12839)

- An `UPDATE` query using a join would be executed incorrectly on a replication slave. (Bug#12618)

- make failed when attempting to build MySQL in different directory other than that containing the source. (Bug#11827)

- On Windows, the server could crash during shutdown if both replication threads and normal client connection threads were active. (Bug#11796)

- An expression in an `ORDER BY` clause failed with `Unknown column '`col_name`' in 'order clause'` if the expression referred to a column alias. (Bug#11694)

- `LOAD DATA INFILE` would not accept the same character for both the `ESCAPED BY` and the `ENCLOSED BY` clauses. (Bug#11203)

- Issuing `STOP SLAVE` after having acquired a global read lock with `FLUSH TABLES WITH READ LOCK` caused a deadlock. Now `STOP SLAVE` is generates an error in such circumstances. (Bug#10942)

- Corrected a memory-copying problem for `big5` values when using icc compiler on Linux IA-64 systems. (Bug#10836)

- `PROCEDURE ANALYSE()` could suggest a data type with a negative display width. (Bug#10716)

- `InnoDB`: Pad UTF-8 `VARCHAR` columns with `0x20`. Pad UCS2 `CHAR` columns with `0x0020`. (Bug#10511)

- Perform character set conversion of constant values whenever possible without data loss. (Bug#10446)

- `PURGE MASTER LOGS` statement that used subquery for date crashed server. (Bug#10308)

- Multiple race conditions existed in OpenSSL, particularly noticeable on Solaris. (Bug#9270)

- The `--interactive-timeout` and `--slave-net-timeout` options for mysqld were not being obeyed on Mac OS X and other BSD-based platforms. (Bug#8731)

- `InnoDB`: During replication, There was a failure to record events in the binary log that still occurred even in the event of a `ROLLBACK`. For example, this sequence of commands:

      BEGIN;
      CREATE TEMPORARY TABLE t1 (a INT) ENGINE=INNODB;
      ROLLBACK;
      INSERT INTO t1 VALUES (1);

  would succeed on the replication master as expected. However, the `INSERT` would fail on the slave because the `ROLLBACK` would (erroneously) cause the `CREATE TEMPORARY TABLE` statement not to be written to the binlog. (Bug#7947)

- Queries of the form `(SELECT ...) ORDER BY ...` were being treated as a `UNION`. This improperly resulted in only distinct values being returned (because `UNION` by default eliminates duplicate results). Also, references to column aliases in `ORDER BY` clauses following parenthesized `SELECT` statements were not resolved properly. (Bug#7672)

- Character set file parsing during `mysql_real_connect()` read past the end of a memory buffer. (Bug#6413)

- Full-text indexing/searching failed for words that end with more than one apostrophe. (Bug#5686)

- On Windows, the server was not ignoring hidden or system directories that Windows may have created in the data directory, and would treat them as available databases. (Bug#4375)

### B.1.10. Changes in MySQL 4.1.15 (13 October 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- MySQL Cluster: The parsing of the `CLUSTERLOG` command by ndb_mgm was corrected to allow multiple items. (Bug#12833)

- The limit of 255 characters on the input buffer for mysql on Windows has been lifted. The exact limit depends on what the system allows, but can be up to 64K characters. A typical limit is 16K characters. (Bug#12929)

- Added the `myisam_stats_method`, which controls whether `NULL` values in indexes are considered the same or different when collecting statistics for `MyISAM` tables. This influences the query optimizer as described in Section 7.4.7, “`MyISAM` Index Statistics Collection”. (Bug#12232)

- A new command line argument was added to mysqld to ignore client character set information sent during handshake, and use server side settings instead, to reproduce 4.0 behavior :

      mysqld --skip-character-set-client-handshake

  (Bug#9948)

- `RAND()` no longer allows non-constant initializers. (Prior to MySQL 4.1.15, the effect of non-constant initializers is undefined.) (Bug#6172)

- When using `IF NOT EXISTS` with `CREATE DATABASE` or `CREATE TABLE`, a warning now is generated if the database or table already exists. : (Bug#6008)

- Better detection of connection timeout for replication servers on Windows allows elimination of extraneous `Lost connection` errors in the error log. (Bug#5588)

Bugs fixed:

- MySQL Cluster: Adding an index to a table with a large number of columns (more then 100) crashed the storage node. (Bug#13316)

- MySQL Cluster: The cluster management client `START BACKUP` command could be interrupted by a `SHOW` command. (Bug#13054)

- MySQL Cluster: Updating a column of one of the `TEXT` types during a cluster backup could cause the ndbd process to crash, due to the incorrect use of charset-normalized reads. This could also lead to character data having the wrong lettercase in the backup if such a column was updated during the backup; for example, supposing that the column used `latin_ci`, then “`aAa`” might be stored in the backup as “`AAA`”. (Bug#12950)

- MySQL Cluster: When it could not copy a fragment, ndbd exited without printing a message about the condition to the error log. Now the message is written. (Bug#12900)

- MySQL Cluster: When a Disk is full condition occurred, ndbd exited without reporting this condition in the error log. (Bug#12716)

- MySQL Cluster: An `ALTER TABLE` command caused loss of data stored prior to the issuing of the command. (Bug#12118)

- MySQL Cluster: Invalid values in `config.ini` caused ndb_mgmd to crash. (Bug#12043)

- MySQL Cluster: Multiple ndb_mgmd processes in a cluster did not know each other's IP addresses. (Bug#12037)

- MySQL Cluster: When a schema was detected to be corrupt, ndb neglected to close it, resulting in a file already open error if the schema was opened again later. written. (Bug#12027)

- MySQL Cluster: With two mgmd processes in a cluster, ndb_mgm output for `SHOW` would display the same IP address for both processes, even when they were on different hosts. (Bug#11595)

- MySQL Cluster: MySQL failed to compile when `--with-ndb-ccflags` was specified. (Bug#11538)

- MySQL Cluster: Improved error messages related to filesystem issues. (Bug#11218)

- MySQL Cluster: `LOAD DATA INFILE` with a large data file failed. (Bug#10694)

- MySQL Cluster: A cluster shutdown following the crash of a data node failed to terminate any remaining node processes, even though ndb_mgm showed the shutdown request as having been completed. (Bug#9996, Bug#10938, Bug#11623)

- MySQL Cluster: When deleting a great many (tens of thousands of) rows at once from an `NDB` table, an improperly dereferenced pointer could cause the mysqld process to crash. (Bug#9282)

- The server could over-allocate memory when performing a `FULLTEXT` search for stopwords only. (Bug#13582)

- After running configure with the `--with-embedded-privilege-control` option, the embedded server failed to build. (Bug#13501)

- `UNION` of two `DECIMAL` columns returned wrong field type. (Bug#13372)

- Comparisons involving row constructors containing constants could cause a server crash. (Bug#13356)

- MySQL would pass an incorrect key length to storage engines for `MIN()`. This could cause spurious warnings such as InnoDB: Warning: using a partial-field key prefix in search to appear in the `.err` log. (Bug#13218, Bug#11039)

- Aggregate functions sometimes incorrectly were allowed in the `WHERE` clause of `UPDATE` and `DELETE` statements. (Bug#13180)

- If special characters such as `'_'` , `'%'`, or the escape character were included within the prefix of a column index, `LIKE` pattern matching on the indexed column did not return the correct result. (Bug#13046, Bug#13919)

- `SHOW CREATE TABLE` did not display any `FOREIGN KEY` clauses if a temporary file could not be created. Now `SHOW CREATE TABLE` displays an error message in an SQL comment if this occurs. (Bug#13002)

- On HP-UX 11.x (PA-RISC), the `-L` option caused mysqlimport to crash. (Bug#12958)

- The counters for the `Key_read_requests`, `Key_reads`, `Key_write_requests`, and `Key_writes` status variables were changed from `unsigned long` to `unsigned longlong` to accommodate larger values before the variables roll over and restart from 0. (Bug#12920)

- For queries with `DISTINCT` and `WITH ROLLUP`, the `DISTINCT` should be applied after the rollup operation, but was not always. (Bug#12887)

- A column that can be `NULL` was not handled properly for `WITH ROLLUP` in a subquery or view. (Bug#12885)

- `MIN()` and `MAX()` sometimes returned a non-`NULL` value for an empty row set (for example, `SELECT MAX(1) FROM empty_table`). (Bug#12882)

- `GROUP_CONCAT()` ignored an empty string if it was the first value to occur in the result. (Bug#12863)

- `SELECT GROUP_CONCAT(...) FROM DUAL` in a subquery could cause the client to hang. (Bug#12861)

- If a client has opened an `InnoDB` table for which the `.ibd` file is missing, `InnoDB` would not honor a `DROP TABLE` statement for the table. (Bug#12852)

- The server crashed when one thread resized the query cache while another thread was using it. (Bug#12848)

- A concurrency problem for `CREATE ... SELECT` could cause a server crash. (Bug#12845)

- The `ARCHIVE` storage engine does not support deletes, but it was possible to delete by using `DELETE` or `TRUNCATE TABLE` with a `FEDERATED` table that points to an `ARCHIVE` table. (Bug#12836)

- After changing the character set with `SET CHARACTER SET`, the result of the `GROUP_CONCAT()` function was not converted to the proper character set. (Bug#12829)

- Reverted a change introduced in MySQL 4.1.13 (`SHOW FIELDS` truncated the `TYPE` column to 40 characters). This fix was reverted for MySQL 4.1 because it broke existing applications. The fix will be made in MySQL 5.0 instead (5.0.13). (Bug#12817)

  The patch for the following bugs was reverted: Bug#7142.

- An optimizer estimate of zero rows for a non-empty `InnoDB` table used in a left or right join could cause incomplete rollback for the table. (Bug#12779)

- Shared-memory connections were not working on Windows. (Bug#12723)

- Performing an `IS NULL` check on the `MIN()` or `MAX()` of an indexed column in a complex query could produce incorrect results. (Bug#12695)

- `CHECKSUM TABLE` locked `InnoDB` tables and did not use a consistent read. (Bug#12669)

- A `SELECT DISTINCT` query with a constant value for one of the columns would return only a single row. (Bug#12625)

- The `LIKE ... ESCAPE` syntax produced invalid results when escape character was larger than one byte. (Bug#12611)

- `DELETE` or `UPDATE` for an indexed `MyISAM` table could fail. This was due to a change in end-space comparison behavior from 4.0 to 4.1. (Bug#12565)

- When any `--replicate-wild-* option` is used, the slave ignores `SET ONE_SHOT TIME_ZONE` statements as belonging to a non-replicated table. (Bug#12542)

- A `UNION` of long `utf8` `VARCHAR` columns was sometimes returned as a column with a `LONGTEXT` data type rather than `VARCHAR`. This could prevent such queries from working at all if selected into a `MEMORY` table because the `MEMORY` storage engine does not support the `TEXT` data types. (Bug#12537)

- A client connection thread cleanup problem caused the server to crash when closing the connection if the binary log was enabled. (Bug#12517)

- `MEMORY` tables using `B-Tree` index on 64-bit platforms could produce false table is full errors. (Bug#12460)

- Deadlock occurred when several account management statements were run (particularly between `FLUSH PRIVILEGES`/`SET PASSWORD` and `GRANT`/`REVOKE` statements). (Bug#12423)

- `InnoDB` was too permissive with `LOCK TABLE ... READ LOCAL` and allowed new inserts into the table. Now `READ LOCAL` is equivalent to `READ` for `InnoDB`. This will cause slightly more locking in mysqldump, but makes `InnoDB` table dumps consistent with `MyISAM` table dumps. (Bug#12410)

- A prepared statement failed with `Illegal mix of collations` if the client character set was `utf8` and the statement used a table that had a character set of `latin1`. (Bug#12371)

- The value of `character_set_results` could be set to `NULL`, but returned the string `"NULL"` when retrieved. (Bug#12363)

- On Windows, the server was preventing tables from being created if the table name was a prefix of a forbidden name. For example, `nul` is a forbidden name because it's the same as a Windows device name, but a table with the name of `n` or `nu` was being forbidden as well. (Bug#12325)

- Users created using an IP address or other alias rather than a hostname listed in `/etc/hosts` could not set their own passwords. (Bug#12302)

- `CHECKSUM TABLE` command returned incorrect results for tables with deleted rows. After upgrading, users who used stored checksum information to detect table changes should rebuild their checksum data. (Bug#12296)

- For `VARCHAR` columns with the `ucs2` character set, `InnoDB` trimmed trailing `0x20` bytes rather than `0x0020` words, resulting in incorrect index lookups later. (Bug#12178)

- Outer join elimination was erroneously applied for some queries that used a `NOT BETWEEN` condition, an `IN(`value_list`)` condition, or an `IF()` condition. (Bug#12102, Bug#12101)

- `LOAD DATA INFILE` did not respect the `NO_AUTO_VALUE_ON_ZERO` SQL mode setting. (Bug#12053)

- `TRUNCATE TABLE` did not work with `TEMPORARY` `InnoDB` tables. (Bug#11816)

- Queries that created implicit temporary tables could return incorrect data types for some columns. (Bug#11718)

- Use of a user-defined function within the `HAVING` clause of a query resulted in an `Unknown column` error. (Bug#11553)

- `ALTER TABLE `db_name.t` RENAME `t`` did not move the table to default database unless the new name was qualified with the database name. (Bug#11493)

- mysqld_multi now quotes arguments on command lines that it constructs to avoid problems with arguments that contain shell metacharacters. (Bug#11280)

- The `--replicate-rewrite-db` and `--replicate-do-table` options did not work for statements in which tables were aliased to names other than those listed by the options. (Bug#11139)

- Spatial index corruption could occur during updates. (Bug#9645)

- The `have_innodb` read-only system variable could not be selected with `SELECT @@have_innodb`. (Bug#9613)

- Queries against a `MERGE` table that has a composite index could produce incorrect results. (Bug#9112)

- Display of the `AUTO_INCREMENT` attribute by `SHOW CREATE TABLE` was not controlled by the `NO_FIELD_OPTIONS` SQL mode as it should have been. (Bug#7977)

- The data type for `DECIMAL` columns was not respected when updating the column from another column. For example, updating a `DECIMAL(10,1)` column with the value from a `DECIMAL(10,5)` column resulted in a `DECIMAL(10,5)` value being stored. Similarly, altering a column with a `DECIMAL(10,5)` datatype to a `DECIMAL(10,1)` data type did not properly convert data values. (Bug#7598)

- MySQL programs in binary distributions for Solaris 8/9/10 x86 systems would not run on Pentium III machines. (Bug#6772)

- On Windows when the `--innodb_buffer_pool_awe_mem_mb` option has been given, the server detects whether AWE support is available and has been compiled into the server, and displays an appropriate error message if not. (Bug#6581)

- If a `DROP DATABASE` fails on a master server due to the presence of a non-database file in the database directory, the master have the database tables deleted, but not the slaves. To deal with failed database drops, we now write `DROP TABLE` statements to the binary log for the tables so that they are dropped on slaves. (Bug#4680)

- myisampack did not properly pack `BLOB` values larger than 224 bytes. (Bug#4214)

### B.1.11. Changes in MySQL 4.1.14 (17 August 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- MySQL Cluster: Improved handling of the configuration variables `NoOfPagesToDiskDuringRestartACC`, `NoOfPagesToDiskAfterRestartACC`, `NoOfPagesToDiskDuringRestartTUP`, and `NoOfPagesToDiskAfterRestartTUP` should result in noticeably faster startup times for MySQL Cluster. (Bug#12149)

- MySQL Cluster: A new `-P` option is available for use with the ndb_mgmd client. When called with this option, ndb_mgmd prints all configuration data to `stdout`, then exits.

- If a thread (connection) has tables locked, the query cache is switched off for that thread. This prevents invalid results where the locking thread inserts values between a second thread connecting and selecting from the table. (Bug#12385)

- Added an optimization that avoids key access with `NULL` keys for the `ref` method when used in outer joins. (Bug#12144)

- Added support of where clause for queries with `FROM DUAL`. (Bug#11745)

- `SHOW CHARACTER SET` and `INFORMATION_SCHEMA` now properly report the `Latin1` character set as `cp1252`. (Bug#11216)

- Added new query cache test for the embedded server to the test suite, there are now specific tests for the embedded and non-embedded servers. (Bug#9508)

- The MySQL server now starts correctly with all combinations of `basedir` and `datadir` resolving an issue introduced by the original fix for this bug in MySQL 4.1.9. (Bug#7249)

  See also Bug#7518

Bugs fixed:

- MySQL Cluster: The temporary tables created by an `ALTER TABLE` on an `NDB` table were visible to all SQL nodes in the cluster. (Bug#12055)

- MySQL Cluster: `NDB` ignored the `Hostname` option in the `[ndbd default]` section of the cluster configuration file. (Bug#12028)

- MySQL Cluster: The output of perror `--help` did not display any information about the `--ndb` option. (Bug#11999)

- MySQL Cluster: Attempting to create or drop tables during a backup would cause the cluster to shut down. (Bug#11942)

- MySQL Cluster: ndb_mgmd leaked file descriptors. (Bug#11898)

- Mishandling of comparison for rows containing `NULL` values against rows produced by an `IN` subquery could cause a server crash. (Bug#12392)

- Concatenating `USER()` or `DATABASE()` with a column produced invalid results. (Bug#12351)

- Creation of the `mysql` group account failed during the RPM installation. (Bug#12348)

- Renamed the `rest()` macro in `my_list.h` to `list_rest()` to avoid name clashes with user code. (Bug#12327)

- Performing `DATE(LEFT(`column`,8))` on a `DATE` column produces incorrect results. (Bug#12266)

- myisampack failed to delete `.TMD` temporary files when run with `-T` option. (Bug#12235)

- Updated dependency list for RPM builds to include missing dependencies such as `useradd` and `groupadd`. (Bug#12233)

- `InnoDB`: Do not flush after each write, not even before setting up the doublewrite buffer. Flushing can be extremely slow on some systems. (Bug#12125)

- Two threads could potentially initialize different characters sets and overwrite each other. (Bug#12109)

- `GROUP_CONCAT` ignores the `DISTINCT` modifier when used in a query joining multiple tables where one of the tables has a single row. (Bug#12095)

- `big5` strings were not being stored in `FULLTEXT` index. (Bug#12075)

- `SHOW BINARY LOGS` displayed a file size of 0 for all log files but the current one if the files were not located in the data directory. (Bug#12004)

- `mysql_next_result()` returns incorrect value if final query in a batch fails. (Bug#12001)

- Character data truncated when GBK characters `0xA3A0` and `0xA1` are present. (Bug#11987)

- `UNION` query with `FULLTEXT` could cause server crash. (Bug#11869)

- Corrected an optimizer problem with `NOT NULL` constraints within a subquery in an `UPDATE` statement that resulted in a server crash. (Bug#11868)

- Some subqueries of the form `SELECT ... WHERE ROW(...) IN (`subquery)`` were being handled incorrectly. (Bug#11867)

- Creating a table with a `SET` or `ENUM` column with the `DEFAULT 0` clause caused a server crash if the table's character set was `utf8`. (Bug#11819)

- Comparisons like `SELECT "A\\" LIKE "A\\";` fail when using `SET NAMES utf8;`. (Bug#11754)

- The `mysql_info()` C API function could return incorrect data when executed as part of a multi-statement that included a mix of statements that do and do not return information. (Bug#11688)

- Attempting to repair a table having a fulltext index on a column containing words whose length exceeded 21 characters and where `myisam_repair_threads` was greater than 1 would crash the server. (Bug#11684)

- LIKE pattern matching using prefix index didn't return correct result. (Bug#11650)

- Corrected a problem with the optimizer incorrectly adding `NOT NULL` constraints, producing in incorrect results for complex queries. (Bug#11482)

- Queries with subqueries that contain outer joins could return wrong results. (Bug#11479)

- Multiplying `ABS()` output by a negative number would return incorrect results. (Bug#11402)

- For PKG installs on Mac OS X, the preinstallation and postinstallation scripts were being run only for new installations and not for upgrade installations, resulting in an incomplete installation process. (Bug#11380)

- Prepared statement parameters could cause errors in the binary log if the character set was `cp932`. (Bug#11338)

- The `LPAD()` and `RPAD()` functions returned the wrong length to `mysql_fetch_fields()`. (Bug#11311)

- For prepared statements, the SQL parser did not disallow “ `?` ” parameter markers immediately adjacent to other tokens, which could result in malformed statements in the binary log. (For example, `SELECT * FROM t WHERE? = 1` could become `SELECT * FROM t WHERE0 = 1`.) (Bug#11299)

- The C API function `mysql_stmt_reset()` did not clear error information. (Bug#11183)

- `myisam.test` failed when server compiled using `--without-geometry` option. (Bug#11083)

- User variables were not automatically cast for comparisons, causing queries to fail if the column and connection character sets differed. Now when mixing strings with different character sets but the same coercibility, allow conversion if one character set is a superset of the other. (Bug#10892)

- Slave I/O threads were considered to be in the running state when launched (rather than after successfully connecting to the master server), resulting in incorrect `SHOW SLAVE STATUS` output. (Bug#10780)

- `SELECT @@local...` returned `@@session...` in the column header. (Bug#10724)

- When two threads competed for the same table, a deadlock could occur if one thread also had a lock on another table through `LOCK TABLES` and the thread was attempting to remove the table in some manner while the other thread tried to place locks on both tables. (Bug#10600)

- Incorrect error message displayed if user attempted to create a table in a non-existing database using `CREATE `database_name`.`table_name`` syntax. (Bug#10407)

- `GROUP_CONCAT()` sometimes returned a result with a different collation from that of its arguments. (Bug#10201)

- `INSERT ... SELECT ... ON DUPLICATE KEY UPDATE` could fail with an erroneous “Column '`col_name`' specified twice” error. (Bug#10109)

- Multiple-table `UPDATE` queries using `CONVERT_TZ()` would fail with an error. (Bug#9979)

- The value of `max_connections_per_hour` was capped by the unrelated `max_user_connections` setting. (Bug#9947)

- `mysql_fetch_fields()` returned incorrect length information for `MEDIUM` and `LONG` `TEXT` and `BLOB` columns. (Bug#9735)

- `FLUSH TABLES WITH READ LOCK` combined with `LOCK TABLE .. WRITE` caused deadlock. (Bug#9459)

- Server-side prepared statements failed for columns with a character set of `ucs2`. (Bug#9442)

- In SQL prepared statements, comparisons could fail for values not equally space-padded. For example, `SELECT 'a' = 'a ';` returns 1, but `PREPARE s FROM 'SELECT ?=?'; SET @a = 'a', @b = 'a '; PREPARE s FROM 'SELECT ?=?'; EXECUTE s USING @a, @b;` incorrectly returned 0. (Bug#9379)

- References to system variables in an SQL statement prepared with `PREPARE` were evaluated during `EXECUTE` to their values at prepare time, not to their values at execution time. (Bug#9359)

- For server shutdown on Windows, error messages of the form `Forcing close of thread `n` user: '`name`'` were being written to the error log. Now connections are closed more gracefully without generating error messages. (Bug#7403)

- `ISO-8601` formatted dates were not being parsed correctly. (Bug#7308)

- Pathame values for options such as `---basedir` or `--datadir` didn't work on Japanese Windows machines for directory names containing multi-byte characters having a second byte of `0x5C` (“ `\` ”). (Bug#5439)

### B.1.12. Changes in MySQL 4.1.13 (15 July 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Incompatible Change: Previously, conversion of `DATETIME` values to numeric form by adding zero produced a result in `YYYYMMDDHHMMSS` format. The result of `DATETIME+0` is now in `YYYYMMDDHHMMSS.000000` format. (Bug#12268)

- System variables are now treated as having `SYSVAR` (system constant) coercibility. For example, `@@version` is now treated like `VERSION()` and `@@character_set_client` is now treated like `CHARSET( USER() )`. See Section 9.1.5.4, “Some Special Cases Where the Collation Determination Is Tricky”. (Bug#10904)

- `MEMORY` tables now support indexes of up to 500 bytes. See Section 13.4, “The `MEMORY` (`HEAP`) Storage Engine”. (Bug#10566)

- The `table`, `type`, and `rows` columns of `EXPLAIN` output can now be `NULL`. This is required for using `EXPLAIN` on `SELECT` queries that use no tables, such as `EXPLAIN SELECT 1`). (Bug#9899)

- You can again refer to other tables in the `ON DUPLICATE KEY UPDATE` part of an `INSERT ... SELECT` statement as long as there is no `GROUP BY` in the `SELECT` part. One side effect of this is that you may have to qualify non-unique column names in the values part of `ON DUPLICATE KEY UPDATE`. (Bug#9728, Bug#8147)

- Added the `--log-slow-admin-statements` server option to request logging of slow administrative statements such as `OPTIMIZE TABLE`, `ANALYZE TABLE`, and `ALTER TABLE` to the slow query log. These statements were logged in MySQL 4.0, but not in 4.1. (Bug#9141)

- Expanded on information provided in general log and slow query log for prepared statements. (Bug#8367, Bug#9334)

- Added `mysql_set_character_set()` C API function for setting the default character set of the current connection. This allows clients to affect the character set used by `mysql_real_escape_string()`. (Bug#8317)

- Some data definition statements (`CREATE TABLE` where the table was not a temporary table, `TRUNCATE TABLE`, `DROP DATABASE`, and `CREATE DATABASE`) were not being written to the binary log after a `ROLLBACK`. This also caused problems with replication.

  ### Important

  As a result of this fix, the folowing statements now cause an implicit commit:

  - `CREATE TABLE`

  - `TRUNCATE TABLE`

  - `DROP DATABASE`

  - `CREATE DATABASE`

  (Bug#6883)

- Added the `--add-drop-database` option to `mysqldump`. (Bug#3716)

- `SHOW BINARY LOGS` now displays a `File_size` column that indicates the size of each file.

- Security improvement: Applied a patch to fix a UDF library-loading vulnerability that could result in a buffer overflow and code execution. (CVE-2005-2558)

- `InnoDB`: When creating or extending an InnoDB data file, allocate at most one megabyte at a time for initializing the file. Previously, InnoDB used to allocate and initialize 1 or 8 megabytes of memory, even if a few 16-kilobyte pages were to be written. This fix improves the performance of `CREATE TABLE` in `innodb_file_per_table` mode.

Bugs fixed:

- Security Fix: A vulnerability in `zlib` could result in a buffer overflow and arbitrary code execution. Shortly after MySQL 4.1.13 was released, a second potential `zlib` security flaw was discovered and fixed. A patch for this flaw was applied to the 4.1.13 sources, and the result published as MySQL 4.1.13a. The affected binaries were rebuilt. (Bug#11844, CVE-2005-2096, CVE-2005-1849)

- Security Fix: On Windows systems, a user with any of the following privileges

  - `REFERENCES`

  - `CREATE TEMPORARY TABLES`

  - `GRANT OPTION`

  - `CREATE`

  - `SELECT`

  on `*.*` could crash mysqld by issuing a `USE LPT1;` or `USE PRN;` command. In addition, any of the commands `USE NUL;`, `USE CON;`, `USE COM1;`, or `USE AUX;` would report success even though the database was not in fact changed. (Bug#9148)

- MySQL Cluster: `NDB` failed to build with gcc 4.0. (Bug#11377)

- MySQL Cluster: When trying to open a table that could not be discovered or unpacked, the cluster returned error codes which the MySQL server falsely interpreted as operating system errors. (Bug#10365)

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

- Selecting the result of an aggregate function for an `ENUM` or `SET` column within a subquery could result in a server crash. (Bug#11821)

- Corrected an optimization failure where a query returned an incorrect result for use of a newly populated table until the table was flushed. (Bug#11700)

- The `--master-data` option for mysqldump resulted in no error if the binary log was not enabled. Now an error occurs unless the `--force` option is given. (Bug#11678)

- Invoking the `DES_ENCRYPT()` function could cause a server crash if the server was started without the `--des-key-file` option. (Bug#11643)

- mysqldump now exports `HASH` index definitions using `USING` rather than `TYPE` when the index name is optional. This corrects a problem when reloading the output for `PRIMARY KEY` definition, because `TYPE` must be preceded an index name, which is not given for a `PRIMARY KEY`. (Bug#11635)

- IP addresses not shown in `ndb_mgm SHOW` command on second ndb_mgmd (or on ndb_mgmd restart). (Bug#11596)

- Modifying a `CHAR` column with the `utf8` character set to a shorter length did not properly truncate values due to not computing their length in `utf8` character units. (Bug#11591)

- MySQL would not compile correctly on QNX due to missing `rint()` function. (Bug#11544)

- A `ROLLUP` query could return a wrong result set when its `GROUP BY` clause contained references to the same column. (Bug#11543)

- Queries with subqueries in the `FROM` clause were not being added to the query cache. (Bug#11522)

- Using `CONCAT_WS()` on a column set `NOT NULL` caused incorrect results when used in a `LEFT JOIN`. (Bug#11469)

- Prepared statement with subqueries returned corrupt data. (Bug#11458)

- Temporary tables were created in the data directory instead of `tmpdir`. (Bug#11440)

- Errors could occur when performing `GROUP BY` on calculated values of a single row table. These could sometimes cause the server to crash on Windows. (Bug#11414)

- `LOAD DATA ... REPLACE INTO ...` on a replication slave failed for an `InnoDB` table having a unique index in addition to the primary key. (Bug#11401)

- Server crashed when using `GROUP BY` on the result of a `DIV` operation on a `DATETIME` value. (Bug#11385)

- Manually inserting a row with `host=''` into `mysql.tables_priv` and performing a `FLUSH PRIVILEGES` would cause the server to crash. (Bug#11330)

- Possible `NULL` values in `BLOB` columns could crash the server when a `BLOB` was used in a `GROUP BY` query. (Bug#11295)

- Optimizer performed range check when comparing unsigned integers to negative constants, could cause errors. (Bug#11185)

- Some internal functions did not take into account that, for multi-byte character sets, `CHAR` and `VARCHAR` columns could exceed 255 bytes, which could cause the server to crash. (Bug#11167)

- Fixed a portability problem testing for `crypt()` support that caused compilation problems when using OpenSSL/yaSSL on HP-UX and Mac OS X. (Bug#11150, Bug#10675)

- The `NULLIF()` function could produce incorrect results if the first argument was `NULL`. (Bug#11142)

- `mysqld_safe` would sometimes fail to remove the pid file for the old `mysql` process after a crash. As a result, the server would fail to start due to a false `A mysqld process already exists...` error. (Bug#11122)

- `SHOW WARNINGS` with a `LIMIT 0` clause returned all messages rather than an empty result set. (Bug#11095)

- Fixed a server crash resulting from an attempt to allocate too much memory when `GROUP BY `blob_col`` and `COUNT(DISTINCT)` were used. (Bug#11088)

- Fixed 64 bit compiler warning for packet length in replication. (Bug#11064)

- A `CREATE TABLE `db_name`.`tbl_name` LIKE ...` statement would crash the server when no database was selected. (Bug#11028)

- The `mysql_config` script did not handle symbolic linking properly. (Bug#10986)

- The value returned by the `FIELD()` function was incorrect when its parameter list contained one or more instances of `NULL`. (Bug#10944)

- The hostname cache was not working. (Bug#10931)

- `INSERT ... SELECT ... ON DUPLICATE KEY UPDATE` produced inaccurate results. (Bug#10886)

- A three byte buffer overflow in the client functions caused improper exiting of the client when reading a command from the user. (Bug#10841)

- The mysql client would output a prompt twice following input of very long strings, because it incorrectly assumed that a call to the _cgets() function would clear the input buffer. (Bug#10840)

- Setting `@@SQL_MODE = NULL` caused an erroneous error message. (Bug#10732)

- Inserting a `DOUBLE` value into a `utf8` string column crashed the server on Windows. (Bug#10714)

- On Mac OS X, `libmysqlclient_r.a` now is built with `--fno-common` to make it possible to link a shared two-level namespace library against `libmysqlclient_r.a`. (Bug#10638)

- `InnoDB` wrongly reported in the `.err` log that MySQL wass trying to drop a nonexistent table, if no more room remained in the tablespace. (Bug#10607)

- Executing `LOAD INDEX INTO CACHE` for a table while other threads where selecting from the table caused a deadlock. (Bug#10602)

- `DES_ENCRYPT()` and `DES_DECRYPT()` require SSL support to be enabled, but were not checking for it. Checking for incorrect arguments or resource exhaustion was also improved for these functions. (Bug#10589)

- The `LAST_DAY()` failed to return `NULL` when supplied with an invalid argument. See Section 11.6, “Date and Time Functions”. (Bug#10568)

- Queries of the form `UPDATE ... (SELECT ... ) SET ...` run on a replication master would crash all the slaves. (Bug#10442, CVE-2004-4380)

- Fixed a server crash for `INSERT ... ON DUPLICATE KEY UPDATE` with `MERGE` tables, which do not have unique indexes. (Bug#10400)

- A problem with the `my_global.h` file caused compilation of MySQL to fail on single-processor Linux systems running 2.6 kernels. (Bug#10364)

- `SUBSTRING()` did not work properly for input in the `ucs2` character set. (Bug#10344)

- `DROP DATABASE` failed check for all referencing `InnoDB` tables from other databases before dropping any tables. (Bug#10335)

- Fixed a mysqldump crash that occurred with the `--complete-insert` option when dumping tables with a large number of long column names. (Bug#10286)

- When used within a subquery, `SUBSTRING()` returned an empty string. (Bug#10269)

- Queries against a table using a compound index based on the length of a UTF-8 text column produced incorrect results. For example, given a table with an index defined as shown:

      CREATE TABLE t (
        id INT NOT NULL,
        city VARCHAR(20) NOT NULL,
        KEY (city(7),id)
      ) TYPE=MYISAM CHARACTER SET=utf8;

  Assuming that suitable data has been inserted into the table, then a query such as `SELECT * FROM t WHERE city = 'Durban';` would fail. (Bug#10253)

- Using `#pragma interface` or `#pragma implementation` in source files caused portability issues for `cygwin`. (Bug#10241)

- Fixed a server crash resulting from `CREATE TABLE ... SELECT` that selected from a table being altered by `ALTER TABLE`. (Bug#10224)

- Fixed a server crash resulting from invalid string pointer when inserting into the `mysql.host` table. (Bug#10181)

- For `MEMORY` tables, it was possible for updates to be performed using outdated key statistics when the updates involved only very small changes in a very few rows. This resulted in the random failures of queries such as `UPDATE t SET col = col + 1 WHERE col_key = 2;` where the same query with no `WHERE` clause would succeed. (Bug#10178)

- `CASE` operator returns incorrect result when its arguments are not constants and its return value is put into a regular or temporary table (temporary == created by SQL engine for `UNION`/non-indexed `GROUP BY` and such operations). (Bug#10151)

- When used in joins, `SUBSTRING()` failed to truncate to zero those string values that could not be converted to numbers. (Bug#10124)

- Fixed a problem creating the result set for a `UNION` that involved long string values. Values were not being converted correctly to `TEXT` values. (Bug#10025)

- Fixed an overly strict debugging assertion that caused debug server builds to fail for some ``col_name` = `const_expr`` , where `const_expr` was a constant expression such as a subquery. (Bug#10020)

- The handling by the `HEX()` function of numbers larger than 264 was improved. (Bug#9854)

- Fixed a problem with the `cp1250_czech_cs` collation that caused some `LIKE` comparisons to fail. (Bug#9759)

- On Windows, with `lower_case_table_names` set to 2, using `ALTER TABLE` to alter a `MEMORY` or `InnoDB` table that had a mixed-case name also improperly changed the name to lowercase. (Bug#9660)

- `mysqldump --xml` did not format `NULL` column values correctly. (Bug#9657)

- `ALTER TABLE ... ENABLE INDEXES` treated `NULL` values as equal when collecting index statistics for `MyISAM` tables, resulting in different statistics from those generated by `ANALYZE TABLE` and causing the optimizer to make poor index choices later. The same problem occurred for bulk insert statistics collection. Now `NULL` values are treated as unequal, just as for `ANALYZE TABLE`. (Bug#9622)

- The `--no-data` option for mysqldump was being ignored if table names were given after the database name. (Bug#9558)

- MySQL sometimes reported erroneously that certain character values had crashed a table when trying to convert other character sets to UTF-8. (Bug#9557)

- `CREATE TABLE t AS SELECT UUID()` created a `VARCHAR(12)` column, which is too small to hold the 36-character result from `UUID()`. (Bug#9535)

- Fixed a problem resolving table names with `lower_case_table_names=2` when the table name lettercase differed in the `FROM` and `WHERE` clauses. (Bug#9500)

- `SHOW WARNINGS` did not properly display warnings generated by executing a cached query. (Bug#9414)

- Incorrect results when searching using `IN()` where search items included `NULL` and `0`. (Bug#9393)

- An `UPDATE` query containing a subquery caused replication to fail. (Bug#9361)

- mysqldump could crash for illegal or non-existent table names. (Bug#9358)

- `SELECT DISTINCT ... GROUP BY `constant`` returned multiple rows (it should return a single row). (Bug#8614)

- The server timed out SSL connections too quickly on Windows. (Bug#8572)

- For a `MERGE` table with `MyISAM` tables in other, symlinked, databases, `SHOW CREATE TABLE` reported the `MyISAM` tables using the name of the symlinked directory rather than the database name. (Bug#8183)

- `OPTIMIZE` run on an `InnoDB` table did not return a Table is full error if there was insufficient room in the tablespace. (Bug#8135)

- The `mysqlhotcopy` script was not parsing the output of `SHOW SLAVE STATUS` correctly when called with the `--record_log_pos` option. (Bug#7967)

- Fixed a problem causing an incorrect result for columns that include an aggregate function as part of an expression when `WITH ROLLUP` is added to `GROUP BY`. (Bug#7914)

- Queries with `ROLLUP` returned wrong results for expressions containing`GROUP BY` columns. (Bug#7894)

- Fixed hang/crash with Boolean full-text search where a query contained more query terms that one-third of the query length (it could be achieved with truncation operator: 'a*b*c*d*'). (Bug#7858)

- `GROUP_CONCAT()` with `DISTINCT` and `WITH ROLLUP` ignored `DISTINCT` for some rows. (Bug#7405)

- `SHOW FIELDS` truncated the `TYPE` column to 40 characters.

  ### Note

  This fix was reverted in MySQL 4.1.15 because it broke existing applications.

  (Bug#7142)

  See also Bug#12817

- Added a missing mutex when rotating the relay logs. Also, the server now logs an error message if the size of a relay log cannot be read. (Bug#6987)

- Locking for `CREATE TABLE ... SELECT` for `InnoDB` tables was too weak. It allowed `INSERT` statements issued for the created table while the `CREATE TABLE` statement was still running to appear in the binary log before the `CREATE TABLE` statement. (Bug#6678)

- The incorrect sequence of statements `HANDLER `tbl_name` READ `index_name` NEXT` without a preceding `HANDLER `tbl_name` READ `index_name` = (`value_list`)` for an `InnoDB` table resulted in a server crash rather than an error. (Bug#5373)

- `REFERENCES`

- `SELECT`

- `CREATE TEMPORARY TABLES`

- `GRANT OPTION`

- `CREATE`

### B.1.13. Changes in MySQL 4.1.12 (13 May 2005)

### Note

The fix for interpretation of `MERGE` table `.MRG` files (Bug#10687) was made for Windows builds after MySQL 4.1.12 was released and is present in MySQL 4.1.12a.

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Incompatible Change: The behavior of `LOAD DATA INFILE` and `SELECT ... INTO OUTFILE` has changed when the `FIELDS TERMINATED BY` and `FIELDS ENCLOSED BY` values both are empty. Formerly, a column was read or written the display width of the column. For example, `INT(4)` was read or written using a field with a width of 4. Now columns are read and written using a field width wide enough to hold all values in the field. However, data files written before this change was made might not be reloaded correctly with `LOAD DATA INFILE` for MySQL 4.1.12 and up. This change also affects data files read by mysqlimport and written by mysqldump --tab, which use `LOAD DATA INFILE` and `SELECT ... INTO OUTFILE`. For more information, see Section 12.2.5, “`LOAD DATA INFILE` Syntax”. (Bug#12564)

- When the server cannot read a table because it cannot read the `.frm` file, print a message that the table was created with a different version of MySQL. (This can happen if you create tables that use new features and then downgrade to an older version of MySQL.) (Bug#10435)

- `InnoDB`: When `FOREIGN_KEY_CHECKS=0`, `ALTER TABLE` and `RENAME TABLE` will ignore any type incompatibilities between referencing and referenced columns. Thus, it will be possible to convert the character sets of columns that participate in a foreign key. Be sure to convert all tables before modifying any data! (Bug#9802)

- New `/*>` prompt for mysql. This prompt indicates that a `/* ... */` comment was begun on an earlier line and the closing `*/` sequence has not yet been seen. (Bug#9186)

- `InnoDB`: When the maximum length of `SHOW INNODB STATUS` output would be exceeded, truncate the beginning of the list of active transactions, instead of truncating the end of the output. (Bug#5436)

- Updated version of `libedit` to 2.9. (Bug#2596)

- Previously in MySQL 4.1, an `Illegal mix of collations` error occurred when mixing strings from same character set when one had a non-binary collation and the other a binary collation. Now the binary collation takes precedence, so that both strings are treated as having the binary collation. This restores compatibility with MySQL 4.0 behavior.

- Added the `cp932` Japanese character set.

- `InnoDB`: If `innodb_locks_unsafe_for_binlog` option set and isolation level of the transaction is not set to serializable then `InnoDB` uses a consistent read for select in clauses like `INSERT INTO ... SELECT` and `UPDATE ... (SELECT)` that do not specify `FOR UPDATE` or `IN SHARE MODE`. Thus no locks are set to rows read from selected table.

- Added `--debug` option to my_print_defaults.

Bugs fixed:

- Security Fix: mysql_install_db created the `mysql_install_db.X` file with a predictable filename and insecure permissions, which allowed local users to execute arbitrary SQL statements by modifying the file's contents. (CVE-2005-1636)

- `MERGE` tables could fail on Windows due to incorrect interpretation of pathname separator characters for filenames in the `.MRG` file. (Bug#10687)

- `CHAR` and `VARCHAR` columns that used the `sjis` character set were not being saved correctly, causing the following columns to be corrupted. (Bug#10493)

- Fixed handling of floats and doubles when using prepared statement API in the embedded server. (Bug#10443)

- The `--delimiter` option for the nds_select program was non-functional. (Bug#10287)

- Fixed a portability problem in compiling `mysql.cc` with VC++ on Windows. (Bug#10245)

- Fixed a bug in the key cache that caused a core dump. (Bug#10167)

- When `SELECT `constant`` was the final `SELECT` in a `UNION`, a trailing `LIMIT ...` worked, but a trailing `ORDER BY ...` or `ORDER BY ... LIMIT ...` did not. (Bug#10032)

- Fixed some awk script portability problems in cmd-line-utils/libedit/makelist.sh. (Bug#9954)

- The error message for exceeding `MAX_CONNECTIONS_PER_HOUR` mistakenly referred to `max_connections`. (Bug#9947)

- Fixed a bug that caused concurrent inserts to be allowed into the tables in the `SELECT ... UNION ...` part of `INSERT ... SELECT ... UNION ...`. This could result in the incorrect order of queries in the binary log. (Bug#9922)

- For a user-defined function invoked from within a prepared statement, the UDF's initialization routine was invoked for each execution of the statement, but the deinitialization routine was not. (It was invoked only when the statement was closed.) For UDFs that have an expensive deinit function (such as `myperl`), this fix has negative performance consequences. (Bug#9913)

- `RENAME TABLE` for an `ARCHIVE` table failed if the `.arn` file was not present. (Bug#9911)

- mysql.server no longer uses non-portable alias command or LSB functions. (Bug#9852)

- my_print_defaults was ignoring the `--defaults-extra-file` option or crashing when the option was given. (Bug#9851, Bug#9136)

- `SELECT ROUND(`expr`)` produced a different result from `CREATE TABLE ... SELECT ROUND(`expr`)`. (Bug#9837)

- Security fix: If mysqld was started with `--user=`non_existent_user`` , it would run using the privileges of the account it was invoked from, even if that was `root`. (Bug#9833)

- Starting mysqld with the `--skip-innodb` and `--default-storage-engine=innodb` (or `--default-table-type=innodb` caused a server crash. (Bug#9815)

- Queries containing `CURRENT_USER()` incorrectly were registered in the query cache. (Bug#9796)

- Corrected some failures of prepared statements for SQL (`PREPARE` plus `EXECUTE`) to return all rows for some `SELECT` statements. (Bug#9777, Bug#9096)

- Fix `CREATE TABLE ... LIKE` to work when `lower_case_table_names` is set on a case-sensitive filesystem and the source table name is not given in lowercase. (Bug#9761)

- `net_read_timeout` and `net_write_timeout` were not being respected on Windows. (Bug#9721)

- Use of a subquery that used `WITH ROLLUP` in the `FROM` clause of the main query sometimes resulted in a `Column cannot be null` error. (Bug#9681)

- Fix for auto-increment not working with `INSERT..SELECT` and NDB storage engine. (Bug#9675)

- `InnoDB`: Fix assertion failures of type `ut_a(cursor->old_stored == BTR_PCUR_OLD_STORED)` and `prebuilt->template_type == 0`. This bug was introduced in 4.1.10 and 4.0.24. (Bug#9670)

- An error occurred if you specified a default value of `TRUE` or `FALSE` for a `BOOL` column. (Bug#9666)

- A server installed as a Windows service and started with `--shared-memory` could not be stopped. (Bug#9665)

- Fixed a `readline`-related crash in mysql when the user pressed Control-R. (Bug#9568)

- Fixed incorrect memory block allocation for the query cache in the embedded server. (Bug#9549)

- `ENUM` and `SET` columns in `InnoDB` tables were treated incorrectly as character strings. This bug did not manifest itself with `latin1` collations, but it caused malfunction with `utf8`. Old tables will continue to work. In new tables, `ENUM` and `SET` will be stored internally as unsigned integers. (Bug#9526)

- Fixed a segmentation fault in mysqlcheck that occurred when the last table checked in `--auto-repair` mode returned an error (such as the table being a `MERGE` table). (Bug#9492)

- Fixed some problems with myisampack on 64-bit systems that resulted in segmentation violations. (Bug#9487)

- Changed metadata for result of `SHOW KEYS`: Data type for `Sub_part` column now is `SMALLINT` rather than `TINYINT` because key part length can be longer than 255. (Bug#9439)

- An `InnoDB` test suite failure was caused by a locking conflict between two server instances at server shutdown or startup. This conflict on advisory locks appears to be the result of a bug in the operating system; these locks should be released when the files are closed, but somehow that does not always happen immediately in Linux. (Bug#9381)

- Fixed an optimizer bug in computing the union of two ranges for the `OR` operator. (Bug#9348)

- `MAX()` for an `INT UNSIGNED` (unsigned 4-byte integer) column could return negative values if the column contained values larger than 231. (Bug#9298)

- Fixed an index corruption problem for `MyISAM` tables that resulted from the 4.1 behavior of padding values with blanks for comparison: Dumping a table with mysqldump, reloading it, and then re-running the binary log against it crashed the index and necessitated a repair. (Bug#9188)

- mysqldump dumped core when invoked with `--tmp` and `--single-transaction` options and a non-existent table name. (Bug#9175)

- Multiple-table updates could produce spurious data-truncation warnings if they used a join across columns that are indexed using a column prefix. (Bug#9103)

- Fixed an optimizer problem where extraneous comparisons between `NULL` values in indexed columns were being done for operators such as `=` that are never true for `NULL`. (Bug#8877)

- Fixed compile problem with MinGW. Thanks to Nils Durner for patch! (Bug#8872)

- Fixed the client/server protocol for prepared statements so that reconnection works properly when the connection is killed while reconnect is enabled. (Bug#8866)

- The warning message from `GROUP_CONCAT()` did not always indicate the correct number of lines. (Bug#8681)

- Remove extra slashes in `--tmpdir` value (for example, convert `/var//tmp` to `/var/tmp`, because they caused various errors. (Bug#8497)

- MySQL no longer automatically blocks IP numbers for which `gethostbyname_r()` fails when the reason is that the DNS server is down. Thanks to Jeremy Cole for patch. (Bug#8467)

- An error in the implementation of the `MyISAM` compression algorithm caused `myisampack` to fail with very large sets of data (total size of all the records in a single column needed to be at least 3 GB in order to trigger this issue). (Bug#8321)

- `TIMEDIFF()` with a negative time first argument and positive time second argument produced incorrect results. (Bug#8068)

- A deadlock could occur on an update followed by a `SELECT` on an `InnoDB` table without any explicit locks being taken. `InnoDB` now takes an exclusive lock when `INSERT ON DUPLICATE KEY UPDATE` is checking duplicate keys. (Bug#7975)

- Fixed a configure problem in checking for capability of performing atomic operations. (Bug#7970)

- Fixed a deadlock resulting from use of `FLUSH TABLES WITH READ LOCK` while an `INSERT DELAYED` statement is in progress. (Bug#7823)

- `INSERT ... ON DUPLICATE KEY UPDATE` incorrectly updated a `TIMESTAMP` column to the current timestamp, even if the update list included ``col_name` = `col_name`` for that column to prevent the update. (Bug#7806)

- Additional fix for `mysql_server_init()` and `mysql_server_end()` C API functions so that stopping and restarting the embedded server would not cause a crash. (Bug#7344)

- Setting the initial `AUTO_INCREMENT` value for an `InnoDB` table using `CREATE TABLE ... AUTO_INCREMENT = `n`` did not work, and `ALTER TABLE ... AUTO_INCREMENT = `n`` did not reset the current value. (Bug#7061)

- `CAST(`string_argument` AS UNSIGNED)` didn't work for big integers above the signed range. Now this function and `CAST(`string_argument` AS SIGNED)` also produces warnings for wrong string arguments. (Bug#7036)

- The `latin2_croatian_ci` collation was not sorted correctly. After upgrading to MySQL 4.1.12, all tables that have indexes using this collation are treated as crashed; for each such table, you must use `CHECK TABLE` and possibly repair the table.

  Support for the `cp1250_croatian_ci` collation was also added as part of the fix for this bug. (Bug#6505)

- For `MERGE` tables, avoid writing absolute pathnames in the `.MRG` file for the names of the constituent `MyISAM` tables so that if the data directory is moved, `MERGE` tables will not break. For mysqld, write just the `MyISAM` table name if it is in the same database as the `MERGE` table, and a path relative to the data directory otherwise. For the embedded servers, absolute pathnames may still be used. (Bug#5964)

- mysqld was not checking whether the PID file was successfully created. (Bug#5843)

- `InnoDB`: Prevent `ALTER TABLE` from changing the storage engine if there are foreign key constraints on the table. (Bug#5574, Bug#5670)

- With `DISTINCT CONCAT(`col`,...)` returned incorrect results when the arguments to `CONCAT()` were columns with an integer data type declared with a display width narrower than the values in the column. (For example, if an `INT(1)` column contain `1111`.) (Bug#4082)

- configure did not properly recognize whether NPTL was available on Linux. (Bug#2173)

- `InnoDB`: Add fault tolerance in the scan of `.ibd` files at a crash recovery; formerly a single failure of `readdir_get_next` caused the rest of the directory to be skipped.

- `InnoDB`: Fix a problem in crash recovery of `.ibd` files on Windows if the user used `lower_case_table_names=0` or `2`; the directory scan in crash recovery forgot to put all paths to lower case, so that the tablespace name would be consistent with the internal data dictionary of InnoDB.

- `InnoDB`: Fix a performance bug: At the shutdown, write the latest lsn only to the first pages of the `ibdata` files of the system tablespace, NOT to the `.ibd` files; writing to tens of thousands `.ibd` files can take minutes.

### B.1.14. Changes in MySQL 4.1.11 (01 April 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- MySQL Cluster: More informative error messages are provided when a query is issued against an `NDB` table that has been modified by another mysqld server. (Bug#6762)

- The use of `SESSION` or `GLOBAL` is now disallowed for user variables. (Bug#9286)

- mysqld_safe will create the directory where the UNIX socket file is to be located if the directory does not exist. This applies only to the last component of the directory pathname. (Bug#8513)

- `ONLY_FULL_GROUP_BY` no longer is included in the `ANSI` composite SQL mode. (Bug#8510)

- Added a new global system variable `slave_transaction_retries`: If the replication slave SQL thread fails to execute a transaction because of an `InnoDB` deadlock or exceeded `InnoDB`'s `innodb_lock_wait_timeout` or `NDBCluster`'s `TransactionDeadlockDetectionTimeout` or `TransactionInactiveTimeout`, it automatically retries `slave_transaction_retries` times before stopping with an error. The default is 0, and you must explicitly set the value greater than 0 to enable the “retry” behavior. (Bug#8325)

- For slave replication servers started with `--replicate-*` options, statements that should not be replicated according those options no longer are written to the slave's general query log. (Bug#8297)

- Added `SQL_NOTES` session variable to cause `Note`-level warnings not to be recorded. (Bug#6662)

- Modified the parser to allow `SELECT` statements following the `UNION` keyword to be subqueries in parentheses. (Bug#2435)

- `InnoDB`: Commit after every 10,000 copied rows when executing `CREATE INDEX`, `DROP INDEX` or `OPTIMIZE TABLE`, which are internally implemented as `ALTER TABLE`. This makes it much faster to recover from an aborted operation.

- User variable coercibility has been changed from “coercible” to “implicit.” That is, user variables have the same coercibility as column values.

- Added `--with-big-tables` compilation option to configure. (Previously it was necessary to pass `-DBIG_TABLES` to the compiler manually in order to enable large table support.) See Section 2.9.2, “Typical configure Options”, for details.

- The coercibility for the return value of functions such as `USER()` or `VERSION()` now is “system constant” rather than “implicit.” This makes these functions more coercible than column values so that comparisons of the two do not result in `Illegal mix of collations` errors. `COERCIBILITY()` was modified to accommodate this new coercibility value. See Section 11.10.3, “Information Functions”.

- Added configuration directives `!include` and `!includedir` for including option files and searching directories for option files. See Section 4.2.2.2, “Using Option Files”, for usage.

- `NULL` now is considered more coercible than string constants. This resolves some `Illegal mix of collations` conflicts.

Bugs fixed:

- For `MyISAM` tables, `REPAIR TABLE` no longer discard rows that have incorrect checksum. (Bug#9824)

- Fixed option-parsing code for the embedded server to understand `K`, `M`, and `G` suffixes for the `net_buffer_length` and `max_allowed_packet` options. (Bug#9472)

- Some user variables were not being handled with “implicit” coercibility. (Bug#9425)

- Fixed a crash when using `TIMESTAMP` columns with no minute or second parts in `GROUP BY` with the `new` system variable set to 1. (Bug#9401)

- Allow extra HKSCS and cp950 characters (`big5` extension characters) to be accepted in `big5` columns. (Bug#9357)

- Fixed incorrect evaluation of `ALL/ANY` subqueries that contain a `HAVING` clause. (Bug#9350)

- `BLOB(`M`)` and `TEXT(`M`)` columns, with `M` less than 256, were being created as `BLOB` and `TEXT` columns rather than `TINYBLOB` or `TINYTEXT` columns. (Bug#9303)

- `InnoDB`: If MySQL wrote to its binlog, but for some reason `trx->update_undo` and `trx->insert_undo` were NULL in InnoDB, then `trx->commit_lsn` was garbage, and InnoDB could assert in the log flush of `trx_commit_complete_for_mysql()`. (Bug#9277)

- Fixed `utf8_spanish2_ci` and `ucs2_spanish2_ci` collations to not consider “ `r` ” equal to “ `rr` ”. If you upgrade to this version from an earlier version, you should rebuild the indexes of affected tables. (Bug#9269)

- Depending on index statistics, `GROUP BY `col1`, `col2`, ...` could return incorrect results if the first table processed for a join had several indexes that cover the grouped columns. (Bug#9213)

- Fixed a problem with `OPTIMIZE TABLE` for `InnoDB` tables being written twice to the binary log. (Bug#9149)

- The `CHARSET()`, `COLLATION()`, and `COERCIBILITY()` functions sometimes returned `NULL`. `CHARSET()` and `COLLATION()` returned `NULL` when given any of these arguments that evaluated to `NULL`: A system function such as `DATABASE()`; a column value; and a user variable. Now `CHARSET()` and `COLLATION()` return the system character set and collation; the column character set and collation; and `binary`. `COERCIBILITY(NULL)` now returns “ignorable” coercibility rather than `NULL`. (Bug#9129)

- mysqldump misinterpreted “ `_` ” and “ `%` ” characters in the names of tables to be dumped as wildcard characters. (Bug#9123)

- Bundled `zlib` in the source distribution was upgraded to 1.2.2. (Bug#9118)

- Setting the `max_error_count` system variable to 0 resulted in a setting of 1. (Bug#9072)

- The use of `XOR` together with `NOT ISNULL()` erroneously resulted in some outer joins being converted to inner joins by the optimizer. (Bug#9017)

- `MIN(`col_name`)` and `MAX(`col_name`)` could fail to produce the correct result if `col_name` was contained in multiple indexes and the optimizer did not choose the first index that contained the column. (Bug#8893)

- Fixed server crash when left expression of `IN/ALL/ANY` comparison was a subquery. (Bug#8888)

- Fixed a problem with the `cp1250_czech_cs` collation that caused empty literal strings not to compare equal to empty character columns. (Bug#8840)

- Binary data stored in `BLOB` or `BINARY` columns would be erroneously dumped if mysqldump was invoked with `--hex-blob` and `--skip-extended-insert` arguments. This happened if data contained characters larger then 0x7F . (Bug#8830)

- Fixed a server crash caused by use of `NOW()` is a subquery. (Bug#8824)

- In prepared statements, subqueries containing parameters were erroneously treated as `const` tables during preparation, resulting in a server crash. (Bug#8807)

- Fixed a bug in the filesort routine such that killing a filesort could cause an assertion failure. (Bug#8799)

- Expressions involving nested `CONCAT()` calls and character set conversion of string constants could return an incorrect result. (Bug#8785)

- Do not try to space-pad `BLOB` columns containing `ucs2` characters. (Bug#8771)

  This regression was introduced by Bug#7350

- If `max_join_size` was set, a query containing a subquery that exceeded the examined-rows limit could hang. (Bug#8726)

- Table creation for a `MyISAM` table failed if `DATA DIRECTORY` or `INDEX DIRECTORY` options were given that specified the pathname to the database directory where the table files would be created by default. (Bug#8707)

- Fixed a rare race condition which could lead to `FLUSH TABLES WITH READ LOCK` hanging. (Bug#8682)

- `InnoDB`: If one used `LOCK TABLES`, created an InnoDB temp table, and did a multiple-table update where a `MyISAM` table was the update table and the temp table was a read table, then InnoDB asserted in `row0sel.c` because `n_mysql_tables_in_use` was 0. Also, we remove the assertion altogether and just print an error to the `.err` log if this important consistency check fails. (Bug#8677)

- `AES_DECRYPT(`col_name`,`key`)` could fail to return `NULL` for invalid values in `col_name`, if `col_name` was declared as `NOT NULL`. (Bug#8669)

- Use of `GROUP_CONCAT(`x`)` in a subquery, where `x` was an alias to a column in the outer query, resulted in a server crash. (Bug#8656)

- Too many rows were returned from queries that combined `ROLLUP` and `LIMIT` if `SQL_CALC_FOUND_ROWS` was given. (Bug#8617)

- Incorrect results were returned from queries that combined `SELECT DISTINCT`, `GROUP BY` , and `ROLLUP`. (Bug#8616)

- Fixed server crash resulting from queries that combined `SELECT DISTINCT`, `SUM()`, and `ROLLUP`. (Bug#8615)

- A join on two tables failed when each contained a `BIGINT UNSIGNED` column that were compared when their values exceeded 263 – 1. The match failed and the join returned no rows. (Bug#8562)

- Fixed a problem with `LIKE` pattern-matching for strings with the `cp1251_bin` binary collation. (Bug#8560)

- Fixed a bug in `MATCH ... AGAINST` in natural language mode that could cause a server crash if the `FULLTEXT` index was not used in a join (`EXPLAIN` did not show `fulltext` join mode) and the search query matched no rows in the table . (Bug#8522)

- perror was printing a spurious extra line of output ("Error code ###: Unknown error ###" printed directly before the correct line with the error message). (Bug#8517)

- Fixed a problem with the `tee` command in mysql that resulted in mysql crashing. (Bug#8499)

- The `MEMORY` storage engine did not properly increment an `AUTO_INCREMENT` column if there was a second composite index that included the column. (Bug#8489)

- `REPAIR TABLE` did not invalidate query results in the query cache that were generated from the table. (Bug#8480)

- For a statement string that contained multiple slow queries, only the last one would be written to the slow query log. (Bug#8475)

- When the server was started with `--skip-name-resolve`, specifying hostname values that included netmasks in `GRANT` statements did not work. (Bug#8471)

- If multiple semicolon-separated statements were received in a single packet, they were written to the binary log as a single event rather than as separate per-statement events. For a server serving as a replication master, this caused replication to fail when the event was sent to slave servers. (Bug#8436)

- Fixed a bug in replication that caused the master to stamp generated statements (such as `SET` commands) with an `error_code` intended only for another statement. This could happen, for example, when a statements generates a duplicate key error on the master but must be replicated. (Bug#8412)

- Fixed a problem with the Cyrillic letters I and SHORT I being treated the same by the `utf8_general_ci` collation. (Bug#8385)

- With a database was dropped with `lower_case_table_names=2`, tables in the database also were dropped but not being flushed properly from the table cache. If the database was re-created, the tables also would appear to have been re-created. (Bug#8355)

- Fixed a problem with boolean full-text searches on `utf8` columns where a double quote in the search string caused a server crash. (Bug#8351)

- The `MAX_CONNECTIONS_PER_HOUR` resource limit was not being reset hourly and thus imposed an absolute limit on number of connections per account until the server is restarted or the limits flushed. (Bug#8350)

- The `--set-character-set` option for myisamchk was changed to `--set-collation`. The value needed for specifying how to sort indexes is a collation name, not a character set name. (Bug#8349)

- Corruption of `MyISAM` table indexes could occur with `TRUNCATE TABLE` if the table had already been opened. For example, this was possible if the table had been opened implicitly by selecting from a `MERGE` table that mapped to the `MyISAM` table. The server now issues an error message for `TRUNCATE TABLE` under these conditions. (Bug#8306)

- In string literals with an escape character (“ `\` ”) followed by a multi-byte character that has a second byte of “ `\` ”, the literal was not interpreted correctly. The next character now is escaped, not just the next byte. (Bug#8303)

- On Windows, create shared memory objects with the proper access rights to make them usable when the client and server are running under different accounts. (Bug#8226)

- For a query with both `GROUP BY` and `COUNT(DISTINCT)` clauses and a `FROM` clause with a subquery, `NULL` was returned for any `VARCHAR` column selected by the subquery. (Bug#8218)

- With `lower_case_table_names` set to 1, mysqldump on Windows could write the same table name in different lettercase for different SQL statements. (Bug#8216)

- Fixed handling of table-name matching in mysqlhotcopy to accommodate `DBD::mysql` 2.9003 and up (which implement identifier quoting). (Bug#8136)

- If the slave was running with `--replicate-*-table` options which excluded one temporary table and included another, and the two tables were used in a single `DROP TEMPORARY TABLE IF EXISTS` statement, as the ones the master automatically writes to its binary log upon client's disconnection when client has not explicitly dropped these, the slave could forget to delete the included replicated temporary table. Only the slave needs to be upgraded. (Bug#8055)

- Creating a table using a name containing a character that is illegal in `character_set_client` resulted in the character being stripped from the name and no error. The character now is considered an error. (Bug#8041)

- mysqldump now avoids writing `SET NAMES` to the dump output if the server is older than version 4.1 and would not understand that statement. (Bug#7997)

- Mixed-case database and table names in the grant tables were ignored for authentication if the `lower_case_table_names` system variable was set. `GRANT` will not create such privileges when `lower_case_table_names` is set, but it is possible to create them by direct manipulation of the grant tables, or that old grant records were present before setting the variable. (Bug#7989)

- Fixed a problem with accented letters improperly being treated as distinct with the `utf_general_ci` collation. (Bug#7878)

- Fix conversion of strings -> double to get higher accuracy for floating point values that are integers, like: `123.45E+02` . (Bug#7840)

- `ENUM` and `SET` columns in privilege tables incorrectly had a case-sensitive collation, resulting in failure of assignments of values that did not have the same lettercase as given in the column definitions. The collation was changed to be case insensitive. (Bug#7617)

- The output of the `STATUS` (`\s`) command in mysql had the values for the server and client character sets reversed. (Bug#7571)

- Fixed a problem in index cost calculation that caused a `USE INDEX` or `FORCE INDEX` hint not to be used properly for a `LEFT JOIN` across indexed `BLOB` columns. (Bug#7520)

- Ordering by an unsigned expression (more complex than a column reference) was treating the value as signed, producing incorrectly sorted results. `HAVING` was also treating unsigned columns as signed. (Bug#7425)

- Changed `mysql_server_end()` C API function to restore more variables to their initial state so that a subsequent call to `mysql_server_init()` would not cause a client program crash. (Bug#7344)

- Made the `relay_log_space_limit` system variable show up in the output of `SHOW VARIABLES`. (Bug#7100)

- An expression that tested a case-insensitive character column against string constants that differed in lettercase could fail because the constants were treated as having a binary collation. (For example, `WHERE city='London' AND city='london'` could fail.) (Bug#7098, Bug#8690)

- When setting integer system variables to a negative value with `SET VARIABLES`, the value was treated as a positive value modulo 232. (Bug#6958)

- Treat user variables as having `IMPLICIT` derivation (coercibility) to avoid “Illegal mix of collations” errors when replicating user variables. (Bug#6676)

- If a `MyISAM` table on Windows had `INDEX DIRECTORY` or `DATA DIRECTORY` table options, mysqldump dumped the directory pathnames with single-backslash pathname separators. This would cause syntax errors when importing the dump file. mysqldump now changes “ `\` ” to “ `/` ” in the pathnames on Windows. (Bug#6660)

- Fixed an optimizer bug that caused incorrectly ordered result from a query that used a `FULLTEXT` index to retrieve rows and there was another index that was usable for `ORDER BY`. For such a query, `EXPLAIN` showed `fulltext` join type, but regular (not `FULLTEXT`) index in the `Key` column. (Bug#6635)

- Neither `SHOW ERRORS` nor `SHOW WARNINGS` were displaying Error-level messages. (Bug#6572)

- Retrieving from a view defined as a `SELECT` that mixed `UNION ALL` and `UNION DISTINCT` resulted in a different result than retrieving from the original `SELECT`. (Bug#6565)

- A problem with static variables did not allow building the server on Fedora Core 3. (Bug#6554)

- Fixed a collation coercibility problem that caused a union between binary and non-binary columns to fail. (Bug#6519)

- The `CHAR()` function was not ignoring `NULL` arguments, contrary to the documentation. (Bug#6317)

- `FOUND_ROWS()` returned an incorrect value for preceding `SELECT` statements that used no table or view. (Bug#6089)

- `InnoDB`: Honor the `--tmpdir` startup option when creating temporary files. Previously, `InnoDB` temporary files were always created in the temporary directory of the operating system. On Netware, `InnoDB` will continue to ignore `--tmpdir`. (Bug#5822)

- Fixed a bug in bundled `readline` library that caused segmentation fault in mysql when user entered Shift+Enter. (Bug#5672)

- The data type for `MAX(`datetime_col`)` was returned as `VARCHAR` rather than `DATETIME` if the query included a `GROUP BY` clause. (Bug#5615)

- Worked around a bug in support for NSS support in `glibc` when static linking is used and LDAP is one of the NSS sources. The workaround is to detect when the bug causes a segmentation fault and issue a diagnostic message with information about the problem. (Bug#4872, Bug#3037)

- If the mysql prompt was configured to display the default database name, and that database was dropped, mysql did not update the prompt. (Bug#4802)

- Platform and architecture information in version information produced for `--version` option on Windows was always `Win95/Win98 (i32)`. More accurately determine platform as `Win32` or `Win64` for 32-bit or 64-bit Windows, and architecture as `ia32` for x86, `ia64` for Itanium, and `axp` for Alpha. (Bug#4445)

- Hostname matching didn't work if a netmask was specified for table-specific privileges. (Bug#3309)

- InnoDB: Fixed a bug: MySQL 4.1.8 to 4.1.10 could complain that an InnoDB table created with MySQL 3.23.49 or earlier was in the new compact InnoDB table format of 5.0.3 or later, and InnoDB would refuse to use that table. There is nothing wrong with the table, it is mysqld that is in error. Workaround: wait that 4.1.11 is released before doing an upgrade, or dump the table and re-create it with any MySQL version >= 3.23.50 before upgrading.

- InnoDB: Fixed a memory corruption bug if one created a table with a primary key that contained at least two column prefixes. An example: `CREATE TABLE t(a char(100), b tinyblob, PRIMARY KEY(a(5), b(10)))`.

- `InnoDB`: If InnoDB cannot allocate memory, keep retrying for 60 seconds before we intentionally crash `mysqld`; maybe the memory shortage is just temporary.

- Fixed a bug in my_print_defaults that made it ignore the `--defaults-extra-file` and `--defaults-file` options.

- Fixed a bug that under certain circumstances could allow a privilege escalation via database wildcards in `GRANT`. (CVE-2004-0957)

- InnoDB: Work around a problem in AIX 5.1 patched with ML7 security patch: InnoDB would refuse to open its `ibdata` files, complaining about an operating system error 0.

### B.1.15. Changes in MySQL 4.1.10 (12 February 2005)

### Note

The security improvements related to creation of table files and to user-defined functions were made after MySQL 4.1.10 was released and are present in MySQL 4.1.10a. We would like to thank Stefano Di Paola `<stefano.dipaola@wisec.it>` for making us aware of these.

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Thread stack size was increased from 192KB to 256KB on Linux/IA-64 (too small stack size was causing server crashes on some queries). (Bug#8391)

- Setting the connection collation to a value different from the server collation followed by a `CREATE TABLE` statement that included a quoted default value resulted in a server crash. (Bug#8235)

- The server now issues a warning when `lower_case_table_names=2` and the data directory is on a case-sensitive filesystem, just as when `lower_case_table_names=0` on a case-insensitive filesystem. (Bug#7887)

- The server now issues a warning to the error log when it encounters older tables that contain character columns that might be interpreted by newer servers to have a different column length. See Section 2.11.1, “Upgrading from MySQL 4.0 to 4.1”, for a discussion of this problem and what to do about it. (Bug#6913)

- Added `mysql_library_init()` and `mysql_library_end()` as synonyms for the `mysql_server_init()` and `mysql_server_end()` C API functions. `mysql_library_init()` and `mysql_library_end()` are `#define` symbols, but the names more clearly indicate that they should be called when beginning and ending use of a MySQL C API library no matter whether the application uses `libmysqlclient` or `libmysqld`. (Bug#6149)

- From the Windows distribution, predefined accounts without passwords for remote users ("root@%", "@%") were removed (other distributions never had them).

- InnoDB: When MySQL/InnoDB is compiled on Mac OS X 10.2 or earlier, detect the operating system version at run time and use the `fcntl()` file flush method on Mac OS X versions 10.3 and later. In Mac OS X, `fsync()` does not flush the write cache in the disk drive, but the special `fcntl()` does; however, the flush request is ignored by some external devices. Failure to flush the buffers may cause severe database corruption at power outages.

- Security improvement: User-defined functions should have at least one symbol defined in addition to the `xxx` symbol that corresponds to the main `xxx()` function. These auxiliary symbols correspond to the `xxx_init()`, `xxx_deinit()`, `xxx_reset()`, `xxx_clear()`, and `xxx_add()` functions. mysqld by default no longer loads UDFs unless they have at least one auxiliary symbol defined in addition to the main symbol. The `--allow-suspicious-udfs` option controls whether UDFs that have only an `xxx` symbol can be loaded. By default, the option is off. mysqld also checks UDF filenames when it reads them from the `mysql.func` table and rejects those that contain directory pathname separator characters. (It already checked names as given in `CREATE FUNCTION` statements.) See Section 19.2.4.1, “UDF Calling Sequences for Simple Functions”, Section 19.2.4.2, “UDF Calling Sequences for Aggregate Functions”, and Section 19.2.4.6, “User-Defined Function Security Precautions”. Thanks to Stefano Di Paola `<stefano.dipaola@wisec.it>` for finding and informing us about this issue. (CVE-2005-0709, CVE-2005-0710)

- Added back faster subquery execution from 4.1.8. This adds also back a bug from 4.1.8 in comparing `NULL` to the value of a subquery. See Section A.1.8.4, “Open Issues in MySQL”.

- InnoDB: Relaxed locking in `INSERT ... SELECT`, single table `UPDATE ... (SELECT)` and single table `DELETE ... (SELECT)` clauses when `innodb_locks_unsafe_for_binlog` is used and isolation level of the transaction is not serializable. `InnoDB` uses consistent read in these cases for a selected table.

- Security improvement: The server creates `.frm`, `.MYD`, `.MYI`, `.MRG`, `.ISD`, and `.ISM` table files only if a file with the same name does not already exist. Thanks to Stefano Di Paola `<stefano.dipaola@wisec.it>` for finding and informing us about this issue. (CVE-2005-0711)

- InnoDB: A shared record lock (`LOCK_REC_NOT_GAP`) is now taken for a matching record in the foreign key check because inserts can be allowed into gaps.

Bugs fixed:

- Fixed `LOAD INDEX` statement to actually load index in memory. (Bug#8452)

- Fixed a server crash caused by `DELETE FROM `tbl_name` ... WHERE ... ORDER BY `tbl_name`.`col_name`` when the `ORDER BY` column was qualified with the table name. (Bug#8392)

- Fixed a bug in cardinality estimations for `HASH` indexes of `TEMPORARY` tables created using `MEMORY` storage engine. As a result queries that were using this index (as shown by `EXPLAIN`) could have returned incorrect results. (Bug#8371)

- If multiple prepared statements were executed without retrieving their results, executing one of them again would cause the client program to crash. (Bug#8330)

- Fixed a crash in a boolean full-text search in certain joins. (Bug#8234)

- Add description of `debug` command to mysqladmin help output. (Bug#8207)

- Removed a dependence of boolean full-text search on `--default-character-set` option. (Bug#8159)

- Modify `SET` statements produced by mysqldump to write quoted strings using single quotes rather than double quotes. This avoids problems if the dump file is reloaded while the `ANSI_QUOTES` SQL mode is in effect. (Bug#8148)

- Fixed erroneous comparison where strings that began with `CHAR(31)` were considered equal to the empty string. (Bug#8134)

- Fixed server crash resulting from re-execution of prepared statements containing subqueries. (Bug#8125)

- Certain correlated subqueries with forward references (referring to an alias defined later in the outer query) could crash the server. (Bug#8025)

- Corrected a problem with references to `DUAL` where statements such as `SELECT 1 AS a FROM DUAL` would succeed but statements such as `SELECT 1 AS a FROM DUAL LIMIT 1` would fail. (Bug#8023)

- Fixed server crash in comparing a nested row expression (for example `row(1,(2,3))`) with a subquery. (Bug#8022)

- InnoDB: Fixed a bug introduced in 4.1.9 to the Windows version if you used `innodb_file_per_table`. mysqld would stop and complain about Windows error number 87 in a file operation. (See the Bugs database or the 4.1.9 change notes about a workaround for that bug in 4.1.9). (Bug#8021)

- The number of columns in a row comparison against a subquery was calculated incorrectly. (Bug#8020)

- mysqld had problems finding its language files if the `basedir` value was specified as a very long pathname. (Bug#8015)

- `mysql_stmt_close()` C API function was not clearing an error indicator when a previous prepare call failed, causing subsequent invocations of error-retrieving calls to indicate spurious error values. (Bug#7990)

- Fixed a problem in the server where executing a multi-statement query more than once with the query cache active could yield incorrect result sets. (Bug#7966)

- A slave running MySQL 3.23.51 or newer hung while trying to connect to a master running MySQL 3.23.50 or older. (The reason for this was a bug in the old masters — `SELECT @@`unknown_var`` caused the server to hang — which was fixed in MySQL 3.23.50.) (Bug#7965)

- Fixed erroneous output resulting from `SELECT DISTINCT` combined with a subquery and `GROUP BY`. (Bug#7946)

- `FOUND_ROWS()` returned an incorrect value after a `SELECT SQL_CALC_FOUND_ROWS DISTINCT` statement that selected constants and included `GROUP BY` and `LIMIT` clauses. (Bug#7945)

- Fixed problem with `SHOW INDEX` reporting `Sub_part` values in bytes rather than characters for columns with a multi-byte character set. (Bug#7943)

- Changed mysql client so that including `\p` as part of a prompt command uses the name of the shared memory connection when the connection is using shared memory. (Bug#7922)

- If one used `CONVERT_TZ()` function in `SELECT`, which in its turn was used in `CREATE TABLE` statements, then system time zone tables were added to list of tables joined in SELECT and thus erroneous result was produced. (Bug#7899)

- Fixed a bug where comparing the result of a subquery to a non-existent column caused a server crash on Windows. (Bug#7885)

- Fixed a bug where `ALTER TABLE` improperly would accept an index on a `TIMESTAMP` column that `CREATE TABLE` would reject. (Bug#7884)

- MySQL allowed concurrent updates (including inserts and deletes) to a table if binary logging was enabled. Now, all updates are executed in a serialized fashion, because they are executed serialized when the binlog is replayed. (Bug#7879)

- Ensured that mysqldump --single-transaction sets its transaction isolation level to `REPEATABLE READ` before proceeding (otherwise if the MySQL server was configured to run with a default isolation level lower than `REPEATABLE READ` it could give an inconsistent dump). (Bug#7850)

- InnoDB: `ALTER TABLE ... ADD CONSTRAINT PRIMARY KEY ...` complained about bad foreign key definition. (Bug#7831)

- mysqlbinlog forgot to add backquotes around the collation of user variables (causing later parsing problems as `BINARY` is a reserved word). (Bug#7793)

- Fixed a bug in `max_heap_table_size` handling, that resulted in `Table is full` error when the table was still smaller than the limit. . (Bug#7791)

- Fixed a bug in multiple-table `UPDATE` statements that could cause spurious `Table '#sql_....' is full` errors if the number of rows to update is big enough. (Bug#7788)

- Fixed conversion of floating-point values to character fields when the absolute value of the float was less than 1, and also fixed calculation of length for negative values. (Bug#7774)

- Fixed a bug where the use of `GROUP_CONCAT()` with `HAVING` caused a server crash. (Bug#7769)

- Fixed a bug in `CONV()` function returning unsigned `BIGINT` number (third argument is positive, and return value does not fit in 32 bits). (Bug#7751)

- Fixed a failure of the `IN()` operator to return correct result if all values in the list were constants and some of them were using substring functions, for example, `LEFT()`, `RIGHT()`, or `MID()`. (Bug#7716)

- Fixed a crash in `CONVERT_TZ()` function when its second or third argument was from a `const` table (see Section 7.2.1, “Optimizing Queries with `EXPLAIN`”). (Bug#7705)

- Fixed a bug which caused `TIMEDIFF()` function to return wrong results if one of its arguments had non-zero microsecond part . (Bug#7586)

- Fixed a bug which caused `TIMESTAMP` columns with display width specified to be not identical to `DATETIME` columns when server was run in `MAXDB` mode . (Bug#7418)

- perror.exe was always returning “Unknown error” on Windows. See Section 4.8.1, “perror — Explain Error Codes”. (Bug#7390)

- Fixed a problem where `SHOW INDEX` on a `MERGE` table could crash a debugging version of the server. (Bug#7377)

- Corrected the handling of trailing spaces in the `ucs2` character set. (Bug#7350)

- Fixed a problem where adding an `ORDER BY` clause for an indexed column would cause a `SELECT` to return an empty result. (Bug#7331)

- Fixed a problem where `ALTER TABLE` on a `TEMPORARY` table with a mixed-lettercase name could cause the table to disappear when `lower_case_table_names` was set to 2. (Bug#7261)

- For indexes, `SHOW CREATE TABLE` now displays the index type even if it is the default, for storage engines that support multiple index types. (Bug#7235)

- Fixed a failure of multiple-table updates to replicate properly on slave servers when `--replicate-*-table` options had been specified. (Bug#7011)

- Updates were being written to the binary log when there were `binlog-do-db` or `binlog-ignore-db` options even when there was no current database, contrary to Section 5.3.4, “The Binary Log”. (Bug#6749)

- Fixed failure of `CREATE TABLE ... LIKE` Windows when the source or destination table was located in a symlinked database directory. (Bug#6607)

- Column headers in query results retrieved from the query cache could be corrupted when a non-4.1 client was served a result originally generated for a 4.1 client. The query cache was not keeping track of which client/server protocol was being used. (Bug#6511)

- Correct a problem with mysql_config, which was failing to produce proper `zlib` option for linking under some circumstances. (Bug#6273)

- Non-numeric values inserted into a `YEAR` column were being stored as `2000` rather than as `0000`. (Bug#6067)

- Fixed a problem that caused `mysql_stmt_prepare()` to be very slow when used in client programs on Windows. (Bug#5787)

- A `HAVING` clause that referred to `RAND()` or a user-defined function in the `SELECT` part of a query through an alias could cause MySQL to crash or to return an incorrect value. (Bug#5185)

- Fixed a problem with key cache statistics being reported incorrectly by the server after receipt of a `SIGHUP` signal. (Bug#4285)

- Fixed a bug in `UNION` statements that resulted in the wrong number of the examined rows reported in the slow query log.

- Fixed a symlink vulnerability in the mysqlaccess script. Reported by Javier Fernandez-Sanguino Pena and Debian Security Audit Team. (CVE-2005-0004)

- InnoDB: Use native `tmpfile()` function on Netware. All InnoDB temporary files are created under `sys:\tmp`. Previously, InnoDB temporary files were never deleted on Netware.

- Fixed a bug in a combination of `-not` and `trunc*` operators of full-text search. Using more than one truncated negative search term, was causing empty result set.

- InnoDB: Fix a race condition that could cause the assertion `space->n_pending_flushes == 0` to fail in `fil0fil.c`, in `fil_space_free()`, in `DROP TABLE` or in `ALTER TABLE`.

### B.1.16. Changes in MySQL 4.1.9 (11 January 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- mysqld_safe no longer tests for the presence of the data directory when using a relatively located server binary. It just assumes the directory is there, and fails to start up if it is not. This allows the data directory location to be specified on the command line, and avoids running a server binary that was not intended. (Bug#7249)

  See also Bug#7518

- The `MySQL-shared-compat` Linux RPM now includes the 3.23 as well as the 4.0 `libysqlclient.so` shared libraries. (Bug#6342)

- The Mac OS X 10.3 installation disk images now include a MySQL Preference Pane for the Mac OS X Control Panel that enables the user to start and stop the MySQL server via the GUI and activate and deactivate the automatic MySQL server startup on bootup.

- The naming scheme of the Windows installation packages has changed slightly:

  - The platform suffix was changed from `-win` to `-win32`

  - The product descriptions `-noinstall` and `-essential` have been moved in front of the version number

  Examples: `mysql-essential-4.1.9-win32.msi`, `mysql-noinstall-4.1.9-win32.zip` See Section 2.3, “Installing MySQL on Windows”.

- `Seconds_Behind_Master` is `NULL` (which means “unknown”) if the slave SQL thread is not running, or if the slave I/O thread is not running or not connected to master. It is zero if the SQL thread has caught up with the I/O thread. It no longer grows indefinitely if the master is idle.

- InnoDB: Do not acquire an internal `InnoDB` table lock in `LOCK TABLES` if `AUTOCOMMIT=1`. This helps in porting old `MyISAM` applications to `InnoDB`. `InnoDB` table locks in that case caused deadlocks very easily.

- The binary log file and binary log index file now behave like `MyISAM` when there is a "disk full" or "quota exceeded" error. See Section A.1.4.3, “How MySQL Handles a Full Disk”.

- The product descriptions `-noinstall` and `-essential` have been moved in front of the version number

- InnoDB: Print a more descriptive error and refuse to start `InnoDB` if the size of `ibdata` files is smaller than what is stored in the tablespace header; `innodb_force_recovery` overrides this.

- The platform suffix was changed from `-win` to `-win32`

- The MySQL server aborts immediately instead of simply issuing a warning if it is started with the `--log-bin` option but cannot initialize the binary log at startup (that is, an error occurs when writing to the binary log file or binary log index file).

Bugs fixed:

- Fixed that, when encountering a “disk full” or “quota exceeded” write error, `MyISAM` sometimes didn't sleep and retry the write, thus resulting in a corrupted table. (Bug#7714)

- Fixed problem where running mysql_fix_privilege_tables could result in grant table columns with too-short lengths if the server character set had been set to a multi-byte character set first. (Bug#7539)

- Added a `--default-character-set` option to mysqladmin to avoid problems when the default character set is not `latin1`. (Bug#7524)

- InnoDB: Fixed the critical bug if you enabled `innodb_file_per_table` in `my.cnf`. If you shut down mysqld, records could disappear from the secondary indexes of a table. Unfortunately, on Windows a new Bug#8021 was introduced. Windows users of `innodb_file_per_table` should put a line `innodb_flush_method=unbuffered` to their `my.cnf` or `my.ini` to work around 8021. (Bug#7496)

- Fixed a bug that caused microseconds to be gobbled from the string result of the `STR_TO_DATE` function, if there is some other specifier in the format string following `%f`. (Bug#7458)

- mysqladmin password now checks whether the server has `--old-passwords` turned on or predates 4.1 and uses the old-format password if so. (Bug#7451)

- Fixed a bug that caused a linking failure when linking both the MySQL client library and IMAP library. (Bug#7428)

- Fix a problem with truncation of `FLOAT` values. (Bug#7361)

- Made the MySQL server accept executing `SHOW CREATE DATABASE` even if the connection has an open transaction or locked tables. Refusing it made mysqldump --single-transaction sometimes fail to print a complete `CREATE DATABASE` statement for some dumped databases. (Bug#7358)

- Fixed that `--expire-log-days` was not honored if using only transactions. (Bug#7236)

- Include compression library flags in the output from mysql_config --lib_r. (Bug#7021)

- Corrected a problem with mysql_config not producing all relevant flags from `CFLAGS`. (Bug#6964)

- Fixed a bug that caused incorrect results for complex datetime expressions containing casts of datetime values to `TIME` or `DATE` values. (Bug#6914)

- Fixed that a slave could crash after replicating many `ANALYZE TABLE`, `OPTIMIZE TABLE`, or `REPAIR TABLE` statements from the master. (Bug#6461, Bug#7658)

- InnoDB: Fixed a bug: 32-bit mysqld binaries built on HP-UX-11 did not work with `InnoDB` files greater than 2 GB in size. (Bug#6189)

- Corrected a problem with mysqld_safe not properly capturing output from ps. (Bug#5878)

- Fixed a bug in `PROCEDURE ANALYSE()`, which did not quote some `ENUM` values properly. (Bug#2813)

- InnoDB: Use the `fcntl(F_FULLFSYNC)` flush method on Mac OS X versions 10.3 and up instead of `fsync()` that could cause corruption at power outages.

- InnoDB: Fix a little bug: we looked at the physical size of a stored SQL `NULL` value from a wrong field in the index; this has probably caused no bugs visible to the user. It caused only some extra space to be used in some rare cases.

- InnoDB: Fixed a bug: if we dropped a table where an `INSERT` was waiting for a lock to check a `FOREIGN KEY` constraint, then an assertion would fail in `lock_reset_all_on_table()`.

- InnoDB: Return a sensible error code from `DISCARD TABLESPACE` if it fails because the table is referenced by a `FOREIGN KEY`.

- Fixed table corruption bug when using `INSERT DELAYED` with prepared statements.

- InnoDB: Fixed a bug: `InnoDB` failed to drop a table in the background drop queue if the table was referenced by a `FOREIGN KEY` constraint.

### B.1.17. Changes in MySQL 4.1.8 (14 December 2004)

### Note

Due to a libtool-related bug in the source distribution, the creation of shared `libmysqlclient` libraries was not possible (the resulting files were missing the `.so` file name extension). The file `ltmain.sh` was updated to fix this problem and the resulting source distribution was released as `mysql-4.1.8a.tar.gz`. This modification did not affect the binary packages. (Bug#7401)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- MySQL Cluster: Added support for a `[mysql_cluster]` section to the `my.cnf` file for configuration settings specific to MySQL Cluster. The `ndb-connectstring` variable was moved here.

- A connection doing a rollback now displays "Rolling back" in the `State` column of `SHOW PROCESSLIST`.

- Added `--lock-all-tables` to mysqldump to lock all tables by acquiring a global read lock.

- In the normal log MySQL now prints the log position for `Binlog Dump` requests.

- `mysqlbinlog` now prints an informative commented line (thread id, timestamp, server id, and so forth) before each `LOAD DATA INFILE`, like it does for other queries; unless `--short-form` is used.

- Added `--disable-log-bin` option to mysqlbinlog. Using this option you can disable binary logging for the statements produced by mysqlbinlog. That is, `mysqlbinlog --disable-log-bin <file_name> | mysql` won't write any statements to the MySQL server binary log.

- `mysqldump --single-transaction --master-data` now is able to take an online (non-blocking) dump of InnoDB and report the corresponding binary log coordinates. This makes a backup suitable for point-in-time recovery, roll-forward or replication slave creation. See Section 4.5.4, “mysqldump — A Database Backup Program”.

- Automatic character set conversion formerly was done for operations that mix a column and a string such as assigning a string to a column, when this was possible without loss of information. Automatic conversion for operations that mix columns and strings has been expanded to cover many functions (such as `CONCAT()`) and assignment operators. This reduces the frequency of `Illegal mix of collations` errors.

- For `ALTER DATABASE`, the database name now can be omitted to apply the change to the default database.

- Added `WITH CONSISTENT SNAPSHOT` clause to `START TRANSACTION` to begin a transaction with a consistent read.

- The statements `CREATE TABLE`, `TRUNCATE TABLE`, `DROP DATABASE`, and `CREATE DATABASE` cause an implicit commit.

- The `--master-data` option for mysqldump now takes an optional argument of 1 or 2 to produce a non-commented or commented `CHANGE MASTER TO` statement. The default is 1 for backward compatibility.

- Added `--hex-blob` option to mysqldump for dumping binary string columns using hexadecimal notation.

- Added `--order-by-primary` to mysqldump, to sort each table's data in a dump file. This may be useful when dumping a `MyISAM` table which will be loaded into an InnoDB table. Dumping a `MyISAM` table with this option is considerably slower than without.

- InnoDB: Commit after every 10,000 copied rows when executing `ALTER TABLE`. This makes it much faster to recover from an aborted `ALTER TABLE` or `OPTIMIZE TABLE`.

- `FULLTEXT` index block size is changed to be 1024 instead of 2048.

- InnoDB: Do not periodically write `SHOW INNODB STATUS` information to a temporary file unless the configuration option `innodb_status_file=1` is set.

- Added `mysql_hex_string()` C API function that hex-encodes a string.

Bugs fixed:

- Fixed a bug in authentication code that allowed a malicious user to crash the server with specially crafted packets (using a modified client library). (Bug#7187)

- Fixed a crashing bug in a string function `LEFT`, when this function is part of the expression which is used as `GROUP BY` field. (Bug#7101)

- InnoDB: Refuse to open new-style tables created with MySQL 5.0.3 or later. (Bug#7089)

- Fixed incorrect referencing to column by name from subquery to outer query in case of using temporary table by outer query and placing subquery in the `WHERE` clause. (Bug#7079)

- Fixed an insufficient privilege check in `SHOW CREATE TABLE` command. (Bug#7043)

- `mysql_stmt_data_seek(stmt,0)` now rewinds a counter and enables buffered rows to be re-fetched on the client side. (Bug#6996)

- Fixed execution of complex queries with subqueries. (Bug#6841, Bug#6406)

- InnoDB: Do not intentionally crash `mysqld` if the buffer pool is exhausted by the lock table; return error 1206 instead. Do not intentionally crash `mysqld` if we cannot allocate the memory for the InnoDB buffer pool. (Bug#6817, Bug#6827)

- Fixed `NULL` value handling in case of empty results in subqueries. (Bug#6806)

- Fixed spurious "duplicate key" error from `REPLACE` or `INSERT ... ON DUPLICATE KEY UPDATE` statements performing multiple-row insert in the table that had unique and full-text indexes. (Bug#6784)

- MySQL required explicit privileges on system time zone description tables for implicit access to them (that is, if one set the `time_zone` variable or used the `CONVERT_TZ()` function) in cases where some table-level or column-level privileges already existed. (Bug#6765)

- Fixed a bug that could cause "Record has changed since last read in table" error message in some queries on `HEAP` tables that contain only one row. (Bug#6748)

- InnoDB: Fixed a bug: `innodb_locks_unsafe_for_binlog` still uses next-key locking . InnoDB used next-key locking when record matched completely to search tuple. This unnecessary next-key locking is now removed when `innodb_locks_unsafe_for_binlog` option is used. (Bug#6747)

- A sequence of `BEGIN` (or `SET AUTOCOMMIT=0`), `FLUSH TABLES WITH READ LOCK`, transactional update, `COMMIT`, `FLUSH TABLES WITH READ LOCK` could hang the connection forever and possibly the MySQL server itself. This happened for example when running the `innobackup` script several times. (Bug#6732)

- Prevent adding `CREATE TABLE .. SELECT` query to the binary log when the insertion of new records partially failed. (Bug#6682)

- mysqlbinlog did not print `SET PSEUDO_THREAD_ID` statements in front of `LOAD DATA INFILE` statements inserting into temporary tables, thus causing potential problems when rolling forward these statements after restoring a backup. (Bug#6671)

- Backported a fix for the full-text interface from MySQL 5.0. (Bug#6523)

- If a connection was interrupted by a network error and did a rollback, the network error code got stored into the `BEGIN` and `ROLLBACK` binary log events; that caused superfluous slave stops. (Bug#6522)

- Fixed initialization of some internal structures for first execution. (Bug#6517)

- Fixed a bug in execution of subqueries in `SET` and `DO` statements which caused wrong results to be returned from subsequent queries. (Bug#6462)

- Changed semantics of `CREATE/ALTER/DROP DATABASE` statements so that replication of `CREATE DATABASE` is possible when using `--binlog-do-db` and `--binlog-ignore-db`. (Bug#6391)

- A multiple-table `DELETE` could cause MySQL to crash when using `InnoDB` tables. (Bug#6378, Bug#5837)

- `LOAD DATA INFILE` now works with option replicate-rewrite-db. (Bug#6353)

- InnoDB: Made the foreign key parser better aware of quotes. (Bug#6340)

- InnoDB: If one used `INSERT IGNORE` to insert several rows at a time, and the first inserts were ignored because of a duplicate key collision, then InnoDB in a replication slave assigned `AUTO_INCREMENT` values 1 bigger than in the master. This broke the MySQL replication. (Bug#6287)

- `INSERT ... SELECT` no longer reports spurious "column truncated" warnings (Bug#6284)

- Fixed a rare memory corruption (that resulted in a crash) in `MATCH ... AGAINST` on columns that use multi-byte character sets. (Bug#6269)

- Fixed a bug that allowed server to accept datetime values with wrong year part. The server now also performs same checks for datetime values passed through `MYSQL_TIME` structures as for datetime values passed as strings. (Bug#6266)

- Fixed a bug with `INSERT` for a table with `FULLTEXT` indexes. Under rare circumstances, this could result in a corrupted table if words of different lengths may be considered equal. This is possible in some collations, for example, in `utf8_general_ci` or `latin1_german2_ci`. (Bug#6265)

- Fixed `NULL` processing in `ALL`/`SOME` subqueries. (Bug#6247)

- Fixed a bug which caused a crash when only the slave I/O thread was stopped and started. (Bug#6148)

- If `STMT_ATTR_UPDATE_MAX_LENGTH` is set for a prepared statement, `mysql_stmt_store_result()` updates `field->max_length` for numeric columns as well. (Bug#6096)

- If a connection had an open transaction but had done no updates to transactional tables (for example if had just done a `SELECT FOR UPDATE` then executed a non-transactional update, that update automatically committed the transaction (thus releasing InnoDB's row-level locks etc). (Bug#5714)

- `OPTIMIZE TABLE`, `REPAIR TABLE`, and `ANALYZE TABLE` are now replicated without any error code in the binary log. (Bug#5551)

- InnoDB: Fix two hangs: `FOREIGN KEY` constraints treated table and database names as case-insensitive. `RENAME TABLE t TO T` would hang in an endless loop if `t` had a foreign key constraint defined on it. Fix also a hang over the dictionary mutex that would occur if one tried in `ALTER TABLE` or `RENAME TABLE` to create a foreign key constraint name that collided with another existing name. (Bug#3478)

- Fixed crash when a call to `mysql_stmt_store_result()` occurred without a preceding call to `mysql_stmt_bind_result()`.

- `CREATE TABLE `created_table`` didn't signal when table was created. This could cause a `DROP TABLE `created_table`` in another thread to wait "forever".

- Prepared statements now handle `ZEROFILL` when converting `integer` to `string`.

- `GROUP_CONCAT(...ORDER BY)` when used with prepared statements gave wrong sorting order.

- The server was interpreting `CHAR BINARY` and `VARCHAR BINARY` columns from 4.0 tables as having the `BINARY` and `VARBINARY` data types. Now they are interpreted as `CHAR` and `VARCHAR` columns that have the binary collation of the column's character set. (This is the same way that `CHAR BINARY` and `VARCHAR BINARY` are handled for new tables created in 4.1.)

- InnoDB: Do not call `rewind()` when displaying `SHOW INNODB STATUS` information on `stderr`.

- Fixed crash in prepared statements when using `SELECT * FROM t1 NATURAL JOIN t2...`.

- Fixed crash in prepared statements when using subqueries.

- Fixed crash in prepared statements when using `SELECT ... PROCEDURE`.

- mysqld_safe was in many cases ignoring any `--no-defaults`, `--defaults-file`, or `--defaults-extra-file` arguments. Those arguments are now honored, and this may change what options are passed to mysqld in some installations.

- Improved performance of identifier comparisons (if many tables or columns are specified).

- InnoDB: Let InnoDB's `FOREIGN KEY` parser to remove the `latin1` character `0xA0` from the end of an unquoted identifier. The EMS MySQL Manager in `ALTER TABLE` adds that character after a table name, which caused error 121 when we tried to add a new constraint.

- InnoDB: Fixed a bug: InnoDB ignored in `innodb_data_file_path` the `max` specification in `:autoextend:max:2000M`. This bug was introduced in 4.1.1.

- Server warnings now are reset when you execute a prepared statement.

### B.1.18. Changes in MySQL 4.1.7 (23 October 2004: Production)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- `MOD()` no longer rounds arguments with a fractional part to integers. Now it returns exact remainder after division. (Bug#6138)

- Added a startup option and settable system variable `innodb_table_locks` for making `LOCK TABLE` acquire locks on `InnoDB` tables. The default value is 1, which means that `LOCK TABLES` also causes `InnoDB` to take a table lock internally. In applications using `AUTOCOMMIT=1` and `LOCK TABLES`, `InnoDB`'s internal table locks (added in MySQL 4.0.20 and 4.1.2) can cause deadlocks. You can set `innodb_table_locks=0` in `my.cnf` to remove that problem.

  In addition, `SHOW TABLE STATUS` now shows the creation time of `InnoDB` tables. That this timestamp might not always be correct because (for example) it was changed by `ALTER TABLE`. See Section 13.2.17, “Restrictions on `InnoDB` Tables”. (Bug#3299, Bug#5998)

- InnoDB: If `innodb_thread_concurrency` would be exceeded, let a thread sleep 10 ms before entering the FIFO queue; previously, the value was 50 ms.

Bugs fixed:

- Fixed bug which allowed one to circumvent missing UPDATE privilege if one had INSERT and SELECT privileges for table with primary key. (Bug#6173)

- Fixed a bug that could cause `MyISAM` index corruption when key values start with character codes below `BLANK`. This was caused by the new key sort order in 4.1. (Bug#6151)

- Now implicit access to system time zone description tables (which happens when you set the `time_zone` variable or use `CONVERT_TZ()` function) does not require any privileges. (Bug#6116)

- Fixed a bug with `FOUND_ROWS()` used together with `LIMIT` clause in prepared statements. (Bug#6088)

- Fixed crash when selecting from a `HEAP` table with `key_column IS NOT NULL`. This could also cause a crash if not all index parts where used. (Bug#6082)

- Fixed a bug which caused the server to crash when the deprecated `libmysqlclient` function `mysql_create_db()` was called. (Bug#6081)

- Fixed a bug in the prepared statements protocol when wrong metadata was sent for `SELECT` statements not returning a result set (such as `SELECT ... INTO OUTFILE`). (Bug#6059)

- Fixed a bug in `libmysqlclient` with wrong conversion of zero date values (`0000-00-00`) to strings. (Bug#6058)

- Fixed a bug in join of tables from different databases having columns with identical names (prepared statements). (Bug#6050)

- Fixed a bug in `libmysqlclient` with wrong conversion of negative time values to strings. . (Bug#6049)

- Fixed a bug with `NATURAL JOIN` in prepared statements. . (Bug#6046)

- Fixed a bug with handling of `DATE`, `TIME`, and `DATETIME` columns in the binary protocol. The problem is compiler-specific and could have been observed on HP-UX, AIX, Solaris9, when compiling with native compiler. (Bug#6025)

- Fixed a bug with handling of `TINYINT` columns in the binary protocol. The problem is specific to platforms where the C compiler has the `char` data type unsigned by default. (Bug#6024)

- Fixed a bug that caused the server to crash on attempt to prepare a statement with `RAND(?)`. (Bug#5985)

- InnoDB: Release the dictionary latch during a long cascaded `FOREIGN KEY` operation, so that we do not starve other users doing `CREATE TABLE` or other DDL operation. This caused a notorious 'Long semaphore wait' message to be printed to the `.err` log. (Bug#5961)

- Fixed problem introduced in MySQL 4.0.21 where a connection starting a transaction, doing updates, then `FLUSH TABLES WITH READ LOCK`, followed by `COMMIT`, would cause replication slaves to stop (error 1223). This issue occurred when using the `InnoDB` innobackup script. (Bug#5949)

- InnoDB: Fixed a bug in `LOAD DATA INFILE…REPLACE` printing duplicate key error when executing the same load query several times. (Bug#5835)

- `REVOKE ALL PRIVILEGES, GRANT OPTION FROM `user`` did not remove all privileges correctly. (Bug#5831)

### B.1.19. Changes in MySQL 4.1.6 (10 October 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- InnoDB: The `innodb_autoextend_increment` startup option that was introduced in release 4.1.5 was made a settable global variable. (Bug#5736)

- If a write to a `MyISAM` table fails because of a full disk or an exceeded disk quota, it now prints a message to the error log every 10 minutes, and waits until disk space becomes available. (Bug#3248)

- `TIMESTAMP` columns now can store `NULL` values. To create such a column, you must explicitly specify the `NULL` attribute in the column specification. (Unlike all other data types, `TIMESTAMP` columns are `NOT NULL` by default.)

- Now if `ALTER TABLE` converts some column to `TIMESTAMP NOT NULL` column it converts `NULL` values to current timestamp value (One can still get old behavior by setting system `TIMESTAMP` variable to zero).

- Added option `--sigint-ignore` to the `mysql` command line client to make it ignore `SIGINT` signals (typically the result of the user pressing Control-C).

- InnoDB: Added the startup option and settable global variable `innodb_max_purge_lag` for delaying `INSERT`, `UPDATE` and `DELETE` operations when the purge operations are lagging. The default value of this parameter is zero, meaning that there are no delays. See Section 13.2.13, “Implementation of Multi-Versioning”.

- InnoDB: If `DROP TABLE` is invoked on an InnoDB table for which the `.ibd` file is missing, print to error log that the table was removed from the `InnoDB` data dictionary, and allow MySQL to delete the `.frm` file. Maybe `DROP TABLE` should issue a warning in this case.

- On Windows, the MySQL configuration files included in the package now use `.ini` instead of `.cnf` as the file name suffix.

- Now if `ALTER TABLE` converts one `AUTO_INCREMENT` column to another `AUTO_INCREMENT` column it preserves zero values (this includes the case that we don't change such column at all).

Bugs fixed:

- InnoDB: Change error code to `HA_ERR_ROW_IS_REFERENCED` if we cannot `DROP` a parent table referenced by a `FOREIGN KEY` constraint; this error number is less misleading than the previous number `HA_ERR_CANNOT_ADD_FOREIGN`, but misleading still. (Bug#6202)

- Fixed a bug that caused the server to sometimes choose non-optimal execution plan for a prepared statement executed with changed placeholder values. (Bug#6042)

- Fixed a bug that caused the server to crash on attempt to execute a prepared statement with a subquery inside a boolean expression. (Bug#5987)

- InnoDB: Fixed some (not all) UTF-8 bugs in column prefix indexes. (Bug#5975)

- InnoDB: If one updated a column so that its size changed, or updated it to an externally stored (`TEXT` or `BLOB`) value, then ANOTHER externally stored column would show up as 512 bytes of good data + 20 bytes of garbage in a consistent read that fetched the old version of the row. (Bug#5960)

- Behavior of `ALTER TABLE` converting column containing `NULL` values to `AUTO_INCREMENT` column is no longer affected by `NO_AUTO_VALUE_ON_ZERO` mode. . (Bug#5915)

- InnoDB: Make the check for excessive semaphore waits tolerate glitches in the system clock (do not crash the server if the system time is adjusted while InnoDB is under load.). (Bug#5898)

- InnoDB: Fixed a bug in the InnoDB `FOREIGN KEY` parser that prevented `ALTER TABLE` of tables containing “ `#` ” in their names. (Bug#5856)

- InnoDB: Fixed a bug that prevented `ALTER TABLE `t` DISCARD TABLESPACE` from working. (Bug#5851)

- Fixed that if the slave SQL thread found a syntax error in a query (which should be rare, as the master parsed it successfully), it stops. (Bug#5711)

- Fixed slave SQL thread so that the `SET COLLATION_SERVER...` statements it replicates don't advance its position (so that if it gets interrupted before the actual update query, it later redoes the `SET`). (Bug#5705)

- Fixed a bug that caused the server to crash when character set conversion was implicitly used in prepared mode; for example, as in `'abc' LIKE CONVERT('abc' as utf8)`. (Bug#5688)

- Fixed a bug when inserting `NULL` into an `AUTO_INCREMENT` column failed, when using prepared statements. (Bug#5510)

- The `mysql_change_user()` C API function now frees all prepared statements associated with the connection. (Bug#5315)

- InnoDB: `SHOW CREATE TABLE` now obeys the `SET SQL_MODE=ANSI` and `SET SQL_QUOTE_SHOW_CREATE=0` settings. (Bug#5292)

- InnoDB: Fixed a bug that caused `CREATE TEMPORARY TABLE ... ENGINE=InnoDB` to terminate mysqld when running in `innodb_file_per_table` mode. Per-table tablespaces for temporary tables from now on are created in the temporary directory of mysqld. (Bug#5137)

### B.1.20. Changes in MySQL 4.1.5 (16 September 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- `InnoDB`: The new Windows installation wizard of MySQL makes InnoDB as the MySQL default table type on Windows, unless explicitly specified otherwise. Note that it places the `my.ini` file in the installation directory of the MySQL server. See Section 2.3.4.14, “The Location of the my.ini File”.

- `InnoDB`: Added configuration option `innodb_autoextend_increment` for setting the size in megabytes by which `InnoDB` tablespaces are extended when they become full. The default value is 8, corresponding to the fixed increment of 8MB in previous versions of MySQL.

Bugs fixed:

- Fixed a bug which caused the server to crash on attempt to execute a prepared statement with `BETWEEN ? AND ?` and a datetime column. (Bug#5748)

- Fixed detection of using same table for updating and selecting in multi-update queries. (Bug#5455)

- InnoDB: Fixed a bug that InnoDB only allowed a maximum of 1000 connections inside InnoDB at the same time. A higher number could cause an assertion failure in sync0arr.c, line 384. Now we allow 1000, 10000, or 50000, depending on the buffer pool size. (Bug#5414)

- Fixed a bug in the server when after reaching a certain limit of prepared statements per connection (97), statement ids began to overlap, so occasionally wrong statements were chosen for execution. (Bug#5399)

- The values of the `max_sort_length`, `sql_mode`, and `group_concat_max_len` system variables now are stored in the query cache with other query information to avoid returning an incorrect result from the query cache. (Bug#5394, Bug#5515)

- Fixed a bug in `OPTIMIZE TABLE` that could cause table corruption on `FULLTEXT` indexes. (Bug#5327)

- Fixed name resolving of external fields of subqueries if subquery placed in select list of query with grouping. (Bug#5326)

- Fixed syntax analyzer with `sql_mode=IGNORE_SPACE`. It happened to take phrases like `default .07` as `identifier.identifier`. (Bug#5318)

- Fixed a buffer overflow in prepared statements API (libmysqlclient) when a statement containing thousands of placeholders was executed. (Bug#5194)

- Fixed illegal internal field length of user variables of integer type. This showed up when creating a table as `SELECT @`var_name`` . (Bug#4788)

- Fixed a bug in prepared statements when `LIKE` used with arguments in different character sets crashed server on first execute. (Bug#4368)

- Fixed a bug in prepared statements when providing '0000-00-00' date to a parameter lead to server crash. (Bug#4231, Bug#4562)

### B.1.21. Changes in MySQL 4.1.4 (26 August 2004: Gamma)

### Note

To fix a compile problem on systems that do not have `automake` 1.7 installed, an updated 4.1.4a source tarball has been published. In addition to resolving this `automake` dependency (Bug#5319), it also fixes some reported `libedit` compile errors when using a non-`gcc` compiler (Bug#5353).

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Made internal representation of `TIMESTAMP` values in `InnoDB` in 4.1 to be the same as in 4.0. This difference resulted in incorrect datetime values in `TIMESTAMP` columns in `InnoDB` tables after an upgrade from 4.0 to 4.1. Warning: extra steps during upgrade required! Unfortunately this means that if you are upgrading from 4.1.x, where x <= 3, to 4.1.4 you should use mysqldump for saving and then restoring your `InnoDB` tables with `TIMESTAMP` columns. (Bug#4492)

- Made the MySQL server ignore `SIGHUP` and `SIGQUIT` on Mac OS X 10.3. This is needed because under this OS, the MySQL server receives lots of these signals. (Bug#2030)

- Support of usage of column aliases qualified by table name or alias in `ORDER BY` and `GROUP BY` was dropped. For example the following query `SELECT a AS b FROM t1 ORDER BY t1.b` is not allowed. One should use `SELECT a AS b FROM t1 ORDER BY t1.a` or `SELECT a AS b FROM t1 ORDER BY b` instead. This was non-standard (since aliases are defined on query level not on table level) and caused problems with some queries.

- Corrected the name of the Mac OS X StartupItem script (it must match the name of the subdirectory, which was renamed to `MySQLCOM` in MySQL 4.1.2). Thanks to Bryan McCormack for reporting this.

- Added Latin language collations for the `ucs2` and `utf8` Unicode character sets. These are called `ucs2_roman_ci` and `utf8_roman_ci`.

- Added `--start-datetime`, `--stop-datetime`, `--start-position`, and `--stop-position` options to `mysqlbinlog`. These make point-in-time recovery easier.

- Added the `CSV` storage engine.

- Killing a `CHECK TABLE` statement does not result in the table being marked as “corrupted” any more; the table remains as if `CHECK TABLE` had not even started. See Section 12.5.5.3, “`KILL` Syntax”.

- The mysqld-opt Windows server was renamed to mysqld. This completes the Windows server renaming begun in MySQL 4.1.2. See Section 2.3.8, “Selecting a MySQL Server Type”.

Bugs fixed:

- Fixed a bug that caused libmysql to crash when attempting to fetch a value of `MEDIUMINT` column. (Bug#5126)

- Fixed that `disable-local-infile` option had no effect if client read it from a configuration file using `mysql_options(...,MYSQL_READ_DEFAULT,...)`. (Bug#5073)

- Fixed that `SET GLOBAL SYNC_BINLOG` did not work on some platforms (Mac OS X). (Bug#5064)

- Fixed that mysql-test-run failed on the `rpl_trunc_binlog` test if running test from the installed (the target of 'make install') directory. (Bug#5050)

- Fixed that `mysql_options(...,MYSQL_OPT_LOCAL_INFILE,...)` failed to disable `LOAD DATA LOCAL INFILE`. (Bug#5038)

- Fixed a bug that caused the MySQL server to crash when attempting to execute a prepared statement with `SELECT ... INTO @var` for a second time. (Bug#5034)

- The counter for an `AUTO_INCREMENT` column was not reset by `TRUNCATE TABLE` if the table was a temporary one. (Bug#5033)

- Fixed a bug that omitted the `.err` extension of the error log file (`--log-error`) when the hostname contained a domain name. The domain name is now replaced by the extension. (Bug#4997)

- Fixed that `CREATE TABLE ... TYPE=HEAP ... AS SELECT...` caused replication slave to stop. (Bug#4971)

- `FLUSH TABLES WITH READ LOCK` now blocks `COMMIT` statements if the server is running with binary logging enabled; this ensures that the binary log position is trustable when doing a full backup of tables and the binary log. (Bug#4953)

- Fixed a bug that caused server crash on attempt to execute for a second time a prepared statement with `NOT` in `WHERE` or `ON` clauses. (Bug#4912)

- Fixed a crash in myisamchk. (Bug#4901)

- Fixed a crash when one connection got `KILL`ed while it was doing `START SLAVE`. (Bug#4827)

- Prohibited resolving of table fields in inner queries if fields do not take part in grouping for queries with grouping (inside aggregate function arguments, all table fields are still allowed). (Bug#4814)

- Fixed an unlikely deadlock which could happen when using `KILL`. (Bug#4810)

- Fixed a bug (hang) in `NATURAL JOIN` where joined table had no common column. (Bug#4807)

- `MATCH ... AGAINST` now works in a subquery. (Bug#4769)

- Support for `%T, %r, %V, %v` and `%X, %x` format specifiers was added to `STR_TO_DATE()` function. (Bug#4756)

- Fixed that mysql-test-run failed on the `grant_cache` test when run as Unix user 'root'. (Bug#4678)

- Fixed a crash after `SLAVE STOP` if the IO thread was in a special state. (Bug#4629)

- Fixed that when a multiple-table `DROP TABLE` failed to drop a table on the master server, the error code was not written to the binary log. (Bug#4553)

- If `CREATE TEMPORARY TABLE t SELECT` failed while loading the data, the temporary table was not dropped. (Bug#4551)

- Fixed a bug which caused server crash if one used the `CONVERT_TZ()` function with time zone described in database as parameter and this time zone was not used before. (Bug#4508)

- mysqlbinlog --read-from-remote-server sometimes could not accept 2 binary logs in a single invocation. (Bug#4507)

- mysqlbinlog --position --read-from-remote-server had incorrect output for `# at `log_pos``. (Bug#4506)

- Fixed a crash caused by `UNHEX(NULL)`. (Bug#4441)

- Fixed execution of optimized `IN` subqueries that use compound indexes. (Bug#4435)

- Fixed an assertion failure when reading the grant tables (Bug#4407)

- When the slave SQL thread was replicating a `LOAD DATA INFILE` statement, it didn't show the statement in the output of `SHOW PROCESSLIST`. (Bug#4326)

- An error was reported when a column from an `ORDER BY` clause was present in two tables participating in a `SELECT`, even if the second instance of column in select list was renamed. (For example, `SELECT t1.a AS c FROM t1, t2 ORDER BY a` produced an error if both `t1` and `t2` tables contain column `a`).

  Now MySQL does not prefer columns, mentioned in a select list but renamed, over columns from other tables participating in a `FROM` clause when it resolves the `ORDER BY` clause. (Bug#4302)

- mysql_fix_privilege_tables did not handle the `--password=`password_val`` option correctly. (Bug#4240, Bug#4543)

- Fixed an old bug in concurrent accesses to `MERGE` tables (even one `MERGE` table and `MyISAM` tables), that could have resulted in a crash or hang of the server. (Bug#2408)

### B.1.22. Changes in MySQL 4.1.3 (28 June 2004: Beta)

### Note

The initial release of MySQL 4.1.3 for Windows was accidentally compiled without support for the Spatial Extensions (OpenGIS). This was fixed by rebuilding from the same 4.1 code snapshot with the missing option and releasing those packages as version 4.1.3a.

To enable compiling the newly released PHP 5 against MySQL 4.1.3 on Windows, the Windows packages had to be rebuilt once more to add a few missing symbols to the MySQL client library. These packages were released as MySQL 4.1.3b.

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Incompatible Change: C API change: `mysql_shutdown()` now requires a second argument. This is a source-level incompatibility that affects how you compile client programs; it does not affect the ability of compiled clients to communicate with older servers. See Section 16.2.3.63, “`mysql_shutdown()`”.

- Incompatible Change: The `timezone` system variable has been removed and replaced by `system_time_zone`. See Section 5.1.3, “System Variables”.

- `LIKE` now supports the use of a prepared statement parameter or delimited constant expression as the argument to `ESCAPE` . (Bug#4200)

- `DROP DATABASE IF EXISTS`, `DROP TABLE IF EXISTS`, single-table `DELETE` and single-table `UPDATE` are now written to the binary log even if they changed nothing on the master (for example, even if the `DELETE` matched no row). The old behavior sometimes caused bad surprises in replication setups.

- Basic time zone conversion function `CONVERT_TZ()` was added. It assumes that its first argument is a datetime value in the time zone specified by its second argument and returns the equivalent datetime value in the time zone specified by its third argument.

- Changed the slave SQL thread to print fewer useless error messages (no more message duplication; no more messages when an error is skipped (because of `slave-skip-errors`).

- Language-specific collations were added for the `ucs2` and `utf8` Unicode character sets: Icelandic, Latvian, Romanian, Slovenian, Polish, Estonian, Swedish, Turkish, Czech, Danish, Lithuanian, Slovak, Spanish, Traditional Spanish.

- Support for per-connection time zones was added. Now you can set the current time zone for a connection by setting the `@@time_zone` system variable to a value such as `'+10:00'` or `'Europe/Moscow'` (where `'Europe/Moscow'` is the name of one of the time zones described in the system tables). Functions like `CURRENT_TIMESTAMP`, `UNIX_TIMESTAMP`, and so forth honor this time zone. Values of `TIMESTAMP` type are also interpreted as values in this time zone. So now our `TIMESTAMP` type behaves similar to Oracle's `TIMESTAMP WITH LOCAL TIME ZONE`. That is, values stored in such a column are normalized toward UTC and converted back to the current connection time zone when they are retrieved from such a column. To set up the tables that store time zone information, see Section 2.10, “Post-Installation Setup and Testing”.

- `sync_frm` is now a settable global variable (not only a startup option).

- Added `--innodb-safe-binlog` server option, which adds consistency guarantees between the content of `InnoDB` tables and the binary log. See Section 5.3.4, “The Binary Log”.

- Added the `ARCHIVE` storage engine.

- `OPTIMIZE TABLE` for `InnoDB` tables is now mapped to `ALTER TABLE` instead of `ANALYZE TABLE`.

- `CHECK TABLE` now can be killed. It then marks the table as corrupted. See Section 12.5.5.3, “`KILL` Syntax”.

- Added the `sync_binlog=N` global variable and startup option, which makes the MySQL server synchronize its binary log to disk (`fdatasync()`) after every `N`th write to the binary log.

- Added SQL syntax for prepared statements. See Section 12.7, “SQL Syntax for Prepared Statements”.

- Replication and mysqlbinlog now have better support for the case that the session character set and collation variables are changed within a given session. See Section 6.7, “Replication Features and Known Problems”.

Bugs fixed:

- Replication: Complex expressions using `AND`, `OR`, or both could result in a crash if the query containing the expression query was ignored, either by a replication server due to `--replicate-*-table` rules, or by any MySQL server due to a syntax error. (Bug#3969, Bug#4494)

- Fixed `CREATE DATABASE IF NOT EXISTS` for Win32 which caused an error if database existed. (Bug#4378)

- Fixed a bug of using parameters in some prepared statements via SQL syntax. (Bug#4280)

- Fixed bug in prepared `EXPLAIN` statement which led to server crash. (Bug#4271)

- Added missing `root` account to Windows version of mysqld. (Bug#4242)

- Fixed a bug with server crash on attempt to execute a non-prepared statement. (Bug#4236)

- Fixed some byte order bugs with prepared statements on machines with high-byte-first. (Bug#4173)

- Fixed unlikely bug in the range optimizer when using many `IN()` queries on different key parts. (Bug#4157)

- Fixed a bug with server crash on attempt to prepare a statement with character set introducer. (Bug#4105)

- Fixed problem with `NULL` and derived tables. (Bug#4097)

- Fixed a bug in `mysql_stmt_close()`, which hung up when attempting to close statement after failed `mysql_stmt_fetch()`. (Bug#4079)

- Fixed wrong `UNION` results if display length of fields for numeric types was set less than real length of values in them. (Bug#4067)

- Made `DROP DATABASE` honor the value of `lower_case_table_names`. (Bug#4066)

- During the installation process of the server RPM on Linux, if mysqld was run as the `root` system user and with `--log-bin` pointing to a directory outside of `/var/lib/mysql`, it created binary log files owned by `root` in this directory, which remained owned by `root` after the installation. Now mysqld is started as the `mysql` system user instead. (Bug#4038)

- Fixed a bug in client-side conversion of string column to `MYSQL_TIME` application buffer (prepared statements API). (Bug#4030)

- Fixed a bug in prepared statements protocol, when microseconds part of `MYSQL_TYPE_TIME`/`MYSQL_TYPE_DATETIME` columns was not sent to the client. (Bug#4026)

- Fixed potential memory overrun in `mysql_real_connect()` (which required a compromised DNS server and certain operating systems). (Bug#4017)

- Fixed a bug in `MERGE` tables created with `INSERT_METHOD=LAST`, that were not able to report a key number that caused “Duplicate entry” error for `UNIQUE` key in `INSERT`. As a result, error message was not precise enough (error 1022 instead of error 1062) and `INSERT ... ON DUPLICATE KEY UPDATE` did not work. (Bug#4008)

- Fixed a bug that using `--with-charset` with configure didn't affect the MySQL client library. (Bug#3990)

- Fixed too-early unlocking of tables if we have subquery in `HAVING` clause. (Bug#3984)

- Fixed a bug in `MATCH ... AGAINST(... IN BOOLEAN MODE)` that under rare circumstances could cause wrong results if in the data's collation one byte could match many (like in `utf8_general_ci` or `latin1_german2_ci`.) (Bug#3964)

- Fixed a bug with `COUNT(DISTINCT)` performance degradation in cases like `COUNT(DISTINCT a TEXT, b CHAR(1))` (no index used). (Bug#3904)

- mysqlbinlog didn't escape the string content of user variables, and did not deal well when these variables were in non-ASCII character sets; this is now fixed by always printing the string content of user variables in hexadecimal. The character set and collation of the string is now also printed. (Bug#3875)

- The slave SQL thread refused to replicate `INSERT ... SELECT` if it examined more than 4 billion rows. (Bug#3871)

- Fixed a bug in `DELETE` from a table with `FULLTEXT` indexes which under rare circumstances could result in a corrupted table, if words of different lengths may be considered equal (which is possible in some collations, for example, in `utf8_general_ci` or `latin1_german2_ci`.) (Bug#3808)

- Fixed bug with wrong result of `CONCAT(?, `col_name`)` in prepared statements. (Bug#3796)

- Fixed bug of re-execution optimized `COUNT(*)`, `MAX()` and `MIN()` functions in prepared statements. (Bug#2687)

- Fixed bug which caused different number of warnings to be generated when bad datetime as string or as number was inserted into `DATETIME` or `TIMESTAMP` column. (Bug#2336)

- Fixed a bug in mysqldump when it didn't return an error if the output device was filled (Bug#1851)

- Fixed a bug in authentication code that allowed a malicious user to bypass password verification with specially crafted packets, using a modified client library. (CVE-2004-0627, CVE-2004-0628)

### B.1.23. Changes in MySQL 4.1.2 (28 May 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Incompatible Change: String comparison now works according to the SQL standard. Because we have that `'a' = 'a '` then from it must follow that `'a' > 'a\t'`. (The latter was not the case before MySQL 4.1.2.) To implement it, we had to change how storage engines compare strings internally. As a side effect, if you have a table where a `CHAR` or `VARCHAR` column in some row has a value with the last character less than `ASCII(32)`, you have to repair this table. `CHECK TABLES` tells you if this problem exists. (Bug#3152)

- Incompatible Change: The `Type` output column for `SHOW TABLE STATUS` now is labeled `Engine`.

- Incompatible Change: Handling of the `FLOAT` and `DOUBLE` floating-point data types is more strict to follow standard SQL. For example, a data type of `FLOAT(3,1)` stores a maximum value of 99.9. Previously, the server allowed larger numbers to be stored. That is, it stored a value such as 100.0 as 100.0. Now the server clips 100.0 to the maximum allowable value of 99.9. If you have tables that were created before MySQL 4.1.2 and that contain floating-point data not strictly legal for the column type, you should alter the data types of those columns. For example:

      ALTER TABLE tbl_name MODIFY col_name FLOAT(4,1);

- Incompatible Change: Added support for `DEFAULT CURRENT_TIMESTAMP` and for `ON UPDATE CURRENT_TIMESTAMP` specifications for `TIMESTAMP` columns. Now you can explicitly say that a `TIMESTAMP` column should be set automatically to the current timestamp for `INSERT` and/or `UPDATE` statements, or even prevent the column from updating automatically. Only one column with such an auto-set feature per table is supported. `TIMESTAMP` columns created with earlier versions of MySQL behave as before. Behavior of `TIMESTAMP` columns that were created without explicit specification of default/on as earlier depends on its position in table: If it is the first `TIMESTAMP` column, it be treated as having been specified as `TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP`. In other cases, it would be treated as a `TIMESTAMP DEFAULT 0` column. `NOW` is supported as an alias for `CURRENT_TIMESTAMP`.

  Unlike in previous versions, explicit specification of default values for `TIMESTAMP` column is never ignored and turns off the auto-set feature (unless you have `CURRENT_TIMESTAMP` as the default).

- Incompatible Change: Renamed prepared statements C API functions:

  Old Name | New Name
  `mysql_bind_param()` | `mysql_stmt_bind_param()`
  `mysql_bind_result()` | `mysql_stmt_bind_result()`
  `mysql_prepare()` | `mysql_stmt_prepare()`
  `mysql_execute()` | `mysql_stmt_execute()`
  `mysql_fetch()` | `mysql_stmt_fetch()`
  `mysql_fetch_column()` | `mysql_stmt_fetch_column()`
  `mysql_param_count()` | `mysql_stmt_param_count()`
  `mysql_param_result()` | `mysql_stmt_param_metadata()`
  `mysql_get_metadata()` | `mysql_stmt_result_metadata()`
  `mysql_send_long_data()` | `mysql_stmt_send_long_data()`

  Now all functions that operate with a `MYSQL_STMT` structure begin with the prefix `mysql_stmt_`.

- Incompatible Change: The signature of the `mysql_stmt_prepare()` function was changed to `int mysql_stmt_prepare(MYSQL_STMT *stmt, const char *query, unsigned long length)`. To create a `MYSQL_STMT` handle, you should use the `mysql_stmt_init()` function, not `mysql_stmt_prepare()`.

- The `FLOAT` and `DECIMAL` types now obey (precision,scale) settings. (Bug#10897)

- The `--defaults-file=`file_name`` option now requires that the filename must exist (safety fix). (Bug#3413)

- `REVOKE ALL PRIVILEGES, GRANT FROM user_list` is changed to a more consistent `REVOKE ALL PRIVILEGES, GRANT OPTION FROM user_list`. (Bug#2642)

- Now `SQL_SELECT_LIMIT` variable has no influence on subqueries. (Bug#2600)

- For replication of `MEMORY` (`HEAP`) tables: Made the master automatically write a `DELETE FROM` statement to its binary log when a `MEMORY` table is opened for the first time since the master's startup. This is for the case where the slave has replicated a non-empty `MEMORY` table, and then the master is shut down and restarted: the table is now empty on the master; the `DELETE FROM` empties it on the slave as well.

  Even with this fix, between the master's restart and the first use of the table on master, the slave still has out-of-date data in the table. However, if you use the `--init-file` option to populate the `MEMORY` table on the master at startup, it ensures that the failing time interval is zero. (Bug#2477)

- `ALTER TABLE DROP PRIMARY KEY` no longer drops the first `UNIQUE` index if there is no primary index. (Bug#2361)

- MySQL now issues a warning when a `SET` or `ENUM` column with duplicate values in the list is created. (Bug#1427)

- A name of “Primary” no longer can be specified as an index name. (That name is reserved for the `PRIMARY KEY` if the table has one.) (Bug#856)

- `SHOW GRANTS` with no `FOR` clause or with `FOR CURRENT_USER()` shows the privileges for the current session.

- mysqld_multi now creates the log in the directory named by `datadir` (from the `[mysqld]` section in `my.cnf` or compiled in), not in `/tmp`. Thanks to Christian Hammers from Debian Security Team for reporting this. (CVE-2004-0388)

- Changed that when the MySQL server has binary logging disabled (that is, no `--log-bin` option was used), then no transaction binary log cache is allocated for connections. This should save `binlog_cache_size` bytes of memory (32KB by default) for every connection.

- Added support for character set conversion and `MYSQL_TYPE_BLOB` type code in prepared statement protocol.

- When a session having open temporary tables terminates, the statement automatically written to the binary log is now `DROP TEMPORARY TABLE IF EXISTS` instead of `DROP TEMPORARY TABLE`, for more robustness.

- Added option `--to-last-log` to mysqlbinlog, for use in conjunction with `--read-from-remote-server`.

- mysql command-line client now supports multiple `-e` options. (Bug#591)

- New `myisam_data_pointer_size` system variable. See Section 5.1.3, “System Variables”.

- MySQL now supports up to 64 indexes per table.

- The Mac OS X Startup Item has been moved from the directory `/Library/StartupItems/MySQL` to `/Library/StartupItems/MySQLCOM` to avoid a file name collision with the MySQL Startup Item installed with Mac OS X Server. See Section 2.13.2, “Mac OS X Notes”.

- Multi-line statements in the `mysql` command-line client now are stored in the history file as a single line.

- `UNHEX()` function implemented. See Section 11.4, “String Functions”.

- Added the `ENGINE` table option as a synonym for the `TYPE` option for `CREATE TABLE` and `ALTER TABLE`.

- The `--log-warnings` server option now is enabled by default. Disable with `--skip-log-warnings`.

- Internal string-to-number conversion now supports only SQL:2003 compatible syntax for numbers. In particular, `'0x10'+0` does not work anymore. (Actually, it worked only on some systems before, such as Linux. It did not work on others, such as FreeBSD or Solaris. Making these queries OS-independent was the goal of this change.) Use `CONV()` to convert hexadecimal numbers to decimal. Example: `CONV(MID('0x10',3),16,10)+0`.

- Added the `EXAMPLE` storage engine.

- Added explanation of hidden `SELECT` of `UNION` in output of `EXPLAIN SELECT` statement.

- Added the `storage_engine` system variable as a synonym for `table_type`.

- Added `Binlog_cache_use` and `Binlog_cache_disk_use` status variables that count the number of transactions that used transaction binary log and that had to flush this temporary binary log to disk instead of using only the in-memory buffer. They can be used for tuning the `binlog_cache_size` system variable.

- Added `latin1_spanish_ci` (Modern Spanish) collation for the `latin1` character set.

- The improved character set support introduced in MySQL 4.1.0 for the `MyISAM` and `HEAP` storage engines is now available for `InnoDB` as well.

- If you try to create a key with a key part that is too long, and it is safe to auto-truncate it to a smaller length, MySQL now does so. A warning is generated, rather than an error.

- The mysql command-line client no longer stores in the history file multiple copies of identical queries that are run consecutively.

- C API enhancement: `SERVER_QUERY_NO_INDEX_USED` and `SERVER_QUERY_NO_GOOD_INDEX_USED` flags are now set in the `server_status` field of the `MYSQL` structure. It is these flags that make the query to be logged as slow if mysqld was started with `--log-slow-queries --log-queries-not-using-indexes`.

- Added `Handler_discover` status variable.

- Added the `mysql_set_local_infile_handler()` and `mysql_set_local_infile_default()` C API functions.

- Added `init_connect` and `init_slave` system variables. The values should be SQL statements to be executed when each client connects or each time a slave's SQL thread starts, respectively.

- The MySQL server now returns an error if `SET SQL_LOG_BIN` or `SET SQL_LOG_UPDATE` is issued by a user without the `SUPER` privilege (in previous versions it just silently ignored the statement in this case).

- The mysqld Windows server was renamed to mysqld-debug. See Section 2.3.8, “Selecting a MySQL Server Type”.

- `MyISAM` and `InnoDB` tables now support index prefix lengths up to 1000 bytes long.

- Added the `--default-storage-engine` server option as a synonym for `--default-table-type`.

- Prepared statements with all types of subqueries fixed.

- `UUID()` function implemented. Note that it does not work with replication yet. See Section 11.10.4, “Miscellaneous Functions”.

- mysqlhotcopy now works on NetWare.

- `CHAR BYTE` is an alias for the `BINARY` data type. (Previously, it was an alias for `CHAR BINARY`.)

- Added option `--replicate-same-server-id`.

- `MyISAM` tables now support keys up to 1000 bytes long.

- The `ft_boolean_syntax` variable now can be changed while the server is running. See Section 5.1.3, “System Variables”.

Bugs fixed:

- Replication: Following a non-fatal error during the execution of a statement that later succeeded, the master failed to reset the error code to 0, so the error code was written into the binary log. This caused false Did not get the same error as on master errors on the slave. (Bug#2083)

- Fixed a bug in `REPAIR TABLE` that resulted sometimes in a corrupted table, if the table contained `FULLTEXT` indexes and many words of different lengths that are considered equal (which is possible in certain collations, such as `latin1_german2_ci` or `utf8_general_ci`). (Bug#3835)

- If `server-id` was not set using startup options but with `SET GLOBAL`, the replication slave still complained that it was not set. (Bug#3829)

- Fixed a crash of mysqld that was started with binary logging disabled, but with a non-zero value for the `expire_logs_days` system variable. (Bug#3807)

- Fixed crash of `GROUP_CONCAT()` on expression with `ORDER BY` and external `ORDER BY` in a query. (Bug#3752)

- Fixed a bug in a query that used `DISTINCT` and `ORDER BY` by column's real name, while the column had an alias, specified in `SELECT` clause. (Bug#3681)

- Fixed a bug in `ALL`/`SOME` subqueries in case of optimization (key field present in subquery). (Bug#3646)

- mysqld could crash when a table was altered and used at the same time. This was a 4.1.2-specific bug. . (Bug#3643)

- Fixed check of `EXPLAIN` of `UNION`. (Bug#3639)

- Fixed crash on second execution of prepared statement with `UNION`. (Bug#3577)

- Fixed a crash of the MySQL slave server when it was built with `--with-debug` and replicating itself. (Bug#3568)

- Fixed incorrect results of aggregate functions in subquery with empty result set. (Bug#3505)

- Multiple-table `DELETE` statements were always replicated by the slave if there were some `--replicate-*-ignore-table` options and no `--replicate-*-do-table` options. (Bug#3461)

- Memory could be corrupted by replicating a `LOAD DATA INFILE` from a MySQL 3.23 master. Some less critical issues remain; see Section 6.7, “Replication Features and Known Problems”. (Bug#3422)

- mysqlbinlog failed to print a `USE` statement under those rare circumstances where the binary log contained a `LOAD DATA INFILE` statement. (Bug#3415)

- Incorrect error message when wrong table used in multiple-table `DELETE` statement in prepared statements. (Bug#3411)

- Fixed prepared statement support for `INSERT`, `REPLACE`, `CREATE`, `DELETE`, `SELECT`, `DO`, `SET` and `SHOW`. All other commands are prohibited via prepared statement interface. (Bug#3406, Bug#3398, Bug#2811)

- Fixed security problem in new authentication where password was not checked for changed `GRANT` accounts until `FLUSH PRIVILEGES` was executed. (Bug#3404)

- Fixed a bug in `SHOW GRANTS` and `EXPLAIN SELECT` character set conversion. (Bug#3403)

- Fixed a rare error condition that caused the slave SQL thread spuriously to print the message `Binlog has bad magic number` and stop when it was not necessary to do so. (Bug#3401)

- Fixed the `Exec_master_log_pos` column and its disk image in the `relay-log.info` file to be correct if the master had version 3.23. (The value was too big by six bytes.) This bug does not exist in MySQL 5.0. (Bug#3400)

- Aggregate functions could lead to server crashes when used in prepared statements. (Bug#3360)

- Fixed that in some replication error messages, a very long query caused the rest of the message to be invisible (truncated), by putting the query last in the message. (Bug#3357)

- Fixed bug that caused execution of prepared statements to fail then table that this statement were using left table cache. This bug showed up as if this prepared statement used random garbage as column names or as server crashes. (Bug#3307)

- Fixed a problem resulting from setting the `character_set_results` variable to `NULL`. (Bug#3296)

- Fixed a symlink vulnerability in the `mysqlbug` script. (Bug#3284)

- Fixed bug in privilege checking of `ALTER TABLE RENAME`. (Bug#3270)

- Fixed unknown error when negative value bind to unsigned. (Bug#3223)

- Fixed mysqlbinlog --read-from-remote-server to print the exact positions of events in the "at #" lines. (Bug#3214)

- mysqlbinlog --read-from-remote-server read all binary logs following the one that was requested. It now stops at the end of the requested file, the same as it does when reading a local binary log. There is an option `--to-last-log` to get the old behavior. (Bug#3204)

- `CONCAT_WS()` makes the server die in case of illegal mix of collations. (Bug#3087)

- Changed that when a thread handling `INSERT DELAYED` (also known as a `delayed_insert` thread) is killed, its statements are recorded with an error code of value zero (killing such a thread does not endanger replication, so we thus avoid a superfluous error on the slave). (Bug#3081)

- Fixed memory leak in the client library when statement handle was freed on closed connection (call to `mysql_stmt_close()` after `mysql_close()`). (Bug#3073)

- Changed that when a `DROP TEMPORARY TABLE` statement is automatically written to the binary log when a session ends, the statement is recorded with an error code of value zero (this ensures that killing a `SELECT` on the master does not result in a superfluous error on the slave). (Bug#3063)

- Added support for unsigned integer types to prepared statement API . (Bug#3035)

- Fixed crash in prepared statements when subquery in the `FROM` clause with parameter used. (Bug#3020)

- Fixed that when a `Rotate` event is found by the slave SQL thread in the middle of a transaction, the value of `Relay_Log_Pos` in `SHOW SLAVE STATUS` remains correct. (Bug#3017)

- Corrected the master's binary log position that `InnoDB` reports when it is doing a crash recovery on a slave server. (Bug#3015)

- Fixed a bug in full-text search on multi-byte character set (such as UTF8) that appeared when a search word was shorter than a matching word from the index (for example, searching for “Uppsala” when table data contain “Uppsa*la”). (Bug#3011)

- `--replicate-wild-*-table` rules now apply to `ALTER DATABASE` when the table pattern is `%`, as is the case for `CREATE DATABASE` and `DROP DATABASE`. (Bug#3000)

- Fixed that a statement never triggers a superfluous error on the slave, if it must be excluded given the `--replicate-*` options. The bug was that if the statement had been killed on the master, the slave would stop. (Bug#2983)

- UTF8 charset breaks joins with mixed column/string constant. (Bug#2959)

- Fixed a bug in the `GRANT` system. When a password was assigned to an account at the global level and then privileges were granted at the database level (without specifying any password), the existing password was replaced temporarily in memory until the next `FLUSH PRIVILEGES` operation or the server was restarted. (Bug#2953)

- Fixed a segmentation fault when running `LOAD DATA FROM MASTER` after `RESET SLAVE`. (Bug#2922)

- Fixed deadlock when two `START SLAVE` commands were run at the same time. (Bug#2921)

- Fixed comparison of tables/database names with `--lower_case_table_names` option. (Bug#2880)

- Fixed using subqueries with `OR` and `AND` functions. (Bug#2838)

- Changed the column `Seconds_Behind_Master` in `SHOW SLAVE STATUS` to never show a value of -1. (Bug#2826)

- Table default character set affects `LONGBLOB` columns. (Bug#2821)

- Fixed server segmentation faults when processing malformed prepared statements. (Bug#2795, Bug#2274)

- Made clearer the error message that one gets when an update is refused because of the `--read-only` option. (Bug#2757)

- Fixed calculation of `Index_length` in `HEAP` table status for `BTREE` indexes. (Bug#2719)

- Fixed crash in `MATCH ... AGAINST()` on a phrase search operator with a missing closing double quote. (Bug#2708)

- Fixed output of mysqldump --tab. (Bug#2705)

- The MySQL server did not report any error if a statement (submitted through `mysql_real_query()` or `mysql_stmt_prepare()`) was terminated by garbage characters. This can happen if you pass a wrong `length` parameter to these functions. The result was that the garbage characters were written into the binary log. (Bug#2703)

- An issue with the range optimizer caused a segmentation fault on some very rare queries. (Bug#2698)

- Fixed a lot of bugs in `GROUP_CONCAT()`. (Bug#2695, Bug#3319, Bug#3381)

- Fixed processing of `RAND()` in subqueries with static tables. (Bug#2645)

- Fixed bug in `ALTER TABLE RENAME`, when rename to the table with the same name in another database silently dropped destination table if it existed. (Bug#2628)

- Fixed bug with `SHOW CREATE TABLE ...` which didn't properly double quotes. (Bug#2593)

- Fixed bug with mysqldump not quoting “tricky” names correctly. (Bug#2592)

- Fixed bug with quoting of table names in mysqldump for various values of `sql_mode` of server. (Bug#2591)

- Fixed bug in replication with `CREATE TABLE ... LIKE ...` that resulted in a statement not being written to the binary log. (Bug#2557)

- Fix for a bug in `UNION` operations with `InnoDB` storage engine, when some columns from one table were used in one `SELECT` statement and some were used in another `SELECT` statement. (Bug#2552)

- Fix for a bug that prevented table / column privileges from being loaded on startup. (Bug#2546)

- Multiple-table `DELETE` statements were never replicated by the slave if there were any `--replicate-*-table` options. (Bug#2527)

- Fix for a bug in `UNION` operations that prevented proper handling of `NULL` columns. This happened only if a column in the first `SELECT` node was `NOT NULL`. (Bug#2508)

- Fixed memory leak in `INSERT ... ON DUPLICATE KEY UPDATE ...`. (Bug#2438)

- Fixed incorrect parsing of subqueries in the `FROM` clause. (Bug#2421)

- Fixed a rare table corruption on adding data (`INSERT`, `REPLACE`, `UPDATE`, etc. but not `DELETE`) to a `FULLTEXT` index. (Bug#2417)

- Removed try to check `NULL` if index built on column where `NULL` is impossible in `IN` subquery optimization. (Bug#2393)

- Fixed bug in `ANALYZE TABLE` on a `BDB` table inside a transaction that hangs server thread. (Bug#2342)

- `ALTER DATABASE` caused the client to hang if the database did not exist. (Bug#2333)

- Fixed parsing of short-form IP addresses in `INET_ATON()`. (Bug#2310)

- Compile the `MySQL-client` RPM package against `libreadline` instead of `libedit`. (Bug#2289)

- Fixed bug in client library that caused `mysql_stmt_fetch()` and `mysql_stmt_store_result()` to hang if they were called without prior call of `mysql_stmt_execute()`. Now they give an error instead. (Bug#2248)

- Fixed `mysql_stmt_affected_rows()` call to always return number of rows affected by given statement. (Bug#2247)

- Fixed bug when using impossible `WHERE` with `PROCEDURE ANALYSE()`. . (Bug#2238)

- Fix for a crashing bug that occurred in the mysql client program when database name was longer then expected. (Bug#2221)

- Fix for a bug that caused wrong results when `CAST()` was applied on `NULL` to signed or unsigned integer column. (Bug#2219)

- Fix for a bug that caused client/server communication to be broken when `mysql_set_server_option()` was invoked. (Bug#2207)

- Fixed a bug in `CHECK TABLE` that sometimes resulted in a spurious error `Found key at page ... that points to record outside datafile` for a table with a `FULLTEXT` index. (Bug#2190)

- Fixed bug in `GRANT` with table-level privilege handling. (Bug#2178)

- Fixed bug in `ORDER BY` on a small column. (Bug#2147)

- Fixed a crash when the replication slave was unable to create the first relay log. (Bug#2145)

- Removed a misleading "check permissions on master.info" from a replication error message, because the cause of the problem could be different from permissions. (Bug#2121)

- Queries with subqueries in `FROM` clause locks all tables at once for now. This also fixed bugs in `EXPLAIN` of subqueries in `FROM` output. (Bug#2120)

- Fixed bug with storing values that are out of range for `DOUBLE` and `FLOAT` columns. (Bug#2082)

- Fixed a hang in full-text indexing of strings in multi-byte (all besides `utf8`) charsets. (Bug#2065)

- Added optimization that allows for prepared statements using a large number of tables or tables with a large number of columns to be re-executed significantly faster. (Bug#2050)

- Fixed a crash in full-text indexing of UTF8 data. (Bug#2033)

- Fix for a crashing bug that was caused by not setting `vio_timeout()` virtual function for all protocols. This bug occurred on Windows only. (Bug#2025)

- Replication: a rare race condition in the slave SQL thread that could lead to an incorrect complaint that the relay log is corrupted. (Bug#2011)

- Fixed a bug in myisamchk and `CHECK TABLE` that sometimes resulted in a spurious error `Found key at page ... that points to record outside datafile` for a table with a `FULLTEXT` index. (Bug#1977)

- Replication: If a client connects to a slave server and issues an administrative statement for a table (for example, `OPTIMIZE TABLE` or `REPAIR TABLE`), this could sometimes stop the slave SQL thread. This does not lead to any corruption, but you must use `START SLAVE` to get replication going again. (Bug#1858)

- Replication: in the slave SQL thread, a multiple-table `UPDATE` could produce an incorrect complaint that some record was not found in one table, if the `UPDATE` was preceded by a `INSERT ... SELECT`. (Bug#1701)

- Fixed `mysql_stmt_send_long_data()` behavior on second execution of prepared statement and in case when long data had zero length. (Bug#1664)

- Fixed bug with compiling `--with-pstack` with binutils 2.13.90. (Bug#1661)

- You can now call `mysql_stmt_attr_set(..., STMT_ATTR_UPDATE_MAX_LENGTH)` to tell the client library to update `MYSQL_FIELD->max_length` when doing `mysql_stmt_store_result()`. . (Bug#1647)

- Fixed a bug with the `INTERVAL()` function when 8 or more comparison arguments are provided. (Bug#1561)

- A query that uses both `UNION [DISTINCT]` and `UNION ALL` now works correctly. (Bug#1428)

- Fixed a bug in parallel repair (myisamchk -p, `myisam_repair_threads`); sometimes the repair process failed to repair a table. (Bug#1334)

- Fixed query cache statistics.

- Fixed bug in the parser, making the syntax `CONVERT(`expr`,`type`)` legal again.

- Packaging: Fixed a bug in the Mac OS PKG `postinstall` script (mysql_install_db was called with an obsolete argument).

- Requiring `UPDATE` privilege for tables which are not updated in multiple-table `UPDATE` statement in prepared statements.

- Fixed a bug in multiple-table `UPDATE` statements that resulted in an error when one of the tables was not updated but was used in the nested query, contained therein.

- Fixed `DROP DATABASE` to report number of tables deleted.

- The `--local-load` option of mysqlbinlog now requires an argument.

- Fixed a bug that made `Max_used_connections` to be less than the actual maximum number of connections in use simultaneously.

- Packaging: Added missing file `mysql_create_system_tables` to the server RPM package. This bug was fixed for the 4.1.1 RPMs by updating the MySQL-server RPM from `MySQL-server-4.1.1-0` to `MySQL-server-4.1.1-1`. The other RPMs were not affected by this change.

- Fixed a bug in `CREATE ... SELECT` that sometimes caused a string column with a multi-byte character set (such as `utf8`) to have insufficient length to hold the data.

- `UNION` statements did not consult `SQL_SELECT_LIMIT` value when set. This is now fixed properly, which means that this limit is applied to the top level query, unless `LIMIT` for entire `UNION` is used.

- Prepare statements parameter do not cause error message as fields used in select list but not included in `ORDER BY` list.

### B.1.24. Changes in MySQL 4.1.1 (01 December 2003)

This release includes all fixes in MySQL 4.0.16 and most of the fixes in MySQL 4.0.17.

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Incompatible Change: Client authentication now is based on 41-byte passwords in the `user` table, not 45-byte passwords as in 4.1.0. Any 45-byte passwords created for 4.1.0 must be reset after running the mysql_fix_privilege_tables script.

- Incompatible Change: Renamed the C API `mysql_prepare_result()` function to `mysql_get_metadata()` because the old name was confusing.

- The `--old-protocol` option for mysqld is no longer supported and has been removed.

- When using `SET sql_mode='mode'` for a complex mode (such as `ANSI`), we now update the `sql_mode` variable to include all the individual options implied by the complex mode.

- `CHAR`, `VARCHAR`, and `TEXT` columns now have lengths measured in characters rather than in bytes. The character size depends on the column's character set. This means, for example, that a `CHAR(`n`)` column for a multi-byte character set takes more storage than before. Similarly, index values on such columns are measured in characters, not bytes.

- Renamed `CLIENT_MULTI_QUERIES` connect option flag to `CLIENT_MULTI_STATEMENTS`. To allow for a transition period, the old option continues to be recognized for a while.

- `ANALYZE TABLE`, `OPTIMIZE TABLE`, `REPAIR TABLE`, and `FLUSH` statements are now stored in the binary log and thus replicated to slaves. This logging does not occur if the optional `NO_WRITE_TO_BINLOG` keyword (or its alias `LOCAL`) is given. Exceptions are that `FLUSH LOGS`, `FLUSH MASTER`, `FLUSH SLAVE`, and `FLUSH TABLES WITH READ LOCK` are not logged in any case. For a syntax example, see Section 12.5.5.2, “`FLUSH` Syntax”.

- Added `--secure-auth` option to mysql command-line client. If this option is set, the client refuses to send passwords in old (pre-4.1.1) format.

- The `mysql_next_result()` C API function now returns `-1` if there are no more result sets.

- ### Important

  If you upgrade to `InnoDB`-4.1.1 or higher, you cannot downgrade to a version lower than 4.1.1 any more! That is because earlier versions of `InnoDB` are not aware of multiple tablespaces.

- It is now possible to create multiple key caches, assign table indexes to particular caches, and to preload indexes into caches. See Section 12.5.5.1, “`CACHE INDEX` Syntax”. See Section 12.5.5.4, “`LOAD INDEX INTO CACHE` Syntax”. Structured system variables are introduced as a means of grouping related key cache parameters. See Section 5.1.4.1, “Structured System Variables”.

- Replication over SSL now works.

- Added `SHOW BDB LOGS` as an alias for `SHOW LOGS`.

- Added `character_set_client`, `character_set_connection`, `character_set_database`, `character_set_results`, `character_set_server`, `character_set_system`, `collation_connection`, `collation_database`, and `collation_server` system variables to provide information about character sets and collations.

- The `DATABASE()` function now returns `NULL` rather than the empty string if there is no database selected.

- Removed unused `ft_max_word_len_for_sort` variable from myisamchk.

- Removed unused `ft_max_word_len_for_sort` system variable.

- Added aggregate function `BIT_XOR()` for bitwise XOR operations.

- Require `DEFAULT` before table and database default character set. This enables us to use `ALTER TABLE `tbl_name` ... CHARACTER SET=...` to change the character set for all `CHAR`, `VARCHAR`, and `TEXT` columns in a table.

- Added `--sql-mode=NO_AUTO_VALUE_ON_ZERO` option to suppress the usual behavior of generating the next sequence number when zero is stored in an `AUTO_INCREMENT` column. With this mode enabled, zero is stored as zero; only storing `NULL` generates a sequence number.

- Added `SHOW MASTER LOGS` as an alias for `SHOW BINARY LOGS`. (In 4.1.0, `SHOW MASTER LOGS` was renamed to `SHOW BINARY LOGS`. Now you can use either one.)

- The `--lower-case-table-names=1` server option now also makes aliases case insensitive. (Bug#534)

- Full-text search now supports multi-byte character sets and the Unicode `utf8` character set. (The Unicode `ucs2` character set is not yet supported.)

- `EXPLAIN` now supports an `EXTENDED` option. When given, `EXPLAIN` generates extra information that may be viewed with the `SHOW WARNINGS` statement.

- Added `IGNORE` option for `DELETE` statement.

- Added `mysql_sqlstate()` and `mysql_stmt_sqlstate()` C API client functions that return the `SQLSTATE` error code for the last error.

- Renamed `bdb_version` system variable to `version_bdb`.

- `LOAD DATA` now produces warnings that can be fetched with `SHOW WARNINGS`.

- Added support for syntax `CREATE TABLE table2 (LIKE table1)` that creates an empty table `table2` with a definition that is exactly the same as `table1`, including any indexes.

- The `START SLAVE` statement now supports an `UNTIL` clause for specifying that the slave SQL thread should be started but run only until it reaches a given position in the master's binary logs or in the slave's relay logs.

- Most subqueries are now much faster than before.

- MySQL source distributions now also include the MySQL Internals Manual `internals.texi`.

- Added `Slave_IO_State` and `Seconds_Behind_Master` columns to the output of `SHOW SLAVE STATUS`. `Slave_IO_State` indicates the state of the slave I/O thread, and `Seconds_Behind_Master` indicates the number of seconds by which the slave is late compared to the master.

- Added `mysql_set_server_option()` C API client function to allow multiple statement handling in the server to be enabled or disabled.

- Added `MATCH ... AGAINST( ... WITH QUERY EXPANSION)` and the `ft_query_expansion_limit` system variable.

- The interface to aggregate user-defined functions has changed a bit. You must now declare a `xxx_clear()` function for each aggregate function `XXX()`. `xxx_clear()` is used instead of `xxx_reset()`.

- Added `preload_buffer_size` system variable.

- Added `delimiter` (`\d`) command to the mysql command-line client for changing the statement delimiter (terminator). The default delimiter is semicolon.

- mysqldump now includes a statement in the dump output to set `FOREIGN_KEY_CHECKS` to 0 to avoid problems with tables having to be reloaded in a particular order when the dump is reloaded. The existing `FOREIGN_KEY_CHECKS` value is saved and restored.

- Phrase search in `MATCH ... AGAINST ( ... IN BOOLEAN MODE)` no longer matches partial words.

- Added new `%f` microseconds format specifier for `DATE_FORMAT()` and `TIME_FORMAT()`.

- Added `secure_auth` global server system variable and `--secure-auth` server option that disallow authentication for accounts that have old (pre-4.1.1) passwords.

- Changed that the relay log is flushed to disk by the slave I/O thread every time it reads a relay log event. This reduces the risk of losing some part of the relay log in case of brutal crash.

- Table aliases are not case sensitive if `lower_case_table_names` is non-zero.

- The `--quote-names` option for mysqldump now is enabled by default.

- Produce warnings even for single-row `INSERT` statements, not just for multiple-row `INSERT` statements. Previously, it was necessary to set `SQL_WARNINGS=1` to generate warnings for single-row statements.

- Added `PURGE BINARY LOGS` as an alias for `PURGE MASTER LOGS`.

- `MyISAM` tables now use a better checksum algorithm (if checksum is enabled with `CREATE TABLE ... CHECKSUM=1`). Old tables will appear to have incorrect checksum, and should be repaired.

- All queries in which at least one `SELECT` does not use indexes properly now are written to the slow query log when long log format is used.

- It is now possible to create a `MERGE` table from `MyISAM` tables in different databases. Formerly, all the `MyISAM` tables had to be in the same database, and the `MERGE` table had to be created in that database as well.

- Added new `ADDTIME()`, `DATE()`, `DATEDIFF()`, `LAST_DAY()`, `MAKEDATE()`, `MAKETIME()`, `MICROSECOND()`, `SUBTIME()`, `TIME()`, `TIMEDIFF()`, `TIMESTAMP()`, `UTC_DATE()`, `UTC_TIME()`, `UTC_TIMESTAMP()`, and `WEEKOFYEAR()` functions.

- `CREATE TABLE `tbl_name` (...) TYPE=`storage_engine`` now generates a warning if the named storage engine is not available. The table is still created as a `MyISAM` table, as before.

- New global system variable `relay_log_purge` to enable or disable automatic relay log purging.

- Added new `COMPRESS()`, `UNCOMPRESS()`, and `UNCOMPRESSED_LENGTH()` functions.

- Added `DROP USER '`user_name`'@'`host_name`'` statement to drop an account that has no privileges.

- New `COERCIBILITY()` function to return the collation coercibility of a string.

- `LIMIT` no longer accepts negative arguments (they used to be treated as very big positive numbers before).

- You can revoke all privileges from a user with `REVOKE ALL PRIVILEGES, GRANT FROM user_list`.

- Added the OLAP (On-Line Analytical Processing) function `ROLLUP`, which provides summary rows for each `GROUP BY` level.

- Disabled the `PURGE LOGS` statement that was added in version 4.1.0. The statement now should be issued as `PURGE MASTER LOGS` or `PURGE BINARY LOGS`.

- Added new syntax for `ADDDATE()` and `SUBDATE()`. The second argument now may be a number representing the number of days to be added to or subtracted from the first date argument.

- `TIME` columns with hour values greater than 24 were returned incorrectly to the client.

- Added new `type` values `DAY_MICROSECOND`, `HOUR_MICROSECOND`, `MINUTE_MICROSECOND`, `SECOND_MICROSECOND`, and `MICROSECOND` for `DATE_ADD()`, `DATE_SUB()`, and `EXTRACT()`.

- New `CHECKSUM TABLE` statement for reporting table checksum values.

- Added `SQLSTATE` codes for all server errors.

Bugs fixed:

- Fixed a bug that under certain circumstances could allow a privilege escalation via database wildcards in `GRANT`. (Bug#3924)

- Fixed bug in `ALTER TABLE RENAME`, when rename to the table with the same name in another database silently dropped destination table if it existed. (Bug#2628)

- `SLAVE START` (which is a deprecated syntax, `START SLAVE` should be used instead) could crash the slave. (Bug#2516)

- Fixed bug with prepared statements: after call to mysql_prepare placeholders became allowed in all consequent statements, even if they are not prepared (Bug#1946)

- Fixed a bug in privilege handling that caused connections from certain IP addresses to be assigned incorrect database-level privileges. A connection could be assigned the database privileges of the previous successful authentication from one of those IP addresses, even if the IP address username and database name were different. (Bug#1636)

- Fixed bug with prepared statements: Using the `?` prepared statement parameter as the argument to certain functions or statement clauses caused a server crash when `mysql_prepare()` was invoked. (Bug#1500)

- When an undefined user variable was used in a updating query on the master (such as `INSERT INTO t VALUES(@a)`, where `@a` had never been set by this connection before), the slave could replicate the query incorrectly if a previous transaction on the master used a user variable of the same name. (Bug#1331)

- Fixed a bug in `UNION` that prohibited `NULL` values from being inserted into result set columns where the first `SELECT` of the `UNION` retrieved `NOT NULL` columns. The type and max_length of the result column is now defined based on all `UNION` parts.

- Fixed name resolution of columns of reduced subqueries in unions. (Bug#745)

- Fixed memory overrun in subqueries in select list with `WHERE` clause bigger than outer query `WHERE` clause. (Bug#726)

- `HASH`, `BTREE`, `RTREE`, `ERRORS`, and `WARNINGS` no longer are reserved words. (Bug#724)

- Fix for bug in `ROLLUP` when all tables were `const` tables. (Bug#714)

- Fixed bug in marking columns of reduced subqueries. (Bug#679)

- Fixed a bug with double freed memory.

- Fixed a bug that made `CREATE FULLTEXT INDEX` syntax illegal.

- Fixed a bug that caused `MyISAM` tables with `FULLTEXT` indexes created in 4.0.x to be unreadable in 4.1.x.

- When not specify hostname in `SET PASSWORD FOR user` it's now defaulted to `%` instead of the current host.

- Fixed a crashing bug when attempting to create a table containing a spatial (GIS) column with a storage engine that does not support spatial types.

- Fixed a crashing bug in `UNION` operations that involved temporary tables.

- Fixed a crashing bug in `UNION` caused by the empty select list and a non-existent column being used in some of the individual `SELECT` statements.

- Fixed a rare table corruption bug in `DELETE` from a big table with a new (created by MySQL-4.1) full-text index.

- Fixed missing last character in function output. (Bug#447)

- Fixed name resolution of outer columns of subquery in `INSERT`/`REPLACE` statements. (Bug#446)

- Fixed reduced subquery processing in `ORDER BY` and `GROUP BY` clauses. (Bug#442)

- Fixed a crashing bug in `DELETE` with `ORDER BY` and `LIMIT` caused by an uninitialized array of reference pointers.

- The new `PASSWORD()` function in 4.1 is now properly replicated. (Bug#344)

- Fixed merging types and length of result set columns for `UNION` operations. The types and lengths now are determined taking into account values for all `SELECT` statements in the `UNION`, not just the first `SELECT`.

- Fixed mysql parser not to erroneously interpret “ `;` ” character within `/* ... */` comment as statement terminator.

- Fixed a bug in the `USER()` function caused by an error in the size of the allocated string.

- Fixed a security bug: A server compiled without SSL support still allowed connections by users who had the `REQUIRE SSL` option specified for their accounts.

- Fixed a crashing bug in `DERIVED TABLES` when `EXPLAIN` is used on a `DERIVED TABLES` with a join.

- Fixed a replication bug with a 3.23 master and a 4.0 slave: The slave lost the replicated temporary tables if `FLUSH LOGS` was issued on the master. (Bug#254)

- Fixed a crash when a `SELECT` that required a temporary table (marked by `Using temporary` in `EXPLAIN` output) was used as a derived table in `EXPLAIN` command. (Bug#251)

- Fixed a data loss bug in `REPAIR TABLE ... USE_FRM` when used with tables that contained `TIMESTAMP` columns and were created in 4.0.x.

- `CONNECTION_ID()` now is properly replicated. (Bug#177)

- Error-handling functions were not called properly when an error resulted from `[CREATE | REPLACE| INSERT] ... SELECT` statements.

- Fixed a rare replication bug when a transaction spanned two or more relay logs, and the slave was stopped while executing the part of the transaction that was in the second or later relay log. Then replication would resume at the beginning of the second or later relay log, which was incorrect. (It should resume at `BEGIN`, in the first relay log.) (Bug#53)

- `LAST_INSERT_ID()` now returns 0 if the last `INSERT` statement didn't insert any rows.

### B.1.25. Changes in MySQL 4.1.0 (03 April 2003: Alpha)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Incompatible Change: `TIMESTAMP` is now returned as a string of type `'YYYY-MM-DD HH:MM:SS'` and different timestamp lengths are not supported.

  This change was necessary for SQL standards compliance. In a future version, a further change will be made (backward compatible with this change), allowing the timestamp length to indicate the desired number of digits of fractions of a second.

- Allow index type to be specified explicitly for some storage engines via `USING type_name` syntax in index definition.

- Allow `DEFAULT(`col_name`)` in expressions; it produces the column's default value.

- Added database and real table name (in case of alias) to the `MYSQL_FIELD` structure.

- Renamed `SHOW MASTER LOGS` statement to `SHOW BINARY LOGS`.

- Unicode (UTF8) support.

- Allow one to change mode for `ANSI_QUOTES` on the fly.

- Faster embedded server (new internal communication protocol).

- One can specify many temporary directories to be used in a round-robin fashion with: `--tmpdir=dirname1:dirname2:dirname3`.

- New faster client/server protocol that supports prepared statements, bound parameters, and bound result columns, binary transfer of data, warnings.

- Aliases are now forced in derived tables, as per standard SQL.

- Fixed bug in `libmysqlclient` that fetched column defaults.

- Support for GIS (Geometrical data). See Chapter 15, Spatial Extensions.

- `REPAIR TABLE` and `OPTIMIZE TABLE` now can be killed. See Section 12.5.5.3, “`KILL` Syntax”.

- Replication now works with `RAND()` and user variables `@var`.

- Added `record_in_range()` method to `MERGE` tables to be able to choose the right index when there are many to choose from.

- New `CHARSET()` and `COLLATION()` functions to return the character set and collation of a string.

- Fixed bug in `mysql` command-line client in interpreting quotes within comments. (Bug#539)

- Added new `VARIANCE(`expr`)` function returns the variance of `expr`

- In `CREATE TABLE foo (a INT not null primary key)` the `PRIMARY` word is now optional.

- `CHAR BYTE` is an alias for the `CHAR BINARY` data type.

- `VARCHARACTER` is an alias for `VARCHAR`.

- Added support for `UNION` in derived tables.

- `SHOW [COUNT(*)] WARNINGS` shows warnings from the last command.

- New operators `integer MOD integer` and `integer DIV integer`. `DIV` is now a reserved word.

- One can specify a data type for a column in `CREATE TABLE ... SELECT` by defining the column in the `CREATE` part.

      CREATE TABLE foo (a TINYINT NOT NULL) SELECT b+1 AS a FROM bar;

- ``expr` SOUNDS LIKE `expr`` same as `SOUNDEX(`expr`)=SOUNDEX(`expr`)`.

- Multi-line queries: You can now issue several queries at once and then read the results in one go.

- New `CONVERT(... USING ...)` syntax for converting string values between character sets.

- `ALTER DATABASE`.

- Added `old-password` command to mysqladmin for changing password but storing it using the old password-hashing format.

- In `CREATE TABLE` the attribute `SERIAL` is now an alias for `BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE`.

- One can specify the different `BLOB`/`TEXT` types with the syntax `BLOB(`length`)` and `TEXT(`length`)`. MySQL automatically changes it to one of the internal `BLOB`/`TEXT` types.

- New more secure client authentication based on 45-byte passwords in the `user` table. (CVE-2000-0981)

- Subqueries: `SELECT * from t1 where t1.a=(SELECT t2.b FROM t2)`.

- `START SLAVE` (`STOP SLAVE`) no longer returns an error if the slave is started (stopped); it returns a warning instead.

- New options `--reconnect` and `--skip-reconnect` for the mysql client, to reconnect automatically or not if the connection is lost.

- `TRUE` and `FALSE` added as alias for 1 and 0, respectively.

- `DATE`/`DATETIME` checking is now a bit stricter to support the ability to automatically distinguish between date, datetime, and time with microseconds. For example, dates of type `YYYYMMDD HHMMDD` are no longer supported; you must either have separators between each `DATE`/`TIME` part or not at all.

- `REPAIR TABLE` of `MyISAM` tables now uses less temporary disk space when sorting char columns.

- Derived tables:

      SELECT a.col1, b.col2
             FROM (SELECT MAX(col1) AS col1 FROM root_table) a,
             other_table b
             WHERE a.col1=b.col1;

- Added `--compatible` option to mysqldump for producing output that is compatible with other database systems or with older MySQL servers.

- `DROP TEMPORARY TABLE` now drops only temporary tables and doesn't end transactions.

- Fixed `SELECT .. LIMIT 0` to return proper row count for `SQL_CALC_FOUND_ROWS`.

- One can create a table from the existing table using `CREATE [TEMPORARY] TABLE [IF NOT EXISTS] `table` (LIKE `table`)`. The table can be either normal or temporary.

- One can add a comment per column in `CREATE TABLE`.

- `SERIAL DEFAULT VALUE` added as an alias for `AUTO_INCREMENT`.

- New function `IS_USED_LOCK()` for determining the connection identifier of the client that holds a given advisory lock.

- `SELECT ... FROM DUAL` is an alias for `SELECT ...`. (To be compatible with some other database systems).

- `EXPLAIN SELECT` now can be killed. See Section 12.5.5.3, “`KILL` Syntax”.

- Server side help for all MySQL functions. One can now type `help week` in the mysql client and get help for the `week()` function.

- Allow empty index lists to be specified for `USE INDEX`, `IGNORE INDEX`, and `FORCE INDEX`.

- `SHOW FULL COLUMNS FROM `tbl_name`` shows column comments.

- Character sets to be defined per column, table and database.

- Added new `mysql_get_server_version()` C API client function.

- New `CRC32()` function to compute cyclic redundancy check value.

- `BTREE` index on `MEMORY` (`HEAP`) tables.

- If one creates a too long `CHAR`/`VARCHAR` it's now automatically changed to `TEXT` or `BLOB`; One get a warning in this case.

- On Windows, we are now using shared memory to communicate between server and client when they are running on the same machine and you are connecting to `localhost`.

- `SLAVE START` and `SLAVE STOP` are no longer accepted by the query parser; use `START SLAVE` and `STOP SLAVE` instead.

- The `--opt` option for mysqldump now is enabled by default, as are all the options implied by `--opt`.

## B.2. Changes in release 4.0.x

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Version 4.0 of the MySQL server includes many enhancements and new features:

- The `InnoDB` storage engine is now included in the standard binaries, adding transactions, row-level locking, and foreign keys. See Section 13.2, “The `InnoDB` Storage Engine”.

- A query cache, offering vastly increased performance for many applications. By caching complete result sets, later identical queries can return instantly. See Section 7.5.3, “The MySQL Query Cache”.

- Improved full-text indexing with boolean mode, truncation, and phrase searching. See Section 11.8, “Full-Text Search Functions”.

- Enhanced `MERGE` tables, now supporting `INSERT` statements and `AUTO_INCREMENT`. See Section 13.3, “The `MERGE` Storage Engine”.

- `UNION` syntax in `SELECT`. See Section 12.2.7.3, “`UNION` Syntax”.

- Multiple-table `DELETE` statements. See Section 12.2.1, “`DELETE` Syntax”.

- `libmysqld`, the embedded server library. See Section 16.1, “libmysqld, the Embedded MySQL Server Library”.

- Additional `GRANT` privilege options for even tighter control and security. See Section 12.5.1.2, “`GRANT` Syntax”.

- Management of user resources in the `GRANT` system, particularly useful for ISPs and other hosting providers. See Section 5.6.4, “Limiting Account Resources”.

- Dynamic server variables, allowing configuration changes to be made without having to stop and restart the server. See Section 12.5.3, “`SET` Syntax”.

- Improved replication code and features. See Chapter 6, Replication.

- Numerous new functions and options.

- Changes to existing code for enhanced performance and reliability.

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

### B.2.1. Changes in release 4.0.31 (Not yet released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.0 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. 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 http://www.mysql.com/products/enterprise.

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#321111, CVE-2007-5969)

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

### B.2.2. Changes in release 4.0.30 (12 February 2007)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.0 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. 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 http://www.mysql.com/products/enterprise.

Bugs fixed:

- Idle connections were not killed during timeout when using the Native POSIX Thread Library (NPTL) and mysqld. In the course of this fix, code to detect and handle the NPTL has been backported from 4.1 to 4.0. (Bug#16995)

### B.2.3. Changes in release 4.0.29 (Not released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.0 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. 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 http://www.mysql.com/products/enterprise.

Bugs fixed:

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

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

### B.2.4. Changes in release 4.0.28 (Not released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.0 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. 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 http://www.mysql.com/products/enterprise.

Functionality added or changed:

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

Bugs fixed:

- Deleting entries from a large `MyISAM` index could cause index corruption when it needed to shrink. Deletes from an index can happen when a record is deleted, when a key changes and must be moved, and when a key must be un-inserted because of a duplicate key. This can also happen in `REPAIR TABLE` when a duplicate key is found and in myisamchk when sorting the records by an index. (Bug#22384)

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

- A server or network failure with an open client connection would cause the client to hang even though the server was no longer available. (Bug#9678)

- mysqlhotcopy did not copy `RAID` directories with names that contained non-decimal hex digits. (It copied only directories containing the characters `0` through `9` and ignored those containing `a` through `f`.) (Bug#18777)

- Using `SELECT` and a table join while running a concurrent `INSERT` operation would join incorrect rows. (Bug#14400)

- A query with a `WHERE` clause containing ``column` = ELT(`int_value_1`, `value_list`) OR `column` = ELT(`int_value_2`, `value_list`)` could return unexpected results. (Bug#12728)

### B.2.5. Changes in release 4.0.27 (06 May 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a security fix release and bugfix release for the MySQL 4.0 release family.

This release includes the patches for recently reported security vulnerabilites in the MySQL client-server protocol. We would like to thank Stefano Di Paola `<stefano.dipaola@wisec.it>` for finding and reporting these to us.

Functionality added or changed:

- The `MySQL-server` RPM now explicitly assigns the `mysql` system user to the `mysql` user group during the postinstallation process. This corrects an issue with upgrading the server on some Linux distributions whereby a previously existing `mysql` user was not changed to the `mysql` group, resulting in wrong groups for files created following the installation. (Bug#12823)

- Better detection of connection timeout for replication servers on Windows allows elimination of extraneous `Lost connection` errors in the error log. (Bug#5588)

Bugs fixed:

- Security fix: A malicious client, using specially crafted invalid login or `COM_TABLE_DUMP` packets was able to read uninitialized memory, which potentially, though unlikely in MySQL, could have led to an information disclosure. (CVE-2006-1516, CVE-2006-1517) Thanks to Stefano Di Paola `<stefano.dipaola@wisec.it>` for finding and reporting this bug.

- `MySQL-shared-compat-4.0.26-0.i386.rpm` incorrectly depend on `glibc` 2.3 and cannot not be installed on a `glibc` 2.2 system. For MySQL 4.0, we recommend using the older `MySQL-shared-compat-4.0.25-0.i386.rpm` package. (Bug#16539)

- Running myisampack followed by myisamchk with the `--unpack` option would corrupt the `auto_increment` key. (Bug#12633)

- When myisamchk needed to rebuild a table, `AUTO_INCREMENT` information was lost. (Bug#10405)

- Avoid trying to include `<asm/atomic.h>` when it doesn't work in C++ code. (Bug#13621)

- `BIT_COUNT()` could return an incorrect value for right table columns in a `LEFT JOIN`. (Bug#13044)

- MySQL would not compile on Linux distributions that use the tinfo library. (Bug#18912)

- An `UPDATE` statement which tried to update a column with a name beginning with an asterisk would cause the server to crash. This was because the server would wrongly expand the `*` character to the list of all table columns, causing the list of columns to become longer than the list of values. Now the server performs this expansion only if the `*` character is followed by a space. (Bug#16510)

- An `INSERT ... SELECT` statement between tables in a `MERGE` set can return errors when statement involves insert into child table from merge table or vice-versa. (Bug#5390)

- Fixed problems with static variables to allow building on Fedora Core 3. (Bug#6554)

- A `LIMIT`-related optimization failed to take into account that `MyISAM` table indexes can be disabled, causing Error 124 when it tried to use such an index. (Bug#14616)

- For a table that had been opened with `HANDLER OPEN`, issuing `OPTIMIZE TABLE`, `ALTER TABLE`, or `REPAIR TABLE` caused a server crash. (Bug#14397)

- Queries of the form `(SELECT ...) ORDER BY ...` were being treated as a `UNION`. This improperly resulted in only distinct values being returned (because `UNION` by default eliminates duplicate results). Also, references to column aliases in `ORDER BY` clauses following parenthesized `SELECT` statements were not resolved properly. (Bug#7672)

- `SELECT DISTINCT` with a `GROUP BY` clause caused a server crash. (Bug#13855)

- `SHOW CREATE TABLE` did not display any `FOREIGN KEY` clauses if a temporary file could not be created. Now `SHOW CREATE TABLE` displays an error message in an SQL comment if this occurs. (Bug#13002)

- MySQL programs in binary distributions for Solaris 8/9/10 x86 systems would not run on Pentium III machines. (Bug#6772)

- Queries against a `MERGE` table that has a composite index could produce incorrect results. (Bug#9112)

- The counters for the `Key_read_requests`, `Key_reads`, `Key_write_requests`, and `Key_writes` status variables were changed from `unsigned long` to `unsigned longlong` to accommodate larger values before the variables roll over and restart from 0. (Bug#12920)

- A concurrency problem for `CREATE ... SELECT` could cause a server crash. (Bug#12845)

- On HP-UX 11.x (PA-RISC), the `-L` option caused mysqlimport to crash. (Bug#12958)

- The server crashed when one thread resized the query cache while another thread was using it. (Bug#12848)

### B.2.6. Changes in release 4.0.26 (08 September 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Added the `mysql_get_client_version()` C API function to the embedded server library. (It was present in the regular client library but inadvertently omitted from the embedded library.) (Bug#10266)

Bugs fixed:

- An optimizer estimate of zero rows for a non-empty `InnoDB` table used in a left or right join could cause incomplete rollback for the table. (Bug#12779)

- Query cache is switched off if a thread (connection) has tables locked. This prevents invalid results where the locking thread inserts values between a second thread connecting and selecting from the table. (Bug#12385)

- For PKG installs on Mac OS X, the preinstallation and postinstallation scripts were being run only for new installations and not for upgrade installations, resulting in an incomplete installation process. (Bug#11380)

- On Windows, applications that used the embedded server made it not possible to remove certain files in the data directory, even after the embedded server had been shut down. This occurred because a file descriptor was being held open. (Bug#12177)

- Creation of the `mysql` group account failed during the RPM installation. (Bug#12348)

- Attempting to repair a table having a fulltext index on a column containing words whose length exceeded 21 characters and where `myisam_repair_threads` was greater than 1 would crash the server. (Bug#11684)

- When two threads compete for the same table, a deadlock could occur if one thread has also a lock on another table through `LOCK TABLES` and the thread is attempting to remove the table in some manner and the other thread want locks on both tables. (Bug#10600)

### B.2.7. Changes in release 4.0.25 (05 July 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Security improvement: Applied a patch to fix a UDF library-loading vulnerability that could result in a buffer overflow and code execution. (CVE-2005-2558)

- Added `--with-big-tables` compilation option to configure. (Previously it was necessary to pass `-DBIG_TABLES` to the compiler manually in order to enable large table support.) See Section 2.9.2, “Typical configure Options”, for details.

Bugs fixed:

- On Mac OS X, `libmysqlclient_r.a` now is built with `--fno-common` to make it possible to link a shared two-level namespace library against `libmysqlclient_r.a`. (Bug#10638)

- An error in the implementation of the `MyISAM` compression algorithm caused `myisampack` to fail with very large sets of data (total size of all the records in a single column needed to be >= 3 GB in order to trigger this issue). (Bug#8321)

- A problem with the `my_global.h` file caused compilation of MySQL to fail on single-processor Linux systems running 2.6 kernels. (Bug#10364)

- Fixed a portability problem testing for `crypt()` support that caused compilation problems when using OpenSSL/yaSSL on HP-UX and Mac OS X. (Bug#10675, Bug#11150)

- `MyISAM` table corruption could occur with `ANALYZE TABLE` if a write lock was acquired with `LOCK TABLES` and then an `INSERT` or `DELETE` was done prior to analyzing the table. (Bug#10901)

- Fixed a server crash resulting from `CREATE TABLE ... SELECT` that selected from a table being altered by `ALTER TABLE`. (Bug#10224)

- `InnoDB`: In `DROP DATABASE`, check for all referencing tables from other databases before dropping any tables. (Bug#10335)

- Fixed a problem with incorrect constant propagation resulting in incorrect evaluation of `AND/OR` queries. (Bug#10095)

- Fixed wrong buffer usage for auto-increment key with blob part that caused `CHECK TABLE` to report that the table was wrong. (Bug#10045)

- No error was raised for `BOOLEAN` full-text searches for storage engines that do not support full-text. (Bug#7709)

- The test in configure to see whether `CXX` specified gcc failed if gcc was specified as a full pathname. (Bug#9690)

- In the `mysql_real_escape_string()` C API function, when a multi-byte character is encountered that is illegal in the current character set, escape only the first byte, not each byte. This avoids creating a valid character from an invalid one. (Bug#9864; this is a backport of Bug#8378 from MySQL 4.1.11 to 4.0.25)

- Fixed a deadlock resulting from use of `FLUSH TABLES WITH READ LOCK` while an `INSERT DELAYED` statement is in progress. (Bug#7823)

- Fixed a segmentation fault in mysqlcheck that occurred when the last table checked in `--auto-repair` mode returned an error (such as the table being a `MERGE` table). (Bug#9492)

- Fixed faulty display of `TIMESTAMP` columns retrieved as ``col_name`+0` while the `new` system variable is set to 1. (Bug#8894)

- Queries containing `CURRENT_USER()` incorrectly were registered in the query cache. (Bug#9796)

- An `UPDATE` that updated only some of the columns in a multiple-column index could result in a loop. (Bug#8942)

- `REPAIR TABLE` did not invalidate query results in the query cache that were generated from the table. (Bug#8480)

- Fixed a bug that caused concurrent inserts to be allowed into the tables in the `SELECT ... UNION ...` part of `INSERT ... SELECT ... UNION ...`. This could result in the incorrect order of queries in the binary log. (Bug#9922)

- Fixed a bug that under certain circumstances could allow a privilege escalation via database wildcards in `GRANT`. (Bug#3924, CVE-2004-0957)

- `<=>` was not properly comparing `NULL` values in the `WHERE` clause of outer joins. (Bug#8711)

- InnoDB: Fixed a bug: MySQL-4.0.23 and 4.0.24 could complain that an InnoDB table created with MySQL-3.23.49 or earlier was in the new compact InnoDB table format of 5.0.3 or later, and InnoDB would refuse to use that table. (The same bug exists in 4.1.8 - 4.1.10.) There is nothing wrong with the table, it is mysqld that is in error. Workaround: wait that 4.0.25 or 4.1.11 is released before doing an upgrade, or dump the table and re-create it with any MySQL version >= 3.23.50 before upgrading to 4.0.23 or 4.0.24.

### B.2.8. Changes in release 4.0.24 (04 March 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Security improvement: The server creates `.frm`, `.MYD`, `.MYI`, `.MRG`, `.ISD`, and `.ISM` table files only if a file with the same name does not already exist. Thanks to Stefano Di Paola `<stefano.dipaola@wisec.it>` for finding and informing us about this issue. (CVE-2005-0711)

- Security improvement: User-defined functions should have at least one symbol defined in addition to the `xxx` symbol that corresponds to the main `xxx()` function. These auxiliary symbols correspond to the `xxx_init()`, `xxx_deinit()`, `xxx_reset()`, `xxx_clear()`, and `xxx_add()` functions. mysqld by default no longer loads UDFs unless they have at least one auxiliary symbol defined in addition to the main symbol. The `--allow-suspicious-udfs` option controls whether UDFs that have only an `xxx` symbol can be loaded. By default, the option is off. mysqld also checks UDF filenames when it reads them from the `mysql.func` table and rejects those that contain directory pathname separator characters. (It already checked names as given in `CREATE FUNCTION` statements.) See Section 19.2.4.1, “UDF Calling Sequences for Simple Functions”, Section 19.2.4.2, “UDF Calling Sequences for Aggregate Functions”, and Section 19.2.4.6, “User-Defined Function Security Precautions”. Thanks to Stefano Di Paola `<stefano.dipaola@wisec.it>` for finding and informing us about this issue. (CVE-2005-0709, CVE-2005-0710)

- `InnoDB`: Added configuration option and settable global variable `innodb_autoextend_increment` for setting the size in megabytes by which `InnoDB` tablespaces are extended when they become full. The default value is 8, corresponding to the fixed increment of 8MB in previous versions of MySQL.

- InnoDB: Do not acquire an internal `InnoDB` table lock in `LOCK TABLES` if `AUTOCOMMIT=1`. This helps in porting old `MyISAM` applications to `InnoDB`. `InnoDB` table locks in that case caused deadlocks very easily.

Bugs fixed:

- `AES_DECRYPT(`col_name`,`key`)` could fail to return `NULL` for invalid values in `col_name`, if `col_name` was declared as `NOT NULL`. (Bug#8669)

- `FOUND_ROWS()` returned an incorrect value after a `SELECT SQL_CALC_FOUND_ROWS DISTINCT` statement that selected constants and included `GROUP BY` and `LIMIT` clauses. (Bug#7945)

- Index cardinality was not being updated properly for `TEMPORARY` tables under some circumstances, such as `CREATE TABLE ... SELECT` followed by `ANALYZE TABLE`. (Bug#7519)

- Fixed a server crash caused by `DELETE FROM `tbl_name` ... WHERE ... ORDER BY `tbl_name`.`col_name`` when the `ORDER BY` column was qualified with the table name. (Bug#8392)

- Fixed a bug in `MATCH ... AGAINST` in natural language mode that could cause a server crash if the `FULLTEXT` index was not used in a join (`EXPLAIN` did not show `fulltext` join mode) and the search query matched no rows in the table (Bug#8522).

- Platform and architecture information in version information produced for `--version` option on Windows was always `Win95/Win98 (i32)`. More accurately determine platform as `Win32` or `Win64` for 32-bit or 64-bit Windows, and architecture as `ia32` for x86, `ia64` for Itanium, and `axp` for Alpha. (Bug#4445)

- Fixed an optimization problem that allowed a negative number to be stored in a `DOUBLE UNSIGNED` column when it was assigned a value from a signed `DOUBLE` column. (Bug#7700)

- Fixed a failure of multiple-table updates to replicate properly on slave servers when `--replicate-*-table` options had been specified. (Bug#7011)

- Renamed `set_bit()` and `clear_bit()` functions in source code to avoid a conflict with functions of the same names in Linux kernel header files. (Bug#7971)

- Part of the information being used to cache access-permission lookups was not always reinitialized properly, particularly for connections from localhost on Windows. The result was connection failures that appeared to occur randomly. (Bug#5569)

- Corrected a problem with the `QUOTE()` function returning bad results. (Bug#8248)

- Fixed a problem where `INSERT INTO ...SELECT` failed when the source and target table were the same. (Bug#6034)

- Fixed a problem where RPM installation on Linux as a non-privileged user would result in incomplete installation. (Bug#7347)

- Change thread stack size used for building Linux RPM distributions to avoid warnings about stack size during server startup. (Bug#6226)

- Fixed a symlink vulnerability in the mysqlaccess script. Reported by Javier Fernandez-Sanguino Pena and Debian Security Audit Team. (CVE-2005-0004)

- Fixed support for C API function `mysql_list_fields()`, which was accidentally broken in 4.0.22 (Bug#6761)

- Make `query_cache_wlock_invalidate` system variable visible in `SHOW VARIABLES` output. (Bug#7594)

- Fixed a bug which caused `FROM_UNIXTIME()` function to return `NULL` for zero argument instead of the Epoch. (Bug#7515)

- Now in datetime values two digit year is interpreted as year in 20th or 21st century even with zero month and day. (Bug#7297)

- Fixed a bug in `QUOTE` function when used in conjunction with some other string functions. This lead to severe buffer overflow and server crashing. (Bug#7495)

- InnoDB: Work around a problem in AIX 5.1 patched with ML7 security patch: InnoDB would refuse to open its `ibdata` files, complaining about an operating system error 0.

- InnoDB: Fixed a memory corruption bug if one created a table with a primary key that contained at least two column prefixes. An example: `CREATE TABLE t(a char(100), b tinyblob, PRIMARY KEY(a(5), b(10)))`.

- InnoDB: Use native `tmpfile()` function on Netware. All InnoDB temporary files are created under `sys:\tmp`. Previously, InnoDB temporary files were never deleted on Netware.

- `InnoDB`: Honor the `--tmpdir` startup option when creating temporary files. Previously, `InnoDB` temporary files were always created in the temporary directory of the operating system. On Netware, `InnoDB` will continue to ignore `--tmpdir`. (Bug#5822)

- InnoDB: Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs `INSERT ... SELECT ...` (binlog not enabled), or a multiple-table `UPDATE` or `DELETE`, and only the read tables are InnoDB type, the rest are `MyISAM`; this also fixes Bug#7879 for InnoDB type tables. (Bug#7879)

- InnoDB: Fixed a bug: 32-bit mysqld binaries built on HP-UX-11 did not work with `InnoDB` files greater than 2 GB in size. (Bug#6189)

- InnoDB: Fixed a bug: InnoDB failed to drop a table in the background drop queue if the table was referenced by a foreign key constraint.

- InnoDB: Fixed a bug: if we dropped a table where an `INSERT` was waiting for a lock to check a `FOREIGN KEY` constraint, then an assertion would fail in `lock_reset_all_on_table()`, since that operation assumes no waiting locks on the table or its records.

- Fixed that, when encountering a “disk full” or “quota exceeded” write error, `MyISAM` sometimes didn't sleep and retry the write, thus resulting in a corrupted table. (Bug#7714)

- Fixed that a slave could crash after replicating many `ANALYZE TABLE`, `OPTIMIZE TABLE`, or `REPAIR TABLE` statements from the master. (Bug#6461, Bug#7658)

- Fixed a bug where MySQL was allowing concurrent updates (inserts, deletes) to a table if binary logging is enabled. Changed to ensure that all updates are executed in a serialized fashion, because they are executed serialized when binlog is replayed. (Bug#7879)

- Fixed a bug in replication that caused the master to stamp generated statements (such as `SET` commands) with an `error_code` intended only for another statement. This could happen, for example, when a statements generates a duplicate key error on the master but must be replicated. (Bug#8412)

- Documented problem with using `mysqldump` in 4.0.x to dump `TIMESTAMP(2)` and `TIMESTAMP(4)` data types. (Bug#6530)

### B.2.9. Changes in release 4.0.23 (18 December 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

### Note

Due to a libtool-related bug in the source distribution, the creation of shared `libmysqlclient` libraries was not possible (the resulting files were missing the `.so` file name extension). The file `ltmain.sh` was updated to fix this problem and the resulting source distribution was released as `mysql-4.0.23a.tar.gz`. This modification did not affect the binary packages. (Bug#7401)

Functionality added or changed:

- Added `--hex-blob` option to mysqldump for dumping binary string columns using hexadecimal notation.

- Added `mysql_hex_string()` C API function that hex-encodes a string.

- InnoDB: Do not periodically write `SHOW INNODB STATUS` information to a temporary file unless the configuration option `innodb_status_file=1` is set.

- InnoDB: Made the foreign key parser better aware of quotes. (Bug#6340)

- `mysqlbinlog` now prints an informative commented line (thread id, timestamp, server id, and so forth) before each `LOAD DATA INFILE`, like it does for other queries; unless `--short-form` is used.

Bugs fixed:

- A multiple-table `DELETE` could cause MySQL to crash when using `InnoDB` tables. (Bug#5837, Bug#6378)

- Corrected accounts in the `mysql.user` table in Windows distributions that had been created with a `Host` value of `build` rather than `%`. (Bug#6000)

- Prevent adding `CREATE TABLE .. SELECT` query to the binary log when the insertion of new records partially failed. (Bug#6682)

- Fixed bug which caused `FROM_UNIXTIME()` function to return wrong result if the argument was too big. (Bug#6439)

- Fixed bug which caused MySQL server to store wrong values in `TIMESTAMP` columns and give wrong results for `UNIX_TIMESTAMP()` function if it was run in time zone with leap seconds. (Bug#6387)

- InnoDB: Fixed a bug in `LOAD DATA INFILE…REPLACE` printing duplicate key error when executing the same load query several times. (Bug#5835)

- InnoDB: Refuse to open new-style tables created with MySQL 5.0.3 or later. (Bug#7089)

- InnoDB: Do not call `rewind()` when displaying `SHOW INNODB STATUS` information on `stderr`.

- InnoDB: If one used `INSERT IGNORE` to insert several rows at a time, and the first inserts were ignored because of a duplicate key collision, then InnoDB in a replication slave assigned `AUTO_INCREMENT` values 1 bigger than in the master. This broke the MySQL replication. (Bug#6287)

- InnoDB: Fix two hangs: `FOREIGN KEY` constraints treated table and database names as case-insensitive. `RENAME TABLE t TO T` would hang in an endless loop if `t` had a foreign key constraint defined on it. Fix also a hang over the dictionary mutex that would occur if one tried in `ALTER TABLE` or `RENAME TABLE` to create a foreign key constraint name that collided with another existing name. (Bug#3478)

- InnoDB: Treat character `0xA0` as space in InnoDB's `FOREIGN KEY` parser if MySQL treats it as space in the default charset. EMS MySQL Manager inserts character `0xA0` after the table name in an `ALTER`, which confused InnoDB's parser.

- Fixed a bug which caused a crash when only the slave I/O thread was stopped and restarted. (Bug#6148)

- If a connection had an open transaction but had done no updates to transactional tables (for example if had just done a `SELECT FOR UPDATE` then executed a non-transactional update, that update automatically committed the transaction (thus releasing InnoDB's row-level locks etc). (Bug#5714)

- If a connection was interrupted by a network error and did a rollback, the network error code got stored into the `BEGIN` and `ROLLBACK` binary log events; that caused superfluous slave stops. (Bug#6522)

- A sequence of `BEGIN` (or `SET AUTOCOMMIT=0`), `FLUSH TABLES WITH READ LOCK`, transactional update, `COMMIT`, `FLUSH TABLES WITH READ LOCK` could hang the connection forever and possibly the MySQL server itself. This happened for example when running the `innobackup` script several times. (Bug#6732)

### B.2.10. Changes in release 4.0.22 (27 October 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- The `--with-openssl` option for configure now accepts a path prefix as an argument. `--with-openssl-includes` and `--with-openssl-libs` are still supported, but are needed only to override the default values. (Bug#5494)

- Added new `--without-man` option to configure to suppress building/installing the manual pages. (Bug#5379)

- InnoDB: New mysqld option `--innodb-table-locks` and session variable `innodb_table_locks` (on by default). In applications using `AUTOCOMMIT=1` and MySQL's `LOCK TABLES` command, InnoDB's internal table locks that were added in 4.0.20 can cause deadlocks. You can set `innodb_table_locks=0` in `my.cnf` to remove that problem. See Section 13.2.17, “Restrictions on `InnoDB` Tables”. (Bug#3299, Bug#5998)

- InnoDB: Added the startup option and settable global variable `innodb_max_purge_lag` for delaying `INSERT`, `UPDATE` and `DELETE` operations when the purge operations are lagging. The default value of this parameter is zero, meaning that there are no delays. See Section 13.2.13, “Implementation of Multi-Versioning”.

- InnoDB: Change error code to `HA_ERR_ROW_IS_REFERENCED` if we cannot `DROP` a parent table because it is referenced by a `FOREIGN KEY` constraint.

Bugs fixed:

- Fixed bug in server which caused connection stall when one of deprecated `libmysqlclient` functions `mysql_create_db()` and `mysql_rm_db()` were called and were going to return error. (Bug#6081)

- Fixed returning wrong query result from query cache if a temporary table was hiding a real table after putting results to query cache. (Bug#6084)

- Fixed `ENABLE KEYS`, which failed if `tmpdir` ran out of space. Now, a full repair is done in this case. (Bug#5625)

- Fixed an improper error message when trying to drop a table which is referenced by a `FOREIGN KEY` constraint. (Bug#5784)

- Fixed a bug that allowed `FLUSH TABLE(S)` to close `HANDLER` tables. `HANDLER` tables are now reopened after a `FLUSH TABLE(S)` the next time they are used. However, they lose their file position if this happens. (Bug#4286)

- Fixed a bug that allowed `HANDLER` tables with the same alias to be opened multiple times. `HANDLER` aliases must now be unique, even though it is syntactically correct in versions below 4.1 to qualify them with their base table's database name (for example, `test_db.handler_tbl` now conflicts with `another_db.handler_tbl`). (Bug#4335)

- Fixed crash when using MySQL 4.0 with privilege tables from MySQL 5.0.

- mysqlimport now reads input files locally from the client host only if the `--local` option is given. Previously, it assumed incorrectly in some cases that files were local even without `--local`. (Bug#5829)

- InnoDB: Make the check for excessive semaphore waits to tolerate glitches in the system clock (do not crash the server if the system time is adjusted while InnoDB is under load.). (Bug#5898)

- InnoDB: Fixed a bug in the InnoDB `FOREIGN KEY` parser that prevented `ALTER TABLE` of tables containing “`#`” in their names. (Bug#5856)

- InnoDB: Fixed problem introduced in 4.0.21 where a connection starting a transaction, doing updates, then `FLUSH TABLES WITH READ LOCK`, then `COMMIT`, would cause replication slaves to stop (complaining about error 1223). Bug surfaced when using the InnoDB `innobackup` script. (Bug#5949)

- InnoDB: If one updated a column so that its size changed, or updated it to an externally stored (`TEXT` or `BLOB`) value, then ANOTHER externally stored column would show up as 512 bytes of good data + 20 bytes of garbage in a consistent read that fetched the old version of the row. (Bug#5960)

- InnoDB: Release the dictionary latch during a long cascaded `FOREIGN KEY` operation, so that we do not starve other users doing `CREATE TABLE` or other DDL operations. This caused a notorious 'Long semaphore wait' message to be printed to the `.err` log. (Bug#5961)

- InnoDB: Let InnoDB remember row locking type (X or S) inside `LOCK TABLES`, also over plain consistent read `SELECT`s.

- InnoDB: Fixed a bug introduced in 4.0.21. An assertion failed if one used mysqldump with the option `-l` or `--opt`, or if one used `LOCK TABLES ... LOCAL`. (Workaround in 4.0.21: use `--quick` and `--single-transaction`. (Bug#5538)

- InnoDB: Having a column prefix index in the primary key, and the same column fully in a secondary key could cause an assertion failure in row_build_row_ref(). (Bug#5180)

- Fixed a bug which resulted in an erroneously calculated number of examined rows in `UNION`s. This value is printed in the slow query log. (Bug#5879)

- Fixed bug with crash of server on some values of `read_rnd_buffer_size` (Bug#5492)

- Fixed bug which caused truncation of values read from or into `TIMESTAMP` fields if `--new` mode was enabled. (Bug#4131)

- mysqladmin now returns a status of 0 even when the server denies access; such an error means the server is running. (Bug#3120)

- Fixed that if the slave SQL thread found a syntax error in a query (which should be rare, as the master parsed it successfully), it stops. (Bug#5711)

- Fixed that if a write to a `MyISAM` table fails because of a full disk or an exceeded disk quota, it prints a message to the error log every 10 minutes, and waits until disk becomes free. (Bug#3248)

- Fixed problem with symlinked databases on Windows being shown with `SHOW DATABASES` even if the database name doesn't match the given wildcard (Bug#5539)

### B.2.11. Changes in release 4.0.21 (06 September 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Print `version_comment` (from `./configure --comment` during compilation) when starting the server. Example: `Version: '4.0.21-debug' socket: '/tmp/mysql.sock' port: 0 Official MySQL Binary`

- Made the MySQL server not react to signals `SIGHUP` and `SIGQUIT` on Mac OS X 10.3. This is needed because under this OS, the MySQL server receives lots of these signals (reported as Bug#2030).

- On Windows, the mysqld-nt and mysqld-max-nt servers now write error messages to the Windows event log in addition to the MySQL error log.

Bugs fixed:

- Fixed an old bug in concurrent accesses to `MERGE` tables (even one `MERGE` table and `MyISAM` tables), that could've resulted in a crash or hang of the server. (Bug#2408, CVE-2004-0837)

- Fixed a bug that caused incorrect results from `GROUP BY` queries with expression in `HAVING` clause that refers to a columns such as `BLOB`, `TEXT`, or `TINYBLOB`. (Bug#4358)

- Fixed a bug when memory was not released when `HEAP` table is dropped. It could only happen on Windows when a symlink file (.sym) is used and if that symlink file contained double backslashes (\\). (Bug#4973)

- Fixed a bug which prevented `TIMESTAMP(19)` fields from being created. (Bug#4491)

- Fixed a bug that caused wrong results in queries that were using index to search for `NULL` values in `BLOB` (`TINYBLOB`, `TEXT`, `TINYTEXT`, etc) columns of `MyISAM` tables. (Bug#4816)

- Fixed a bug in the function `ROUND()` reporting incorrect metadata (number of digits after the decimal point). It can be seen, for example, in `CREATE TABLE t1 SELECT ROUND(1, 34)`. (Bug#4393)

- Fixed precision loss bug in some mathematical functions such as `SQRT()` and `LOG()`. (Bug#4356)

- Fixed a long-standing problem with `LOAD DATA` with the `LOCAL` option. The problem occurs when an error happens during the `LOAD DATA` operation. Previously, the connection was broken. Now the error message is returned and connection stays open.

- Optimizer now treats `col IN (val)` the same way it does for `col = val`.

- Fixed a problem with `net_buffer_length` when building the `DBD::mysql` Perl module. (Bug#4206)

- `lower_case_table_names=2` (keep case for table names) was not honored with `ALTER TABLE` and `CREATE/DROP INDEX`. (Bug#3109)

- Fixed a crash on declaration of `DECIMAL(0,...)` column. (Bug#4046)

- Fixed a bug in `IF()` function incorrectly determining the result type if aggregate functions were involved. (Bug#3987)

- Fixed bug in privilege checking where, under some conditions, one was able to grant privileges on the database, he has no privileges on. (Bug#3933)

- Fixed crash in `MATCH ... AGAINST()` on a phrase search operator with a missing closing double quote. (Bug#3870, CVE-2004-0956)

- Fixed a bug with truncation of big values (> 4294967295) of 64-bit system variables. (Bug#3754)

- If `server-id` was not set using startup options but with `SET GLOBAL`, the replication slave still complained that it was not set. (Bug#3829)

- Fixed potential memory overrun in `mysql_real_connect()` (which required a compromised DNS server and certain operating systems). (Bug#4017, CVE-2004-0836)

- During the installation process of the server RPM on Linux, mysqld was run as the `root` system user, and if you had `--log-bin=`somewhere_out_of_var_lib_mysql`` it created binary log files owned by `root` in this directory, which remained owned by `root` after the installation. This is now fixed by starting mysqld as the `mysql` system user instead. (Bug#4038)

- Made `DROP DATABASE` honor the value of `lower_case_table_names`. (Bug#4066)

- The slave SQL thread refused to replicate `INSERT ... SELECT` if it examined more than 4 billion rows. (Bug#3871)

- Fixed incorrect destruction of expression which led to crash of server on complex `AND`/`OR` expressions if query was ignored (either by a replication server because of `--replicate-*-table` rules, or by any MySQL server because of a syntax error). (Bug#3969, Bug#4494)

- Fixed that mysqlbinlog --position --read-from-remote-server had wrong `# at` lines. (Bug#4506)

- If `CREATE TEMPORARY TABLE t SELECT` failed while loading the data, the temporary table was not dropped. (Bug#4551)

- Fixed that when a multiple-table `DROP TABLE` failed to drop a table on the master server, the error code was not written to the binary log. (Bug#4553)

- When the slave SQL thread was replicating a `LOAD DATA INFILE` statement, it didn't show the statement in the output of `SHOW PROCESSLIST`. (Bug#4326)

- Fixed that `CREATE TABLE ... TYPE=HEAP ... AS SELECT...` caused replication slave to stop. (Bug#4971)

- Fixed that `disable-local-infile` option had no effect if client read it from a configuration file using `mysql_options(...,MYSQL_READ_DEFAULT,...)`. (Bug#5073)

- Fixed that mysql-test-run failed on the `rpl_trunc_binlog` test if running test from the installed (the target of 'make install') directory. (Bug#5050)

- Fixed an unlikely deadlock which could happen when using `KILL`. (Bug#4810)

- Fixed a crash when one connection got `KILL`ed while it was doing `START SLAVE`. (Bug#4827)

- Made `FLUSH TABLES WITH READ LOCK` block `COMMIT` if server is running with binary logging; this ensures that the binary log position is trustable when doing a full backup of tables and the binary log. (Bug#4953)

- Fixed that the counter of an `auto_increment` column was not reset by `TRUNCATE TABLE` is the table was a temporary one. (Bug#5033)

- Made database names to compare case-insensitively in fully qualified column names (`database.table.column`) when `lower_case_table_names=1`. (Bug#4792)

- Fixed that `SET CHARACTER SET` was not replicated correctly. MySQL 4.1 does not have that bug. (Bug#4500)

- Fixed a symlink vulnerability in the `mysqlhotcopy` script. (CVE-2004-0457)

### B.2.12. Changes in release 4.0.20 (17 May 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

### Note

The windows packages had to be repackaged and re-released several times to resolve packaging issues (such as missing files). This did not affect the binaries included (they have not been recompiled), therefore the installation packages are of version 4.0.20d, while the binaries included still identify themselves as version 4.0.20b.

Functionality added or changed:

- From the Windows distribution, predefined accounts without passwords for remote users ("root@%", "@%") were removed (other distributions never had them).

- Phrase search in `MATCH ... AGAINST ( ... IN BOOLEAN MODE)` no longer matches partial words.

Bugs fixed:

- A crashing bug (race condition) was fixed in InnoDB diagnostic logging. It was introduced in 4.0.19. (Bug#3596)

- Fixed a bug in division `/` reporting incorrect metadata (number of digits after the decimal point). It can be seen, for example, in `CREATE TABLE t1 SELECT "0.01"/"3"`. (Bug#3612)

- Fixed a problem with non-working `DROP DATABASE` on some configurations (in particular, Linux 2.6.5 with ext3 are known to expose this bug). (Bug#3594)

- Fixed that in some replication error messages, a very long query caused the rest of the message to be invisible (truncated), by putting the query last in the message. (Bug#3357)

### B.2.13. Changes in release 4.0.19 (04 May 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

### Note

The MySQL 4.0.19 binaries were uploaded to the download mirrors on May, 10th. However, a potential crashing bug was found just before the 4.0.19 release was publicly announced and published from the 4.0 download pages at http://dev.mysql.com/.

A fix for the bug was pushed into the MySQL source tree shortly after it could be reproduced and is included in MySQL 4.0.20. Users upgrading from MySQL 4.0.18 should upgrade directly to MySQL 4.0.20 or later.

See (Bug#3596) for details (it was reported against MySQL-4.1, but was confirmed to affect 4.0.19 as well).

Functionality added or changed:

- If length of a timestamp field is defined as 19, the timestamp is displayed as `"YYYY-MM-DD HH:MM:SS`. This is done to make it easier to use tables created in MySQL 4.1 to be used in MySQL 4.0.

- If you use `RAID_CHUNKS` with a value > 255 it is set to 255. This was made to ensure that all raid directories are always 2 hex bytes. (Bug#3182)

- Changed that the optimizer now considers the index specified in `FORCE INDEX` clause as a candidate to resolve `ORDER BY` as well.

- The `--log-warnings` server option now is enabled by default. Disable with `--skip-log-warnings`.

- Until now, in `SELECT ... UNION SELECT ... ORDER BY ...`, it was possible to qualify a column name in the `ORDER BY` clause with a table name. This is no longer possible. Column names in `ORDER BY` should refer to names established in the first `SELECT` of the `UNION`. (Bug#3064)

- Added `max_insert_delayed_threads` system variable as a synonym for `max_delayed_threads`.

- Added `query_cache_wlock_invalidate` system variable. It allows emulation of `MyISAM` table write-locking behavior, even for queries in the query cache. (Bug#2693)

- The keyword `MASTER_SERVER_ID` is not reserved anymore.

- The following is relevant mainly for Mac OS X users who use a case-insensitive filesystem. This is not relevant for Windows users as `InnoDB` in this case always stores filenames in lower case:

  You can now force `lower_case_table_names` to 0 from the command line or a configuration file. This is useful with case-insensitive filesystems when you have previously not used `lower_case_table_names=1` or `lower_case_table_names=2` and you have created `InnoDB` tables. With `lower_case_table_names=0`, `InnoDB` tables were stored in mixed case while setting lower_case_table_names to a non-zero value now forces it to lower case (to make the table names case insensitive).

  Because it's possible to crash `MyISAM` tables by referring to them with different case on a case-insensitive filesystem, we recommend that you use `lower_case_table_names` or `lower_case_table_names=2` on such filesystems.

  The easiest way to convert to use `lower_case_table_names=2` is to dump all your `InnoDB` tables with mysqldump, drop them and then restore them.

- Changed that the relay log is flushed to disk by the slave I/O thread every time it reads a relay log event. This reduces the risk of losing some part of the relay log in case of brutal crash.

- When a session having open temporary tables terminates, the statement automatically written to the binary log is now `DROP TEMPORARY TABLE IF EXISTS` instead of `DROP TEMPORARY TABLE`, for more robustness.

- Added option `--replicate-same-server-id`.

Bugs fixed:

- Added missing full-text variable `ft_stopword_file` to myisamchk.

- Don't allow stray `','` at the end of field specifications. (Bug#3481)

- `INTERVAL` now can handle big values for seconds, minutes and hours. (Bug#3498)

- Blank hostname did not work as documented for table and column privileges. Now it's works the same way as `'%'`. (Bug#3473)

- Fixed a harmless buffer overflow in `replace` utility. (Bug#3541)

- Fixed `SOUNDEX()` to ignore non-alphabetic characters also in the beginning of the string. (Bug#3556)

- Fixed a bug in `MATCH ... AGAINST()` searches when another thread was doing concurrent inserts into the `MyISAM` table in question. The first --- full-text search --- query could return incorrect results in this case (for example, “phantom” rows or not all matching rows, even an empty result set). The easiest way to check whether you are affected is to start mysqld with `--skip-concurrent-insert` switch and see whether it helps.

- Fixed bug when doing `DROP DATABASE` on a directory containing non- MySQL files. Now a proper error message is returned.

- Fixed bug in `ANALYZE TABLE` on a `BDB` table inside a transaction that hangs server thread. (Bug#2342)

- Fixed a symlink vulnerability in the `mysqlbug` script. (Bug#3284, CVE-2004-0381)

- Fixed core dump bug in `SELECT DISTINCT` where all selected parts where constants and there were hidden columns in the created temporary table. (Bug#3203)

- Fixed core dump bug in `COUNT(DISTINCT)` when there was a lot of values and one had a big value for `max_heap_table_size`.

- Fixed problem with multiple-table-update and BDB tables. (Bug: #3098)

- Fixed memory leak when dropping database with `RAID` tables. (Bug#2882)

- Fixed core dump crash in replication during relay-log switch when the relay log went over `max_relay_log_size` and the slave thread did a `flush_io_cache()` at the same time.

- Fixed hangup bug when issuing multiple `SLAVE START` from different threads at the same time. (Bug#2921)

- Fixed bug when using `DROP DATABASE` with `lower_case_table_names=2`.

- Fixed wrong result in `UNION` when using `lower_case_table_names=2`. (Bug#2858)

- One can now kill threads that is 'stuck' in the join optimizer (can happen when there is MANY tables in the join in which case the optimizer can take really long time). (Bug#2825)

- Rollback `DELETE` and `UPDATE` statements if thread is killed. (Bug#2422)

- Ensure that all rows in an `INSERT DELAYED` statement is written at once if binary logging is enabled. (Bug#2491).

- Fixed bug in query cache statistic, more accurate formula linked statistic variables mentioned in the manual.

- Fixed a bug in parallel repair (myisamchk -p, `myisam_repair_threads`) - sometimes repair process failed to repair a table. (Bug#1334)

- Fixed bugs with names of tables, databases, and columns that end to space (Bug#2985)

- Fixed a bug in multiple-table `UPDATE` statements involving at least one constant table. Bug was exhibited in allowing non matching row to be updated. (Bug#2996).

- Fixed all bugs in scripts for creating/upgrading system database (Bug#2874) Added tests which guarantee against such bugs in the future.

- Fixed bug in `mysql` command-line client in interpreting quotes within comments. (Bug#539)

- `--set-character-set` and `--character-sets-dir` options in myisamchk now work.

- Fixed a bug in mysqlbinlog that caused one pointer to be free'd twice in some cases.

- Fixed a bug in boolean full-text search, that sometimes could lead to false matches in queries with several levels of subexpressions using `+` operator (for example, `MATCH ... AGAINST('+(+(word1 word2)) +word3*' IN BOOLEAN MODE)`.

- Fixed Windows-specific portability bugs in `myisam_ftdump`.

- Fixed a bug in multiple-table `DELETE` that was caused by foreign key constraints. If the order of the tables established by MySQL optimizer did not match parent-child order, no rows were deleted and no error message was provided. (Bug#2799)

- Fixed a few years old bug in the range optimizer that caused a segmentation fault on some very rare queries. (Bug#2698)

- Replication: If a client connects to a slave server and issues an administrative statement for a table (for example, `OPTIMIZE TABLE` or `REPAIR TABLE`), this could sometimes stop the slave SQL thread. This does not lead to any corruption, but you must use `START SLAVE` to get replication going again. (Bug#1858) The bug was accidentally not fixed in 4.0.17 as it was unfortunately earlier said.

- Fixed that when a `Rotate` event is found by the slave SQL thread in the middle of a transaction, the value of `Relay_Log_Pos` in `SHOW SLAVE STATUS` remains correct. (Bug#3017)

- Corrected the master's binary log position that `InnoDB` reports when it is doing a crash recovery on a slave server. (Bug#3015)

- Changed that when a `DROP TEMPORARY TABLE` statement is automatically written to the binary log when a session ends, the statement is recorded with an error code of value zero (this ensures that killing a `SELECT` on the master does not result in a superfluous error on the slave). (Bug#3063)

- Changed that when a thread handling `INSERT DELAYED` (also known as a `delayed_insert` thread) is killed, its statements are recorded with an error code of value zero (killing such a thread does not endanger replication, so we thus avoid a superfluous error on the slave). (Bug#3081)

- Fixed deadlock when two `START SLAVE` commands were run at the same time. (Bug#2921)

- Fixed that a statement never triggers a superfluous error on the slave, if it must be excluded given the `--replicate-*` options. The bug was that if the statement had been killed on the master, the slave would stop. (Bug#2983)

- The `--local-load` option of mysqlbinlog now requires an argument.

- Fixed a segmentation fault when running `LOAD DATA FROM MASTER` after `RESET SLAVE`. (Bug#2922)

- Fixed a rare error condition that caused the slave SQL thread spuriously to print the message `Binlog has bad magic number` and stop when it was not necessary to do so. (Bug#3401)

- Fixed bug in privilege checking of `ALTER TABLE RENAME`. (Bug#3270, CVE-2004-0835)

- Fixed the column `Exec_master_log_pos` (and its disk image in the `relay-log.info` file) to be correct if the master had version 3.23 (it was too big by 6 bytes). This bug does not exist in the 5.0 version. (Bug#3400)

- Fixed that mysqlbinlog does not forget to print a `USE` command under rare circumstances where the binary log contained a `LOAD DATA INFILE` command. (Bug#3415)

- Fixed a memory corruption when replicating a `LOAD DATA INFILE` when the master had version 3.23. Some smaller problems remain in this setup, See Section 6.7, “Replication Features and Known Problems”. (Bug#3422)

- Multiple-table `DELETE` statements were always replicated by the slave if there were some `--replicate-*-ignore-table` options and no `--replicate-*-do-table` options. (Bug#3461)

- Fixed a crash of the MySQL slave server when it was built with `--with-debug` and replicating itself. (Bug#3568)

### B.2.14. Changes in release 4.0.18 (12 February 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Fixed processing of `LOAD DATA` by mysqlbinlog in remote mode. (Bug#1378)

- The ft_dump utility program was renamed to myisam_ftdump, and is included in binary distributions.

- `ENGINE` is now a synonym for the `TYPE` option for `CREATE TABLE` and `ALTER TABLE`.

- `lower_case_table_names` system variable now can take a value of `2`, to store table names in mixed case on case-insensitive filesystems. It's forced to 2 if the database directory is located on a case-insensitive filesystem.

- For replication of `MEMORY` (`HEAP`) tables: Made the master automatically write a `DELETE FROM` statement to its binary log when a `MEMORY` table is opened for the first time since master's startup. This is for the case where the slave has replicated a non-empty `MEMORY` table, then the master is shut down and restarted: the table is now empty on master; the `DELETE FROM` empties it on slave too. Note that even with this fix, between the master's restart and the first use of the table on master, the slave still has out-of-date data in the table. But if you use the `init-file` option to populate the `MEMORY` table on the master at startup, it ensures that the failing time interval is zero. (Bug#2477)

- Optimizer is now better tuned for the case where the first used key part (of many) is a constant. (Bug#1679)

- Removed old non-working `--old-rpl-compat` server option, which was a holdover from the very first 4.0.x versions. (Bug#2428)

- Added option `--sync-frm`. It's on by default, to instruct MySQL to sync to disk each time `.frm` file is created. Use `--disable-sync-frm` to disable.

Bugs fixed:

- mysqlhotcopy now works on NetWare.

- `DROP DATABASE` could not drop databases with RAID tables that had more than nine `RAID_CHUNKS`. (Bug#2627)

- Fixed bug in range optimizer when using overlapping ranges. (Bug#2448)

- Limit `wait_timeout` to 2147483 on Windows (OS limit). (Bug#2400)

- Fixed bug when `--init-file` crashes MySQL if it contains a large `SELECT`. (Bug#2526)

- `SHOW KEYS` now shows `NULL` in the `Sub_part` column for `FULLTEXT` indexes.

- The signal thread's stack size was increased to enable mysqld to run on Debian/IA-64 with a TLS-enabled `glibc`. (Bug#2599)

- Now only the `SELECT` privilege is needed for tables that are only read in multiple-table `UPDATE` statements. (Bug#2377)

- Give proper error message if one uses `LOCK TABLES ... ; INSERT ... SELECT` and one used the same table in the `INSERT` and `SELECT` part. (Bug#2296)

- `SELECT INTO ... DUMPFILE` now deletes the generated file on error.

- Fixed foreign key reference handling to allow references to column names that contain spaces. (Bug#1725)

- Fixed problem with index reads on character columns with `BDB` tables. The symptom was that data could be returned in the wrong lettercase. (Bug#2509)

- Fixed a spurious table corruption problem that could sometimes appear on tables with indexed `TEXT` columns if these columns happened to contain values having trailing spaces. This bug was introduced in 4.0.17.

- Fixed a problem where some queries could hang if a condition like ``indexed_TEXT_column` = `expr`` was present and the column contained values having trailing spaces. This bug was introduced in 4.0.17.

- Fixed a bug that could cause incorrect results from a query that involved range conditions on indexed `TEXT` columns that happened to contain values having trailing spaces. This bug was introduced in 4.0.17. (Bug#2295)

- Fixed incorrect path names in some of the manual pages. (Bug#2270)

- Fixed spurious “table corrupted” errors in parallel repair operations. See Section 5.1.3, “System Variables”.

- Fixed a crashing bug in parallel repair operations. See Section 5.1.3, “System Variables”.

- Fixed bug in updating `MyISAM` tables for `BLOB` values longer than 16MB. (Bug#2159)

- Fixed bug in mysqld_safe when running multiple instances of MySQL. (Bug#2114)

- Fixed a bug in using `HANDLER` statement with tables not from a current database. (Bug#2304)

- Fixed a crashing bug that occurred due to the fact that multiple-table `UPDATE` statements did not check that there was only one table to be updated. (Bug#2103)

- Fixed a crashing bug that occurred due to `BLOB` data type index size being calculated incorrectly in `MIN()` and `MAX()` optimizations. (Bug#2189)

- Fixed a bug with incorrect syntax for `LOCK TABLES` in mysqldump. (Bug#2242)

- Fixed a bug in mysqld_safe that caused mysqld to generate a warning about duplicate `user=`xxx`` options if this option was specified in the `[mysqld]` or `[server]` sections of `my.cnf`. (Bug#2163)

- `INSERT DELAYED ... SELECT ...` could cause table corruption because tables were not locked properly. This is now fixed by ignoring `DELAYED` in this context. (Bug#1983)

- Replication: Sometimes the master gets a non-fatal error during the execution of a statement that does not immediately succeed. (For example, a write to a `MyISAM` table may first receive “no space left on device,” but later complete when disk space becomes available. See Section A.1.4.3, “How MySQL Handles a Full Disk”.) The bug was that the master forgot to reset the error code to 0 after success, so the error code got into its binary log, thus causing the slave to issue false alarms such as “did not get the same error as on master.” (Bug#2083)

- Removed a misleading “check permissions on master.info” from a replication error message, because the cause of the problem could be something other than permissions. (Bug#2121)

- Fixed a crash when the replication slave was unable to create the first relay log. (Bug#2145)

- Replication of `LOAD DATA INFILE` for an empty file from a 3.23 master to a 4.0 slave caused the slave to print an error. (Bug#2452)

- When automatically forcing `lower_case_table_names` to 1 if the file system was case insensitive, mysqld could crash. This bug existed only in MySQL 4.0.17. (Bug#2481)

- Restored ability to specify default values for `TIMESTAMP` columns that was erroneously disabled in previous release. (Bug#2539) Fixed `SHOW CREATE TABLE` to reflect these values. (Bug#1885) Note that because of the auto-update feature for the first `TIMESTAMP` column in a table, it makes no sense to specify a default value for the column. Any such default is silently ignored (unless another `TIMESTAMP` column is added before this one). Also fixed the meaning of the `DEFAULT` keyword when it is used to specify the value to be inserted into a `TIMESTAMP` column other than the first. (Bug#2464)

- Fixed bug for out-of-range arguments on QNX platform that caused `UNIX_TIMESTAMP()` to produce incorrect results or that caused non-zero values to be inserted into `TIMESTAMP` columns. (Bug#2523) Also, current time zone now is taken into account when checking if datetime values satisfy both range boundaries for `TIMESTAMP` columns. The range allowed for a `TIMESTAMP` column is time zone-dependent and equivalent to a range of `1970-01-01 00:00:01` UTC to `2037-12-31 23:59:59` UTC.

- Multiple-table `DELETE` statements were never replicated by the slave if there were any `--replicate-*-table` options. (Bug#2527)

- Changes to session counterparts of variables `query_prealloc_size`, `query_alloc_block_size`, `trans_prealloc_size`, `trans_alloc_block_size` now have an effect. (Bug#1948)

- Fixed bug in `ALTER TABLE RENAME`, when rename to the table with the same name in another database silently dropped destination table if it existed. (Bug#2628)

### B.2.15. Changes in release 4.0.17 (14 December 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- mysqldump no longer dumps data for `MERGE` tables. (Bug#1846)

- `lower_case_table_names` is now forced to 1 if the database directory is located on a case-insensitive filesystem. (Bug#1812)

- Symlink creation is now disabled on systems where `realpath()` doesn't work. (Before one could use `CREATE TABLE .. DATA DIRECTORY=..` even if `HAVE_BROKEN_REALPATH` was defined. This is now disabled to avoid problems when running `ALTER TABLE`).

- Inserting a negative `AUTO_INCREMENT` value in a `MyISAM` table no longer updates the `AUTO_INCREMENT` counter to a big unsigned value. (Bug#1366)

- Added four new modes to `WEEK(..., mode)` function. (Bug#1178)

- Allow `UNION DISTINCT` syntax.

- MySQL now syncs to disk each time `.frm` file is created.

- `mysql_server_init()` now returns 1 if it can't initialize the environment. (Previously `mysql_server_init()` called `exit(1)` if it could not create a key with `pthread_key_create()`. (Bug#2062)

- Allow spaces in Windows service names.

- Changed the default Windows service name for mysqld from `MySql` to `MySQL`. This should not affect usage, because service names are not case sensitive.

- When you install mysqld as a service on Windows systems, mysqld reads startup options in option files from the option group with the same name as the service name. (Except when the service name is `MySQL`).

Bugs fixed:

- Sending `SIGHUP` to mysqld crashed the server if it was running with `--log-bin`. (Bug#2045)

- One can now configure MySQL as a Windows service as a normal user. (Bug#1802). Thanks to Richard Hansen for fixing this.

- Database names are now compared in lowercase in `ON` clauses when `lower_case_table_names` is set. (Bug#1736)

- `IGNORE ... LINES` option to `LOAD DATA INFILE` didn't work when used with fixed length rows. (Bug#1704)

- Fixed problem with `UNIX_TIMESTAMP()` for timestamps close to 0. (Bug#1998)

- Fixed problem with character values greater than 128 in the `QUOTE()` function. (Bug#1868)

- Fixed searching of `TEXT` with endspace. (Bug#1651)

- Fixed caching bug in multiple-table updates where same table was used twice. (Bug#1711)

- Fixed directory permissions for the MySQL-server RPM documentation directory. (Bug#1672)

- Fixed server crash when updating an `ENUM` column that is set to the empty string (for example, with `REPLACE()`). (Bug#2023)

- mysql client program now correctly prints connection identifier returned by `mysql_thread_id()` as unsigned integer rather than as signed integer. (Bug#1951)

- `FOUND_ROWS()` could return incorrect number of rows after a query with an impossible `WHERE` condition. (Bug#1468)

- `SHOW DATABASES` no longer shows `.sym` files (on Windows) that do not point to a valid directory. (Bug#1385)

- Fixed a possible memory leak on Mac OS X when using the shared `libmysql.so` library. (from `pthread_key_create()`). (Bug#2061)

- Fixed bug in `UNION` statement with alias `*`. (Bug#1249)

- Fixed a bug in `DELETE ... ORDER BY ... LIMIT` where the rows were not deleted in the proper order. (Bug#1024, Bug#1697).

- Fixed serious problem with multi-threaded programs on Windows that used the embedded MySQL libraries. (Locks of tables were not handled correctly between different threads).

- Code cleanup: Fixed a few code defects (potential memory leaks, null pointer dereferences, uninitialized variables). Thanks to Reasoning Inc. for informing us about these findings.

- Fixed a buffer overflow error that occurred with prepended “`0`” characters in some columns of type `DECIMAL`. (Bug#2128)

- Filesort was never shown in `EXPLAIN` if query contained an `ORDER BY NULL` clause. (Bug#1335)

- Fixed invalidation of whole query cache on `DROP DATABASE`. (Bug#1898)

- Fixed bug in range optimizer that caused wrong results for some unlikely `AND`/`OR` queries. (Bug#1828)

- Fixed a crash in `ORDER BY` when ordering by expression and identifier. (Bug#1945)

- Fixed a crash in an open `HANDLER` when an `ALTER TABLE` was executed in a different connection. (Bug#1826)

- Fixed a bug in `trunc*` operator of full-text search which sometimes caused MySQL not to find all matched rows.

- Fixed bug in prepending “`0`” characters to `DECIMAL` column values.

- Fixed optimizer bug, introduced in 4.0.16, when `REF` access plan was preferred to more efficient `RANGE` on another column.

- Fixed problem when installing a MySQL server as a Windows service using a command of the form mysqld --install mysql --defaults-file=`path-to-file`. (Bug#1643)

- Fixed an incorrect result from a query that uses only `const` tables (such as one-row tables) and non-constant expression (such as `RAND()`). (Bug#1271)

- Fixed bug when the optimizer did not take `SQL_CALC_FOUND_ROWS` into account if `LIMIT` clause was present. (Bug#1274)

- mysqlbinlog now asks for a password at the console when the `-p` or `--password` option is used with no argument. This is consistent with the way that other clients such mysqladmin and mysqldump behave.

  ### Note

  A consequence of this change is that it is no longer possible to invoke mysqlbinlog as mysqlbinlog -p pass_val (with a space between the `-p` option and the following password value). (Bug#1595)

- Fixed bug accidentally introduced in 4.0.16 where the slave SQL thread deleted its replicated temporary tables when `STOP SLAVE` was issued.

- In a “chain” replication setup `A->B->C`, if 2 sessions on A updated temporary tables of the same name at the same time, the binary log of `B` became incorrect, resulting in `C` becoming confused. (Bug#1686)

- In a “chain” replication setup `A->B->C`, if `STOP SLAVE` was issued on `B` while it was replicating a temporary table from `A`, then when `START SLAVE` was issued on `B`, the binary log of `B` became incorrect, resulting in `C` becoming confused. (Bug#1240)

- When `MASTER_LOG_FILE` and `MASTER_LOG_POS` were not specified, `CHANGE MASTER` used the coordinates of the slave I/O thread to set up replication, which broke replication if the slave SQL thread lagged behind the slave I/O thread. This caused the slave SQL thread to lose some events. The new behavior is to use the coordinates of the slave SQL thread instead. See Section 12.6.2.1, “`CHANGE MASTER TO` Syntax”. (Bug#1870)

- Now if integer is stored or converted to `TIMESTAMP` or `DATETIME` value checks of year, month, day, hour, minute and second ranges are performed and numbers representing illegal timestamps are converted to 0 value. This behavior is consistent with manual and with behavior of string to `TIMESTAMP`/`DATETIME` conversion. (Bug#1448)

- Fixed bug when `BIT_AND()` and `BIT_OR()` group functions returned incorrect value if `SELECT` used a temporary table and no rows were found. (Bug#1790).

- `BIT_AND()` is now unsigned in all contexts. This means that it now returns 18446744073709551615 (= 0xffffffffffffffff) instead of -1 if there were no rows in the result.

- Fixed bug with `BIT_AND()` still returning signed value for an empty set in some cases. (Bug#1972)

- Fixed bug with `^` (XOR) and `>>` (bit shift) still returning signed value in some cases. (Bug#1993)

- Replication: a rare race condition in the slave SQL thread, which could lead to a wrong complain that the relay log is corrupted. (Bug#2011)

- Replication: in the slave SQL thread, a multiple-table `UPDATE` could produce a wrong complain that some record was not found in one table, if the `UPDATE` was preceded by a `INSERT ... SELECT`. (Bug#1701)

- Fixed deficiency in MySQL code which is responsible for scanning directories. This deficiency caused `SHOW TABLE STATUS` to be very slow when a database contained a large number of tables, even if a single particular table were specified. (Bug#1952)

### B.2.16. Changes in release 4.0.16 (17 October 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Option values in option files now may be quoted. This is useful for values that contain whitespace or comment characters.

- Write memory allocation information to error log when doing mysqladmin debug. This works only on systems that support the `mallinfo()` call (like newer Linux systems).

- Added the following new system variables to allow more precise memory allocation: `range_alloc_block_size`, `query_alloc_block_size`, `query_prealloc_size`, `transaction_alloc_block_size`, and `transaction_prealloc_size`.

- mysqlbinlog now reads option files. To make this work, you must now specify `--read-from-remote-server` when reading binary logs from a MySQL server. (Note that using a remote server is deprecated and may disappear in future mysqlbinlog versions).

- Block `SIGPIPE` signals also for non-threaded programs. The blocking is moved from `mysql_init()` to `mysql_server_init()`, which is automatically called on the first call to `mysql_init()`.

- Added `--libs_r` and `--include` options to mysql_config.

- New ``>` prompt for mysql. This prompt is similar to the `'>` and `">` prompts, but indicates that an identifier quoted with backticks was begun on an earlier line and the closing backtick has not yet been seen.

- Updated mysql_install_db to be able to use the local machine's IP address instead of the hostname when building the initial grant tables if `skip-name-resolve` has been specified. This option can be helpful on FreeBSD to avoid thread-safety problems with the FreeBSD resolver libraries. (Thanks to Jeremy Zawodny for the patch.)

- A documentation change: Added a note that when backing up a slave, it is necessary also to back up the `master.info` and `relay-log.info` files, as well as any `SQL_LOAD-*` files located in the directory specified by the `--slave-load-tmpdir` option. All these files are needed when the slave resumes replication after you restore the slave's data.

Bugs fixed:

- Fixed a spurious error `ERROR 14: Can't change size of file (Errcode: 2)` on Windows in `DELETE FROM `tbl_name`` without a `WHERE` clause or `TRUNCATE TABLE `tbl_name``, when `tbl_name` is a `MyISAM` table. (Bug#1397)

- Fixed a bug that resulted in `thr_alarm queue is full` warnings after increasing the `max_connections` variable with `SET GLOBAL`. (Bug#1435)

- Made `LOCK TABLES` to work when `Lock_tables_priv` is granted on the database level and `Select_priv` is granted on the table level.

- Fixed crash of `FLUSH QUERY CACHE` on queries that use same table several times (Bug#988).

- Fixed core dump bug when setting an enum system variable (such as `SQL_WARNINGS`) to `NULL`.

- Extended the default timeout value for Windows clients from 30 seconds to 1 year. (The timeout that was added in MySQL 4.0.15 was way too short). This fixes a bug that caused `ERROR 2013: Lost connection to MySQL server during query` for queries that lasted longer than 30 seconds, if the client didn't specify a limit with `mysql_options()`. Users of 4.0.15 on Windows should upgrade to avoid this problem.

- More “out of memory” checking in range optimizer.

- Fixed and documented a problem when setting and using a user variable within the same `SELECT` statement. (Bug#1194).

- Fixed bug in overrun check for `BLOB` values with compressed tables. This was a bug introduced in 4.0.14. It caused MySQL to regard some correct tables containing `BLOB` values as corrupted. (Bug#770, Bug#1304, and maybe Bug#1295)

- `SHOW GRANTS` showed `USAGE` instead of the real column-level privileges when no table-level privileges were given.

- When copying a database from the master, `LOAD DATA FROM MASTER` dropped the corresponding database on the slave, thus erroneously dropping tables that had no counterpart on the master and tables that may have been excluded from replication using `--replicate-*-table` rules. Now `LOAD DATA FROM MASTER` no longer drops the database. Instead, it drops only the tables that have a counterpart on the master and that match the `--replicate-*-table` rules. `--replicate-*-db` rules can still be used to include or exclude a database as a whole from `LOAD DATA FROM MASTER`. A database also is included or excluded as a whole if there are some rules like `--replicate-wild-do-table=db1.%` or `--replicate-wild-ignore-table=db1.%`, as is the case for `CREATE DATABASE` and `DROP DATABASE` in replication. (Bug#1248)

- Fixed a bug where mysqlbinlog crashed with a segmentation fault when used with the `-h` or `--host` option. (Bug#1258)

- Fixed a bug where mysqlbinlog crashed with a segmentation fault when used on a binary log containing only final events for `LOAD DATA`. (Bug#1340)

- mysqlbinlog does not reuse temporary filenames from previous runs. Previously mysqlbinlog failed if was used several times on the same binary log file that contained a `LOAD DATA` command.

- Fixed compilation problem when compiling with OpenSSL 0.9.7 with disabled old DES support (If `OPENSSL_DISABLE_OLD_DES_SUPPORT` option was enabled).

- Fixed a bug when two (or more) MySQL servers were running on the same machine, and they were both slaves, and at least one of them was replicating some `LOAD DATA INFILE` command from its master. The bug was that one slave MySQL server sometimes deleted the `SQL_LOAD-*` files (used for replication of `LOAD DATA INFILE` and located in the `slave-load-tmpdir` directory, which defaults to `tmpdir`) belonging to the other slave MySQL server of this machine, if these slaves had the same `slave-load-tmpdir` directory. When that happened, the other slave could not replicate `LOAD DATA INFILE` and complained about not being able to open some `SQL_LOAD-*` file. (Bug#1357)

- If `LOAD DATA INFILE` failed for a small file, the master forgot to write a marker (a `Delete_file` event) in its binary log, so the slave could not delete 2 files (`SQL_LOAD-*.info` and `SQL_LOAD-*.data` from its `tmpdir`. (Bug#1391)

- On Windows, the slave forgot to delete a `SQL_LOAD-*.info` file from `tmpdir` after successfully replicating a `LOAD DATA INFILE` command. (Bug#1392)

- When a connection terminates, MySQL writes `DROP TEMPORARY TABLE` statements to the binary log for all temporary tables which the connection had not explicitly dropped. MySQL forgot to use backticks to quote the database and table names in the statement. (Bug#1345)

- On some 64-bit machines (some HP-UX and Solaris machines), a slave installed with the 64-bit MySQL binary could not connect to its master (it connected to itself instead). (Bug#1256, Bug#1381)

- Code was introduced in MySQL 4.0.15 for the slave to detect that the master had died while writing a transaction to its binary log. This code reported an error in a legal situation: When the slave I/O thread was stopped while copying a transaction to the relay log, the slave SQL thread would later pretend that it found an unfinished transaction. (Bug#1475)

### B.2.17. Changes in release 4.0.15 (03 September 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

### Important

If you are using this release on Windows, you should upgrade at least your clients (any program that uses `libmysql.lib`) to 4.0.16 or above. This is because the 4.0.15 release had a bug in the Windows client library that causes Windows clients using the library to die with a `Lost connection to MySQL server during query` error for queries that take more than 30 seconds. This problem is specific to Windows; clients on other platforms are unaffected.

Functionality added or changed:

- mysqldump now correctly quotes all identifiers when communicating with the server. This assures that during the dump process, mysqldump never sends queries to the server that result in a syntax error. This problem is not related to the mysqldump program's output, which was not changed. (Bug#1148)

- Change result set metadata information so that `MIN()` and `MAX()` report that they can return `NULL` (this is true because an empty set returns `NULL`). (Bug#324)

- Produce an error message on Windows if a second mysqld server is started on the same TCP/IP port as a running mysqld server.

- The mysqld system variables `wait_timeout`, `net_read_timeout`, and `net_write_timeout` now work on Windows. One can now also set timeouts for read and writes in Windows clients with `mysql_options()`.

- Added option `--sql-mode=NO_DIR_IN_CREATE` to make it possible for slaves to ignore `INDEX DIRECTORY` and `DATA DIRECTORY` options given to `CREATE TABLE`. When this is mode is on, `SHOW CREATE TABLE` does not show the given directories.

- `SHOW CREATE TABLE` now shows the `INDEX DIRECTORY` and `DATA DIRECTORY` options, if they were specified when the table was created.

- The `open_files_limit` system variable now shows the real open files limit.

- `MATCH ... AGAINST()` in natural language mode now treats words that are present in more than 2,000,000 rows as stopwords.

- The Mac OS X installation disk images now include an additional `MySQLStartupItem.pkg` package that enables the automatic startup of MySQL on system startup. See Section 2.5, “Installing MySQL on Mac OS X”.

- Most of the documentation included in the binary tarball distributions (`.tar.gz`) has been moved into a subdirectory `docs`. See Section 2.1.5, “Installation Layouts”.

- The manual is now included as an additional `info` file in the binary distributions. (Bug#1019)

- The binary distributions now include the embedded server library (`libmysqld.a`) by default. Due to a linking problem with non-gcc compilers, it was not included in all packages of the initial 4.0.15 release. The affected packages were rebuilt and released as 4.0.15a. See Section 1.5.1, “MySQL 4.0 in a Nutshell”.

- MySQL can now use range optimization for `BETWEEN` with non-constant limits. (Bug#991)

- Replication error messages now include the default database, so that users can check which database the failing query was run for.

- A documentation change: Added a paragraph about how the `binlog-do-db` and `binlog-ignore-db` options are tested against the database on the master (see Section 5.3.4, “The Binary Log”), and a paragraph about how `--replicate-do-db`, `--replicate-do-table` and analogous options are tested against the database and tables on the slave (see Section 6.8, “Replication Startup Options”).

- Now the slave does not replicate `SET PASSWORD` if it is configured to exclude the `mysql` database from replication (using for example `--replicate-wild-ignore-table=mysql.%`). This was the case for `GRANT` and `REVOKE` since version 4.0.13 (although there was Bug#980 in 4.0.13 & 4.0.14, which has been fixed in 4.0.15).

- Rewrote the information shown in the `State` column of `SHOW PROCESSLIST` for replication threads and for `MASTER_POS_WAIT()` and added the most common states for these threads to the documentation, see Section 6.3, “Replication Implementation Details”.

- Added a test in replication to detect the case where the master died in the middle of writing a transaction to the binary log; such unfinished transactions now trigger an error message on the slave.

- A `GRANT` command that creates an anonymous user (that is, an account with an empty username) no longer requires `FLUSH PRIVILEGES` for the account to be recognized by the server. (Bug#473)

- `CHANGE MASTER` now flushes `relay-log.info`. Previously this was deferred to the next run of `START SLAVE`, so if mysqld was shutdown on the slave after `CHANGE MASTER` without having run `START SLAVE`, the relay log's name and position were lost. At restart they were reloaded from `relay-log.info`, thus reverting to their old (incorrect) values from before `CHANGE MASTER` and leading to error messages (as the old relay log did not exist any more) and the slave threads refusing to start. (Bug#858)

Bugs fixed:

- Fixed buffer overflow in password handling which could potentially be exploited by MySQL users with `ALTER` privilege on the `mysql.user` table to execute random code or to gain shell access with the UID of the mysqld process (thanks to Jedi/Sector One for spotting and reporting this bug). (CVE-2003-0780)

- Fixed server crash on `FORCE INDEX` in a query that contained "Range checked for each record" in the `EXPLAIN` output. (Bug#1172)

- Fixed table/column grant handling: The proper sort order (from most specific to less specific, see Section 5.5.6, “Access Control, Stage 2: Request Verification”) was not honored. (Bug#928)

- Fixed rare bug in `MYISAM` introduced in 4.0.3 where the index file header was not updated directly after an `UPDATE` of split dynamic rows. The symptom was that the table had a corrupted delete-link if mysqld was shut down or the table was checked directly after the update.

- Fixed `Can't unlock file` error when running myisamchk --sort-index on Windows. (Bug#1119)

- Fixed possible deadlock when changing `key_buffer_size` while the key cache was actively used. (Bug#1088)

- Fixed overflow bug in `MyISAM` and `ISAM` when a row is updated in a table with a large number of columns and at least one `BLOB/TEXT` column.

- Fixed incorrect result when doing `UNION` and `LIMIT #,#` when braces were not used around the `SELECT` parts.

- Fixed incorrect result when doing `UNION` and `ORDER BY .. LIMIT #` when one didn't use braces around the `SELECT` parts.

- Fixed problem with `SELECT SQL_CALC_FOUND_ROWS ... UNION ALL ... LIMIT #` where `FOUND_ROWS()` returned incorrect number of rows.

- Fixed unlikely stack bug when having a BIG expression of type `1+1-1+1-1...` in certain combinations. (Bug#871)

- Fixed the bug that sometimes prevented a table with a `FULLTEXT` index from being marked as "analyzed".

- Fixed MySQL so that the column length (in C API) for the second column in `SHOW CREATE TABLE` is always larger than the data length. The only known application that was affected by the old behavior was Borland dbExpress, which truncated the output from the command. (Bug#1064)

- Fixed crash in comparisons of strings using the `tis620` character set. (Bug#1116)

- Fixed `ISAM` bug in `MAX()` optimization.

- myisamchk --sort-records=N no longer marks table as crashed if sorting failed because of an inappropriate key. (Bug#892)

- Fixed a minor bug in `MyISAM` compressed table handling that sometimes made it impossible to repair compressed table in "Repair by sort" mode. "Repair with keycache" (myisamchk --safe-recover) worked, though. (Bug#1015)

- Fixed bug in propagating the version number to the manual included in the distribution files. (Bug#1020)

- Fixed key sorting problem (a `PRIMARY` key declared for a column that is not explicitly marked `NOT NULL` was sorted after a `UNIQUE` key for a `NOT NULL` column).

- Fixed the result of `INTERVAL` when applied to a `DATE` value. (Bug#792)

- Fixed compiling of the embedded server library in the RPM spec file. (Bug#959)

- Added some missing files to the RPM spec file and fixed some RPM building errors that occurred on Red Hat Linux 9. (Bug#998)

- Fixed incorrect `XOR` evaluation in `WHERE` clause. (Bug#992)

- Fixed bug with processing in query cache merged tables constructed from more then 255 tables. (Bug#930)

- Fixed incorrect results from outer join query (for example, `LEFT JOIN`) when `ON` condition is always false, and range search in used. (Bug#926)

- Fixed a bug causing incorrect results from `MATCH ... AGAINST()` in some joins. (Bug#942)

- `MERGE` tables do not ignore `Using index` (from `EXPLAIN` output) anymore.

- Fixed a bug that prevented an empty table from being marked as "analyzed". (Bug#937)

- Fixed myisamchk --sort-records crash when used on compressed table.

- Fixed slow (as compared to 3.23) `ALTER TABLE` and related commands such as `CREATE INDEX`. (Bug#712)

- Fixed segmentation fault resulting from `LOAD DATA FROM MASTER` when the master was running without the `--log-bin` option. (Bug#934)

- Fixed a security bug: A server compiled without SSL support still allowed connections by users who had the `REQUIRE SSL` option specified for their accounts.

- Fixed a random bug: Sometimes the slave would replicate `GRANT` or `REVOKE` queries even if it was configured to exclude the `mysql` database from replication (for example, using `--replicate-wild-ignore-table=mysql.%`). (Bug#980)

- The `Last_Errno` and `Last_Error` fields in the output of `SHOW SLAVE STATUS` are now cleared by `CHANGE MASTER` and when the slave SQL thread starts. (Bug#986)

- A documentation mistake: It said that `RESET SLAVE` does not change connection information (master host, port, user, and password), whereas it does. The statement resets these to the startup options (`master-host` etc) if there were some. (Bug#985)

- `SHOW SLAVE STATUS` now shows correct information (master host, port, user, and password) after `RESET SLAVE` (that is, it shows the new values, which are copied from the startup options if there were some). (Bug#985)

- Disabled propagation of the original master's log position for events because this caused unexpected values for `Exec_Master_Log_Pos` and problems with `MASTER_POS_WAIT()` in A->B->C replication setup. (Bug#1086)

- Fixed a segmentation fault in mysqlbinlog when `--position=x` was used with `x` being between a `Create_file` event and its fellow `Append_block`, `Exec_load` or `Delete_file` events. (Bug#1091)

- mysqlbinlog printed superfluous warnings when using `--database`, which caused syntax errors when piped to mysql. (Bug#1092)

- Made mysqlbinlog --database filter `LOAD DATA INFILE` too (previously, it filtered all queries except `LOAD DATA INFILE`). (Bug#1093)

- mysqlbinlog in some cases forgot to put a leading `'#'` in front of the original `LOAD DATA INFILE` (this command is displayed only for information, not to be run; it is later reworked to `LOAD DATA LOCAL` with a different filename, for execution by mysql). (Bug#1096)

- `binlog-do-db` and `binlog-ignore-db` incorrectly filtered `LOAD DATA INFILE` (it was half-written to the binary log). This resulted in a corrupted binary log, which could cause the slave to stop with an error. (Bug#1100)

- When, in a transaction, a transactional table (such as an `InnoDB` table) was updated, and later in the same transaction a non-transactional table (such as a `MyISAM` table) was updated using the updated content of the transactional table (with `INSERT ... SELECT` for example), the queries were written to the binary log in an incorrect order. (Bug#873)

- When, in a transaction, `INSERT ... SELECT` updated a non-transactional table, and `ROLLBACK` was issued, no error was returned to the client. Now the client is warned that some changes could not be rolled back, as this was the case for normal `INSERT`. (Bug#1113)

- Fixed a potential bug: When `STOP SLAVE` was run while the slave SQL thread was in the middle of a transaction, and then `CHANGE MASTER` was used to point the slave to some non-transactional statement, the slave SQL thread could get confused (because it would still think, from the past, that it was in a transaction).

### B.2.18. Changes in release 4.0.14 (18 July 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Added `default_week_format` system variable. The value is used as the default mode for the `WEEK()` function.

- mysqld now reads an additional option file group having a name corresponding to the server's release series: `[mysqld-4.0]` for 4.0.x servers, `[mysqld-4.1]` for 4.1.x servers, and so forth. This allows options to be specified on a series-specific basis.

- The `CONCAT_WS()` function no longer skips empty strings. (Bug#586).

- `InnoDB` now supports indexing a prefix of a column. This means, in particular, that `BLOB` and `TEXT` columns can be indexed in `InnoDB` tables, which was not possible before.

- A documentation change: Function `INTERVAL(NULL, ...)` returns `-1`.

- Enabled `INSERT` from `SELECT` when the table into which the records are inserted is also a table listed in the `SELECT`.

- Allow `CREATE TABLE` and `INSERT` from any `UNION`.

- The `SQL_CALC_FOUND_ROWS` option now always returns the total number of rows for any `UNION`.

- Removed `--table` option from mysqlbinlog to avoid repeating mysqldump functionality.

- Comment lines in option files can now start from the middle of a line, too (like `basedir=c:\mysql # installation directory`).

- Changed optimizer slightly to prefer index lookups over full table scans in some boundary cases.

- Added thread-specific `max_seeks_for_key` variable that can be used to force the optimizer to use keys instead of table scans even if the cardinality of the index is low.

- Added optimization that converts `LEFT JOIN` to normal join in some cases.

- A documentation change: added a paragraph about failover in replication (how to use a surviving slave as the new master, how to resume to the original setup). See Section 6.10, “Replication FAQ”.

- A documentation change: added warning notes about safe use of the `CHANGE MASTER` command. See Section 12.6.2.1, “`CHANGE MASTER TO` Syntax”.

- MySQL now issues a warning (not an error, as in 4.0.13) when it opens a table that was created with MySQL 4.1.

- Added `--nice` option to mysqld_safe to allow setting the niceness of the mysqld process. (Thanks to Christian Hammers for providing the initial patch.) (Bug#627)

- Added `--read-only` option to cause mysqld to allow no updates except from slave threads or from users with the `SUPER` privilege. (Original patch from Markus Benning).

- `SHOW BINLOG EVENTS FROM x` where `x` is less than 4 now silently converts `x` to 4 instead of printing an error. The same change was done for `CHANGE MASTER TO MASTER_LOG_POS=x` and `CHANGE MASTER TO RELAY_LOG_POS=x`.

- mysqld now only adds an interrupt handler for the `SIGINT` signal if you start it with the new `--gdb` option. This is done because some MySQL users encountered strange problems when they accidentally sent `SIGINT` to mysqld threads.

- `RESET SLAVE` now clears the `Last_Errno` and `Last_Error` fields in the output of `SHOW SLAVE STATUS`.

- Added `max_relay_log_size` variable; the relay log is rotated automatically when its size exceeds `max_relay_log_size`. But if `max_relay_log_size` is 0 (the default), `max_binlog_size` is used (as in older versions). `max_binlog_size` still applies to binary logs in any case.

- `FLUSH LOGS` now rotates relay logs in addition to the other types of logs it rotates.

Bugs fixed:

- Comparison/sorting for `latin1_de` character set was rewritten. The old algorithm could not handle cases like `"sä" > "ßa"`. See Section 9.2.1, “Using the German Character Set”. In rare cases it resulted in table corruption.

- Fixed a problem with the password prompt on Windows. (Bug#683)

- `ALTER TABLE ... UNION=(...)` for `MERGE` table is now allowed even if some underlying `MyISAM` tables are read only. (Bug#702)

- Fixed a problem with `CREATE TABLE t1 SELECT x'41'`. (Bug#801)

- Removed some incorrect lock warnings from the error log.

- Fixed memory overrun when doing `REPAIR TABLE` on a table with a multiple-part auto_increment key where one part was a packed `CHAR`.

- Fixed a probable race condition in the replication code that could potentially lead to `INSERT` statements not being replicated in the event of a `FLUSH LOGS` command or when the binary log exceeds `max_binlog_size`. (Bug#791)

- Fixed a crashing bug in `INTERVAL` and `GROUP BY` or `DISTINCT`. (Bug#807)

- Fixed bug in mysqlhotcopy so it actually aborts for unsuccessful table copying operations. Fixed another bug so that it succeeds when there are thousands of tables to copy. (Bug#812)

- Fixed problem with mysqlhotcopy failing to read options from option files. (Bug#808)

- Fixed bugs in optimizer that sometimes prevented MySQL from using `FULLTEXT` indexes even though it was possible (for example, in `SELECT * FROM t1 WHERE MATCH a,b AGAINST("index") > 0`).

- Fixed a bug with “table is full” in `UNION` operations.

- Fixed a security problem that enabled users with no privileges to obtain information on the list of existing databases by using `SHOW TABLES` and similar commands.

- Fixed a stack problem on UnixWare/OpenUnix.

- Fixed a configuration problem on UnixWare/OpenUNIX and OpenServer.

- Fixed a problem with `max_user_connections`.

- `HANDLER` without an index now works properly when a table has deleted rows. (Bug#787)

- Fixed a bug with `LOAD DATA` in mysqlbinlog. (Bug#670)

- Fixed that `SET CHARACTER SET DEFAULT` works. (Bug#462)

- Fixed `MERGE` table behavior in `ORDER BY ... DESC` queries. (Bug#515)

- Fixed server crash on `PURGE MASTER LOGS` or `SHOW MASTER LOGS` when the binary log is off. (Bug#733)

- Fixed password-checking problem on Windows. (Bug#464)

- Fixed the bug in comparison of a `DATETIME` column and an integer constant. (Bug#504)

- Fixed remote mode of mysqlbinlog. (Bug#672)

- Fixed `ERROR 1105: Unknown error` that occurred for some `SELECT` queries, where a column that was declared as `NOT NULL` was compared with an expression that took `NULL` value.

- Changed timeout in `mysql_real_connect()` to use `poll()` instead of `select()` to work around problem with many open files in the client.

- Fixed incorrect results from `MATCH ... AGAINST` used with a `LEFT JOIN` query.

- Fixed a bug that limited the maximum value for mysqld variables to 4294967295 when they are specified on the command line.

- Fixed a bug that sometimes caused spurious “Access denied” errors in `HANDLER ... READ` statements, when a table is referenced via an alias.

- Fixed portability problem with `safe_malloc`, which caused MySQL to give "Freeing wrong aligned pointer" errors on SCO 3.2.

- `ALTER TABLE ... ENABLE/DISABLE KEYS` could cause a core dump when done after an `INSERT DELAYED` statement on the same table.

- Fixed problem with conversion of localtime to GMT where some times resulted in different (but correct) timestamps. Now MySQL should use the smallest possible timestamp value in this case. (Bug#316)

- Very small query cache sizes could crash mysqld. (Bug#549)

- Fixed a bug (accidentally introduced by us but present only in version 4.0.13) that made `INSERT ... SELECT` into an `AUTO_INCREMENT` column not replicate well. This bug is in the master, not in the slave. (Bug#490)

- Fixed a bug: When an `INSERT ... SELECT` statement inserted rows into a non-transactional table, but failed at some point (for example, due to a “Duplicate key” error), the query was not written to the binary log. Now it is written to the binary log, with its error code, as all other queries are. About the `slave-skip-errors` option for how to handle partially completed queries in the slave, see Section 6.8, “Replication Startup Options”. (Bug#491)

- `SET FOREIGN_KEY_CHECKS=0` was not replicated properly. The fix probably will not be backported to 3.23.

- On a slave, `LOAD DATA INFILE` which had no `IGNORE` or `REPLACE` clause on the master, was replicated with `IGNORE`. Although this is not a problem if the master and slave data are identical (a `LOAD` that produces no duplicate conflicts on the master produces none on the slave anyway), which is true in normal operation, it is better for debugging not to silently add the `IGNORE`. That way, you can get an error message on the slave and discover that for some reason, the data on master and slave are different and investigate why. (Bug#571)

- On a slave, `LOAD DATA INFILE` printed an incomplete “Duplicate entry '%-.64s' for key %d'” message (the key name and value were not mentioned) in case of duplicate conflict (which does not happen in normal operation). (Bug#573)

- When using a slave compiled with `--debug`, `CHANGE MASTER TO RELAY_LOG_POS` could cause a debug assertion failure. (Bug#576)

- When doing a `LOCK TABLES WRITE` on an `InnoDB` table, commit could not happen, if the query was not written to the binary log (for example, if `--log-bin` was not used, or `binlog-ignore-db` was used). (Bug#578)

- If a 3.23 master had open temporary tables that had been replicated to a 4.0 slave, and the binary log got rotated, these temporary tables were immediately dropped by the slave (which caused problems if the master used them subsequently). This bug had been fixed in 4.0.13, but in a manner which caused an unlikely inconvenience: If the 3.23 master died brutally (power failure), without having enough time to automatically write `DROP TABLE` statements to its binary log, then the 4.0.13 slave would not notice the temporary tables have to be dropped, until the slave mysqld server is restarted. This minor inconvenience is fixed in 3.23.57 and 4.0.14 (meaning the master must be upgraded to 3.23.57 and the slave to 4.0.14 to remove the inconvenience). (Bug#254)

- If `MASTER_POS_WAIT()` was waiting, and the slave was idle, and the slave SQL thread terminated, `MASTER_POS_WAIT()` would wait forever. Now when the slave SQL thread terminates, `MASTER_POS_WAIT()` immediately returns `NULL` (“slave stopped”). (Bug#651)

- After `RESET SLAVE; START SLAVE;`, the `Relay_Log_Space` value displayed by `SHOW SLAVE STATUS` was too big by four bytes. (Bug#763)

- If a query was ignored on the slave (because of `--replicate-ignore-table` and other similar rules), the slave still checked if the query got the same error code (0, no error) as on the master. So if the master had an error on the query (for example, “Duplicate entry” in a multiple-row insert), then the slave stopped and warned that the error codes didn't match. (Bug#797)

### B.2.19. Changes in release 4.0.13 (16 May 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- `PRIMARY KEY` now implies `NOT NULL`. (Bug#390)

- The Windows binary packages are now compiled with `--enable-local-infile` to match the Unix build configuration.

- Removed timing of tests from mysql-test-run. `time` does not accept all required parameters on many platforms (for example, QNX) and timing the tests is not really required (it's not a benchmark anyway).

- `SHOW MASTER STATUS` and `SHOW SLAVE STATUS` required the `SUPER` privilege; now they accept `REPLICATION CLIENT` as well. (Bug#343)

- Added multi-threaded `MyISAM` repair optimization and `myisam_repair_threads` variable to enable it. See Section 5.1.3, “System Variables”.

- Added `innodb_max_dirty_pages_pct` variable which controls amount of dirty pages allowed in `InnoDB` buffer pool.

- `CURRENT_USER()` and `Access denied` error messages now report the hostname exactly as it was specified in the `GRANT` command.

- Removed benchmark results from the source and binary distributions. They are still available in the BK source tree, though.

- `InnoDB` tables now support `ANALYZE TABLE`.

- MySQL now issues an error when it opens a table that was created with MySQL 4.1.

- Option `--new` now changes binary items (`0xFFDF`) to be treated as binary strings instead of numbers by default. This fixes some problems with character sets where it's convenient to input the string as a binary item. After this change you have to convert the binary string to `INTEGER` with a `CAST` if you want to compare two binary items with each other and know which one is bigger than the other. `SELECT CAST(0xfeff AS UNSIGNED) < CAST(0xff AS UNSIGNED)`. This is the default behavior in MySQL 4.1. (Bug#152)

- Enabled `delayed_insert_timeout` on Linux (most modern `glibc` libraries have a fixed `pthread_cond_timedwait()`). (Bug#211)

- Don't create more insert delayed threads than given by `max_delayed_threads`. (Bug#211)

- Changed `UPDATE ... LIMIT` to apply the limit to rows that were matched, whether or not they actually were changed. Previously the limit was applied as a restriction on the number of rows changed.

- Tuned optimizer to favor clustered index over table scan.

- `BIT_AND()` and `BIT_OR()` now return an unsigned 64-bit value.

- Added warnings to error log of why a secure connection failed (when running with `--log-warnings`).

- Deprecated options `--skip-symlink` and `--use-symbolic-links` and replaced these with `--symbolic-links`.

- The default option for `innodb_flush_log_at_trx_commit` was changed from 0 to 1 to make `InnoDB` tables ACID by default. See Section 13.2.5, “`InnoDB` Startup Options and System Variables”.

- Added a feature to `SHOW KEYS` to display keys that are disabled by `ALTER TABLE DISABLE KEYS` command.

- When using a non-existing table type with `CREATE TABLE`, first try if the default table type exists before falling back to `MyISAM`.

- Added `MEMORY` as an alias for `HEAP`.

- Renamed function `rnd` to `my_rnd` as the name was too generic and is an exported symbol in `libmysqlclient` (thanks to Dennis Haney for the initial patch).

- Portability fix: renamed `include/dbug.h` to `include/my_dbug.h`.

- mysqldump no longer silently deletes the binary logs when invoked with the `--master-data` or `--first-slave` option; while this behavior was convenient for some users, others may suffer from it. Now you must explicitly ask for binary logs to be deleted by using the new `--delete-master-logs` option.

- If the slave is configured (using for example `--replicate-wild-ignore-table=mysql.%`) to exclude `mysql.user`, `mysql.host`, `mysql.db`, `mysql.tables_priv` and `mysql.columns_priv` from replication, then `GRANT` and `REVOKE` are not replicated.

Bugs fixed:

- Logged `Access denied` error message had incorrect `Using password` value. (Bug#398)

- Fixed bug with `NATURAL LEFT JOIN`, `NATURAL RIGHT JOIN` and `RIGHT JOIN` when using many joined tables. The problem was that the `JOIN` method was not always associated with the tables surrounding the `JOIN` method. If you have a query that uses many `RIGHT JOIN` or `NATURAL ... JOINS` you should verify that they work as you expected after upgrading MySQL to this version. (Bug#291)

- Fixed mysql parser not to erroneously interpret “`'`” or “`"`” characters within `/* ... */` comment as beginning a quoted string.

- mysql command-line client no longer looks for `\*` commands inside backtick-quoted strings.

- Fixed `Unknown error` when using `UPDATE ... LIMIT`. (Bug#373)

- Fixed problem with ANSI mode and `GROUP BY` with constants. (Bug#387)

- Fixed bug with `UNION` and `OUTER JOIN`. (Bug#386)

- Fixed bug if one used a multiple-table `UPDATE` and the query required a temporary table bigger than `tmp_table_size`. (Bug#286)

- Run mysql_install_db with the `-IN-RPM` option for the Mac OS X installation to not fail on systems with improperly configured hostname configurations.

- `LOAD DATA INFILE` now reads `000000` as a zero date instead of `"2000-00-00"`.

- Fixed bug that caused `DELETE FROM table WHERE const_expression` always to delete the whole table (even if expression result was false). (Bug#355)

- Fixed core dump bug when using `FORMAT('nan',#)`. (Bug#284)

- Fixed name resolution bug with `HAVING ... COUNT(DISTINCT ...)`.

- Fixed incorrect result from truncation operator (`*`) in `MATCH ... AGAINST()` in some complex joins.

- Fixed a crash in `REPAIR ... USE_FRM` command, when used on read-only, non-existing table or a table with a crashed index file.

- Fixed a crashing bug in mysql monitor program. It occurred if program was started with `--no-defaults`, with a prompt that contained the hostname and a connection to a non-existent database was requested.

- Fixed problem when comparing a key for a multi-byte character set. (Bug#152)

- Fixed bug in `LEFT`, `RIGHT` and `MID` when used with multi-byte character sets and some `GROUP BY` queries. (Bug#314)

- Fix problem with `ORDER BY` being discarded for some `DISTINCT` queries. (Bug#275)

- Fixed that `SET SQL_BIG_SELECTS=1` works as documented (This corrects a new bug introduced in 4.0)

- Fixed some serious bugs in `UPDATE ... ORDER BY`. (Bug#241)

- Fixed unlikely problem in optimizing `WHERE` clause with constant expression like in `WHERE 1 AND (a=1 AND b=1)`.

- Fixed that `SET SQL_BIG_SELECTS=1` works again.

- Introduced proper backtick quoting for db.table in `SHOW GRANTS`.

- `FULLTEXT` index stopped working after `ALTER TABLE` that converts `TEXT` column to `CHAR`. (Bug#283)

- Fixed a security problem with `SELECT` and wildcarded select list, when user only had partial column `SELECT` privileges on the table.

- Mark a `MyISAM` table as "analyzed" only when all the keys are indeed analyzed.

- Only ignore world-writable `my.cnf` files that are regular files (and not, for example, named pipes or character devices).

- Fixed few smaller issues with `SET PASSWORD`.

- Fixed error message which contained deprecated text.

- Fixed a bug with two `NATURAL JOIN`s in the query.

- `SUM()` didn't return `NULL` when there was no rows in result or when all values was `NULL`.

- On Unix, symbolic link handling was not enabled by default and there was no way to turn this on.

- Added missing dashes to parameter `--open-files-limit` in mysqld_safe. (Bug#264)

- Fixed incorrect hostname for TCP/IP connections displayed in `SHOW PROCESSLIST`.

- Fixed a bug with `NAN` in `FORMAT(...)` function ...

- Fixed a bug with improperly cached database privileges.

- Fixed a bug in `ALTER TABLE ENABLE / DISABLE KEYS` which failed to force a refresh of table data in the cache.

- Fixed bugs in replication of `LOAD DATA INFILE` for custom parameters (`ENCLOSED`, `TERMINATED` and so on) and temporary tables. (Bug#183, Bug#222)

- Fixed a replication bug when the master is 3.23 and the slave 4.0: the slave lost the replicated temporary tables if `FLUSH LOGS` was issued on the master. (Bug#254)

- Fixed a bug when doing `LOAD DATA INFILE IGNORE`: When reading the binary log, mysqlbinlog and the replication code read `REPLACE` instead of `IGNORE`. This could make the slave's table become different from the master's table. (Bug#218)

- Fixed a deadlock when `relay_log_space_limit` was set to a too small value. (Bug#79)

- Fixed a bug in HAVING clause when an alias is used from the select list.

- Fixed overflow bug in `MyISAM` when a row is inserted into a table with a large number of columns and at least one `BLOB/TEXT` column. Bug was caused by incorrect calculation of the needed buffer to pack data.

- Fixed a bug when `SELECT` @non_existent_variable caused an error in the client/server protocol due to `net_printf()` output being sent to the client twice.

- Fixed a bug in setting `SQL_BIG_SELECTS` option.

- Fixed a bug in `SHOW PROCESSLIST` which only displayed a localhost in the `"Host"` column. This was caused by a glitch that used only current thread information instead of information from the linked list of threads.

- Removed unnecessary Mac OS X helper files from server RPM. (Bug#144)

- Allow optimization of multiple-table update for `InnoDB` tables as well.

- Fixed a bug in multiple-table updates that caused some rows to be updated several times.

- Fixed a bug in mysqldump when it was called with `--master-data`: the `CHANGE MASTER TO` commands appended to the SQL dump had incorrect coordinates. (Bug#159)

- Fixed a bug when an updating query using `USER()` was replicated on the slave; this caused a segmentation fault on the slave. (Bug#178). `USER()` is still badly replicated on the slave (it is replicated to `""`).

### B.2.20. Changes in release 4.0.12 (15 March 2003: Production)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- mysqld no longer reads options from world-writable config files. (CVE-2003-0150)

- Integer values between 9223372036854775807 and 9999999999999999999 are now regarded as unsigned longlongs, not as floats. This makes these values work similar to values between 10000000000000000000 and 18446744073709551615.

- `SHOW PROCESSLIST` now includes the client TCP port after the hostname to make it easier to know from which client the request originated.

- The `--new` option can be used to make a 4.0 server return `TIMESTAMP` as a string in `'YYYY-MM-DD HH:MM:SS'` format, the way that 4.1 servers do. This is also a `new` system variable that can be set for the same effect. See Section 10.3.1.1, “`TIMESTAMP` Properties Prior to MySQL 4.1”.

Bugs fixed:

- Fixed mysqld crash on extremely small values of `sort_buffer` variable.

- `INSERT INTO u SELECT ... FROM t` was written too late to the binary log if t was very frequently updated during the execution of this query. This could cause a problem with mysqlbinlog or replication. The master must be upgraded, not the slave. (Bug#136)

- Fixed checking of random part of `WHERE` clause. (Bug#142)

- Fixed a bug with multiple-table updates with `InnoDB` tables. This bug occurred as, in many cases, `InnoDB` tables cannot be updated “on the fly,” but offsets to the records have to be stored in a temporary table.

- Added missing file mysql_secure_installation to the `server` RPM subpackage. (Bug#141)

- Fixed MySQL (and myisamchk) crash on artificially corrupted `.MYI` files.

- Don't allow `BACKUP TABLE` to overwrite existing files.

- Fixed a bug with multiple-table `UPDATE` statements when user had all privileges on the database where tables are located and there were any entries in `tables_priv` table, that is, `grant_option` was true.

- Fixed a bug that allowed a user with table or column grants on some table, `TRUNCATE` any table in the same database.

- Fixed deadlock when doing `LOCK TABLE` followed by `DROP TABLE` in the same thread. In this case one could still kill the thread with `KILL`.

- `LOAD DATA LOCAL INFILE` was not properly written to the binary log (hence not properly replicated). (Bug#82)

- `RAND()` entries were not read correctly by mysqlbinlog from the binary log which caused problems when restoring a table that was inserted with `RAND()`. `INSERT INTO t1 VALUES(RAND())`. In replication this worked okay.

- `SET SQL_LOG_BIN=0` was ignored for `INSERT DELAYED` queries. (Bug#104)

- `SHOW SLAVE STATUS` reported too old positions (columns `Relay_Master_Log_File` and `Exec_Master_Log_Pos`) for the last executed statement from the master, if this statement was the `COMMIT` of a transaction. The master must be upgraded for that, not the slave. (Bug#52)

- `LOAD DATA INFILE` was not replicated by the slave if `replicate_*_table` was set on the slave. (Bug#86)

- After `RESET SLAVE`, the coordinates displayed by `SHOW SLAVE STATUS` looked un-reset (although they were, but only internally). (Bug#70)

- Fixed query cache invalidation on `LOAD DATA`.

- Fixed memory leak on `ANALYZE` procedure with error.

- Fixed a bug in handling `CHAR(0)` columns that could cause incorrect results from the query.

- Fixed rare bug with incorrect initialization of `AUTO_INCREMENT` column, as a secondary column in a multi-column key (see Section 3.6.9, “Using `AUTO_INCREMENT`”), when data was inserted with `INSERT ... SELECT` or `LOAD DATA` into an empty table.

- On Windows, `STOP SLAVE` didn't stop the slave until the slave got one new command from the master (this bug has been fixed for MySQL 4.0.11 by releasing updated 4.0.11a Windows packages, which include this individual fix on top of the 4.0.11 sources). (Bug#69)

- Fixed a crash when no database was selected and `LOAD DATA` command was issued with full table name specified, including database prefix.

- Fixed a crash when shutting down replication on some platforms (for example, Mac OS X).

- Fixed a portability bug with `pthread_attr_getstacksize` on HP-UX 10.20 (Patch was also included in 4.0.11a sources).

- Fixed the `bigint` test to not fail on some platforms (for example, HP-UX and Tru64) due to different return values of the `atof()` function.

- Fixed the `rpl_rotate_logs` test to not fail on certain platforms (such as Mac OS X) due to a too-long file name (changed `slave-master-info.opt` to `.slave-mi`).

### B.2.21. Changes in release 4.0.11 (20 February 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- `NULL` is now sorted LAST if you use `ORDER BY ... DESC` (as it was before MySQL 4.0.2). This change was required to comply with the SQL standard. (The original change was made because we thought that standard SQL required `NULL` to be always sorted at the same position, but this was incorrect).

- Added `START TRANSACTION` (standard SQL syntax) as alias for `BEGIN`. This is recommended to use instead of `BEGIN` to start a transaction.

- Added `OLD_PASSWORD()` as a synonym for `PASSWORD()`.

- Allow keyword `ALL` in group functions.

- Added support for some new `INNER JOIN` and `JOIN` syntaxes. For example, `SELECT * FROM t1 INNER JOIN t2` didn't work before.

- Novell NetWare 6.0 porting effort completed, Novell patches merged into the main source tree.

Bugs fixed:

- Fixed problem with multiple-table delete and `InnoDB` tables.

- Fixed a problem with `BLOB NOT NULL` columns used with `IS NULL`.

- Re-added missing pre- and post(un)install scripts to the Linux RPM packages (they were missing after the renaming of the server subpackage).

- Fixed that table locks are not released with multiple-table updates and deletes with `InnoDB` storage engine.

- Fixed bug in updating `BLOB` columns with long strings.

- Fixed integer-wraparound when giving big integer (>= 10 digits) to function that requires an unsigned argument, like `CREATE TABLE (...) AUTO_INCREMENT=`N``.

- `MIN(key_column)` could in some cases return `NULL` on a column with `NULL` and other values.

- `MIN(key_column)` and `MAX(key_column)` could in some cases return incorrect values when used in `OUTER JOIN`.

- `MIN(key_column)` and `MAX(key_column)` could return incorrect values if one of the tables was empty.

- Fixed rare crash in compressed `MyISAM` tables with blobs.

- Fixed bug in using aggregate functions as argument for `INTERVAL`, `CASE`, `FIELD`, `CONCAT_WS`, `ELT` and `MAKE_SET` functions.

- When running with `--lower-case-table-names` (default on Windows) and you had tables or databases with mixed case on disk, then executing `SHOW TABLE STATUS` followed with `DROP DATABASE` or `DROP TABLE` could fail with `Errcode 13`.

### B.2.22. Changes in release 4.0.10 (29 January 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Added option `--log-error[=`file_name`]` to mysqld_safe and mysqld. This option forces all error messages to be put in a log file if the option `--console` is not given. On Windows `--log-error` is enabled as default, with a default name of ``host_name`.err` if the name is not specified.

- Changed some messages from `Warning:` to `Note:` in the log files.

- The mysqld server should now compile on NetWare.

- Added optimization that if one does `GROUP BY ... ORDER BY NULL` then result is not sorted.

- New `--ft-stopword-file` command-line option for mysqld to replace/disable the built-in stopword list that is used in full-text searches. See Section 5.1.3, “System Variables”.

- Changed default stack size from 64KB to 192KB; This fixes a core dump problem on Red Hat 8.0 and other systems with a `glibc` that requires a stack size larger than 128K for `gethostbyaddr()` to resolve a hostname. You can fix this for earlier MySQL versions by starting mysqld with `--thread-stack=192K`.

- Added mysql_waitpid to the binary distribution and the `MySQL-client` RPM subpackage (required for mysql-test-run).

- Renamed the main `MySQL` RPM package to `MySQL-server`. When updating from an older version, `MySQL-server.rpm` simply replaces `MySQL.rpm`.

- If a slave is configured with `replicate_wild_do_table=db.%` or `replicate_wild_ignore_table=db.%`, these rules are applied to `CREATE/DROP DATABASE`, too.

- Added timeout value for `MASTER_POS_WAIT()`.

Bugs fixed:

- Fixed initialization of the random seed for newly created threads to give a better `rand()` distribution from the first call.

- Fixed a bug that caused mysqld to hang when a table was opened with the `HANDLER` command and then dropped without being closed.

- Fixed bug in logging to binary log (which affects replication) a query that inserts a `NULL` in an `AUTO_INCREMENT` column and also uses `LAST_INSERT_ID()`.

- Fixed an unlikely bug that could cause a memory overrun when using `ORDER BY constant_expression`.

- Fixed a table corruption in myisamchk parallel repair mode.

- Fixed bug in query cache invalidation on simple table renaming.

- Fixed bug in mysqladmin --relative.

- On some 64-bit systems, `show status` reported a strange number for `Open_files` and `Open_streams`.

- Fixed incorrect number of columns in `EXPLAIN` on empty table.

- Fixed bug in `LEFT JOIN` that caused zero rows to be returned in the case the `WHERE` condition was evaluated as `FALSE` after reading `const` tables. (Unlikely condition).

- `FLUSH PRIVILEGES` didn't correctly flush table/column privileges when `mysql.tables_priv` is empty.

- Fixed bug in replication when using `LOAD DATA INFILE` one a file that updated an `AUTO_INCREMENT` column with `NULL` or `0`. This bug only affected MySQL 4.0 masters (not slaves or MySQL 3.23 masters).

  ### Note

  If you have a slave that has replicated a file with generated `AUTO_INCREMENT` columns, the slave data is corrupted and you should reinitialize the affected tables from the master.

- Fixed possible memory overrun when sending a `BLOB` value larger than 16M to the client.

- Fixed incorrect error message when setting a `NOT NULL` column to an expression that returned `NULL`.

- Fixed core dump bug in ``str` LIKE "%`other_str`%"` where `str` or `other_str` contained characters >= 128.

- Fixed bug: When executing on master `LOAD DATA` and `InnoDB` failed with `table full` error the binary log was corrupted.

### B.2.23. Changes in release 4.0.9 (09 January 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- `OPTIMIZE TABLE` for `MyISAM` tables treats all `NULL` values as different when calculating cardinality. This helps in optimizing joins between tables where one of the tables has a lot of `NULL` values in a indexed column:

      SELECT * from t1, t2 where t1.a=t2.key_with_a_lot_of_null;

- Added join operator `FORCE INDEX (index_list)`. This acts likes `USE INDEX (index_list)` but with the addition that a table scan is assumed to be VERY expensive. One bad thing with this is that it makes `FORCE` a reserved word.

- Reset internal row buffer in `MyISAM` after each query. This reduces memory in case you have a lot of big blobs in a table.

Bugs fixed:

- A security patch in 4.0.8 causes the mysqld server to die if the remote hostname can't be resolved. This is now fixed.

- Fixed crash when replication big `LOAD DATA INFILE` statement that caused log rotation.

### B.2.24. Changes in release 4.0.8 (07 January 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Default `max_packet_length` for `libmysqld.c` is now 1024*1024*1024.

- You can now specify `max_allowed_packet` in a file read by `mysql_options(MYSQL_READ_DEFAULT_FILE)`. for clients.

- When sending a too big packet to the server with the not compressed protocol, the client now gets an error message instead of a lost connection.

- We now send big queries/result rows in bigger hunks, which should give a small speed improvement.

- Fixed some bugs with the compressed protocol for rows > 16MB.

- `InnoDB` tables now also support `ON UPDATE CASCADE` in `FOREIGN KEY` constraints. See the `InnoDB` section in the manual for the `InnoDB` changelog.

Bugs fixed:

- Fixed bug in `ALTER TABLE` with `BDB` tables.

- Fixed core dump bug in `QUOTE()` function.

- Fixed a bug in handling communication packets bigger than 16MB. Unfortunately this required a protocol change; If you upgrade the server to 4.0.8 and above and have clients that use packets >= 255*255*255 bytes (=16581375) you must also upgrade your clients to at least 4.0.8. If you don't upgrade, the clients hang when sending a big packet.

- Fixed bug when sending blobs longer than 16MB to client.

- Fixed bug in `GROUP BY` when used on BLOB column with `NULL` values.

- Fixed a bug in handling `NULL` values in `CASE` ... WHEN ...

### B.2.25. Changes in release 4.0.7 (20 December 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- mysqlbug now also reports the compiler version used for building the binaries (if the compiler supports the option `--version`).

Bugs fixed:

- Fixed compilation problems on OpenUnix and HPUX 10.20.

- Fixed some optimization problems when compiling MySQL with `-DBIG_TABLES` on a 32-bit system.

- `mysql_drop_db()` didn't check permissions properly so anyone could drop another users database. `DROP DATABASE` is checked properly.

### B.2.26. Changes in release 4.0.6 (14 December 2002: Gamma)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Added syntax support for `CHARACTER SET `xxx`` and `CHARSET=`xxx`` table options (to be able to read table dumps from 4.1).

- Fixed replication bug that caused the slave to loose its position in some cases when the replication log was rotated.

- Fixed that a slave restarts from the start of a transaction if it's killed in the middle of one.

- Moved the manual pages from `man` to `man/man1` in the binary distributions.

- The default type returned by `IFNULL(A,B)` is now set to be the more 'general' of the types of `A` and `B`. (The order is `STRING`, `REAL` or `INTEGER`).

- Moved the mysql.server startup script in the RPM packages from `/etc/rc.d/init.d/mysql` to `/etc/init.d/mysql` (which almost all current Linux distributions support for LSB compliance).

- Added `Qcache_lowmem_prunes` status variable (number of queries that were deleted from the cache because of low memory).

- Fixed mysqlcheck so it can deal with table names containing dashes.

- Bulk insert optimization (see Section 5.1.3, “System Variables”) is no longer used when inserting small (less than 100) number of rows.

- Optimization added for queries like `SELECT ... FROM `merge_table` WHERE `indexed_column`=`constant_expr``.

- Added functions `LOCALTIME` and `LOCALTIMESTAMP` as synonyms for `NOW()`.

- `CEIL` is now an alias for `CEILING`.

- The `CURRENT_USER()` function can be used to get a `user@host` value as it was matched in the `GRANT` system. See Section 11.10.3, “Information Functions”.

- Fixed `CHECK` constraints to be compatible with standard SQL. This made `CHECK` a reserved word. (Checking of `CHECK` constraints is still not implemented).

- Added `CAST(... as CHAR)`.

- Added PostgreSQL compatible `LIMIT` syntax: `SELECT ... LIMIT `row_count` OFFSET `offset``

- `mysql_change_user()` now resets the connection to the state of a fresh connect (Ie, `ROLLBACK` any active transaction, close all temporary tables, reset all user variables etc..)

- `CHANGE MASTER` and `RESET SLAVE` now require that slave threads both be stopped; these commands return an error if at least one of these two threads is running.

Bugs fixed:

- Fixed number of found rows returned in `multi table updates`

- Make `--lower-case-table-names` default on Mac OS X as the default filesystem (HFS+) is case insensitive. See Section 8.2.2, “Identifier Case Sensitivity”.

- Transactions in `AUTOCOMMIT=0` mode didn't rotate binary log.

- A fix for the bug in a `SELECT` with joined tables with `ORDER BY` and `LIMIT` clause when `filesort` had to be used. In that case `LIMIT` was applied to `filesort` of one of the tables, although it could not be. This fix also solved problems with `LEFT JOIN`.

- `mysql_server_init()` now makes a copy of all arguments. This fixes a problem when using the embedded server in C# program.

- Fixed buffer overrun in `libmysqlclient` library that allowed a malicious MySQL server to crash the client application. (CVE-2002-1376)

- Fixed security-related bug in `mysql_change_user()` handling. All users are strongly recommended to upgrade to version 4.0.6. (CVE-2002-1374, CVE-2002-1375)

- Fixed bug that prevented `--chroot` command-line option of mysqld from working.

- Fixed bug in phrase operator `"..."` in boolean full-text search.

- Fixed bug that caused `OPTIMIZE TABLE` to corrupt the table under some rare circumstances.

- Part rewrite of multiple-table-update to optimize it, make it safer and more bug-free.

- `LOCK TABLES` now works together with multiple-table-update and multiple-table-delete.

- `--replicate-do=`xxx`` didn't work for `UPDATE` commands. (Bug introduced in 4.0.0)

- Fixed shutdown problem on Mac OS X.

- Major `InnoDB` bugs in `REPLACE, AUTO_INCREMENT, INSERT INTO ... SELECT ...` were fixed. See the `InnoDB` changelog in the `InnoDB` section of the manual.

- `RESET SLAVE` caused a crash if the slave threads were running.

### B.2.27. Changes in release 4.0.5 (13 November 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

- Port number was added to hostname (if it is known) in `SHOW PROCESSLIST` command

- Changed handling of last argument in `WEEK()` so that you can get week number according to the ISO 8601 specification. (Old code should still work).

- Fixed that `INSERT DELAYED` threads don't hang on `Waiting for INSERT` when one sends a `SIGHUP` to mysqld.

- Change that `AND` works according to standard SQL when it comes to `NULL` handling. In practice, this affects only queries where you do something like `WHERE ... NOT (NULL AND 0)`.

- mysqld now resolves `basedir` to its full path (with `realpath()`). This enables one to use relative symlinks to the MySQL installation directory. This however causes `show variables` to report different directories on systems where there is a symbolic link in the path.

- Fixed that MySQL does not use index scan on index disabled with `IGNORE INDEX` or `USE INDEX`. to be ignored.

- Added `--use-frm` option to mysqlcheck. When used with `REPAIR TABLE`, it gets the table structure from the `.frm` file, so the table can be repaired even if the `.MYI` header is corrupted.

- Fixed bug in `MAX()` optimization when used with `JOIN` and `ON` expressions.

- Added support for reading of MySQL 4.1 table definition files.

- `BETWEEN` behavior changed (see Section 11.2.3, “Comparison Functions and Operators”). Now `datetime_col BETWEEN timestamp AND timestamp` should work as expected.

- One can create `TEMPORARY` `MERGE` tables now.

- `DELETE FROM myisam_table` now shrinks not only the `.MYD` file but also the `.MYI` file.

- When one uses the `--open-files-limit=`val`` option to mysqld_safe it's now passed on to mysqld.

- Changed output from `EXPLAIN` from `'where used'` to `'Using where'` to make it more in line with other output.

- Removed variable `safe_show_database` as it was no longer used.

- Updated source tree to be built using automake 1.5 and libtool 1.4.

- Fixed an inadvertently changed option (`--ignore-space`) back to the original `--ignore-spaces` in `mysqlclient`. (Both syntaxes work).

- Don't require `UPDATE` privilege when using `REPLACE`.

- Added support for `DROP TEMPORARY TABLE ...`, to be used to make replication safer.

- When transactions are enabled, all commands that update temporary tables inside a `BEGIN/COMMIT` are now stored in the binary log on `COMMIT` and not stored if one does `ROLLBACK`. This fixes some problems with non-transactional temporary tables used inside transactions.

- Allow braces in joins in all positions. Formerly, things like `SELECT * FROM (t2 LEFT JOIN t3 USING (a)), t1` worked, but not `SELECT * FROM t1, (t2 LEFT JOIN t3 USING (a))`. Note that braces are simply removed, they do not change the way the join is executed.

- `InnoDB` now supports also isolation levels `READ UNCOMMITTED` and `READ COMMITTED`. For a detailed `InnoDB` changelog, see Section B.4, “Changes in `InnoDB`”.

Bugs fixed:

- Fixed bug in `MAX()` optimization when used with `JOIN` and `ON` expressions.

- Fixed that `INSERT DELAY` threads don't hang on `Waiting for INSERT` when one sends a `SIGHUP` to mysqld.

- Fixed that MySQL does not use an index scan on an index that has been disabled with `IGNORE INDEX` or `USE INDEX`.

- Corrected test for `root` user in mysqld_safe.

- Fixed error message issued when storage engine cannot do `CHECK TABLE` or `REPAIR TABLE`.

- Fixed rare core dump problem in complicated `GROUP BY` queries that didn't return any result.

- Fixed mysqlshow to work properly with wildcarded database names and with database names that contain underscores.

- Portability fixes to get MySQL to compile cleanly with Sun Forte 5.0.

- Fixed `MyISAM` crash when using dynamic-row tables with huge numbers of packed columns.

- Fixed query cache behavior with `BDB` transactions.

- Fixed possible floating point exception in `MATCH` relevance calculations.

- Fixed bug in full-text search `IN BOOLEAN MODE` that made `MATCH` to return incorrect relevance value in some complex joins.

- Fixed a bug that limited `MyISAM` key length to a value slightly less that 500. It is exactly 500 now.

- Fixed that `GROUP BY` on columns that may have a `NULL` value doesn't always use disk based temporary tables.

- The filename argument for the `--des-key-file` argument to mysqld is interpreted relative to the data directory if given as a relative pathname.

- Removed a condition that temp table with index on column that can be `NULL` has to be `MyISAM`. This was okay for 3.23, but not needed in 4.*. This resulted in slowdown in many queries since 4.0.2.

- Small code improvement in multiple-table updates.

- Fixed a newly introduced bug that caused `ORDER BY ... LIMIT `row_count`` to not return all rows.

- Fixed a bug in multiple-table deletes when outer join is used on an empty table, which gets first to be deleted.

- Fixed a bug in multiple-table updates when a single table is updated.

- Fixed bug that caused `REPAIR TABLE` and myisamchk to corrupt `FULLTEXT` indexes.

- Fixed bug with caching the `mysql` grant table database. Now queries in this database are not cached in the query cache.

- Small fix in mysqld_safe for some shells.

- Give error if a `MyISAM` `MERGE` table has more than 232 rows and MySQL was not compiled with `-DBIG_TABLES`.

- Fixed some `ORDER BY ... DESC` problems with `InnoDB` tables.

### B.2.28. Changes in release 4.0.4 (29 September 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed bug where `GRANT`/`REVOKE` failed if hostname was given in non-matching case.

- Don't give warning in `LOAD DATA INFILE` when setting a `timestamp` to a string value of `'0'`.

- Fixed bug in myisamchk -R mode.

- Fixed bug that caused mysqld to crash on `REVOKE`.

- Fixed bug in `ORDER BY` when there is a constant in the `SELECT` statement.

- One didn't get an error message if mysqld couldn't open the privilege tables.

- `SET PASSWORD FOR ...` closed the connection in case of errors (bug from 4.0.3).

- Increased maximum possible `max_allowed_packet` in mysqld to 1GB.

- Fixed bug when doing a multiple-row `INSERT` on a table with an `AUTO_INCREMENT` key which was not in the first part of the key.

- Changed `LOAD DATA INFILE` to not re-create index if the table had rows from before.

- Fixed overrun bug when calling `AES_DECRYPT()` with incorrect arguments.

- `--skip-ssl` can now be used to disable SSL in the MySQL clients, even if one is using other SSL options in an option file or previously on the command line.

- Fixed bug in `MATCH ... AGAINST( ... IN BOOLEAN MODE)` used with `ORDER BY`.

- Added `LOCK TABLES` and `CREATE TEMPORARY TABLES` privilege on the database level. You must run the mysql_fix_privilege_tables script on old installations to activate these.

- In `SHOW TABLE ... STATUS`, compressed tables sometimes showed up as `dynamic`.

- `SELECT @@[global|session].`var_name`` didn't report `global | session` in the result column name.

- Fixed problem in replication that `FLUSH LOGS` in a circular replication setup created an infinite number of binary log files. Now a `rotate-binary-log` command in the binary log does not cause slaves to rotate logs.

- Removed `STOP EVENT` from binary log when doing `FLUSH LOGS`.

- Disable the use of `SHOW NEW MASTER FOR SLAVE` as this needs to be completely reworked in a future release.

- Fixed a bug with constant expression (for example, column of a one-row table, or column from a table, referenced by a `UNIQUE` key) appeared in `ORDER BY` part of `SELECT DISTINCT`.

- `--log-binary=a.b.c` now properly strips off `.b.c`.

- `FLUSH LOGS` removed numerical extension for all future update logs.

- `GRANT ... REQUIRE` didn't store the SSL information in the `mysql.user` table if SSL was not enabled in the server.

- `GRANT ... REQUIRE NONE` can now be used to remove SSL information.

- `AND` is now optional between `REQUIRE` options.

- `REQUIRE` option was not properly saved, which could cause strange output in `SHOW GRANTS`.

- Fixed that mysqld --help reports correct values for `--datadir` and `--bind-address`.

- Fixed that one can drop UDFs that didn't exist when mysqld was started.

- Fixed core dump problem with `SHOW VARIABLES` on some 64-bit systems (like Solaris SPARC).

- Fixed a bug in `my_getopt()`; `--set-variable` syntax didn't work for those options that didn't have a valid variable in the `my_option` struct. This affected at least the `default-table-type` option.

- Fixed a bug from 4.0.2 that caused `REPAIR TABLE` and myisamchk --recover to fail on tables with duplicates in a unique key.

- Fixed a bug from 4.0.3 in calculating the default data type for some functions. This affected queries of type `CREATE TABLE `tbl_name` SELECT `expression`(),...`

- Fixed bug in queries of type `SELECT * FROM table-list GROUP BY ...` and `SELECT DISTINCT * FROM ...`.

- Fixed bug with the `--slow-log` when logging an administrator command (like `FLUSH TABLES`).

- Fixed a bug that `OPTIMIZE TABLE` of locked and modified table, reported table corruption.

- Fixed a bug in `my_getopt()` in handling of special prefixes (`--skip-`, `--enable-`). `--skip-external-locking` didn't work and the bug may have affected other similar options.

- Fixed bug in checking for output file name of the `tee` option.

- Added some more optimization to use index for `SELECT ... FROM many_tables .. ORDER BY key limit #`

- Fixed problem in `SHOW OPEN TABLES` when a user didn't have access permissions to one of the opened tables.

### B.2.29. Changes in release 4.0.3 (26 August 2002: Beta)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed problem with types of user variables. (Bug#551)

- Fixed problem with `configure ... --localstatedir=...`.

- Cleaned up mysql.server script.

- Fixed a bug in mysqladmin shutdown when pid file was modified while mysqladmin was still waiting for the previous one to disappear. This could happen during a very quick restart and caused mysqladmin to hang until `shutdown_timeout` seconds had passed.

- Don't increment warnings when setting `AUTO_INCREMENT` columns to `NULL` in `LOAD DATA INFILE`.

- Fixed all boolean type variables/options to work with the old syntax, for example, all of these work: `--lower-case-table-names`, `--lower-case-table-names=1`, `-O lower-case-table-names=1`, `--set-variable=lower-case-table-names=1`

- Fixed shutdown problem (SIGTERM signal handling) on Solaris. (Bug from 4.0.2).

- `SHOW MASTER STATUS` now returns an empty set if binary log is not enabled.

- `SHOW SLAVE STATUS` now returns an empty set if slave is not initialized.

- Don't update `MyISAM` index file on update if not strictly necessary.

- Fixed bug in `SELECT DISTINCT ... FROM many_tables ORDER BY not-used-column`.

- Fixed a bug with `BIGINT` values and quoted strings.

- Added `QUOTE()` function that performs SQL quoting to produce values that can be used as data values in queries.

- Changed variable `DELAY_KEY_WRITE` to an enumeration to allow it to be set for all tables without taking down the server.

- Changed behavior of `IF(condition,column,NULL)` so that it returns the value in the column's data type.

- Made safe_mysqld a symlink to mysqld_safe in binary distribution.

- Fixed security bug when having an empty database name in the `user.db` table.

- Fixed some problems with `CREATE TABLE ... SELECT function()`.

- mysqld now has the option `--temp-pool` enabled by default as this gives better performance with some operating systems.

- Fixed problem with too many allocated alarms on slave when connecting to master many times (normally not a very critical error).

- Fixed hang in `CHANGE MASTER TO` if the slave thread died very quickly.

- Big cleanup in replication code (less logging, better error messages, etc..)

- If the `--code-file` option is specified, the server calls `setrlimit()` to set the maximum allowed core file size to unlimited, so core files can be generated.

- Fixed bug in query cache after temporary table creation.

- Added `--count=`N`` (`-c`) option to mysqladmin, to make the program do only `N` iterations. To be used with `--sleep` (`-i`). Useful in scripts.

- Fixed bug in multiple-table `UPDATE`: when updating a table, `do_select()` became confused about reading records from a cache.

- Fixed bug in multiple-table `UPDATE` when several columns were referenced from a single table

- Fixed bug in truncating non-existing table.

- Fixed bug in `REVOKE` that caused user resources to be randomly set.

- Fixed bug in `GRANT` for the new `CREATE TEMPORARY TABLE` privilege.

- Fixed bug in multiple-table `DELETE` when tables are re-ordered in the table initialization method and ref_lengths are of different sizes.

- Fixed two bugs in `SELECT DISTINCT` with large tables.

- Fixed bug in query cache initialization with very small query cache size.

- Allow `DEFAULT` with `INSERT` statement.

- The startup parameters `myisam_max_sort_file_size` and `myisam_max_extra_sort_file_size` are now given in bytes, not megabytes.

- External system locking of `MyISAM`/`ISAM` files is now turned off by default. One can turn this on with `--external-locking`. (For most users this is never needed).

- Fixed core dump bug with `INSERT ... SET `db_name.tbl_name.col_name`=''`.

- Fixed client hangup bug when using some SQL statements with incorrect syntax.

- Fixed a timing bug in `DROP DATABASE`

- New `SET [GLOBAL | SESSION]` syntax to change thread-specific and global system variables at runtime.

- Added variable `slave_compressed_protocol`.

- Renamed variable `query_cache_startup_type` to `query_cache_type`, `myisam_bulk_insert_tree_size` to `bulk_insert_buffer_size`, `record_buffer` to `read_buffer_size` and `record_rnd_buffer` to `read_rnd_buffer_size`.

- Renamed some SQL variables, but old names still work until 5.0. See Section 2.11.2, “Upgrading from MySQL 3.23 to 4.0”.

- Renamed `--skip-locking` to `--skip-external-locking`.

- Removed unused variable `query_buffer_size`.

- Fixed a bug that made the pager option in the mysql client non-functional.

- Added full `AUTO_INCREMENT` support to `MERGE` tables.

- Extended `LOG()` function to accept an optional arbitrary base parameter. See Section 11.5.2, “Mathematical Functions”.

- Added `LOG2()` function (useful for finding out how many bits a number would require for storage).

- Added `LN()` natural logarithm function for compatibility with other databases. It is synonymous with `LOG(`X`)`.

### B.2.30. Changes in release 4.0.2 (01 July 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Cleaned up `NULL` handling for default values in `DESCRIBE tbl_name`.

- Fixed `TRUNCATE()` to round up negative values to the nearest integer.

- Fixed buffer overflow problem if someone specified a too-long `datadir` parameter to mysqld. (CVE-2002-0969)

- Changed `--chroot=`path`` option to execute `chroot()` immediately after all options have been parsed.

- Don't allow database names that contain “`\`”.

- `lower_case_table_names` now also applies to database names.

- Added `XOR` operator (logical and bitwise `XOR`) with `^` as a synonym for bitwise `XOR`.

- Added function `IS_FREE_LOCK('`lock_name`')`. Based on code contributed by Hartmut Holzgraefe `<hartmut@six.de>`.

- Removed `mysql_ssl_clear()` from C API, as it was not needed.

- `DECIMAL` and `NUMERIC` types can now read exponential numbers.

- Added `SHA1()` function to calculate 160 bit hash value as described in RFC 3174 (Secure Hash Algorithm). This function can be considered a cryptographically more secure equivalent of `MD5()`. See Section 11.10.2, “Encryption and Compression Functions”.

- Added `AES_ENCRYPT()` and `AES_DECRYPT()` functions to perform encryption according to AES standard (Rijndael). See Section 11.10.2, “Encryption and Compression Functions”.

- Added `--single-transaction` option to mysqldump, allowing a consistent dump of `InnoDB` tables. See Section 4.5.4, “mysqldump — A Database Backup Program”.

- Fixed bug in `innodb_log_group_home_dir` in `SHOW VARIABLES`.

- Fixed a bug in optimizer with merge tables when non-unique values are used in summing up (causing crashes).

- Fixed a bug in optimizer when a range specified makes index grouping impossible (causing crashes).

- Fixed a rare bug when `FULLTEXT` index is present and no tables are used.

- Added privileges `CREATE TEMPORARY TABLES`, `EXECUTE`, `LOCK TABLES`, `REPLICATION CLIENT`, `REPLICATION SLAVE`, `SHOW DATABASES` and `SUPER`. To use these, you must have run the mysql_fix_privilege_tables script after upgrading.

- Fixed query cache align data bug.

- Fixed mutex bug in replication when reading from master fails.

- Added missing mutex in `TRUNCATE TABLE`. This fixes some core dump/hangup problems when using `TRUNCATE TABLE`.

- Fixed bug in multiple-table `DELETE` when optimizer uses only indexes.

- Fixed that `ALTER TABLE `tbl_name` RENAME `new_tbl_name`` is as fast as `RENAME TABLE`.

- Fixed bug in `GROUP BY` with two or more columns, where at least one column can contain `NULL` values.

- Use Turbo Boyer-Moore algorithm to speed up `LIKE "%keyword%"` searches.

- Fixed bug in `DROP DATABASE` with symlink.

- Fixed crash in `REPAIR ... USE_FRM`.

- Fixed bug in `EXPLAIN` with `LIMIT offset != 0`.

- Fixed bug in phrase operator `"..."` in boolean full-text search.

- Fixed bug that caused duplicated rows when using truncation operator `*` in boolean full-text search.

- Fixed bug in truncation operator of boolean full-text search (incorrect results when there are only `+word*`s in the query).

- Fixed bug in boolean full-text search that caused a crash when an identical `MATCH` expression that did not use an index appeared twice.

- Query cache is now automatically disabled in mysqldump.

- Fixed problem on Windows 98 that made sending of results very slow.

- Boolean full-text search weighting scheme changed to something more reasonable.

- Fixed bug in boolean full-text search that caused MySQL to ignore queries of `ft_min_word_len` characters.

- Boolean full-text search now supports “phrase searches.”

- New configure option `--without-query-cache`.

- Memory allocation strategy for “root memory” changed. Block size now grows with number of allocated blocks.

- `INET_NTOA()` now returns `NULL` if you give it an argument that is too large (greater than the value corresponding to `255.255.255.255`).

- Fix `SQL_CALC_FOUND_ROWS` to work with `UNION`. It works only if the first `SELECT` has this option and if there is global `LIMIT` for the entire statement. For the moment, this requires using parentheses for individual `SELECT` queries within the statement.

- Fixed bug in `SQL_CALC_FOUND_ROWS` and `LIMIT`.

- Don't give an error for `CREATE TABLE ...(... VARCHAR(0))`.

- Fixed `SIGINT` and `SIGQUIT` problems in `mysql.cc` on Linux with some `glibc` versions.

- Fixed bug in `convert.cc`, which is caused by having an incorrect `net_store_length()` linked in the `CONVERT::store()` method.

- `DOUBLE` and `FLOAT` columns now honor the `UNSIGNED` flag on storage.

- `InnoDB` now retains foreign key constraints through `ALTER TABLE` and `CREATE/DROP INDEX`.

- `InnoDB` now allows foreign key constraints to be added through the `ALTER TABLE` syntax.

- `InnoDB` tables can now be set to automatically grow in size (auto-extend).

- Added `--ignore-lines=`n`` option to mysqlimport. This has the same effect as the `IGNORE n LINES` clause for `LOAD DATA`.

- Fixed bug in `UNION` with last offset being transposed to total result set.

- `REPAIR ... USE_FRM` added.

- Fixed that `DEFAULT_SELECT_LIMIT` is always imposed on `UNION` result set.

- Fixed that some `SELECT` options can appear only in the first `SELECT`.

- Fixed bug with `LIMIT` with `UNION`, where last select is in the braces.

- Fixed that full-text works fine with `UNION` operations.

- Fixed bug with indexless boolean full-text search.

- Fixed bug that sometimes appeared when full-text search was used with `const` tables.

- Fixed incorrect error value when doing a `SELECT` with an empty `HEAP` table.

- Use `ORDER BY column DESC` now sorts `NULL` values first. (In other words, `NULL` values sort first in all cases, whether or not `DESC` is specified.) This is changed back in 4.0.10.

- Fixed bug in `WHERE key_name='constant' ORDER BY key_name DESC`.

- Fixed bug in `SELECT DISTINCT ... ORDER BY DESC` optimization.

- Fixed bug in `... HAVING 'GROUP_FUNCTION'(`xxx`) IS [NOT] NULL`.

- Fixed bug in truncation operator for boolean full-text search.

- Allow value of `--user` option for mysqld to be specified as a numeric user ID (`--user=`user_id``).

- Fixed a bug where `SQL_CALC_ROWS` returned an incorrect value when used with one table and `ORDER BY` and with `InnoDB` tables.

- Fixed that `SELECT 0 LIMIT 0` doesn't hang thread.

- Fixed some problems with `USE/IGNORE INDEX` when using many keys with the same start column.

- Don't use table scan with `BerkeleyDB` and `InnoDB` tables when we can use an index that covers the whole row.

- Optimized `InnoDB` sort-buffer handling to take less memory.

- Fixed bug in multiple-table `DELETE` and `InnoDB` tables.

- Fixed problem with `TRUNCATE` and `InnoDB` tables that produced the error `Can't execute the given command because you have active locked tables or an active transaction`.

- Added `NO_UNSIGNED_SUBTRACTION` to the set of flags that may be specified with the `--sql-mode` option for mysqld. It disables unsigned arithmetic rules when it comes to subtraction. (This makes MySQL 4.0 behave more like 3.23 with `UNSIGNED` columns).

- The result returned for all bit operators (`|`, `<<`, ...) is now of type `unsigned integer`.

- Added detection of `nan` values in `MyISAM` to make it possible to repair tables with `nan` in float or double columns.

- Fixed new bug in myisamchk where it didn't correctly update number of “parts” in the `MyISAM` index file.

- Changed to use autoconf 2.52 (from autoconf 2.13).

- Fixed optimization problem where the MySQL Server was in “preparing” state for a long time when selecting from an empty table which had contained a lot of rows.

- Fixed bug in complicated join with `const` tables. This fix also improves performance a bit when referring to another table from a `const` table.

- First pre-version of multiple-table `UPDATE` statement.

- Fixed bug in multiple-table `DELETE`.

- Fixed bug in `SELECT CONCAT(argument_list) ... GROUP BY 1`.

- `INSERT ... SELECT` did a full rollback in case of an error. Fixed so that we only roll back the last statement in the current transaction.

- Fixed bug with empty expression for boolean full-text search.

- Fixed core dump bug in updating full-text key from/to `NULL`.

- ODBC compatibility: Added `BIT_LENGTH()` function.

- Fixed core dump bug in `GROUP BY BINARY column`.

- Added support for `NULL` keys in `HEAP` tables.

- Use index for `ORDER BY` in queries of type: `SELECT * FROM t WHERE key_part1=1 ORDER BY key_part1 DESC, key_part2 DESC`

- Fixed bug in `FLUSH QUERY CACHE`.

- Added `CAST()` and `CONVERT()` functions. The `CAST` and `CONVERT` functions are nearly identical and mainly useful when you want to create a column with a specific type in a `CREATE ... SELECT` statement. For more information, read Section 11.9, “Cast Functions and Operators”.

- `CREATE ... SELECT` on `DATE` and `TIME` functions now create columns of the expected type.

- Changed order in which keys are created in tables.

- Added new columns `Null` and `Index_type` to `SHOW INDEX` output.

- Added `--no-beep` and `--prompt` options to mysql command-line client.

- New feature: management of user resources.

      GRANT ... WITH MAX_QUERIES_PER_HOUR N1
                     MAX_UPDATES_PER_HOUR N2
                     MAX_CONNECTIONS_PER_HOUR N3;

  See Section 5.6.4, “Limiting Account Resources”.

- Added mysql_secure_installation to the `scripts/` directory.

### B.2.31. Changes in release 4.0.1 (23 December 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `system` command to mysql.

- Fixed bug when `HANDLER` was used with some unsupported table type.

- mysqldump now puts `ALTER TABLE `tbl_name` DISABLE KEYS` and `ALTER TABLE `tbl_name` ENABLE KEYS` in the sql dump.

- Added mysql_fix_extensions script.

- Fixed stack overrun problem with `LOAD DATA FROM MASTER` on OSF/1.

- Fixed shutdown problem on HP-UX.

- Added `DES_ENCRYPT()` and `DES_DECRYPT()` functions.

- Added `FLUSH DES_KEY_FILE` statement.

- Added `--des-key-file` option to mysqld.

- `HEX(`str`)` now returns the characters in `str` converted to hexadecimal.

- Fixed problem with `GRANT` when using `lower_case_table_names=1`.

- Changed `SELECT ... IN SHARE MODE` to `SELECT ... LOCK IN SHARE MODE` (as in MySQL 3.23).

- A new query cache to cache results from identical `SELECT` queries.

- Fixed core dump bug on 64-bit machines when it got an incorrect communication packet.

- `MATCH ... AGAINST(... IN BOOLEAN MODE)` can now work without `FULLTEXT` index.

- Fixed slave to replicate from 3.23 master.

- Miscellaneous replication fixes/cleanup.

- Got shutdown to work on Mac OS X.

- Added `myisam/ft_dump` utility for low-level inspection of `FULLTEXT` indexes.

- Fixed bug in `DELETE ... WHERE ... MATCH ...`.

- Added support for `MATCH ... AGAINST(... IN BOOLEAN MODE)`. Note that you must rebuild your tables with `ALTER TABLE `tbl_name` TYPE=MyISAM` to be able to use boolean full-text search.

- `LOCATE()` and `INSTR()` are now case sensitive if either argument is a binary string.

- Changed `RAND()` initialization so that `RAND(N)` and `RAND(N+1)` are more distinct.

- Fixed core dump bug in `UPDATE ... ORDER BY`.

- In 3.23, `INSERT INTO ... SELECT` always had `IGNORE` enabled. Now MySQL stops (and possibly rolls back) by default in case of an error unless you specify `IGNORE`.

- Ignore `DATA DIRECTORY` and `INDEX DIRECTORY` directives on Windows.

- Added boolean full-text search code. It should be considered early alpha.

- Extended `MODIFY` and `CHANGE` in `ALTER TABLE` to accept the `FIRST` and `AFTER` keywords.

- Indexes are now used with `ORDER BY` on a whole `InnoDB` table.

### B.2.32. Changes in release 4.0.0 (October 2001: Alpha)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `--xml` option to mysql for producing XML output.

- Added full-text variables `ft_min_word_len`, `ft_max_word_len`, and `ft_max_word_len_for_sort` system variables.

- Added full-text variables `ft_min_word_len`, `ft_max_word_len`, and `ft_max_word_len_for_sort` variables to myisamchk.

- Added documentation for `libmysqld`, the embedded MySQL server library. Also added example programs (a mysql client and mysqltest test program) which use `libmysqld`.

- Removed all Gemini hooks from MySQL server.

- Removed `my_thread_init()` and `my_thread_end()` from `mysql_com.h`, and added `mysql_thread_init()` and `mysql_thread_end()` to `mysql.h`.

- Support for communication packets > 16MB. In 4.0.1 we extended `MyISAM` to be able to handle these.

- Secure connections (with SSL).

- Unsigned `BIGINT` constants now work. `MIN()` and `MAX()` now handle signed and unsigned `BIGINT` numbers correctly.

- New character set `latin1_de` which provides correct German sorting.

- `STRCMP()` now uses the current character set when doing comparisons, which means that the default comparison behavior now is case insensitive.

- `TRUNCATE TABLE` and `DELETE FROM `tbl_name`` are now separate functions. One bonus is that `DELETE FROM `tbl_name`` now returns the number of deleted rows, rather than zero.

- `DROP DATABASE` now executes a `DROP TABLE` on all tables in the database, which fixes a problem with `InnoDB` tables.

- Added support for `UNION`.

- Added support for multiple-table `DELETE` operations.

- A new `HANDLER` interface to `MyISAM` tables.

- Added support for `INSERT` on `MERGE` tables. Patch from Benjamin Pflugmann.

- Changed `WEEK(date,0)` to match the calendar in the USA.

- `COUNT(DISTINCT)` is about 30% faster.

- Speed up all internal list handling.

- Speed up `IS NULL`, `ISNULL()` and some other internal primitives.

- Full-text index creation now is much faster.

- Tree-like cache to speed up bulk inserts and `myisam_bulk_insert_tree_size` variable.

- Searching on packed (`CHAR`/`VARCHAR`) keys is now much faster.

- Optimized queries of type: `SELECT DISTINCT * FROM `tbl_name` ORDER by `key_part1` LIMIT `row_count``.

- `SHOW CREATE TABLE` now shows all table attributes.

- `ORDER BY ... DESC` can now use keys.

- `LOAD DATA FROM MASTER` “automatically” sets up a slave.

- Renamed safe_mysqld to mysqld_safe to make this name more in line with other MySQL scripts/commands.

- Added support for symbolic links to `MyISAM` tables. Symlink handling is now enabled by default for Windows.

- Added `SQL_CALC_FOUND_ROWS` and `FOUND_ROWS()`. This makes it possible to know how many rows a query would have returned without a `LIMIT` clause.

- Changed output format of `SHOW OPEN TABLES`.

- Allow `SELECT expression LIMIT ...`.

- Added the `IDENTITY` variable as a synonym for the `LAST_INSERT_ID` variable (like Sybase).

- Added `ORDER BY` syntax to `UPDATE` and `DELETE`.

- `SHOW INDEXES` is now a synonym for `SHOW INDEX`.

- Added `ALTER TABLE `tbl_name` DISABLE KEYS` and `ALTER TABLE `tbl_name` ENABLE KEYS` commands.

- Allow use of `IN` as a synonym for `FROM` in `SHOW` commands.

- Implemented “repair by sort” for `FULLTEXT` indexes. `REPAIR TABLE`, `ALTER TABLE`, and `OPTIMIZE TABLE` for tables with `FULLTEXT` indexes are now up to 100 times faster.

- Allow standard SQL syntax `X'`hexadecimal-number`'`.

- Cleaned up global lock handling for `FLUSH TABLES WITH READ LOCK`.

- Fixed problem with `DATETIME = constant` in `WHERE` optimization.

- Added `--master-data` and `--no-autocommit` options to mysqldump. (Thanks to Brian Aker for this.)

- Added script mysql_explain_log.sh to distribution. (Thanks to mobile.de).

## B.3. Changes in release 3.23.x

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

The 3.23 release has several major features that are not present in previous versions. We have added three new table types:

- `MyISAM`

  A new `ISAM` library which is tuned for SQL and supports large files.

- `InnoDB`

  A transaction-safe storage engine that supports row level locking, and many Oracle-like features.

- `BerkeleyDB` or `BDB`

  Uses the Berkeley DB library from Sleepycat Software to implement transaction-safe tables.

Note that only `MyISAM` is available in the standard binary distribution.

The 3.23 release also includes support for database replication between a master and many slaves, full-text indexing, and much more.

All new features are being developed in the 4.1.x and 5.0.x versions. Only serious bugfixes are added to 3.23.

### B.3.1. Changes in release 3.23.59 (Not yet released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed an old bug in concurrent accesses to `MERGE` tables (even one `MERGE` table and `MyISAM` tables), that could've resulted in a crash or hang of the server. (Bug#2408, CVE-2004-0837)

- Fixed incorrect destruction of expression which led to crash of server on complex `AND`/`OR` expressions if query was ignored (either by a replication server because of `--replicate-*-table` rules, or by any MySQL server because of a syntax error). (Bug#3969, Bug#4494)

- Fixed problem with parsing complex queries on 64-bit architectures. (Bug#4204)

- Fixed a symlink vulnerability in the `mysqlbug` script. (Bug#3284, CVE-2004-0381)

- Fixed bug in privilege checking of `ALTER TABLE RENAME`. (Bug#3270, CVE-2004-0835)

- Fixed bugs in `ACOS()`, `ASIN()` (Bug#2338) and in `FLOOR()` (Bug#3051). The cause of the problem is an overly strong optimization done by gcc in this case.

- Fixed bug in `INSERT ... SELECT` statements where, if a `NOT NULL` column is assigned a value of `NULL`, the following columns in the row might be assigned a value of zero. (Bug#2012)

- If a query was ignored on the slave (because of `--replicate-ignore-table` and other similar rules), the slave still checked if the query got the same error code (0, no error) as on the master. So if the master had an error on the query (for example, “Duplicate entry” in a multiple-row insert), then the slave stopped and warned that the error codes didn't match. This is a backport of the fix for MySQL 4.0. (Bug#797)

- mysqlbinlog now asks for a password at console when the `-p`/`--password` option is used with no argument. This is how the other clients (mysqladmin, mysqldump..) behave. Note that one now has to use mysqlbinlog -p<my_password>; mysqlbinlog -p <my_password> does not work anymore (in other words, put no space after `-p`). (Bug#1595)

- On some 64-bit machines (some HP-UX and Solaris machines), a slave installed with the 64-bit MySQL binary could not connect to its master (it connected to itself instead). (Bug#1256, Bug#1381)

- Fixed a Windows-specific bug present since MySQL 3.23.57 and 3.23.58 that caused Windows slaves to crash when they started replication if a `master.info` file existed. (Bug#1720)

- Fixed bug in `ALTER TABLE RENAME`, when rename to the table with the same name in another database silently dropped destination table if it existed. (Bug#2628)

- Fixed potential memory overrun in `mysql_real_connect()` (which required a compromised DNS server and certain operating systems). (Bug#4017, CVE-2004-0836)

### B.3.2. Changes in release 3.23.58 (11 September 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed buffer overflow in password handling which could potentially be exploited by MySQL users with `ALTER` privilege on the `mysql.user` table to execute random code or to gain shell access with the UID of the mysqld process (thanks to Jedi/Sector One for spotting and reporting this bug). (CVE-2003-0780)

- mysqldump now correctly quotes all identifiers when communicating with the server. This assures that during the dump process, mysqldump never sends queries to the server that result in a syntax error. This problem is not related to the mysqldump program's output, which was not changed. (Bug#1148)

- Fixed table/column grant handling: The proper sort order (from most specific to less specific, see Section 5.5.6, “Access Control, Stage 2: Request Verification”) was not honored. (Bug#928)

- Fixed overflow bug in `MyISAM` and `ISAM` when a row is updated in a table with a large number of columns and at least one `BLOB/TEXT` column.

- Fixed MySQL so that field length (in C API) for the second column in `SHOW CREATE TABLE` is always larger than the data length. The only known application that was affected by the old behavior was Borland dbExpress, which truncated the output from the command. (Bug#1064)

- Fixed `ISAM` bug in `MAX()` optimization.

- Fixed `Unknown error` when doing `ORDER BY` on reference table which was used with `NULL` value on `NOT NULL` column. (Bug#479)

### B.3.3. Changes in release 3.23.57 (06 June 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed problem in alarm handling that could cause problems when getting a packet that is too large.

- Fixed problem when installing MySQL as a service on Windows when two arguments were specified to mysqld (option file group name and service name).

- Fixed `kill pid-of-mysqld` to work on Mac OS X.

- `SHOW TABLE STATUS` displayed incorrect `Row_format` value for tables that have been compressed with myisampack. (Bug#427)

- `SHOW VARIABLES LIKE 'innodb_data_file_path'` displayed only the name of the first data file. (Bug#468)

- Fixed security problem where mysqld didn't allow one to `UPDATE` rows in a table even if one had a global `UPDATE` privilege and a database `SELECT` privilege.

- Fixed a security problem with `SELECT` and wildcarded select list, when user only had partial column `SELECT` privileges on the table.

- Fixed unlikely problem in optimizing `WHERE` clause with a constant expression such as in `WHERE 1 AND (a=1 AND b=1)`.

- Fixed problem on IA-64 with timestamps that caused mysqlbinlog to fail.

- The default option for `innodb_flush_log_at_trx_commit` was changed from 0 to 1 to make `InnoDB` tables ACID by default. See Section 13.2.5, “`InnoDB` Startup Options and System Variables”.

- Fixed problem with too many allocated alarms on slave when connecting to master many times (normally not a very critical error).

- Fixed a bug in replication of temporary tables. (Bug#183)

- Fixed 64-bit bug that affected at least AMD hammer systems.

- Fixed a bug when doing `LOAD DATA INFILE IGNORE`: When reading the binary log, mysqlbinlog and the replication code read `REPLACE` instead of `IGNORE`. This could make the slave's table become different from the master's table. (Bug#218)

- Fixed overflow bug in `MyISAM` when a row is inserted into a table with a large number of columns and at least one `BLOB/TEXT` column. Bug was caused by incorrect calculation of the needed buffer to pack data.

- The binary log was not locked during `TRUNCATE `tbl_name`` or `DELETE FROM `tbl_name`` statements, which could cause an `INSERT` to `tbl_name` to be written to the log before the `TRUNCATE` or `DELETE` statements.

- Fixed rare bug in `UPDATE` of `InnoDB` tables where one row could be updated multiple times.

- Produce an error for empty table and column names.

- Changed `PROCEDURE ANALYSE()` to report `DATE` instead of `NEWDATE`.

- Changed `PROCEDURE ANALYSE(#)` to restrict the number of values in an `ENUM` column to `#` also for string values.

- mysqldump no longer silently deletes the binary logs when invoked with the `--master-data` or `--first-slave` option; while this behavior was convenient for some users, others may suffer from it. Now you must explicitly ask for binary logs to be deleted by using the new `--delete-master-logs` option.

- Fixed a bug in mysqldump when it was invoked with the `--master-data` option: The `CHANGE MASTER TO` statements that were appended to the SQL dump had incorrect coordinates. (Bug#159)

### B.3.4. Changes in release 3.23.56 (13 March 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed mysqld crash on extremely small values of `sort_buffer` variable.

- Fixed a bug in privilege system for `GRANT UPDATE` on the column level.

- Fixed a rare bug when using a date in `HAVING` with `GROUP BY`.

- Fixed checking of random part of `WHERE` clause. (Bug#142)

- Fixed MySQL (and myisamchk) crash on artificially corrupted `.MYI` files.

- Security enhancement: mysqld no longer reads options from world-writable config files. (CVE-2003-0150)

- Security enhancement: mysqld and safe_mysqld now use only the first `--user` option specified on the command line. Normally this comes from `/etc/my.cnf`. (CVE-2003-0150)

- Security enhancement: Don't allow `BACKUP TABLE` to overwrite existing files.

- Fixed unlikely deadlock bug when one thread did a `LOCK TABLE` and another thread did a `DROP TABLE`. In this case one could do a `KILL` on one of the threads to resolve the deadlock.

- `LOAD DATA INFILE` was not replicated by slave if `replicate_*_table` was set on the slave.

- Fixed a bug in handling `CHAR(0)` columns that could cause incorrect results from the query.

- Fixed a bug in `SHOW VARIABLES` on 64-bit platforms. The bug was caused by incorrect declaration of variable `server_id`.

- The `Comment` column in `SHOW TABLE STATUS` now reports that it can contain `NULL` values (which is the case for a crashed `.frm` file).

- Fixed the `rpl_rotate_logs` test to not fail on certain platforms (such as Mac OS X) due to a too-long file name (changed `slave-master-info.opt` to `.slave-mi`).

- Fixed a problem with `BLOB NOT NULL` columns used with `IS NULL`.

- Fixed bug in `MAX()` optimization in `MERGE` tables.

- Better `RAND()` initialization for new connections.

- Fixed bug with connect timeout. This bug was manifested on OS's with `poll()` system call, which resulted in timeout the value specified as it was executed in both `select()` and `poll()`.

- Fixed bug in `SELECT * FROM table WHERE datetime1 IS NULL OR datetime2 IS NULL`.

- Fixed bug in using aggregate functions as argument for `INTERVAL`, `CASE`, `FIELD`, `CONCAT_WS`, `ELT` and `MAKE_SET` functions.

- When running with `--lower-case-table-names=1` (default on Windows) and you had tables or databases with mixed case on disk, then executing `SHOW TABLE STATUS` followed with `DROP DATABASE` or `DROP TABLE` could fail with `Errcode 13`.

- Fixed bug in logging to binary log (which affects replication) a query that inserts a `NULL` in an `auto_increment` field and also uses `LAST_INSERT_ID()`.

- Fixed bug in mysqladmin --relative.

- On some 64-bit systems, `show status` reported a strange number for `Open_files` and `Open_streams`.

### B.3.5. Changes in release 3.23.55 (23 January 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed double `free`'d pointer bug in `mysql_change_user()` handling, that enabled a specially hacked version of MySQL client to crash mysqld. Note that you must log in to the server by using a valid user account to be able to exploit this bug. (CVE-2003-0073)

- Fixed bug with the `--slow-log` when logging an administrator command (like `FLUSH TABLES`).

- Fixed bug in `GROUP BY` when used on BLOB column with `NULL` values.

- Fixed a bug in handling `NULL` values in `CASE ... WHEN ...`.

- Bugfix for `--chroot` (see Section B.3.6, “Changes in release 3.23.54 (05 December 2002)”) is reverted. Unfortunately, there is no way to make it to work, without introducing backward-incompatible changes in `my.cnf`. Those who need `--chroot` functionality, should upgrade to MySQL 4.0. (The fix in the 4.0 branch did not break backward-compatibility).

- Make `--lower-case-table-names` default on Mac OS X as the default filesystem (HFS+) is case insensitive.

- Fixed a bug in `scripts/mysqld_safe.sh` in `NOHUP_NICENESS` testing.

- Transactions in `AUTOCOMMIT=0` mode didn't rotate binary log.

- Fixed a bug in `scripts/make_binary_distribution` that resulted in a remaining `@HOSTNAME@` variable instead of replacing it with the correct path to the `hostname` binary.

- Fixed a very unlikely bug that could cause `SHOW PROCESSLIST` to core dump in pthread_mutex_unlock() if a new thread was connecting.

- Forbid `SLAVE STOP` if the thread executing the query has locked tables. This removes a possible deadlock situation.

### B.3.6. Changes in release 3.23.54 (05 December 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed a bug, that allowed to crash mysqld with a specially crafted packet. (CVE-2002-1373)

- Fixed a rare crash (double `free`'d pointer) when altering a temporary table.

- Fixed buffer overrun in `libmysqlclient` library that allowed malicious MySQL server to crash the client application. (CVE-2002-1376)

- Fixed security-related bug in `mysql_change_user()` handling. All users are strongly recommended to upgrade to the version 3.23.54. (CVE-2002-1374, CVE-2002-1375)

- Fixed bug that prevented `--chroot` command-line option of mysqld from working.

- Fixed bug that made `OPTIMIZE TABLE` to corrupt the table under some rare circumstances.

- Fixed mysqlcheck so it can deal with table names containing dashes.

- Fixed shutdown problem on Mac OS X.

- Fixed bug with comparing an indexed `NULL` field with `<=> NULL`.

- Fixed bug that caused `IGNORE INDEX` and `USE INDEX` sometimes to be ignored.

- Fixed rare core dump problem in complicated `GROUP BY` queries that didn't return any result.

- Fixed a bug where `MATCH ... AGAINST () >=0` was treated as if it was `>`.

- Fixed core dump in `SHOW PROCESSLIST` when running with an active slave (unlikely timing bug).

- Make it possible to use multiple MySQL servers on Windows (code backported from 4.0.2).

- One can create `TEMPORARY` `MERGE` tables now.

- Fixed that `--core-file` works on Linux (at least on kernel 2.4.18).

- Fixed a problem with `BDB` and `ALTER TABLE`.

- Fixed reference to freed memory when doing complicated `GROUP BY ... ORDER BY` queries. Symptom was that mysqld died in function `send_fields`.

- Allocate heap rows in smaller blocks to get better memory usage.

- Fixed memory allocation bug when storing `BLOB` values in internal temporary tables used for some (unlikely) `GROUP BY` queries.

- Fixed a bug in key optimizing handling where the expression `WHERE `col_name` = `key_col_name`` was calculated as true for `NULL` values.

- Fixed core dump bug when doing `LEFT JOIN ... WHERE `key_column`=NULL`.

- Fixed `MyISAM` crash when using dynamic-row tables with huge numbers of packed fields.

- Updated source tree to be built using automake 1.5 and libtool 1.4.

### B.3.7. Changes in release 3.23.53 (09 October 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed crash when `SHOW INNODB STATUS` was used and `skip-innodb` was defined.

- Fixed possible memory corruption bug in binary log file handling when slave rotated the logs (only affected 3.23, not 4.0).

- Fixed problem in `LOCK TABLES` on Windows when one connects to a database that contains uppercase letters.

- Fixed that `--skip-show-database` doesn't reset the `--port` option.

- Small fix in safe_mysqld for some shells.

- Fixed that `FLUSH STATUS` doesn't reset `delayed_insert_threads`.

- Fixed core dump bug when using the `BINARY` cast on a `NULL` value.

- Fixed race condition when someone did a `GRANT` at the same time a new user logged in or did a `USE database`.

- Fixed bug in `ALTER TABLE` and `RENAME TABLE` when running with `-O lower_case_table_names=1` (typically on Windows) when giving the table name in uppercase.

- Fixed that `-O lower_case_table_names=1` also converts database names to lowercase.

- Fixed unlikely core dump with `SELECT ... ORDER BY ... LIMIT`.

- Changed `AND`/`OR` to report that they can return NULL. This fixes a bug in `GROUP BY` on `AND`/`OR` expressions that return `NULL`.

- Fixed a bug that `OPTIMIZE TABLE` of locked and modified `MyISAM` table, reported table corruption.

- Fixed a `BDB`-related `ALTER TABLE` bug with dropping a column and shutting down immediately thereafter.

- Fixed problem with `configure ... --localstatedir=...`.

- Fixed problem with `UNSIGNED BIGINT` on AIX (again).

- Fixed bug in pthread_mutex_trylock() on HPUX 11.0.

- Multi-threaded stress tests for `InnoDB`.

### B.3.8. Changes in release 3.23.52 (14 August 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Wrap `BEGIN`/`COMMIT` around transaction in the binary log. This makes replication honor transactions.

- Fixed security bug when having an empty database name in the `user.db` table.

- Changed initialization of `RAND()` to make it less predicatable.

- Fixed problem with `GROUP BY` on result with expression that created a `BLOB` field.

- Fixed problem with `GROUP BY` on columns that have `NULL` values. To solve this we now create an `MyISAM` temporary table when doing a `GROUP BY` on a possible `NULL` item. From MySQL 4.0.5 we can use in memory `HEAP` tables for this case.

- Fixed problem with privilege tables when downgrading from 4.0.2 to 3.23.

- Fixed thread bug in `SLAVE START`, `SLAVE STOP` and automatic repair of `MyISAM` tables that could cause table cache to be corrupted.

- Fixed possible thread related key-cache-corruption problem with `OPTIMIZE TABLE` and `REPAIR TABLE`.

- Added name of 'administrator command' logs.

- Fixed bug with creating an auto-increment value on second part of a `UNIQUE` key where first part could contain `NULL` values.

- Don't write slave-timeout reconnects to the error log.

- Fixed bug with slave net read timeouting

- Fixed a core-dump bug with `MERGE` tables and `MAX()` function.

- Fixed bug in `ALTER TABLE` with `BDB` tables.

- Fixed bug when logging `LOAD DATA INFILE` to binary log with no active database.

- Fixed a bug in range optimizer (causing crashes).

- Fixed possible problem in replication when doing `DROP DATABASE` on a database with `InnoDB` tables.

- Fixed `mysql_info()` to return 0 for `Duplicates` value when using `INSERT DELAYED IGNORE`.

- Added `-DHAVE_BROKEN_REALPATH` to the Mac OS X (darwin) compile options in `configure.in` to fix a failure under high load.

### B.3.9. Changes in release 3.23.51 (31 May 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fix bug with closing tags missing slash for mysqldump XML output.

- Remove endspace from `ENUM` values. (This fixed a problem with `SHOW CREATE TABLE`.)

- Fixed bug in `CONCAT_WS()` that cut the result.

- Changed name of server variables `Com_show_master_stat` to `Com_show_master_status` and `Com_show_slave_stat` to `Com_show_slave_status`.

- Changed handling of `gethostbyname()` to make the client library thread-safe even if `gethostbyname_r` doesn't exist.

- Fixed core-dump problem when giving a wrong password string to `GRANT`.

- Fixed bug in `DROP DATABASE` with symlinked directory.

- Fixed optimization problem with `DATETIME` and value outside `DATETIME` range.

- Removed Sleepycat's `BDB` doc files from the source tree, as they're not needed (MySQL covers `BDB` in its own documentation).

- Fixed MIT-pthreads to compile with `glibc` 2.2 (needed for make dist).

- Fixed the `FLOAT(X+1,X)` is not converted to `FLOAT(X+2,X)`. (This also affected `DECIMAL`, `DOUBLE` and `REAL` types)

- Fixed the result from `IF()` is case in-sensitive if the second and third arguments are case sensitive.

- Fixed core dump problem on OSF/1 in `gethostbyname_r`.

- Fixed that underflowed decimal fields are not zero filled.

- If we get an overflow when inserting `'+11111'` for `DECIMAL(5,0) UNSIGNED` columns, we just drop the sign.

- Fixed optimization bug with `ISNULL(`expression_which_cannot_be_null`)` and `ISNULL(`constant_expression`)`.

- Fixed host lookup bug in the `glibc` library that we used with the 3.23.50 Linux-x86 binaries.

### B.3.10. Changes in release 3.23.50 (21 April 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed buffer overflow problem if someone specified a too-long `datadir` parameter to mysqld. (CVE-2002-0969)

- Add missing `<row>` tags for mysqldump XML output.

- Fixed problem with `crash-me` and gcc 3.0.4.

- Fixed that `@@unknown_variable` doesn't hang server.

- Added `@@VERSION` as a synonym for `VERSION()`.

- `SHOW VARIABLES LIKE '`xxx`'` is now case-insensitive.

- Fixed timeout for `GET_LOCK()` on HP-UX with DCE threads.

- Fixed memory allocation bug in the glibc library used to build Linux binaries, which caused mysqld to die in `free()`.

- Fixed `SIGINT` and `SIGQUIT` problems in mysql.

- Fixed bug in character table converts when used with big (larger than 64KB) strings.

- `InnoDB` now retains foreign key constraints through `ALTER TABLE` and `CREATE/DROP INDEX`.

- `InnoDB` now allows foreign key constraints to be added through the `ALTER TABLE` syntax.

- `InnoDB` tables can now be set to automatically grow in size (auto-extend).

- Our Linux RPMS and binaries are now compiled with gcc 3.0.4, which should make them a bit faster.

- Fixed some buffer overflow problems when reading startup parameters.

- Because of problems on shutdown we have now disabled named pipes on Windows by default. One can enable named pipes by starting mysqld with `--enable-named-pipe`.

- Fixed bug when using `WHERE key_column = 'J' or key_column='j'`.

- Fixed core-dump bug when using `--log-bin` with `LOAD DATA INFILE` without an active database.

- Fixed bug in `RENAME TABLE` when used with `lower_case_table_names=1` (default on Windows).

- Fixed unlikely core-dump bug when using `DROP TABLE` on a table that was in use by a thread that also used queries on only temporary tables.

- Fixed problem with `SHOW CREATE TABLE` and `PRIMARY KEY` when using 32 indexes.

- Fixed that one can use `SET PASSWORD` for the anonymous user.

- Fixed core dump bug when reading client groups from option files using `mysql_options()`.

- Memory leak (16 bytes per every corrupted table) closed.

- Fixed binary builds to use `--enable-local-infile`.

- Update source to work with new version of bison.

- Updated shell scripts to now agree with new POSIX standard.

- Fixed bug where `DATE_FORMAT()` returned empty string when used with `GROUP BY`.

### B.3.11. Changes in release 3.23.49 (14 February 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- For a `MERGE` table, `DELETE FROM `merge_table`` used without a `WHERE` clause no longer clears the mapping for the table by emptying the `.MRG` file. Instead, it deletes records from the mapped tables.

- Don't give warning for a statement that is only a comment; this is needed for mysqldump --disable-keys to work.

- Fixed unlikely caching bug when doing a join without keys. In this case, the last used field for a table always returned `NULL`.

- Added options to make `LOAD DATA LOCAL INFILE` more secure.

- MySQL binary release 3.23.48 for Linux contained a new `glibc` library, which has serious problems under high load and Red Hat 7.2. The 3.23.49 binary release doesn't have this problem.

- Fixed shutdown problem on NT.

### B.3.12. Changes in release 3.23.48 (07 February 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `--xml` option to mysqldump for producing XML output.

- Changed to use autoconf 2.52 (from autoconf 2.13)

- Fixed bug in complicated join with `const` tables.

- Added internal safety checks for `InnoDB`.

- Some `InnoDB` variables were always shown in `SHOW VARIABLES` as `OFF` on high-byte-first systems (like SPARC).

- Fixed problem with one thread using an `InnoDB` table and another thread doing an `ALTER TABLE` on the same table. Before that, mysqld could crash with an assertion failure in `row0row.c`, line 474.

- Tuned the `InnoDB` SQL optimizer to favor index searches more often over table scans.

- Fixed a performance problem with `InnoDB` tables when several large `SELECT` queries are run concurrently on a multiprocessor Linux computer. Large CPU-bound `SELECT` queries now also generally run faster on all platforms.

- If MySQL binary logging is used, `InnoDB` now prints after crash recovery the latest MySQL binary log name and the offset `InnoDB` was able to recover to. This is useful, for example, when resynchronizing a master and a slave database in replication.

- Added better error messages to help in installation problems of `InnoDB` tables.

- It is now possible to recover MySQL temporary tables that have become orphaned inside the `InnoDB` tablespace.

- `InnoDB` now prevents a `FOREIGN KEY` declaration where the signedness is not the same in the referencing and referenced integer columns.

- Calling `SHOW CREATE TABLE` or `SHOW TABLE STATUS` could cause memory corruption and make mysqld crash. Especially at risk was mysqldump, because it frequently calls `SHOW CREATE TABLE`.

- If inserts to several tables containing an `AUTO_INCREMENT` column were wrapped inside one `LOCK TABLES`, `InnoDB` asserted in `lock0lock.c`.

- In 3.23.47 we allowed several `NULL` values in a `UNIQUE` secondary index for an `InnoDB` table. But `CHECK TABLE` was not relaxed: it reports the table as corrupt. `CHECK TABLE` no longer complains in this situation.

- `SHOW GRANTS` now shows `REFERENCES` instead of `REFERENCE`.

### B.3.13. Changes in release 3.23.47 (27 December 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed bug when using the following construct: `SELECT ... WHERE `key`=@`var_name` OR `key`=@`var_name2``

- Restrict `InnoDB` keys to 500 bytes.

- `InnoDB` now supports `NULL` in keys.

- Fixed shutdown problem on HP-UX. (Introduced in 3.23.46)

- Fixed core dump bug in replication when using `SELECT RELEASE_LOCK()`.

- Added new statement: `DO `expr`[,`expr`]...`

- Added `slave-skip-errors` option.

- Added statistics variables for all MySQL commands. (`SHOW STATUS` is now much longer.)

- Fixed default values for `InnoDB` tables.

- Fixed that `GROUP BY `expr` DESC` works.

- Fixed bug when using `t1 LEFT JOIN t2 ON t2.key=constant`.

- mysql_config now also works with binary (relocated) distributions.

### B.3.14. Changes in release 3.23.46 (29 November 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed problem with aliased temporary table replication.

- `InnoDB` and `BDB` tables now use index when doing an `ORDER BY` on the whole table.

- Fixed bug where one got an empty set instead of a DEADLOCK error when using `BDB` tables.

- One can now kill `ANALYZE TABLE`, `REPAIR TABLE`, and `OPTIMIZE TABLE` when the thread is waiting to get a lock on the table.

- Fixed race condition in `ANALYZE TABLE`.

- Fixed bug when joining with caching (unlikely to happen).

- Fixed race condition when using the binary log and `INSERT DELAYED` which could cause the binary log to have rows that were not yet written to `MyISAM` tables.

- Changed caching of binary log to make replication slightly faster.

- Fixed bug in replication on Mac OS X.

### B.3.15. Changes in release 3.23.45 (22 November 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- `(UPDATE|DELETE) ...WHERE MATCH` bugfix.

- shutdown should now work on Darwin (Mac OS X).

- Fixed core dump when repairing corrupted packed `MyISAM` files.

- `--core-file` now works on Solaris.

- Fix a bug which could cause `InnoDB` to complain if it cannot find free blocks from the buffer cache during recovery.

- Fixed bug in `InnoDB` insert buffer B-tree handling that could cause crashes.

- Fixed bug in `InnoDB` lock timeout handling.

- Fixed core dump bug in `ALTER TABLE` on a `TEMPORARY` `InnoDB` table.

- Fixed bug in `OPTIMIZE TABLE` that reset index cardinality if it was up to date.

- Fixed problem with `t1 LEFT_JOIN t2 ... WHERE t2.date_column IS NULL` when date_column was declared as `NOT NULL`.

- Fixed bug with `BDB` tables and keys on `BLOB` columns.

- Fixed bug in `MERGE` tables on OS with 32-bit file pointers.

- Fixed bug in `TIME_TO_SEC()` when using negative values.

### B.3.16. Changes in release 3.23.44 (31 October 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed `Rows_examined` count in slow query log.

- Fixed bug when using a reference to an `AVG()` column in `HAVING`.

- Fixed that date functions that require correct dates, like `DAYOFYEAR(column)`, return `NULL` for `0000-00-00` dates.

- Fixed bug in const-propagation when comparing columns of different types. (`SELECT * FROM date_col="2001-01-01" and date_col=time_col`)

- Fixed bug that caused error message `Can't write, because of unique constraint` with some `GROUP BY` queries.

- Fixed problem with `sjis` character strings used within quoted table names.

- Fixed core dump when using `CREATE ... FULLTEXT` keys with other storage engines than `MyISAM`.

- Don't use `signal()` on Windows because this appears to not be 100% reliable.

- Fixed bug when doing `WHERE col_name=NULL` on an indexed column that had `NULL` values.

- Fixed bug when doing `LEFT JOIN ... ON (col_name = constant) WHERE col_name = constant`.

- When using replications, aborted queries that contained `%` could cause a core dump.

- `TCP_NODELAY` was not used on some systems. (Speed problem.)

- Applied portability fixes for OS/2. (Patch by Yuri Dario.)

The following changes are for `InnoDB` tables:

- Add missing `InnoDB` variables to `SHOW VARIABLES`.

- Foreign key checking is now done for `InnoDB` tables.

- `DROP DATABASE` now works also for `InnoDB` tables.

- `InnoDB` now supports data files and raw disk partitions bigger than 4GB on those operating systems that have big files.

- `InnoDB` calculates better table cardinality estimates for the MySQL optimizer.

- Accent characters in the default character set `latin1` are ordered according to the MySQL ordering.

  Note: If you are using `latin1` and have inserted characters whose code is greater than 127 into an indexed `CHAR` column, you should run `CHECK TABLE` on your table when you upgrade to 3.23.44, and drop and reimport the table if `CHECK TABLE` reports an error!

- A new `my.cnf` parameter, `innodb_thread_concurrency`, helps in performance tuning in heavily concurrent environments.

- A new `my.cnf` parameter, `innodb_fast_shutdown`, speeds up server shutdown.

- A new `my.cnf` parameter, `innodb_force_recovery`, helps to save your data in case the disk image of the database becomes corrupt.

- `innodb_monitor` has been improved and a new `innodb_table_monitor` added.

- Increased maximum key length from 500 to 7000 bytes.

- Fixed a bug in replication of `AUTO_INCREMENT` columns with multiple-line inserts.

- Fixed a bug when the case of letters changes in an update of an indexed secondary column.

- Fixed a hang when there are more than 24 data files.

- Fixed a crash when `MAX(col)` is selected from an empty table, and `col` is not the first column in a multi-column index.

- Fixed a bug in purge which could cause crashes.

### B.3.17. Changes in release 3.23.43 (04 October 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed a bug in `INSERT DELAYED` and `FLUSH TABLES` introduced in 3.23.42.

- Fixed unlikely bug, which returned non-matching rows, in `SELECT` with many tables and multi-column indexes and 'range' type.

- Fixed an unlikely core dump bug when doing `EXPLAIN SELECT` when using many tables and `ORDER BY`.

- Fixed bug in `LOAD DATA FROM MASTER` when using table with `CHECKSUM=1`.

- Added unique error message when a DEADLOCK occurs during a transaction with `BDB` tables.

- Fixed problem with `BDB` tables and `UNIQUE` columns defined as `NULL`.

- Fixed problem with myisampack when using pre-space filled `CHAR` columns.

- Applied patch from Yuri Dario for OS/2.

- Fixed bug in `--safe-user-create`.

### B.3.18. Changes in release 3.23.42 (08 September 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed problem when using `LOCK TABLES` and `BDB` tables.

- Fixed problem with `REPAIR TABLE` on `MyISAM` tables with row lengths in the range from 65517 to 65520 bytes.

- Fixed rare hang when doing mysqladmin shutdown when there was a lot of activity in other threads.

- Fixed problem with `INSERT DELAYED` where delayed thread could be hanging on `upgrading locks` for no apparent reason.

- Fixed problem with myisampack and `BLOB`.

- Fixed problem when one edited `.MRG` tables by hand. (Patch from Benjamin Pflugmann).

- Enforce that all tables in a `MERGE` table come from the same database.

- Fixed bug with `LOAD DATA INFILE` and transactional tables.

- Fix bug when using `INSERT DELAYED` with wrong column definition.

- Fixed core dump during `REPAIR TABLE` of some particularly broken tables.

- Fixed bug in `InnoDB` and `AUTO_INCREMENT` columns.

- Fixed bug in `InnoDB` and `RENAME TABLE` columns.

- Fixed critical bug in `InnoDB` and `BLOB` columns. If you have used `BLOB` columns larger than 8000 bytes in an `InnoDB` table, it is necessary to dump the table with mysqldump, drop it and restore it from the dump.

- Applied large patch for OS/2 from Yuri Dario.

- Fixed problem with `InnoDB` when one could get the error `Can't execute the given command...` even when no transaction was active.

- Applied some minor fixes that concern Gemini.

- Use real arithmetic operations even in integer context if not all arguments are integers. (Fixes uncommon bug in some integer contexts).

- Don't force everything to lowercase on Windows. (To fix problem with Windows and `ALTER TABLE`.) Now `--lower_case_table_names` also works on Unix.

- Fixed that automatic rollback is done when thread end doesn't lock other threads.

### B.3.19. Changes in release 3.23.41 (11 August 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `--sql-mode=`value`[,`value`[,`value`]]` option to mysqld. See Section 5.1.2, “Command Options”.

- Fixed possible problem with `shutdown` on Solaris where the `.pid` file wasn't deleted.

- `InnoDB` now supports < 4GB rows. The former limit was 8000 bytes.

- The `doublewrite` file flush method is used in `InnoDB`. It reduces the need for Unix `fsync()` calls to a fraction and improves performance on most Unix flavors.

- You can now use the `InnoDB` Monitor to print a lot of `InnoDB` state information, including locks, to the standard output. This is useful in performance tuning.

- Several bugs which could cause hangs in `InnoDB` have been fixed.

- Split `record_buffer` to `record_buffer` and `record_rnd_buffer`. To make things compatible to previous MySQL versions, if `record_rnd_buffer` is not set, then it takes the value of `record_buffer`.

- Fixed optimizing bug in `ORDER BY` where some `ORDER BY` parts where wrongly removed.

- Fixed overflow bug with `ALTER TABLE` and `MERGE` tables.

- Added prototypes for `my_thread_init()` and `my_thread_end()` to `mysql_com.h`

- Added `--safe-user-create` option to mysqld.

- Fixed bug in `SELECT DISTINCT ... HAVING` that caused error message `Can't find record in #...`

### B.3.20. Changes in release 3.23.40 (18 July 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed problem with `--low-priority-updates` and `INSERT` statements.

- Fixed bug in slave thread when under some rare circumstances it could get 22 bytes ahead on the offset in the master.

- Added `slave_net_timeout` for replication.

- Fixed problem with `UPDATE` and `BDB` tables.

- Fixed hard bug in `BDB` tables when using key parts.

- Fixed problem when using `GRANT FILE ON database.* ...`; previously we added the `DROP` privilege for the database.

- Fixed `DELETE FROM `tbl_name` ... LIMIT 0` and `UPDATE FROM `tbl_name` ... LIMIT 0`, which acted as though the `LIMIT` clause was not present (they deleted or updated all selected rows).

- `CHECK TABLE` now checks whether an `AUTO_INCREMENT` column contains the value 0.

- Sending a `SIGHUP` to mysqld now only flushes the logs, but does not reset the replication.

- Fixed parser to allow floats of type `1.0e1` (no sign after `e`).

- Option `--force` to myisamchk now also updates states.

- Added option `--warnings` to mysqld. Now mysqld prints the error `Aborted connection` only if this option is used.

- Fixed problem with `SHOW CREATE TABLE` when you didn't have a `PRIMARY KEY`.

- Properly fixed the rename of `innodb_unix_file_flush_method` variable to `innodb_flush_method`.

- Fixed bug when converting `BIGINT UNSIGNED` to `DOUBLE`. This caused a problem when doing comparisons with `BIGINT` values outside of the signed range.

- Fixed bug in `BDB` tables when querying empty tables.

- Fixed a bug when using `COUNT(DISTINCT)` with `LEFT JOIN` and there weren't any matching rows.

- Removed all documentation referring to the `GEMINI` table type. `GEMINI` is not released under an Open Source license.

### B.3.21. Changes in release 3.23.39 (12 June 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- The `AUTO_INCREMENT` sequence wasn't reset when dropping and adding an `AUTO_INCREMENT` column.

- `CREATE ... SELECT` now creates non-unique indexes delayed.

- Fixed problem where `LOCK TABLES `tbl_name` READ` followed by `FLUSH TABLES` put an exclusive lock on the table.

- `REAL @variable` values were represented with only 2 digits when converted to strings.

- Fixed problem that client “hung” when `LOAD TABLE FROM MASTER` failed.

- myisamchk --fast --force no longer repairs tables that only had the open count wrong.

- Added functions to handle symbolic links to make life easier in 4.0.

- We are now using the `-lcma` thread library on HP-UX 10.20 so that MySQL is more stable on HP-UX.

- Fixed problem with `IF()` and number of decimals in the result.

- Fixed date-part extraction functions to work with dates where day and/or month is 0.

- Extended argument length in option files from 256 to 512 chars.

- Fixed problem with shutdown when `INSERT DELAYED` was waiting for a `LOCK TABLE`.

- Fixed core dump bug in `InnoDB` when tablespace was full.

- Fixed problem with `MERGE` tables and big tables (larger than 4GB) when using `ORDER BY`.

### B.3.22. Changes in release 3.23.38 (09 May 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed a bug when `SELECT` from `MERGE` table sometimes results in incorrectly ordered rows.

- Fixed a bug in `REPLACE()` when using the `ujis` character set.

- Applied Sleepycat `BDB` patches 3.2.9.1 and 3.2.9.2.

- Added `--skip-stack-trace` option to mysqld.

- `CREATE TEMPORARY` now works with `InnoDB` tables.

- `InnoDB` now promotes sub keys to whole keys.

- Added option `CONCURRENT` to `LOAD DATA`.

- Better error message when slave `max_allowed_packet` is too low to read a very long log event from the master.

- Fixed bug when too many rows were removed when using `SELECT DISTINCT ... HAVING`.

- `SHOW CREATE TABLE` now returns `TEMPORARY` for temporary tables.

- Added `Rows_examined` to slow query log.

- Fixed problems with function returning empty string when used together with a group function and a `WHERE` that didn't match any rows.

- New program mysqlcheck.

- Added database name to output for administrative commands like `CHECK TABLE`, `REPAIR TABLE`, `OPTIMIZE TABLE`.

- Lots of portability fixes for `InnoDB`.

- Changed optimizer so that queries like `SELECT * FROM `tbl_name`, `tbl_name2` ... ORDER BY `key_part1` LIMIT `row_count`` use an index on `key_part1` instead of `filesort`.

- Fixed bug when doing `LOCK TABLE `to_table` WRITE,...; INSERT INTO `to_table`... SELECT ...` when `to_table` was empty.

- Fixed bug with `LOCK TABLE` and `BDB` tables.

### B.3.23. Changes in release 3.23.37 (17 April 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed a bug when using `MATCH()` in `HAVING` clause.

- Fixed a bug when using `HEAP` tables with `LIKE`.

- Added `--mysql-version` option to safe_mysqld

- Changed `INNOBASE` to `InnoDB` (because the `INNOBASE` name was in use). All configure options and mysqld start options now use `innodb` instead of `innobase`. This means that before upgrading to this version, you have to change any configuration files where you have used `innobase` options!

- Fixed bug when using indexes on `CHAR(255) NULL` columns.

- Slave threads now start even if `master-host` is not set, as long as `server-id` is set and valid `master.info` is present.

- Partial updates (terminated with kill) are now logged with a special error code to the binary log. Slave refuses to execute them if the error code indicates the update was terminated abnormally, and has to be recovered with `SET SQL_SLAVE_SKIP_COUNTER=1; SLAVE START` after a manual sanity check/correction of data integrity.

- Fixed bug that erroneously logged a drop of internal temporary table on thread termination to the binary log --- this bug affected replication.

- Fixed a bug in `REGEXP` on 64-bit machines.

- `UPDATE` and `DELETE` with `WHERE unique_key_part IS NULL` didn't update/delete all rows.

- Disabled `INSERT DELAYED` for tables that support transactions.

- Fixed bug when using date functions on `TEXT`/`BLOB` column with wrong date format.

- UDFs now also work on Windows. (Patch by Ralph Mason.)

- Fixed bug in `ALTER TABLE` and `LOAD DATA INFILE` that disabled key-sorting. These commands should now be faster in most cases.

- Fixed performance bug where reopened tables (tables that had been waiting for `FLUSH` or `REPAIR TABLE`) would not use indexes for the next query.

- Fixed problem with `ALTER TABLE` to `InnoDB` tables on FreeBSD.

- Added mysqld variables `myisam_max_sort_file_size` and `myisam_max_extra_sort_file_size`.

- Initialize signals early to avoid problem with signals in `InnoDB`.

- Applied patch for the `tis620` character set to make comparisons case-independent and to fix a bug in `LIKE` for this character set.

  ### Note

  All tables that use the `tis620` character set must be fixed with myisamchk -r or `REPAIR TABLE`!

- Added `--skip-safemalloc` option to mysqld.

### B.3.24. Changes in release 3.23.36 (27 March 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed a bug that allowed use of database names containing a “`.`” character. This fixes a serious security issue when mysqld is run as root. (CVE-2001-0407)

- Fixed bug when thread creation failed (could happen when doing a lot of connections in a short time).

- Fixed some problems with `FLUSH TABLES` and `TEMPORARY` tables. (Problem with freeing the key cache and error `Can't reopen table...`.)

- Fixed a problem in `InnoDB` with other character sets than `latin1` and another problem when using many columns.

- Fixed bug that caused a core dump when using a very complex query involving `DISTINCT` and summary functions.

- Added `SET TRANSACTION ISOLATION LEVEL ...`

- Added `SELECT ... FOR UPDATE`.

- Fixed bug where the number of affected rows was not returned when MySQL was compiled without transaction support.

- Fixed a bug in `UPDATE` where keys weren't always used to find the rows to be updated.

- Fixed a bug in `CONCAT_WS()` where it returned incorrect results.

- Changed `CREATE ... SELECT` and `INSERT ... SELECT` to not allow concurrent inserts as this could make the binary log hard to repeat. (Concurrent inserts are enabled if you are not using the binary or update log.)

- Changed some macros to be able to use fast mutex with `glibc` 2.2.

### B.3.25. Changes in release 3.23.35 (15 March 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed newly introduced bug in `ORDER BY`.

- Fixed wrong define `CLIENT_TRANSACTIONS`.

- Fixed bug in `SHOW VARIABLES` when using `INNOBASE` tables.

- Setting and using user variables in `SELECT DISTINCT` didn't work.

- Tuned `SHOW ANALYZE` for small tables.

- Fixed handling of arguments in the benchmark script `run-all-tests`.

### B.3.26. Changes in release 3.23.34a (11 March 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added extra files to the distribution to allow `INNOBASE` support to be compiled.

### B.3.27. Changes in release 3.23.34 (10 March 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added the `INNOBASE` storage engine and the `BDB` storage engine to the MySQL source distribution.

- Updated the documentation about `GEMINI` tables.

- Fixed a bug in `INSERT DELAYED` that caused threads to hang when inserting `NULL` into an `AUTO_INCREMENT` column.

- Fixed a bug in `CHECK TABLE` / `REPAIR TABLE` that could cause a thread to hang.

- Fixed problem that `REPLACE` would not replace a row that conflicts with an `AUTO_INCREMENT` generated key.

- mysqld now only sets `CLIENT_TRANSACTIONS` in `mysql->server_capabilities` if the server supports a transaction-safe storage engine.

- Fixed `LOAD DATA INFILE` to allow numeric values to be read into `ENUM` and `SET` columns.

- Improved error diagnostic for slave thread exit.

- Fixed bug in `ALTER TABLE ... ORDER BY`.

- Added `max_user_connections` variable to mysqld.

- Limit query length for replication by `max_allowed_packet`, not the arbitrary limit of 4MB.

- Allow space around `=` in argument to `--set-variable`.

- Fixed problem in automatic repair that could leave some threads in state `Waiting for table`.

- `SHOW CREATE TABLE` now displays the `UNION=()` for `MERGE` tables.

- `ALTER TABLE` now remembers the old `UNION=()` definition.

- Fixed bug when replicating timestamps.

- Fixed bug in bidirectional replication.

- Fixed bug in the `BDB` storage engine that occurred when using an index on multiple-part key where a key part may be `NULL`.

- Fixed `MAX()` optimization on sub-key for `BDB` tables.

- Fixed problem where garbage results were returned when using `BDB` tables and `BLOB` or `TEXT` fields when joining many tables.

- Fixed a problem with `BDB` tables and `TEXT` columns.

- Fixed bug when using a `BLOB` key where a const row wasn't found.

- Fixed that mysqlbinlog writes the timestamp value for each query. This ensures that one gets same values for date functions like `NOW()` when using mysqlbinlog to pipe the queries to another server.

- Allow `--skip-gemini`, `--skip-bdb`, and `--skip-innodb` options to be specified when invoking mysqld, even if these storage engines are not compiled in to mysqld.

- You can now use `ASC` and `DESC` with `GROUP BY` columns to specify a sort order.

- Fixed a deadlock in the `SET` code, when one ran `SET @foo=bar`, where `bar` is a column reference, an error was not properly generated.

### B.3.28. Changes in release 3.23.33 (09 February 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed DNS lookups not to use the same mutex as the hostname cache. This enables known hosts to be quickly resolved even if a DNS lookup takes a long time.

- Added `--character-sets-dir` option to myisampack.

- Removed warnings when running `REPAIR TABLE ... EXTENDED`.

- Fixed a bug that caused a core dump when using `GROUP BY` on an alias, where the alias was the same as an existing column name.

- Added `SEQUENCE()` as an example user-defined function.

- Changed mysql_install_db to use `BINARY` for `CHAR` columns in the privilege tables.

- Changed `TRUNCATE `tbl_name`` to `TRUNCATE TABLE `tbl_name`` to use the same syntax as Oracle. Until 4.0 we also allow `TRUNCATE `tbl_name`` to not crash old code.

- Fixed “no found rows” bug in `MyISAM` tables when a `BLOB` was first part of a multiple-part key.

- Fixed bug where `CASE` didn't work with `GROUP BY`.

- Added `--sort-recover` option to myisamchk.

- myisamchk -S and `OPTIMIZE TABLE` now work on Windows.

- Fixed bug when using `DISTINCT` on results from functions that referred to a group function, like:

      SELECT a, DISTINCT SEC_TO_TIME(SUM(a))
      FROM tbl_name GROUP BY a, b;

- Fixed buffer overrun in `libmysqlclient` library. Fixed bug in handling `STOP` event after `ROTATE` event in replication.

- Fixed another buffer overrun in `DROP DATABASE`.

- Added `Table_locks_immediate` and `Table_locks_waited` status variables.

- Fixed bug in replication that broke slave server start with existing `master.info`. This fixes a bug introduced in 3.23.32.

- Added `SET SQL_SLAVE_SKIP_COUNTER=n` command to recover from replication glitches without a full database copy.

- Added `max_binlog_size` variable; the binary log is rotated automatically when the size crosses the limit.

- Added `Last_Error`, `Last_Errno`, and `Slave_skip_counter` variables to `SHOW SLAVE STATUS`.

- Fixed bug in `MASTER_POS_WAIT()` function.

- Execute core dump handler on `SIGILL`, and `SIGBUS` in addition to `SIGSEGV`.

- On x86 Linux, print the current query and thread (connection) id, if available, in the core dump handler.

- Fixed several timing bugs in the test suite.

- Extended mysqltest to take care of the timing issues in the test suite.

- `ALTER TABLE` can now be used to change the definition for a `MERGE` table.

- Fixed creation of `MERGE` tables on Windows.

- Portability fixes for OpenBSD and OS/2.

- Added `--temp-pool` option to mysqld. Using this option causes most temporary files created to use a small set of names, rather than a unique name for each new file. This is to work around a problem in the Linux kernel dealing with creating a bunch of new files with different names. With the old behavior, Linux seems to "leak" memory, as it's being allocated to the directory entry cache instead of the disk cache.

### B.3.29. Changes in release 3.23.32 (22 January 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Changed code to get around compiler bug in Compaq C++ on OSF/1, that broke `BACKUP TABLE`, `RESTORE TABLE`, `CHECK TABLE`, `REPAIR TABLE`, and `ANALYZE TABLE`.

- Added option `FULL` to `SHOW COLUMNS`. Now we show the privilege list for the columns only if this option is given.

- Fixed bug in `SHOW LOGS` when there weren't any `BDB` logs.

- Fixed a timing problem in replication that could delay sending an update to the client until a new update was done.

- Don't convert field names when using `mysql_list_fields()`. This is to keep this code compatible with `SHOW FIELDS`.

- `MERGE` tables didn't work on Windows.

- Fixed problem with `SET PASSWORD=...` on Windows.

- Added missing `my_config.h` to RPM distribution.

- `TRIM("foo" from "foo")` didn't return an empty string.

- Added `--with-version-suffix` option to configure.

- Fixed core dump when client aborted connection without `mysql_close()`.

- Fixed a bug in `RESTORE TABLE` when trying to restore from a non-existent directory.

- Fixed a bug which caused a core dump on the slave when replicating `SET PASSWORD`.

- Added `MASTER_POS_WAIT()` function.

### B.3.30. Changes in release 3.23.31 (17 January 2001: Production)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- The test suite now tests all reachable `BDB` interface code. During testing we found and fixed many errors in the interface code.

- Using `HAVING` on an empty table could produce one result row when it shouldn't.

- Fixed the MySQL RPM so it no longer depends on Perl5.

- Fixed some problems with `HEAP` tables on Windows.

- `SHOW TABLE STATUS` didn't show correct average row length for tables larger than 4GB.

- `CHECK TABLE ... EXTENDED` didn't check row links for fixed size tables.

- Added option `MEDIUM` to `CHECK TABLE`.

- Fixed problem when using `DECIMAL()` keys on negative numbers.

- `HOUR()` (and some other `TIME` functions) on a `CHAR` column always returned `NULL`.

- Fixed security bug in `SHOW GRANT` (please upgrade if you are using an earlier MySQL 3.23 version). (CVE-2001-1275)

- Fixed buffer overflow bug when writing a certain error message. (CVE-2001-1274)

- Added usage of `setrlimit()` on Linux to get `-O --open_files_limit=`val`` to work on Linux.

- Added `bdb_version` variable to mysqld.

- Fixed bug when using expression of type:

      SELECT ... FROM t1 LEFT JOIN t2 ON (t1.a=t2.a) WHERE t1.a=t2.a

  In this case the test in the `WHERE` clause was wrongly optimized away.

- Fixed bug in `MyISAM` when deleting keys with possible `NULL` values, but the first key-column was not a prefix-compressed text column.

- Fixed mysql.server to read the `[mysql.server]` option file group rather than the `[mysql_server]` group.

- Fixed safe_mysqld and mysql.server to also read the `server` option section.

- Added `Threads_created` status variable to mysqld.

### B.3.31. Changes in release 3.23.30 (04 January 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `SHOW OPEN TABLES` command.

- Fixed that `myisamdump` works against old mysqld servers.

- Fixed myisamchk -k`N` so that it works again.

- Fixed a problem with replication when the binary log file went over 2G on 32-bit systems.

- `LOCK TABLES` now automatically starts a new transaction.

- Changed `BDB` tables to not use internal subtransactions and reuse open files to get more speed.

- Added `--mysqld=`path`` option to safe_mysqld.

- Allow hex constants in the `--fields-*-by` and `--lines-terminated-by` options to mysqldump and mysqlimport. By Paul DuBois.

- Added `--safe-show-database` option to mysqld.

- Added `have_bdb`, `have_gemini`, `have_innobase`, `have_raid` and `have_openssl` to `SHOW VARIABLES` to make it easy to test for supported extensions.

- Added `--open-files-limit` option to mysqld.

- Changed `--open-files` option to `--open-files-limit` in safe_mysqld.

- Fixed a bug where some rows were not found with `HEAP` tables that had many keys.

- Fixed that `--bdb-no-sync` works.

- Changed `--bdb-recover` to `--bdb-no-recover` as recover should be on by default.

- Changed the default number of `BDB` locks to 10000.

- Fixed a bug from 3.23.29 when allocating the shared structure needed for `BDB` tables.

- Changed mysqld_multi.sh to use configure variables. Patch by Christopher McCrory.

- Added fixing of include files for Solaris 2.8.

- Fixed bug with `--skip-networking` on Debian Linux.

- Fixed problem that some temporary files where reported as having the name `UNOPENED` in error messages.

- Fixed bug when running two simultaneous `SHOW LOGS` queries.

### B.3.32. Changes in release 3.23.29 (16 December 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Configure updates for Tru64, large file support, and better TCP wrapper support. By Albert Chin-A-Young.

- Fixed bug in `<=>` operator.

- Fixed bug in `REPLACE` with `BDB` tables.

- `LPAD()` and `RPAD()` shortens the result string if it's longer than the length argument.

- Added `SHOW LOGS` command.

- Remove unused `BDB` logs on shutdown.

- When creating a table, put `PRIMARY` keys first, followed by `UNIQUE` keys.

- Fixed a bug in `UPDATE` involving multiple-part keys where you specified all key parts both in the update and the `WHERE` part. In this case MySQL could try to update a record that didn't match the whole `WHERE` part.

- Changed drop table to first drop the tables and then the `.frm` file.

- Fixed a bug in the hostname cache which caused mysqld to report the hostname as `''` in some error messages.

- Fixed a bug with `HEAP` type tables; the variable `max_heap_table_size` wasn't used. Now either `MAX_ROWS` or `max_heap_table_size` can be used to limit the size of a `HEAP` type table.

- Changed the default `server-id` value to 1 for masters and 2 for slaves to make it easier to use the binary log.

- Renamed `bdb_lock_max` variable to `bdb_max_lock`.

- Added support for `AUTO_INCREMENT` on sub-fields for `BDB` tables.

- Added `ANALYZE TABLE` of `BDB` tables.

- In `BDB` tables, we now store the number of rows; this helps to optimize queries when we need an approximation of the number of rows.

- If we get an error in a multiple-row statement, we now only roll back the last statement, not the entire transaction.

- If you do a `ROLLBACK` when you have updated a non-transactional table you get an error as a warning.

- Added `--bdb-shared-data` option to mysqld.

- Added `Slave_open_temp_tables` status variable to mysqld

- Added `binlog_cache_size` and `max_binlog_cache_size` variables to mysqld.

- `DROP TABLE`, `RENAME TABLE`, `CREATE INDEX` and `DROP INDEX` are now transaction endpoints.

- If you do a `DROP DATABASE` on a symbolically linked database, both the link and the original database are deleted.

- Fixed `DROP DATABASE` to work on OS/2.

- Fixed bug when doing a `SELECT DISTINCT ... table1 LEFT JOIN table2 ...` when `table2` was empty.

- Added `--abort-slave-event-count` and `--disconnect-slave-event-count` options to mysqld for debugging and testing of replication.

- Fixed replication of temporary tables. Handles everything except slave server restart.

- `SHOW KEYS` now shows whether key is `FULLTEXT`.

- New script mysqld_multi. See Section 4.3.4, “mysqld_multi — Manage Multiple MySQL Servers”.

- Added new script, `mysql-multi.server.sh`. Thanks to Tim Bunce `<Tim.Bunce@ig.co.uk>` for modifying mysql.server to easily handle hosts running many mysqld processes.

- safe_mysqld, mysql.server, and mysql_install_db have been modified to use `my_print_defaults` instead of various hacks to read the `my.cnf` files. In addition, the handling of various paths has been made more consistent with how mysqld handles them by default.

- Automatically remove Berkeley DB transaction logs that no longer are in use.

- Fixed bug with several `FULLTEXT` indexes in one table.

- Added a warning if number of rows changes on `REPAIR TABLE`/`OPTIMIZE TABLE`.

- Applied patches for OS/2 by `Yuri Dario`.

- `FLUSH TABLES `tbl_name`` didn't always flush the index tree to disk properly.

- `--bootstrap` is now run in a separate thread. This fixes a problem that caused mysql_install_db to core dump on some Linux machines.

- Changed `mi_create()` to use less stack space.

- Fixed bug with optimizer trying to over-optimize `MATCH()` when used with `UNIQUE` key.

- Changed `crash-me` and the MySQL benchmarks to also work with FrontBase.

- Allow `RESTRICT` and `CASCADE` after `DROP TABLE` to make porting easier.

- Reset status variable which could cause problem if one used `--slow-log`.

- Added `connect_timeout` variable to mysql and mysqladmin.

- Added `connect-timeout` as an alias for `timeout` for option files read by `mysql_options()`.

### B.3.33. Changes in release 3.23.28 (22 November 2000: Gamma)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added new options `--pager[=...]`, `--no-pager`, `--tee=...` and `--no-tee` to the mysql client. The new corresponding interactive commands are `pager`, `nopager`, `tee` and `notee`. See Section 4.5.1, “mysql — The MySQL Command-Line Tool”, mysql --help and the interactive help for more information.

- Fixed crash when automatic repair of `MyISAM` table failed.

- Fixed a major performance bug in the table locking code when a lot of `SELECT`, `UPDATE` and `INSERT` statements constantly were running. The symptom was that the `UPDATE` and `INSERT` queries were locked for a long time while new `SELECT` statements were executed before the updates.

- When reading `options_files` with `mysql_options()` the `return-found-rows` option was ignored.

- You can now specify `interactive-timeout` in the option file that is read by `mysql_options()`. This makes it possible to force programs that run for a long time (like mysqlhotcopy) to use the `interactive_timeout` time instead of the `wait_timeout` time.

- Added to the slow query log the time and the username for each logged query. If you are using `--log-long-format` then also queries that do not use an index are logged, even if the query takes less than `long_query_time` seconds.

- Fixed a problem in `LEFT JOIN` which caused all columns in a reference table to be `NULL`.

- Fixed a problem when using `NATURAL JOIN` without keys.

- Fixed a bug when using a multiple-part keys where the first part was of type `TEXT` or `BLOB`.

- `DROP` of temporary tables wasn't stored in the update/binary log.

- Fixed a bug where `SELECT DISTINCT * ... LIMIT `row_count`` only returned one row.

- Fixed a bug in the assembler code in `strstr()` for SPARC and cleaned up the `global.h` header file to avoid a problem with bad aliasing with the compiler submitted with Red Hat 7.0. (Reported by Trond Eivind Glomsrød)

- The `--skip-networking` option now works properly on NT.

- Fixed a long outstanding bug in the `ISAM` tables when a row with a length of more than 65KB was shortened by a single byte.

- Fixed a bug in `MyISAM` when running multiple updating processes on the same table.

- Allow one to use `FLUSH TABLE `tbl_name``.

- Added `--replicate-ignore-table`, `--replicate-do-table`, `--replicate-wild-ignore-table`, and `--replicate-wild-do-table` options to mysqld.

- Changed all log files to use our own `IO_CACHE` mechanism instead of `FILE` to avoid OS problems when there are many files open.

- Added `--open-files` and `--timezone` options to safe_mysqld.

- Fixed a fatal bug in `CREATE TEMPORARY TABLE ... SELECT ...`.

- Fixed a problem with `CREATE TABLE ... SELECT NULL`.

- Added variables `large_file_support`,`net_read_timeout`, `net_write_timeout` and `query_buffer_size` to `SHOW VARIABLES`.

- Added status variables `Created_tmp_files` and `Sort_merge_passes` to `SHOW STATUS`.

- Fixed a bug where we didn't allow an index name after the `FOREIGN KEY` definition.

- Added `TRUNCATE `tbl_name`` as a synonym for `DELETE FROM `tbl_name``.

- Fixed a bug in a `BDB` key compare function when comparing part keys.

- Added `bdb_lock_max` variable to mysqld.

- Added more tests to the benchmark suite.

- Fixed an overflow bug in the client code when using overly long database names.

- `mysql_connect()` now aborts on Linux if the server doesn't answer in `timeout` seconds.

- `SLAVE START` did not work if you started with `--skip-slave-start` and had not explicitly run `CHANGE MASTER TO`.

- Fixed the output of `SHOW MASTER STATUS` to be consistent with `SHOW SLAVE STATUS`. (It now has no directory in the log name.)

- Added `PURGE MASTER LOGS TO`.

- Added `SHOW MASTER LOGS` statement to display a list of binary log files.

- Added `--safemalloc-mem-limit` option to mysqld to simulate memory shortage when compiled with the `--with-debug=full` option.

- Fixed several core dumps in out-of-memory conditions.

- `SHOW SLAVE STATUS` was using an uninitialized mutex if the slave had not been started yet.

- Fixed bug in `ELT()` and `MAKE_SET()` when the query used a temporary table.

- `CHANGE MASTER TO` without specifying `MASTER_LOG_POS` would set it to 0 instead of 4 and hit the magic number in the master binary log.

- `ALTER TABLE ... ORDER BY ...` syntax added. This creates the new table with the rows in a specific order.

### B.3.34. Changes in release 3.23.27 (24 October 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed a bug where the automatic repair of `MyISAM` tables sometimes failed when the data file was corrupt.

- Fixed a bug in `SHOW CREATE` when using `AUTO_INCREMENT` columns.

- Changed `BDB` tables to use new compare function in Berkeley DB 3.2.3.

- You can now use Unix socket files with MIT-pthreads.

- Added the `latin5` (turkish) character set.

- Small portability fixes.

### B.3.35. Changes in release 3.23.26 (18 October 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Renamed `FLUSH MASTER` and `FLUSH SLAVE` to `RESET MASTER` and `RESET SLAVE`.

- Fixed `<>` to work properly with `NULL`.

- Fixed a problem with `SUBSTRING_INDEX()` and `REPLACE()`. (Patch by Alexander Igonitchev)

- Fix `CREATE TEMPORARY TABLE IF NOT EXISTS` not to produce an error if the table exists.

- If you don't create a `PRIMARY KEY` in a `BDB` table, a hidden `PRIMARY KEY` is created.

- Added read-only-key optimization to `BDB` tables.

- `LEFT JOIN` in some cases preferred a full table scan when there was no `WHERE` clause.

- When using `--log-slow-queries`, don't count the time waiting for a lock.

- Fixed bug in lock code on Windows which could cause the key cache to report that the key file was crashed even if it was okay.

- Automatic repair of `MyISAM` tables if you start mysqld with `--myisam-recover`.

- Removed the `TYPE=` keyword from `CHECK TABLE` and `REPAIR TABLE`. Allow `CHECK TABLE` options to be combined. (You can still use `TYPE=`, but this usage is deprecated.)

- Fixed mutex bug in the binary replication log --- long update queries could be read only in part by the slave if it did it at the wrong time, which was not fatal, but resulted in a performance-degrading reconnect and a scary message in the error log.

- Changed the format of the binary log --- added magic number, server version, binary log version. Added the server ID and query error code for each query event.

- Replication thread from the slave now kills all the stale threads from the same server.

- Long replication usernames were not being handled properly.

- Added `--replicate-rewrite-db` option to mysqld.

- Added `--skip-slave-start` option to mysqld.

- Updates that generated an error code (such as `INSERT INTO foo(some_key) values (1),(1)`) erroneously terminated the slave thread.

- Added optimization of queries where `DISTINCT` is used only on columns from some of the tables.

- Allow floating-point numbers where there is no sign after the exponent (like `1e1`).

- `SHOW GRANTS` didn't always show all column grants.

- Added `--default-extra-file=`file_name`` option to all MySQL clients.

- Columns referenced in `INSERT` statements now are initialized properly.

- `UPDATE` didn't always work when used with a range on a timestamp that was part of the key that was used to find rows.

- Fixed a bug in `FULLTEXT` index when inserting a `NULL` column.

- Changed to use `mkstemp()` instead of `tempnam()`. Based on a patch from John Jones.

### B.3.36. Changes in release 3.23.25 (29 September 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed that `databasename` works as second argument to mysqlhotcopy.

- The values for the `UMASK` and `UMASK_DIR` environment variables now can be specified in octal by beginning the value with a zero.

- Added `RIGHT JOIN`. This makes `RIGHT` a reserved word.

- Added `@@IDENTITY` as a synonym for `LAST_INSERT_ID()`. (This is for MSSQL compatibility.)

- Fixed a bug in myisamchk and `REPAIR TABLE` when using `FULLTEXT` index.

- `LOAD DATA INFILE` now works with FIFOs. (Patch by Toni L. Harbaugh-Blackford.)

- `FLUSH LOGS` broke replication if you specified a log name with an explicit extension as the value of the `log-bin` option.

- Fixed a bug in `MyISAM` with packed multiple-part keys.

- Fixed crash when using `CHECK TABLE` on Windows.

- Fixed a bug where `FULLTEXT` index always used the `koi8_ukr` character set.

- Fixed privilege checking for `CHECK TABLE`.

- The `MyISAM` repair/reindex code didn't use the `--tmpdir` option for its temporary files.

- Added `BACKUP TABLE` and `RESTORE TABLE`.

- Fixed core dump on `CHANGE MASTER TO` when the slave did not have the master to start with.

- Fixed incorrect `Time` in the processlist for `Connect` of the slave thread.

- The slave now logs when it connects to the master.

- Fixed a core dump bug when doing `FLUSH MASTER` if you didn't specify a filename argument to `--log-bin`.

- Added missing `ha_berkeley.x` files to the MySQL Windows distribution.

- Fixed some mutex bugs in the log code that could cause thread blocks if new log files couldn't be created.

- Added lock time and number of selected processed rows to slow query log.

- Added `--memlock` option to mysqld to lock mysqld in memory on systems with the `mlockall()` call (as in Solaris).

- `HEAP` tables didn't use keys properly. (Bug from 3.23.23.)

- Added better support for `MERGE` tables (keys, mapping, creation, documentation...). See Section 13.3, “The `MERGE` Storage Engine”.

- Fixed bug in mysqldump from 3.23 which caused some `CHAR` columns not to be quoted.

- Merged `analyze`, `check`, `optimize` and repair code.

- `OPTIMIZE TABLE` is now mapped to `REPAIR TABLE` with statistics and sorting of the index tree. This means that for the moment it only works on `MyISAM` tables.

- Added a pre-alloced block to root_malloc to get fewer mallocs.

- Added a lot of new statistics variables.

- Fixed `ORDER BY` bug with `BDB` tables.

- Removed warning that mysqld couldn't remove the `.pid` file under Windows.

- Changed `--log-isam` to log `MyISAM` tables instead of isam tables.

- Fixed `CHECK TABLE` to work on Windows.

- Added file mutexes to make `pwrite()` safe on Windows.

### B.3.37. Changes in release 3.23.24 (08 September 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `Created_tmp_disk_tables` variable to mysqld.

- To make it possible to reliably dump and restore tables with `TIMESTAMP(`X`)` columns, MySQL now reports columns with `X` other than 14 or 8 to be strings.

- Changed sort order for `latin1` as it was before MySQL 3.23.23. Any table that was created or modified with 3.23.22 must be repaired if it has `CHAR` columns that may contain characters with ASCII values greater than 128!

- Fixed small memory leak introduced from 3.23.22 when creating a temporary table.

- Fixed problem with `BDB` tables and reading on a unique (not primary) key.

- Restored the `win1251` character set (it's now only marked deprecated).

### B.3.38. Changes in release 3.23.23 (01 September 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Changed sort order for 'German'; all tables created with 'German' sortorder must be repaired with `REPAIR TABLE` or myisamchk before use!

- Added `--core-file` option to mysqld to get a core file on Linux if mysqld dies on the `SIGSEGV` signal.

- MySQL client mysql now starts with option `--no-named-commands` (`-g`) by default. This option can be disabled with `--enable-named-commands` (`-G`). This may cause incompatibility problems in some cases, for example, in SQL scripts that use named commands without a semicolon! Long format commands still work from the first line.

- Fixed a problem when using many pending `DROP TABLE` statements at the same time.

- Optimizer didn't use keys properly when using `LEFT JOIN` on an empty table.

- Added shorter help text when invoking mysqld with incorrect options.

- Fixed non-fatal `free()` bug in mysqlimport.

- Fixed bug in `MyISAM` index handling of `DECIMAL`/`NUMERIC` keys.

- Fixed a bug in concurrent insert in `MyISAM` tables. In some contexts, usage of `MIN(key_part)` or `MAX(key_part)` returned an empty set.

- Updated mysqlhotcopy to use the new `FLUSH TABLES table_list` syntax. Only tables which are being backed up are flushed now.

- Changed behavior of `--enable-thread-safe-client` so that both non-threaded (`-lmysqlclient`) and threaded (`-lmysqlclient_r`) libraries are built. Users who linked against a threaded `-lmysqlclient` need to link against `-lmysqlclient_r` now.

- Added atomic `RENAME TABLE` command.

- Don't count `NULL` values in `COUNT(DISTINCT ...)`.

- Changed `ALTER TABLE`, `LOAD DATA INFILE` on empty tables and `INSERT ... SELECT ...` on empty tables to create non-unique indexes in a separate batch with sorting. This makes these statements much faster when you have many indexes.

- `ALTER TABLE` now logs the first used insert_id correctly.

- Fixed crash when adding a default value to a `BLOB` column.

- Fixed a bug with `DATE_ADD/DATE_SUB` where it returned a datetime instead of a date.

- Fixed a problem with the thread cache which made some threads show up as `***DEAD***` in `SHOW PROCESSLIST`.

- Fixed a lock in our thr_rwlock code, which could make selects that run at the same time as concurrent inserts crash. This affects only systems that don't have the `pthread_rwlock_rdlock` code.

- When deleting rows with a non-unique key in a `HEAP` table, all rows weren't always deleted.

- Fixed bug in range optimizer for `HEAP` tables for searches on a part index.

- Fixed `SELECT` on part keys to work with `BDB` tables.

- Fixed `INSERT INTO bdb_table ... SELECT` to work with `BDB` tables.

- `CHECK TABLE` now updates key statistics for the table.

- `ANALYZE TABLE` now only updates tables that have been changed since the last `ANALYZE TABLE`. Note that this is a new feature and tables are not marked to be analyzed until they are updated in any way with 3.23.23 or newer. For older tables, you have to do `CHECK TABLE` to update the key distribution.

- Fixed some minor privilege problems with `CHECK TABLE`, `ANALYZE TABLE`, `REPAIR TABLE` and `SHOW CREATE` commands.

- Added `CHANGE MASTER TO` statement.

- Added `FAST`, `QUICK` `EXTENDED` check types to `CHECK TABLES`.

- Changed myisamchk so that `--fast` and `--check-only-changed` are also honored with `--sort-index` and `--analyze`.

- Fixed fatal bug in `LOAD TABLE FROM MASTER` that did not lock the table during index re-build.

- `LOAD DATA INFILE` broke replication if the database was excluded from replication.

- More variables in `SHOW SLAVE STATUS` and `SHOW MASTER STATUS`.

- `SLAVE STOP` now does not return until the slave thread actually exits.

- Full-text search via the `MATCH()` function and `FULLTEXT` index type (for `MyISAM` files). This makes `FULLTEXT` a reserved word.

### B.3.39. Changes in release 3.23.22 (31 July 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed that `lex_hash.h` is created properly for each MySQL distribution.

- Fixed that `MASTER` and `COLLECTION` are not reserved words.

- The log generated by `--slow-query-log` didn't contain the whole queries.

- Fixed that open transactions in `BDB` tables are rolled back if the connection is closed unexpectedly.

- Added workaround for a bug in gcc 2.96 (intel) and gcc 2.9 (IA-64) in `gen_lex_hash.c`.

- Fixed memory leak in the client library when using `host=` in the `my.cnf` file.

- Optimized functions that manipulate the hours/minutes/seconds.

- Fixed bug when comparing the result of `DATE_ADD()`/`DATE_SUB()` against a number.

- Changed the meaning of `-F`, `--fast` for myisamchk. Added `-C`, `--check-only-changed` option to myisamchk.

- Added `ANALYZE `tbl_name`` to update key statistics for tables.

- Changed binary items `0x...` to be regarded as integers by default.

- Fix for SCO and `SHOW PROCESSLIST`.

- Added `auto-rehash` on reconnect for the mysql client.

- Fixed a newly introduced bug in `MyISAM`, where the index file couldn't get bigger than 64MB.

- Added `SHOW MASTER STATUS` and `SHOW SLAVE STATUS`.

### B.3.40. Changes in release 3.23.21 (04 July 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `mysql_character_set_name()` function to the MySQL C API.

- Made the update log ASCII 0 safe.

- Added the mysql_config script.

- Fixed problem when using `<` or `>` with a char column that was only partly indexed.

- One would get a core dump if the log file was not readable by the MySQL user.

- Changed mysqladmin to use `CREATE DATABASE` and `DROP DATABASE` statements instead of the old deprecated API calls.

- Fixed `chown` warning in safe_mysqld.

- Fixed a bug in `ORDER BY` that was introduced in 3.23.19.

- Only optimize the `DELETE FROM `tbl_name`` to do a drop+create of the table if we are in `AUTOCOMMIT` mode (needed for `BDB` tables).

- Added extra checks to avoid index corruption when the `ISAM`/`MyISAM` index files get full during an `INSERT`/`UPDATE`.

- myisamchk didn't correctly update row checksum when used with `-ro` (this only gave a warning in subsequent runs).

- Fixed bug in `REPAIR TABLE` so that it works with tables without indexes.

- Fixed buffer overrun in `DROP DATABASE`.

- `LOAD TABLE FROM MASTER` is sufficiently bug-free to announce it as a feature.

- `MATCH` and `AGAINST` are now reserved words.

### B.3.41. Changes in release 3.23.20 (28 June 2000: Beta)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed bug in 3.23.19; `DELETE FROM `tbl_name`` removed the `.frm` file.

- Added `SHOW CREATE TABLE`.

### B.3.42. Changes in release 3.23.19

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Changed copyright for all files to GPL for the server code and utilities and to LGPL for the client libraries. See http://www.fsf.org/licenses/.

- Fixed bug where all rows matching weren't updated on a `MyISAM` table when doing update based on key on a table with many keys and some key changed values.

- The Linux MySQL RPMs and binaries are now statically linked with a linuxthread version that has faster mutex handling when used with MySQL.

- `ORDER BY` can now use `REF` keys to find subsets of the rows that need to be sorted.

- Changed name of print_defaults program to my_print_defaults to avoid name confusion.

- Fixed `NULLIF()` to work as required by standard SQL.

- Added `net_read_timeout` and `net_write_timeout` as startup parameters to mysqld.

- Fixed bug that destroyed index when doing myisamchk --sort-records on a table with prefix compressed index.

- Added pack_isam and myisampack to the standard MySQL distribution.

- Added the syntax `BEGIN WORK` (the same as `BEGIN`).

- Fixed core dump bug when using `ORDER BY` on a `CONV()` expression.

- Added `LOAD TABLE FROM MASTER`.

- Added `FLUSH MASTER` and `FLUSH SLAVE`.

- Fixed big/little endian problem in the replication.

### B.3.43. Changes in release 3.23.18 (11 June 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed a problem from 3.23.17 when choosing character set on the client side.

- Added `FLUSH TABLES WITH READ LOCK` to make a global lock suitable for making a copy of MySQL data files.

- `CREATE TABLE ... SELECT ... PROCEDURE` now works.

- Internal temporary tables now use compressed index when using `GROUP BY` on `VARCHAR/CHAR` columns.

- Fixed a problem when locking the same table with both a `READ` and a `WRITE` lock.

- Fixed problem with myisamchk and `RAID` tables.

### B.3.44. Changes in release 3.23.17 (07 June 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed a bug in `FIND_IN_SET()` when the first argument was `NULL`.

- Added table locks to Berkeley DB.

- Fixed a bug with `LEFT JOIN` and `ORDER BY` where the first table had only one matching row.

- Added 4 sample `my.cnf` example files in the `support-files` directory.

- Fixed `duplicated key` problem when doing big `GROUP BY` operations. (This bug was probably introduced in 3.23.15.)

- Changed syntax for `INNER JOIN` to match standard SQL.

- Added `NATURAL JOIN` syntax.

- A lot of fixes in the `BDB` interface.

- Added handling of `--no-defaults` and `--defaults-file` to safe_mysqld.sh and mysql_install_db.sh.

- Fixed bug in reading compressed tables with many threads.

- Fixed that `USE INDEX` works with `PRIMARY` keys.

- Added `BEGIN` statement to start a transaction in `AUTOCOMMIT` mode.

- Added support for symbolic links for Windows.

- Changed protocol to let client know if the server is in `AUTOCOMMIT` mode and if there is a pending transaction. If there is a pending transaction, the client library gives an error before reconnecting to the server to let the client know that the server did a rollback. The protocol is still backward-compatible with old clients.

- `KILL` now works on a thread that is locked on a 'write' to a dead client.

- Fixed memory leak in the replication slave thread.

- Added new `log-slave-updates` option to mysqld, to allow daisy-chaining the slaves.

- Fixed compile error on FreeBSD and other systems where `pthread_t` is not the same as `int`.

- Fixed master shutdown aborting the slave thread.

- Fixed a race condition in `INSERT DELAYED` code when doing `ALTER TABLE`.

- Added deadlock detection sanity checks to `INSERT DELAYED`.

### B.3.45. Changes in release 3.23.16 (16 May 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `SLAVE START` and `SLAVE STOP` statements.

- Added `TYPE=QUICK` option to `CHECK TABLE` and to `REPAIR TABLE`.

- Fixed bug in `REPAIR TABLE` when the table was in use by other threads.

- Added a thread cache to make it possible to debug MySQL with gdb when one does a lot of reconnects. This also improves systems where you can't use persistent connections.

- Lots of fixes in the Berkeley DB interface.

- `UPDATE IGNORE` does not abort if an update results in a `DUPLICATE_KEY` error.

- Put `CREATE TEMPORARY TABLE` commands in the update log.

- Fixed bug in handling of masked IP numbers in the privilege tables.

- Fixed bug with `delay_key_write` tables and `CHECK TABLE`.

- Added `--replicate-do-db` and `--replicate-ignore-db` options to mysqld, to restrict which databases get replicated.

- Added `SQL_LOG_BIN` option.

### B.3.46. Changes in release 3.23.15 (08 May 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- To start mysqld as `root`, you must now use the `--user=root` option.

- Added interface to Berkeley DB. (This is not yet functional; play with it at your own risk!)

- Replication between master and slaves.

- Fixed bug that other threads could steal a lock when a thread had a lock on a table and did a `FLUSH TABLES` command.

- Added the `slow_launch_time` variable and the `Slow_launch_threads` status variable to mysqld. These can be examined with mysqladmin variables and mysqladmin extended-status.

- Added functions `INET_NTOA()` and `INET_ATON()`.

- The default type of `IF()` now depends on the second and third arguments and not only on the second argument.

- Fixed case when myisamchk could go into a loop when trying to repair a crashed table.

- Don't write `INSERT DELAYED` to update log if `SQL_LOG_UPDATE=0`.

- Fixed problem with `REPLACE` on `HEAP` tables.

- Added possible character sets and time zone to `SHOW VARIABLES` output.

- Fixed bug in locking code that could result in locking problems with concurrent inserts under high load.

- Fixed a problem with `DELETE` of many rows on a table with compressed keys where MySQL scanned the index to find the rows.

- Fixed problem with `CHECK TABLE` on table with deleted keyblocks.

- Fixed a bug in reconnect (at the client side) where it didn't free memory properly in some contexts.

- Fixed problems in update log when using `LAST_INSERT_ID()` to update a table with an `AUTO_INCREMENT` key.

- Added `NULLIF()` function.

- Fixed bug when using `LOAD DATA INFILE` on a table with `BLOB/TEXT` columns.

- Optimized `MyISAM` to be faster when inserting keys in sorted order.

- `EXPLAIN SELECT ...` now also prints out whether MySQL needs to create a temporary table or use file sorting when resolving the `SELECT`.

- Added optimization to skip `ORDER BY` parts where the part is a constant expression in the `WHERE` part. Indexes can now be used even if the `ORDER BY` doesn't match the index exactly, as long as all the unused index parts and all the extra `ORDER BY` columns are constants in the `WHERE` clause. See Section 7.4.5, “How MySQL Uses Indexes”.

- `UPDATE` and `DELETE` on a whole unique key in the `WHERE` part are now faster than before.

- Changed `RAID_CHUNKSIZE` to be in 1024-byte increments.

- Fixed core dump in `LOAD_FILE(NULL)`.

### B.3.47. Changes in release 3.23.14 (09 April 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added mysqlbinlog program for displaying binary log files in text format.

- Added `mysql_real_escape_string()` function to the MySQL C API.

- Fixed a bug in `CONCAT()` where one of the arguments was a function that returned a modified argument.

- Fixed a critical bug in myisamchk, where it updated the header in the index file when one only checked the table. This confused the mysqld daemon if it updated the same table at the same time. Now the status in the index file is only updated if one uses `--update-state`. With older myisamchk versions you should use `--read-only` when only checking tables, if there is the slightest chance that the mysqld server is working on the table at the same time!

- Fixed that `DROP TABLE` is logged in the update log.

- Fixed problem when searching on `DECIMAL()` key field where the column data contained leading zeros.

- Fix bug in myisamchk when the `AUTO_INCREMENT` column isn't the first key.

- Allow `DATETIME` in ISO8601 format: 2000-03-12T12:00:00

- Dynamic character sets. A mysqld binary can now handle many different character sets (you can choose which when starting mysqld).

- Added `REPAIR TABLE` statement.

- Added `mysql_thread_safe()` function to the MySQL C API.

- Added the `UMASK_DIR` environment variable.

- Added `CONNECTION_ID()` function to return the client connection thread ID.

- When using `=` on `BLOB` or `VARCHAR BINARY` keys, where only a part of the column was indexed, the whole column of the result row wasn't compared.

- Fix for `sjis` character set and `ORDER BY`.

- When running in ANSI mode, don't allow columns to be used that aren't in the `GROUP BY` part.

### B.3.48. Changes in release 3.23.13 (14 March 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed problem when doing locks on the same table more than 2 times in the same `LOCK TABLE` command; this fixed the problem one got when running the test-ATIS test with `--fast` or `--check-only-changed`.

- Added `SQL_BUFFER_RESULT` option to `SELECT`.

- Removed endspace from double/float numbers in results from temporary tables.

- Added `CHECK TABLE` command.

- Added changes for `MyISAM` in 3.23.12 that didn't get into the source distribution because of CVS problems.

- Fixed bug so that mysqladmin shutdown waits for the local server to close down.

- Fixed a possible endless loop when calculating timestamp.

- Added print_defaults program to the `.rpm` files. Removed mysqlbug from the client `.rpm` file.

### B.3.49. Changes in release 3.23.12 (07 March 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed bug in `MyISAM` involving `REPLACE ... SELECT ...` which could give a corrupted table.

- Fixed bug in myisamchk where it incorrectly reset the `AUTO_INCREMENT` value.

- LOTS of patches for Linux Alpha. MySQL now appears to be relatively stable on Alpha.

- Changed `DISTINCT` on `HEAP` temporary tables to use hashed keys to quickly find duplicated rows. This mostly concerns queries of type `SELECT DISTINCT ... GROUP BY ...`. This fixes a problem where not all duplicates were removed in queries of the above type. In addition, the new code is MUCH faster.

- Added patches to make MySQL compile on Mac OS X.

- Added `IF NOT EXISTS` clause to `CREATE DATABASE`.

- Added `--all-databases` and `--databases` options to mysqldump to allow dumping of many databases at the same time.

- Fixed bug in compressed `DECIMAL()` index in `MyISAM` tables.

- Fixed bug when storing 0 into a timestamp.

- When doing mysqladmin shutdown on a local connection, mysqladmin now waits until the PID file is gone before terminating.

- Fixed core dump with some `COUNT(DISTINCT ...)` queries.

- Fixed that myisamchk works properly with RAID tables.

- Fixed problem with `LEFT JOIN` and ``key_col` IS NULL`.

- Fixed bug in `net_clear()` which could give the error `Aborted connection` in the MySQL clients.

- Added options `USE INDEX (`index_list`)` and `IGNORE INDEX (`index_list`)` as parameters in `SELECT`.

- `DELETE` and `RENAME` should now work on `RAID` tables.

### B.3.50. Changes in release 3.23.11 (16 February 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `HIGH_PRIORITY` option to `INSERT`. This overrides the effect of the `--low-priority-updates` server option and does not perform concurrent inserts.

- Allow the `ALTER TABLE `tbl_name` ADD (field_list)` syntax.

- Fixed problem with optimizer that could sometimes use incorrect keys.

- Fixed that `GRANT/REVOKE ALL PRIVILEGES` doesn't affect `GRANT OPTION`.

- Removed extra “`)`” from the output of `SHOW GRANTS`.

- Fixed problem when storing numbers in timestamps.

- Fix problem with time zones that have half hour offsets.

- Allow the syntax `UNIQUE INDEX` in `CREATE` statements.

- mysqlhotcopy - fast online hot-backup utility for local MySQL databases. By Tim Bunce.

- New more secure mysqlaccess. Thanks to Steve Harvey for this.

- Added `--i-am-a-dummy` and `--safe-updates` options to mysql.

- Added `select_limit` and `max_join_size` variables to mysql.

- Added `SQL_MAX_JOIN_SIZE` and `SQL_SAFE_UPDATES` options.

- Added `READ LOCAL` lock that doesn't lock the table for concurrent inserts. (This is used by mysqldump.)

- Changed that `LOCK TABLES ... READ` no longer allows concurrent inserts.

- Added `--skip-delay-key-write` option to mysqld.

- Fixed security problem in the protocol regarding password checking.

- `_rowid` can now be used as an alias for an integer type unique indexed column.

- Added back blocking of `SIGPIPE` when compiling with `--thread-safe-clients` to make things safe for old clients.

### B.3.51. Changes in release 3.23.10 (30 January 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed bug in 3.23.9 where memory wasn't properly freed when using `LOCK TABLES`.

### B.3.52. Changes in release 3.23.9 (29 January 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed problem that affected queries that did arithmetic on group functions.

- Fixed problem with timestamps and `INSERT DELAYED`.

- Fixed that `date_col BETWEEN const_date AND const_date` works.

- Fixed problem when only changing a 0 to `NULL` in a table with `BLOB/TEXT` columns.

- Fixed bug in range optimizer when using many key parts and or on the middle key parts: `WHERE K1=1 and K3=2 and (K2=2 and K4=4 or K2=3 and K4=5)`

- Added `source` command to mysql to allow reading of batch files inside the mysql client. Original patch by Matthew Vanecek.

- Fixed critical problem with the `WITH GRANT OPTION` option.

- Don't give an unnecessary `GRANT` error when using tables from many databases in the same query.

- Added VIO wrapper (needed for SSL support; by Andrei Errapart and Tõnu Samuel).

- Fixed optimizer problem on `SELECT` when using many overlapping indexes. MySQL should now be able to choose keys even better when there are many keys to choose from.

- Changed optimizer to prefer a range key instead of a ref key when the range key can uses more columns than the ref key (which only can use columns with `=`). For example, the following type of queries should now be faster: `SELECT * from key_part_1=const and key_part_2 > const2`

- Fixed bug that a change of all `VARCHAR` columns to `CHAR` columns didn't change row type from dynamic to fixed.

- Disabled floating-point exceptions for FreeBSD to fix core dump when doing `SELECT FLOOR(POW(2,63))`.

- Renamed mysqld startup option from `--delay-key-write` to `--delay-key-write-for-all-tables`.

- Added `read-next-on-key` to `HEAP` tables. This should fix all problems with `HEAP` tables when using non-`UNIQUE` keys.

- Added option to print default arguments to all clients.

- Added `--log-slow-queries` option to mysqld to log all queries that take a long time to a separate log file with a time indicating how long the query took.

- Fixed core dump when doing `WHERE `key_col`=RAND(...)`.

- Fixed optimization bug in `SELECT ... LEFT JOIN ... `key_col` IS NULL`, when `key_col` could contain `NULL` values.

- Fixed problem with 8-bit characters as separators in `LOAD DATA INFILE`.

### B.3.53. Changes in release 3.23.8 (02 January 2000)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed problem when handling indexfiles larger than 8GB.

- Added latest patches to MIT-pthreads for NetBSD.

- Fixed problem with time zones that are < GMT - 11.

- Fixed a bug when deleting packed keys in `NISAM`.

- Fixed problem with `ISAM` when doing some `ORDER BY ... DESC` queries.

- Fixed bug when doing a join on a text key which didn't cover the whole key.

- Option `--delay-key-write` didn't enable delayed key writing.

- Fixed update of `TEXT` column which involved only case changes.

- Fixed that `INSERT DELAYED` doesn't update timestamps that are given.

- Added function `YEARWEEK()` and options `x`, `X`, `v` and `V` to `DATE_FORMAT()`.

- Fixed problem with `MAX(indexed_column)` and `HEAP` tables.

- Fixed problem with `BLOB NULL` keys and `LIKE "prefix%"`.

- Fixed problem with `MyISAM` and fixed-length rows < 5 bytes.

- Fixed problem that could cause MySQL to touch freed memory when doing very complicated `GROUP BY` queries.

- Fixed core dump if you got a crashed table where an `ENUM` field value was too big.

### B.3.54. Changes in release 3.23.7 (10 December 1999)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed workaround under Linux to avoid problems with `pthread_mutex_timedwait()`, which is used with `INSERT DELAYED`. See Section 2.13.1, “Linux Notes”.

- Fixed that one get a 'disk full' error message if one gets disk full when doing sorting (instead of waiting until we got more disk space).

- Fixed a bug in `MyISAM` with keys > 250 characters.

- In `MyISAM` one can now do an `INSERT` at the same time as other threads are reading from the table.

- Added `max_write_lock_count` variable to mysqld to force a `READ` lock after a certain number of `WRITE` locks.

- Inverted flag `delay_key_write` on `show variables`.

- Renamed `concurrency` variable to `thread_concurrency`.

- The following functions are now multi-byte-safe: `LOCATE(`substr`,`str`)`, `POSITION(`substr` IN `str`)`, `LOCATE(`substr`,`str`,`pos`)`, `INSTR(`str`,`substr`)`, `LEFT(`str`,`len`)`, `RIGHT(`str`,`len`)`, `SUBSTRING(`str`,`pos`,`len`)`, `SUBSTRING(`str` FROM `pos` FOR `len`)`, `MID(`str`,`pos`,`len`)`, `SUBSTRING(`str`,`pos`)`, `SUBSTRING(`str` FROM `pos`)`, `SUBSTRING_INDEX(`str`,`delim`,`count`)`, `RTRIM(`str`)`, `TRIM([[BOTH | TRAILING] [`remstr`] FROM] `str`)`, `REPLACE(`str`,`from_str`,`to_str`)`, `REVERSE(`str`)`, `INSERT(`str`,`pos`,`len`,`newstr`)`, `LCASE(`str`)`, `LOWER(`str`)`, `UCASE(`str`)` and `UPPER(`str`)`; patch by Wei He.

- Fix core dump when releasing a lock from a non-existent table.

- Remove locks on tables before starting to remove duplicates.

- Added option `FULL` to `SHOW PROCESSLIST`.

- Added option `--verbose` to mysqladmin.

- Fixed problem when automatically converting `HEAP` to `MyISAM`.

- Fixed bug in `HEAP` tables when doing insert + delete + insert + scan the table.

- Fixed bugs on Alpha with `REPLACE()` and `LOAD DATA INFILE`.

- Added `interactive_timeout` variable to mysqld.

- Changed the argument to `mysql_data_seek()` from `ulong` to `ulonglong`.

### B.3.55. Changes in release 3.23.6 (15 December 1999)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added `-O lower_case_table_names={0|1}` option to mysqld to allow users to force table names to lowercase.

- Added `SELECT ... INTO DUMPFILE`.

- Added `--ansi` option to mysqld to make some functions standard SQL compatible.

- Temporary table names now start with `#sql`.

- Added quoting of identifiers with ``` (`"` in `--ansi` mode).

- Changed to use `snprintf()` when printing floats to avoid some buffer overflows on FreeBSD.

- Made `FLOOR()` overflow safe on FreeBSD.

- Added `--quote-names` option to mysqldump.

- Fixed bug that one could make a part of a `PRIMARY KEY NOT NULL`.

- Fixed `encrypt()` to be thread-safe and not reuse buffer.

- Added `mysql_odbc_escape_string()` function to support big5 characters in MyODBC.

- Rewrote the storage engine to use classes. This introduces a lot of new code, but make table handling faster and better.

- Added patch by Sasha for user-defined variables.

- Changed that `FLOAT` and `DOUBLE` (without any length modifiers) no longer are fixed decimal point numbers.

- Changed the meaning of `FLOAT(`X`)`: Now this is the same as `FLOAT` if `X` <= 24 and a `DOUBLE` if 24 < `X` <= 53.

- `DECIMAL(`X`)` is now an alias for `DECIMAL(`X`,0)` and `DECIMAL` is now an alias for `DECIMAL(10,0)`. The same goes for `NUMERIC`.

- Added option `ROW_FORMAT={DEFAULT | DYNAMIC | FIXED | COMPRESSED}` to `CREATE_TABLE`.

- `DELETE FROM `tbl_name`` didn't work on temporary tables.

- Changed function `CHAR_LENGTH()` to be multi-byte character safe.

- Added function `ORD(string)`.

### B.3.56. Changes in release 3.23.5 (20 October 1999)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed some Y2K problems in the new date handling in 3.23.

- Fixed problem with `SELECT DISTINCT ... ORDER BY RAND()`.

- Added patches by Sergei A. Golubchik for text searching on the `MyISAM` level.

- Fixed cache overflow problem when using full joins without keys.

- Fixed some configure issues.

- Some small changes to make parsing faster.

- Adding a column after the last field with `ALTER TABLE` didn't work.

- Fixed problem when using an `AUTO_INCREMENT` column in two keys

- With `MyISAM`, you now can have an `AUTO_INCREMENT` column as a key sub part: `CREATE TABLE foo (a INT NOT NULL AUTO_INCREMENT, b CHAR(5), PRIMARY KEY (b,a))`

- Fixed bug in `MyISAM` with packed char keys that could be `NULL`.

- `AS` on field name with `CREATE TABLE `tbl_name` SELECT ...` didn't work.

- Allow use of `NATIONAL` and `NCHAR` when defining character columns. This is the same as not using `BINARY`.

- Don't allow `NULL` columns in a `PRIMARY KEY` (only in `UNIQUE` keys).

- Clear `LAST_INSERT_ID()` if one uses this in ODBC: `WHERE auto_increment_column IS NULL`. This seems to fix some problems with Access.

- `SET SQL_AUTO_IS_NULL=0|1` now turns on/off the handling of searching for the last inserted row with `WHERE auto_increment_column IS NULL`.

- Added new variable `concurrency` to mysqld for Solaris.

- Added `--relative` option to mysqladmin to make `extended-status` more useful to monitor changes.

- Fixed bug when using `COUNT(DISTINCT ...)` on an empty table.

- Added support for the Chinese character set GBK.

- Fixed problem with `LOAD DATA INFILE` and `BLOB` columns.

- Added bit operator `~` (negation).

- Fixed problem with user-defined functions.

### B.3.57. Changes in release 3.23.4 (28 September 1999)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Inserting a `DATETIME` into a `TIME` column no longer try to store 'days' in it.

- Fixed problem with storage of float/double on little endian machines. (This affected `SUM()`.)

- Added connect timeout on TCP/IP connections.

- Fixed problem with `LIKE "%"` on an index that may have `NULL` values.

- `REVOKE ALL PRIVILEGES` didn't revoke all privileges.

- Allow creation of temporary tables with same name as the original table.

- When granting an account a `GRANT` option for a database, the account couldn't grant privileges to other users.

- New statement: `SHOW GRANTS FOR user` (by Sinisa).

- New `date_add` syntax: `date/datetime + INTERVAL # interval_type`. By Joshua Chamas.

- Fixed privilege check for `LOAD DATA REPLACE`.

- Automatic fixing of broken include files on Solaris 2.7

- Some configure issues to fix problems with big filesystem detection.

- `REGEXP` is now case-insensitive if you use non-binary strings.

### B.3.58. Changes in release 3.23.3 (13 September 1999)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Added patches for MIT-pthreads on NetBSD.

- Fixed range bug in `MyISAM`.

- `ASC` is now the default again for `ORDER BY`.

- Added `LIMIT` to `UPDATE`.

- Added `mysql_change_user()` function to the MySQL C API.

- Added character set to `SHOW VARIABLES`.

- Added support of `--[whitespace]` comments.

- Allow `INSERT INTO `tbl_name` VALUES ()`, that is, you may now specify an empty value list to insert a row in which each column is set to its default value.

- Changed `SUBSTRING(text FROM pos)` to conform to standard SQL. (Before this construct returned the rightmost `pos` characters.)

- `SUM()` with `GROUP BY` returned 0 on some systems.

- Changed output for `SHOW TABLE STATUS`.

- Added `DELAY_KEY_WRITE` option to `CREATE TABLE`.

- Allow `AUTO_INCREMENT` on any key part.

- Fixed problem with `YEAR(NOW())` and `YEAR(CURDATE())`.

- Added `CASE` construct.

- New `COALESCE()` function.

### B.3.59. Changes in release 3.23.2 (09 August 1999)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed range optimizer bug: `SELECT * FROM `tbl_name` WHERE `key_part1` >= `const` AND (`key_part2` = `const` OR `key_part2` = `const`)`. The bug was that some rows could be duplicated in the result.

- Running myisamchk without `-a` updated the index distribution incorrectly.

- `SET SQL_LOW_PRIORITY_UPDATES=1` was causing a parse error.

- You can now update index columns that are used in the `WHERE` clause. `UPDATE `tbl_name` SET KEY=KEY+1 WHERE KEY > 100`

- Date handling should now be a bit faster.

- Added handling of fuzzy dates (dates where day or month is 0), such as `'1999-01-00'`.

- Fixed optimization of `SELECT ... WHERE `key_part1`=`const1` AND `key_part_2`=`const2` AND `key_part1`=`const4` AND `key_part2`=`const4``; indextype should be `range` instead of `ref`.

- Fixed egcs 1.1.2 optimizer bug (when using `BLOB` values) on Linux Alpha.

- Fixed problem with `LOCK TABLES` combined with `DELETE FROM table`.

- `MyISAM` tables now allow keys on `NULL` and `BLOB/TEXT` columns.

- The following join is now much faster: `SELECT ... FROM t1 LEFT JOIN t2 ON ... WHERE t2.`not_null_column` IS NULL`.

- `ORDER BY` and `GROUP BY` can be done on functions.

- Changed handling of 'const_item' to allow handling of `ORDER BY RAND()`.

- Indexes are now used for `WHERE `key_column` = `function``.

- Indexes are now used for `WHERE `key_column` = `col_name`` even if the columns are not identically packed.

- Indexes are now used for `WHERE `col_name` IS NULL`.

- Changed heap tables to be stored in low_byte_first order (to make it easy to convert to `MyISAM` tables)

- Automatic change of `HEAP` temporary tables to `MyISAM` tables in case of “table is full” errors.

- Added `--init-file=`file_name`` option to mysqld.

- Added `COUNT(DISTINCT `value`, [`value`, ...])`.

- `CREATE TEMPORARY TABLE` now creates a temporary table, in its own namespace, that is automatically deleted if connection is dropped.

- New reserved words (required for `CASE`): `CASE, THEN, WHEN, ELSE and END`.

- New functions `EXPORT_SET()` and `MD5()`.

- Support for the GB2312 Chinese character set.

### B.3.60. Changes in release 3.23.1 (08 July 1999)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- Fixed some compilation problems.

### B.3.61. Changes in release 3.23.0 (05 July 1999: Alpha)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

- A new storage engine library (`MyISAM`) with a lot of new features. See Section 13.1, “The `MyISAM` Storage Engine”.

- You can create in-memory `HEAP` tables which are extremely fast for lookups.

- Support for big files (63-bit) on OSs that support big files.

- New function `LOAD_FILE(filename)` to get the contents of a file as a string value.

- New `<=>` operator that acts as `=` but returns TRUE if both arguments are `NULL`. This is useful for comparing changes between tables.

- Added the ODBC 3.0 `EXTRACT(interval FROM datetime)` function.

- Columns defined as `FLOAT(`X`)` are not rounded on storage and may be in scientific notation (1.0 E+10) when retrieved.

- `REPLACE` is now faster than before.

- Changed `LIKE` character comparison to behave as `=`; This means that `'e' LIKE 'é'` is now true. (If the line doesn't display correctly, the latter 'e' is a French 'e' with an acute accent above.)

- `SHOW TABLE STATUS` returns a lot of information about the tables.

- Added `LIKE` to the `SHOW STATUS` command.

- Added `Privileges` column to `SHOW COLUMNS`.

- Added `Packed` and `Comment` columns to `SHOW INDEX`.

- Added comments to tables (with `CREATE TABLE ... COMMENT '`xxx`'`).

- Added `UNIQUE`, as in `CREATE TABLE `tbl_name` (col INT NOT NULL UNIQUE)`

- New create syntax: `CREATE TABLE `tbl_name` SELECT ...`

- New create syntax: `CREATE TABLE IF NOT EXISTS ...`

- Allow creation of `CHAR(0)` columns.

- `DATE_FORMAT()` now requires “`%`” before any format character.

- `DELAYED` is now a reserved word (sorry about that :( ).

- An example procedure is added: `analyse`, file: `sql_analyse.c`. This describes the data in your query. Try the following:

      SELECT ... FROM ...
      WHERE ... PROCEDURE ANALYSE([max_elements,[max_memory]])

  This procedure is extremely useful when you want to check the data in your table!

- `BINARY` cast to force a string to be compared in case-sensitive fashion.

- Added `--skip-show-database` option to mysqld.

- Check whether a row has changed in an `UPDATE` now also works with `BLOB`/`TEXT` columns.

- Added the `INNER` join syntax. Note that this change makes `INNER` a reserved word!

- Added support for netmasks to the hostname in the MySQL grant tables. You can specify a netmask using the `IP/NETMASK` syntax.

- If you compare a `NOT NULL DATE/DATETIME` column with `IS NULL`, this is changed to a compare against `0` to satisfy some ODBC applications. (By `<shreeve@uci.edu>`.)

- `NULL IN (...)` now returns `NULL` instead of `0`. This ensures that `null_column NOT IN (...)` doesn't match `NULL` values.

- Fix storage of floating-point values in `TIME` columns.

- Changed parsing of `TIME` strings to be more strict. Now the fractional second part is detected (and currently skipped). The following formats are supported:

  - [[DAYS] [H]H:]MM:]SS[.fraction]

  - [[[[[H]H]H]H]MM]SS[.fraction]

- Detect (and ignore) fractional second part from `DATETIME`.

- Added the `LOW_PRIORITY` attribute to `LOAD DATA INFILE`.

- The default index name now uses the same case as the column name on which the index name is based.

- Changed default number of connections to 100.

- Use bigger buffers when using `LOAD DATA INFILE`.

- `DECIMAL(x,y)` now works according to standard SQL.

- Added aggregate user-defined functions. Thanks to Andreas F. Bobak (`<bobak@relog.ch>`) for this!

- `LAST_INSERT_ID()` is now updated for `INSERT INTO ... SELECT`.

- Some small changes to the join table optimizer to make some joins faster.

- `SELECT DISTINCT` is much faster; it uses the new `UNIQUE` functionality in `MyISAM`. One difference compared to MySQL 3.22 is that the output of `DISTINCT` is no longer sorted.

- All C client API macros are now functions to make shared libraries more reliable. Because of this, you can no longer call `mysql_num_fields()` on a `MYSQL` object, you must use `mysql_field_count()` instead.

- Added use of `LIBWRAP`; patch by Henning P. Schmiedehausen.

- Don't allow `AUTO_INCREMENT` for other than numerical columns.

- Using `AUTO_INCREMENT` now automatically makes the column `NOT NULL`.

- Show `NULL` as the default value for `AUTO_INCREMENT` columns.

- Added `SQL_BIG_RESULT`; `SQL_SMALL_RESULT` is now default.

- Added a shared library RPM. This enhancement was contributed by David Fox (`<dsfox@cogsci.ucsd.edu>`).

- Added `--enable-large-files` and `--disable-large-files` options to configure. See `configure.in` for some systems where this is automatically turned off because of broken implementations.

- Upgraded `readline` to 4.0.

- New `CREATE TABLE` options: `PACK_KEYS` and `CHECKSUM`.

- Added `--default-table-type` option to mysqld.

## B.4. Changes in `InnoDB`

Starting from 4.0.22 and 4.1.5, all InnoDB changes are included in the MySQL Change History, and this manual section is no longer separately maintained.

### B.4.1. Changes in MySQL/InnoDB-4.0.21, September 10, 2004

Functionality added or changed:

- Renamed the `innodb.status.`<pid>`` files (created in the data directory) to `innodb_status.`<pid>``. This avoids problems on filesystems that do not allow multiple periods in filenames.

- Added `innodb_status_file` system variable to mysqld to control whether output from `SHOW INNODB STATUS` is written to a `innodb_status.`<pid>`` file in the data directory. By default, the file is not created. To create it, start mysqld with the `--innodb_status_file=1` option.

- Changes for NetWare to exit InnoDB gracefully on NetWare even in a case of an assertion failure, instead of intentionally crashing the ``mysqld'` server process.

Bugs fixed:

- Fixed a bug in `ON DELETE CASCADE` and `ON UPDATE CASCADE` foreign key constraints: long chains of cascaded operations would cause a stack overflow and crash the server. Cascaded operations are now limited to 15 levels. (Bug#4446)

- Fixed a possible bug in `LOCK TABLES` introduced in MySQL/InnoDB-4.0.19: The count of tables explicitly locked by a transaction was incremented only after the locks were granted, but decremented when the lock structures were destroyed.

- Fixed a bug in `UNLOCK TABLES` in `AUTOCOMMIT=0` mode, introduced in MySQL/InnoDB-4.0.19: The memory allocated for some locks acquired by the transaction could be deallocated before those locks were released. The bug can lead to crashes and memory corruption of the buffer pool when the transaction acquires a large number of locks (table locks or row-level locks).

- Increment the InnoDB watchdog timeout during `CHECK TABLE`. A long-running `CHECK TABLE` would cause InnoDB to complain about a 'long semaphore wait', and crash the server, if a query had to wait more than 600 seconds behind that `CHECK TABLE` operation. (Bug#2694)

- If you configure `innodb_additional_mem_pool_size` so small that InnoDB memory allocation spills over from it, then every 4 billionth spill may cause memory corruption. A symptom is a printout like the one following in the `.err` log. The workaround is to make `innodb_additional_mem_pool_size` big enough to hold all memory allocation. Use `SHOW INNODB STATUS` to determine that there is plenty of free space available in the additional mem pool, and the total allocated memory stays rather constant.

      InnoDB: Error: Mem area size is 0. Possibly a memory overrun of the
      InnoDB: previous allocated area!
      InnoDB: Apparent memory corruption: mem dump  len 500; hex

- The special meaning of the table names `innodb_monitor`, `innodb_lock_monitor`, `innodb_tablespace_monitor`, `innodb_table_monitor`, and `innodb_validate` in `CREATE TABLE` and `DROP TABLE` statements was accidentally removed in MySQL/InnoDB-4.0.19. The diagnostic functions attached to these special table names (see Section 13.2.12.1, “`SHOW ENGINE INNODB STATUS` and the `InnoDB` Monitors”) are accessible again in MySQL/InnoDB-4.0.21.

- When the private SQL parser of InnoDB was modified in MySQL/InnoDB-4.0.19 in order to allow the use of the apostrophe (“`'`”) in table and column names, the fix relied on a previously unused function `mem_realloc()`, whose implementation was incorrect. As a result, InnoDB can incorrectly parse column and table names as the empty string. The InnoDB `realloc()` implementation has been corrected in MySQL/InnoDB-4.0.21.

- Fixed a glitch introduced in 4.0.18 and 4.1.2: in `SHOW TABLE STATUS` InnoDB systematically overestimated the row count by 1 if the table fit on a single 16 kB data page.

- InnoDB created temporary files with the C library function `tmpfile()`. On Windows, the files would be created in the root directory of the current file system. To correct this behavior, the invocations of `tmpfile()` were replaced with code that uses the function `create_temp_file()` in the MySQL portability layer. (Bug#3998)

- If `ALTER TABLE ... DROP FOREIGN KEY ...` fails because of a wrong constraint name, return a table handler error number 150 instead of 152.

- If there was little file I/O in InnoDB, but the insert buffer was used, it could happen that 'Pending normal aio reads' was bigger than 0, but the I/O handler thread did not get waken up in 600 seconds. This resulted in a hang, and crashing of InnoDB.

- If we `RENAME`d a table, InnoDB forgot to load the `FOREIGN KEY` constraints that reference the new table name, and forgot to check that they are compatible with the table.

### B.4.2. Changes in MySQL/InnoDB-4.1.4, August 31, 2004

Functionality added or changed:

- ### Important

  Made internal representation of `TIMESTAMP` values in `InnoDB` in 4.1 to be the same as in 4.0. This difference resulted in incorrect datetime values in `TIMESTAMP` columns in `InnoDB` tables after an upgrade from 4.0 to 4.1. (Bug#4492) Warning: extra steps during upgrade required! This means that if you are upgrading from 4.1.x, where x <= 3, to 4.1.4 you should use `mysqldump` for saving and then restoring your `InnoDB` tables with `TIMESTAMP` columns. No conversion is needed if you upgrade from 3.23 or 4.0 to 4.1.4 or later.

- Added a new startup option `innodb_locks_unsafe_for_binlog`. This option forces `InnoDB` not to use next-key locking in searches and index scans.

- Added `innodb_status_file` system variable to mysqld to control whether output from `SHOW INNODB STATUS` is written to a `innodb_status.`<pid>`` file in the data directory. By default, the file is not created. To create it, start mysqld with the `--innodb_status_file=1` option.

- Changes for NetWare to exit InnoDB gracefully on NetWare even in a case of an assertion failure, instead of intentionally crashing the mysqld server process.

- “Gap” type row locks without the `LOCK_INSERT_INTENTION` flag do not need to wait for anything. This is because different users can have conflicting lock types on gaps. This change reduces unnecessary deadlocks.

Bugs fixed:

- Fixed a bug in `ON DELETE CASCADE` and `ON UPDATE CASCADE` foreign key constraints: long chains of cascaded operations would cause a stack overflow and crash the server. Cascaded operations are now limited to 15 levels. (Bug#4446)

- Increment the InnoDB watchdog timeout during `CHECK TABLE`. (Bug#2694)

- If you configure `innodb_additional_mem_pool_size` so small that InnoDB memory allocation spills over from it, then every 4 billionth spill may cause memory corruption. A symptom is a printout like the one following in the `.err` log.

      InnoDB: Error: Mem area size is 0. Possibly a memory overrun of the
      InnoDB: previous allocated area!
      InnoDB: Apparent memory corruption: mem dump  len 500; hex

- Fixed a glitch introduced in 4.0.18 and 4.1.2: in `SHOW TABLE STATUS` InnoDB systematically overestimated the row count by 1 if the table fit on a single 16 kB data page.

- InnoDB created temporary files with the C library function `tmpfile()`. On Windows, the files would be created in the root directory of the current file system. To correct this behavior, the invocations of `tmpfile()` were replaced with code that uses the function `create_temp_file()` in the MySQL portability layer. (Bug#3998)

- If we `RENAME`d a table, InnoDB forgot to load the foreign key constraints that reference the new table name, and forgot to check that they are compatible with the table.

- If there was little file I/O in InnoDB, but the insert buffer was used, it could happen that 'Pending normal aio reads' was bigger than 0, but the I/O handler thread did not get waken up in 600 seconds. This resulted in a hang, and an intentional crashing of mysqld.

### B.4.3. Changes in MySQL/InnoDB-4.1.3, June 28, 2004

Functionality added or changed:

- ### Important

  Starting from MySQL 4.1.3, `InnoDB` uses the same character set comparison functions as MySQL for non-`latin1_swedish_ci` character strings that are not `BINARY`. This changes the sorting order of space and characters < ASCII(32) in those character sets. For `latin1_swedish_ci` character strings and `BINARY` strings, `InnoDB` uses its own pad-spaces-at-end comparison method, which stays unchanged. If you have an `InnoDB` table created with MySQL 4.1.2 or earlier, with an index on a non-`latin1` character set (in the case of 4.1.0 and 4.1.1 with any character set) `CHAR`/`VARCHAR`/or `TEXT` column that is not `BINARY` but may contain characters < ASCII(32), then you should do `ALTER TABLE` or `OPTIMIZE` table on it to regenerate the index, after upgrading to MySQL 4.1.3 or later.

- `OPTIMIZE TABLE` for `InnoDB` tables is now mapped to `ALTER TABLE` rather than to `ANALYZE TABLE`.

- Added an interface for storing the binlog offset in the InnoDB log and flushing the log.

Bugs fixed:

- The critical bug in 4.1.2 (crash recovery skipping all `.ibd` files if you specify `innodb_file_per_table` on Unix) has been fixed. The bug was a combination of two bugs. Crash recovery ignored the files, because the attempt to lock them in the wrong mode failed. From now on, locks are only obtained for regular files opened in read/write mode, and crash recovery stops if an `.ibd` file for a table exists in a database directory but is unaccessible.

- Do not remember the original `select_lock_type` inside `LOCK TABLES`. (Bug#4047)

- The special meaning of the table names `innodb_monitor`, `innodb_lock_monitor`, `innodb_tablespace_monitor`, `innodb_table_monitor`, and `innodb_validate` in `CREATE TABLE` and `DROP TABLE` statements was accidentally removed in MySQL/InnoDB-4.1.2. The diagnostic functions attached to these special table names (see Section 13.2.12.1, “`SHOW ENGINE INNODB STATUS` and the `InnoDB` Monitors”) are accessible again in MySQL/InnoDB-4.1.3.

- When the private SQL parser of InnoDB was modified in MySQL/InnoDB-4.0.19 in order to allow the use of the apostrophe (“`'`”) in table and column names, the fix relied on a previously unused function `mem_realloc()`, whose implementation was incorrect. As a result, InnoDB can incorrectly parse column and table names as the empty string. The InnoDB `realloc()` implementation has been corrected in MySQL/InnoDB-4.1.3.

- In a clean-up of MySQL/InnoDB-4.1.2, the code for invalidating the query cache was broken. Now the query cache should be correctly invalidated for tables affected by `ON UPDATE CASCADE` or `ON DELETE CASCADE` constraints.

- Fixed a bug: in `LIKE 'abc%'`, the `'%'` did not match the empty string if the character set was not `latin1_swedish_ci`. This bug was fixed by changing the sorting order in these character sets. See the above note about data conversion in 4.1.3.

### B.4.4. Changes in MySQL/InnoDB-4.1.2, May 30, 2004

### Note

CRITICAL BUG in 4.1.2 if you specify `innodb_file_per_table` in `my.cnf` on Unix. In crash recovery InnoDB skips the crash recovery for all `.ibd` files and those tables become CORRUPT! The symptom is a message `Unable to lock ...ibd with lock 1, error: 9: fcntl: Bad file descriptor` in the `.err` log in crash recovery.

Functionality added or changed:

- Support multiple character sets. Note that tables created in other collations than `latin1_swedish_ci` cannot be accessed in MySQL/InnoDB 4.0.

- Automatically create a suitable index on a `FOREIGN KEY`, if the user does not create one. Removes most of the cases of `Error 1005 (errno 150)` in table creation.

- Do not assert in `log0log.c`, line 856 if `ib_logfiles` are too small for `innodb_thread_concurrency`. Instead, print instructions how to adjust `my.cnf` and call `exit(1)`.

- If MySQL tries to `SELECT` from an InnoDB table without setting any table locks, print a descriptive error message and assert; some subquery bugs were of this type.

- Allow a key part length in InnoDB to be up to 3,500 bytes; this is needed so that you can create an index on a column with 255 UTF-8 characters.

- All new features from InnoDB-4.0.17, InnoDB-4.0.18, InnoDB-4.0.19 and InnoDB-4.0.20.

Bugs fixed:

- If you configure `innodb_additional_mem_pool_size` so small that InnoDB memory allocation spills over from it, then every 4 billionth spill may cause memory corruption. A symptom is a printout like the one following in the `.err` log.

      InnoDB: Error: Mem area size is 0. Possibly a memory overrun of the
      InnoDB: previous allocated area!
      InnoDB: Apparent memory corruption: mem dump  len 500; hex

- Improved portability to 64-bit platforms, especially Win64.

- Fixed an assertion failure when a purge of a table was not possible because of missing `.ibd` file.

- Fixed a bug: do not retrieve all columns in a table if we only need the 'ref' of the row (usually, the `PRIMARY KEY`) to calculate an `ORDER BY`. (Bug#1942)

- On Unix-like systems, obtain an exclusive advisory lock on InnoDB files, to prevent corruption when multiple instances of MySQL are running on the same set of data files. The Windows version of InnoDB currently takes a mandatory lock on the files. (Bug#3608)

- Added a missing space to the output format of `SHOW INNODB STATUS`; reported by Jocelyn Fournier.

- All bugfixes from InnoDB-4.0.17, InnoDB-4.0.18, InnoDB-4.0.19 and InnoDB-4.0.20.

### B.4.5. Changes in MySQL/InnoDB-4.0.20, May 18, 2004

Bugs fixed:

- Apostrophe characters now are recognized by the internal `InnoDB` parser and can be used within quoted table and column identifiers in `FOREIGN KEY` clauses.

- Make `LOCK TABLE` aware of `InnoDB` row-level locks and `InnoDB` aware of locks set with `LOCK TABLE`. (Bug#3299)

- Fixed race conditions in `SHOW INNODB STATUS`. (Bug#3596)

### B.4.6. Changes in MySQL/InnoDB-4.0.19, May 4, 2004

Functionality added or changed:

- Better error message when the server has to crash because the buffer pool is exhausted by the lock table or the adaptive hash index.

- Print always the count of pending `pread()` and `pwrite()` calls if there is a long semaphore wait.

- Improve space utilization when rows of 1,500 to 8,000 bytes are inserted in the order of the primary key.

- Remove potential buffer overflow errors by sending diagnostic output to stderr or files instead of stdout or fixed-size memory buffers. As a side effect, the output of `SHOW INNODB STATUS` is written to a file ``<datadir>`/innodb.status.`<pid>`` every 15 seconds.

Bugs fixed:

- Fixed a bug: `DROP DATABASE` did not work if `FOREIGN KEY` references were defined within the database. (Bug#3058)

- Remove unnecessary files, functions and variables. Many of these were needed in the standalone version of InnoDB. Remove debug functions and variables from non-debug build.

- Add diagnostic code to analyze an assertion failure in ha_innodb.cc on line 2020 reported by a user. (Bug#2903)

- Fixed a bug: in a `FOREIGN KEY`, `ON UPDATE CASCADE` was not triggered if the update changed a string to another value identical in alphabetical ordering, for example, “`abc`” -> “`aBc`”.

- Protect the reading of the latest foreign key error explanation buffer with a mutex; in theory, a race condition could cause `SHOW INNODB STATUS` print garbage characters after the error info.

- Fixed a bug: The row count and key cardinality estimate was grossly too small if each clustered index page only contained one record.

- Parse `CONSTRAINT FOREIGN KEY` correctly. (Bug#3332)

- Fixed a memory corruption bug on Windows. The bug is present in all InnoDB versions in Windows, but it depends on how the linker places a static array in `srv0srv.c`, whether the bug shows itself. 4 bytes were overwritten with a pointer to a statically allocated string '`get windows aio return value`'.

- Fix a glitch reported by Philippe Lewicki on the general mailing list: do not print a warning to the `.err` log if `read_key` fails with a lock wait timeout error 146.

- Allow quotes to be embedded in strings in the private SQL parser of InnoDB, so that “`'`” can be used in InnoDB table and column names. Display quotes within identifiers properly.

- Debugging: Allow `UNIV_SYNC_DEBUG` to be disabled while `UNIV_DEBUG` is enabled.

- Debugging: Handle magic numbers in a more consistent way.

### B.4.7. Changes in MySQL/InnoDB-4.0.18, February 13, 2004

- Do not allow dropping a table referenced by a `FOREIGN KEY` constraint, unless the user does `SET FOREIGN_KEY_CHECKS=0`. The error message here is somewhat misleading “Cannot delete or update a parent row...,” and must be changed in a future version 4.1.x.

- Make `InnoDB` to remember the `CONSTRAINT` name given by a user for a `FOREIGN KEY`.

- Change the print format of `FOREIGN KEY` constraints spanning multiple databases to ```db_name``.``tbl_name```. But when parsing them, we must also accept ```db_name`.`tbl_name```, because that was the output format in < 4.0.18.

- An optimization in locking: If `AUTOCOMMIT=1`, then we do not need to make a plain `SELECT` set shared locks even on the `SERIALIZABLE` isolation level, because we know that the transaction is read only. A read-only transaction can always be performed on the `REPEATABLE READ` level, and that does not endanger the serializability.

- Implement an automatic downgrade from >= 4.1.1 -> 4.0.18 if the user has not created tables in `.ibd` files or used other 4.1.x features. Consult the manual section on multiple tablespaces carefully if you want to downgrade!

- Fixed a bug: MySQL should not allow `REPLACE` to internally perform an `UPDATE` if the table is referenced by a `FOREIGN KEY`. The MySQL manual states that `REPLACE` must resolve a duplicate-key error semantically with `DELETE` + `INSERT`, and not by an `UPDATE`. In versions < 4.0.18 and < 4.1.2, MySQL could resolve a duplicate key conflict in `REPLACE` by doing an `UPDATE` on the existing row, and `FOREIGN KEY` checks could behave in a semantically wrong way. (Bug#2418)

- Fixed a bug: generate `FOREIGN KEY` constraint identifiers locally for each table, in the form `db_name/tbl_name_ibfk_number`. If the user gives the constraint name explicitly, then remember it. These changes should ensure that foreign key id's in a slave are the same as in the master, and `DROP FOREIGN KEY` does not break replication. (Bug#2167)

- Fixed a bug: allow quoting of identifiers in InnoDB's `FOREIGN KEY` definitions with a backtick (`) and a double quote ("). You can now use also spaces in table and column names, if you quote the identifiers. (Bug#1725, Bug#2424)

- Fixed a bug: `FOREIGN KEY ... ON UPDATE/DELETE NO ACTION` must check the foreign key constraint, not ignore it. Since we do not have deferred constraints in `InnoDB`, this bugfix makes `InnoDB` to check `NO ACTION` constraints immediately, like it checks `RESTRICT` constraints.

- Fixed a bug: `InnoDB` crashed in `RENAME TABLE` if `db_name.tbl_name` is shorter than 5 characters. (Bug#2689)

- Fixed a bug: in `SHOW TABLE STATUS`, `InnoDB` row count and index cardinality estimates wrapped around at 512 million in 32-bit computers. Note that unless MySQL is compiled with the `BIG_TABLES` option, they still wrap around at 4 billion.

- Fixed a bug: If there was a `UNIQUE` secondary index, and `NULL` values in that unique index, then with the `IS NULL` predicate, `InnoDB` returned only the first matching row, though there can be many. This bug was introduced in 4.0.16. (Bug#2483)

### B.4.8. Changes in MySQL/InnoDB-5.0.0, December 24, 2003

- Important note: If you upgrade to MySQL 4.1.1 or higher, it is difficult to downgrade back to 4.0 or 4.1.0! That is because, for earlier versions, `InnoDB` is not aware of multiple tablespaces.

- `InnoDB` in 5.0.0 is essentially the same as InnoDB-4.1.1 with the bugfixes of InnoDB-4.0.17 included.

### B.4.9. Changes in MySQL/InnoDB-4.0.17, December 17, 2003

- Fixed a bug: If you created a column prefix secondary index and updated it so that the last characters in the column prefix were spaces, `InnoDB` would assert in `row0upd.c`, line 713. The same assertion failed if you updated a column in an ordinary secondary index so that the new value was alphabetically equivalent, but had a different length. This could happen, for example, in the UTF8 character set if you updated a letter to its accented or umlaut form.

- Fixed a bug: `InnoDB` could think that a secondary index record was not locked though it had been updated to an alphabetically equivalent value, for example, 'abc' -> 'aBc'.

- Fixed a bug: If you updated a secondary index column to an alphabetically equivalent value, and rolled back your update, `InnoDB` failed to restore the field in the secondary index to its original value.

- There are still several outstanding non-critical bugs reported in the MySQL bugs database. Their fixing has been delayed, because resources were allocated to the 4.1.1 release.

### B.4.10. Changes in MySQL/InnoDB-4.1.1, December 4, 2003

- Important note: If you upgrade to MySQL 4.1.1 or higher, you cannot downgrade to a version lower than 4.1.1 any more! That is because, for earlier versions, `InnoDB` is not aware of multiple tablespaces.

- Multiple tablespaces now available for `InnoDB`. You can store each `InnoDB` type table and its indexes into a separate `.ibd` file into a MySQL database directory, into the same directory where the `.frm` file is stored.

- The MySQL query cache now works for `InnoDB` tables also if `AUTOCOMMIT=0`, or the statements are enclosed inside `BEGIN ... COMMIT`.

- Reduced `InnoDB` memory consumption by a few megabytes if one sets the buffer pool size < 8MB.

- You can use raw disk partitions also in Windows.

### B.4.11. Changes in MySQL/InnoDB-4.0.16, October 22, 2003

- Fixed a bug: in contrary to what was said in the manual, in a locking read `InnoDB` set two record locks if a unique exact match search condition was used on a multi-column unique key. For a single column unique key it worked right.

- Fixed a bug: If you used the rename trick `#sql... -> rsql...` to recover a temporary table, `InnoDB` asserted in `row_mysql_lock_data_dictionary()`.

- There are several outstanding non-critical bugs reported in the MySQL bugs database. Their fixing has been delayed, because resources are allocated to the upcoming 4.1.1 release.

### B.4.12. Changes in MySQL/InnoDB-3.23.58, September 15, 2003

- Fixed a bug: `InnoDB` could make the index page directory corrupt in the first B-tree page splits after mysqld startup. A symptom would be an assertion failure in `page0page.c`, in function `page_dir_find_slot()`.

- Fixed a bug: `InnoDB` could in rare cases return an extraneous row if a rollback, purge, and a `SELECT` coincided.

- Fixed a possible hang over the `btr0sea.c` latch if `SELECT` was used inside `LOCK TABLES`.

- Fixed a bug: If a single `DELETE` statement first managed to delete some rows and then failed in a `FOREIGN KEY` error or a `Table is full` error, MySQL did not roll back the whole SQL statement as it should.

### B.4.13. Changes in MySQL/InnoDB-4.0.15, September 10, 2003

- Fixed a bug: If you updated a row so that the 8000 byte maximum length (without `BLOB` and `TEXT`) was exceeded, `InnoDB` simply removed the record from the clustered index. In a similar insert, `InnoDB` would leak reserved file space extents, which would only be freed at the next mysqld startup.

- Fixed a bug: If you used big `BLOB` values, and your log files were relatively small, `InnoDB` could in a big `BLOB` operation temporarily write over the log produced after the latest checkpoint. If `InnoDB` would crash at that moment, then the crash recovery would fail, because `InnoDB` would not be able to scan the log even up to the latest checkpoint. Starting from this version, `InnoDB` tries to ensure the latest checkpoint is young enough. If that is not possible, `InnoDB` prints a warning to the `.err` log of MySQL and advises you to make the log files bigger.

- Fixed a bug: setting `innodb_fast_shutdown=0` had no effect.

- Fixed a bug introduced in 4.0.13: If a `CREATE TABLE` ended in a comment, that could cause a memory overrun.

- Fixed a bug: If `InnoDB` printed `Operating system error number .. in a file operation` to the `.err` log in Windows, the error number explanation was wrong. Workaround: look at section 13.2 of http://www.innodb.com/ibman.php about Windows error numbers.

- Fixed a bug: If you created a column prefix `PRIMARY KEY` like in `t(a CHAR(200), PRIMARY KEY (a(10)))` on a fixed-length `CHAR` column, `InnoDB` would crash even in a simple `SELECT`. A `CHECK TABLE` would report the table as corrupt, also in the case where the created key was not `PRIMARY`.

### B.4.14. Changes in MySQL/InnoDB-4.0.14, July 22, 2003

- `InnoDB` now supports the `SAVEPOINT` and `ROLLBACK TO SAVEPOINT` SQL statements. See http://www.innodb.com/ibman.php#Savepoints for the syntax.

- You can now create column prefix keys like in `CREATE TABLE t (a BLOB, INDEX (a(10)))`.

- You can also use `O_DIRECT` as the `innodb_flush_method` on the latest versions of Linux and FreeBSD. Beware of possible bugs in those operating systems, though.

- Fixed the checksum calculation of data pages. Previously most OS file system corruption went unnoticed. Note that if you downgrade from version 4.0.14 or up to a version earlier than 4.0.14, `InnoDB` prints warnings in the first startup:

      InnoDB: Warning: An inconsistent page in the doublewrite buffer
      InnoDB: space id 2552202359 page number 8245, 127'th page in dblwr buf.

  but that is not dangerous and can be ignored.

- Modified the buffer pool replacement algorithm so that it tries to flush modified pages if there are no replaceable pages in the last 10 % of the LRU list. This can reduce disk I/O if the workload is a mixture of reads and writes.

- The buffer pool checkpoint flush algorithm now tries to flush also close neighbors of the page at the end of the flush list. This can speed up database shutdown, and can also speed up disk writes if `InnoDB` log files are very small compared to the buffer pool size.

- In 4.0.13 we made `SHOW INNODB STATUS` to print detailed info on the latest `UNIQUE KEY` error, but storing that information could slow down `REPLACE` significantly. We no longer store or print the info.

- Fixed a bug: `SET FOREIGN_KEY_CHECKS=0` was not replicated properly in the MySQL replication. The fix will not be backported to 3.23.

- Fixed a bug: the parameter `innodb_max_dirty_pages_pct` forgot to take into account the free pages in the buffer pool. This could lead to excessive flushing even though there were lots of free pages in the buffer pool. Workaround: `SET GLOBAL innodb_max_dirty_pages_pct = 100`.

- Fixed a bug: If there were big index scans then a file read request could starve and `InnoDB` could assert because of a very long semaphore wait.

- Fixed a bug: If `AUTOCOMMIT=1` then inside `LOCK TABLES` MySQL failed to do the commit after an updating SQL statement if binary logging was not on, and for `SELECT` statements did not commit regardless of binary logging state.

- Fixed a bug: `InnoDB` could make the index page directory corrupt in the first B-tree page splits after a mysqld startup. A symptom would be an assertion in page0page.c, in function page_dir_find_slot().

- Fixed a bug: If in a `FOREIGN KEY` with an `UPDATE CASCADE` clause the parent column was of a different internal storage length than the child column, then a cascaded update would make the column length wrong in the child table and corrupt the child table. Because of MySQL's 'silent column specification changes' a fixed-length `CHAR` column can change internally to a `VARCHAR` and cause this error.

- Fixed a bug: If a non-`latin1` character set was used and if in a `FOREIGN KEY` the parent column was of a different internal storage length than the child column, then all inserts to the child table would fail in a foreign key error.

- Fixed a bug: `InnoDB` could complain that it cannot find the clustered index record, or in rare cases return an extraneous row if a rollback, purge, and a `SELECT` coincided.

- Fixed a possible hang over the btr0sea.c latch if `SELECT` was used inside `LOCK TABLES`.

- Fixed a bug: contrary to what the release note of 4.0.13 said, the group commit still did not work if the MySQL binary logging was on.

- Fixed a bug: os_event_wait() did not work properly in Unix, which might have caused starvation in various log operations.

- Fixed a bug: If a single `DELETE` statement first managed to delete some rows and then failed in a `FOREIGN KEY` error or a `Table is full` error, MySQL did not roll back the whole SQL statement as it should, and also wrote the failed statement to the binary log, reporting there a non-zero error_code.

- Fixed a bug: the maximum allowed number of columns in a table is 1000, but `InnoDB` did not check that limit in `CREATE TABLE`, and a subsequent `INSERT` or `SELECT` from that table could cause an assertion.

### B.4.15. Changes in MySQL/InnoDB-3.23.57, June 20, 2003

- Changed the default value of `innodb_flush_log_at_trx_commit` from 0 to 1. If you have not specified it explicitly in your `my.cnf`, and your application runs much slower with this new release, it is because the value 1 causes a log flush to disk at each transaction commit.

- Fixed a bug: `InnoDB` forgot to call pthread_mutex_destroy() when a table was dropped. That could cause memory leakage on FreeBSD and other non-Linux Unixes.

- Fixed a bug: MySQL could erroneously return 'Empty set' if `InnoDB` estimated an index range size to 0 records though the range was not empty; MySQL also failed to do the next-key locking in the case of an empty index range.

- Fixed a bug: `GROUP BY` and `DISTINCT` could treat NULL values inequal.

### B.4.16. Changes in MySQL/InnoDB-4.0.13, May 20, 2003

- `InnoDB` now supports `ALTER TABLE DROP FOREIGN KEY`. You have to use `SHOW CREATE TABLE` to find the internally generated foreign key ID when you want to drop a foreign key.

- `SHOW INNODB STATUS` now prints detailed information of the latest detected `FOREIGN KEY` and `UNIQUE KEY` errors. If you do not understand why `InnoDB` gives the error 150 from a `CREATE TABLE`, you can use this statement to study the reason.

- `ANALYZE TABLE` now works also for `InnoDB` type tables. It makes eight random dives to each of the index trees and updates index cardinality estimates accordingly. Note that because these are only estimates, repeated runs of `ANALYZE TABLE` may produce different numbers. MySQL uses index cardinality estimates only in join optimization. If some join is not optimized in the right way, you may try using `ANALYZE TABLE`.

- `InnoDB` group commit capability now works also when MySQL binary logging is switched on. There have to be > 2 client threads for the group commit to become active.

- Changed the default value of `innodb_flush_log_at_trx_commit` from 0 to 1. If you have not specified it explicitly in your `my.cnf`, and your application runs much slower with this new release, it is because the value 1 causes a log flush to disk at each transaction commit.

- Added a new global settable MySQL system variable `innodb_max_dirty_pages_pct`. It is an integer in the range 0 - 100. The default is 90. The main thread in `InnoDB` tries to flush pages from the buffer pool so that at most this many percents are not yet flushed at any time.

- If `innodb_force_recovery=6`, do not let `InnoDB` do repair of corrupt pages based on the doublewrite buffer.

- `InnoDB` startup now happens faster because it does not set the memory in the buffer pool to zero.

- Fixed a bug: The `InnoDB` parser for `FOREIGN KEY` definitions was confused by the keywords 'foreign key' inside MySQL comments.

- Fixed a bug: If you dropped a table to which there was a `FOREIGN KEY` reference, and later created the same table with non-matching data types, `InnoDB` could assert in `dict0load.c`, in function `dict_load_table()`.

- Fixed a bug: `GROUP BY` and `DISTINCT` could treat `NULL` values as not equal. MySQL also failed to do the next-key locking in the case of an empty index range.

- Fixed a bug: Do not commit the current transaction when a `MyISAM` table is updated; this also makes `CREATE TABLE` not to commit an `InnoDB` transaction, even when binary logging is enabled.

- Fixed a bug: We did not allow `ON DELETE SET NULL` to modify the same table where the delete was made; we can allow it because that cannot produce infinite loops in cascaded operations.

- Fixed a bug: Allow `HANDLER PREV` and `NEXT` also after positioning the cursor with a unique search on the primary key.

- Fixed a bug: If `MIN()` or `MAX()` resulted in a deadlock or a lock wait timeout, MySQL did not return an error, but returned `NULL` as the function value.

- Fixed a bug: `InnoDB` forgot to call `pthread_mutex_destroy()` when a table was dropped. That could cause memory leakage on FreeBSD and other non-Linux Unix systems.

### B.4.17. Changes in MySQL/InnoDB-4.1.0, April 3, 2003

- `InnoDB` now supports up to 64GB of buffer pool memory in a Windows 32-bit Intel computer. This is possible because `InnoDB` can use the AWE extension of Windows to address memory over the 4GB limit of a 32-bit process. A new startup variable `innodb_buffer_pool_awe_mem_mb` enables AWE and sets the size of the buffer pool in megabytes.

- Reduced the size of buffer headers and the lock table. `InnoDB` uses 2 % less memory.

### B.4.18. Changes in MySQL/InnoDB-3.23.56, March 17, 2003

- Fixed a major bug in `InnoDB` query optimization: queries of type SELECT ... WHERE indexcolumn < x and SELECT ... WHERE indexcolumn > x could cause a table scan even if the selectivity would have been very good.

- Fixed a potential bug if MySQL calls store_lock with TL_IGNORE in the middle of a query.

### B.4.19. Changes in MySQL/InnoDB-4.0.12, March 18, 2003

- In crash recovery `InnoDB` now prints the progress in percents of a transaction rollback.

- Fixed a bug/feature: If your application program used mysql_use_result(), and used >= 2 connections to send SQL queries, it could deadlock on the adaptive hash S-latch in btr0sea.c. Now mysqld releases the S-latch whenever it passes data from a SELECT to the client.

- Fixed a bug: MySQL could erroneously return 'Empty set' if `InnoDB` estimated an index range size to 0 records though the range was not empty; MySQL also failed to do the next-key locking in the case of an empty index range.

### B.4.20. Changes in MySQL/InnoDB-4.0.11, February 25, 2003

- Fixed a bug introduced in 4.0.10: SELECT ... FROM ... ORDER BY ... DESC could hang in an infinite loop.

- An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in the MySQL replication.

### B.4.21. Changes in MySQL/InnoDB-4.0.10, February 4, 2003

- In INSERT INTO t1 SELECT ... FROM t2 WHERE ... MySQL previously set a table level read lock on t2. This lock is now removed.

- Increased SHOW INNODB STATUS maximum printed length to 200KB.

- Fixed a major bug in `InnoDB` query optimization: queries of type SELECT ... WHERE indexcolumn < x and SELECT ... WHERE indexcolumn > x could cause a table scan even if the selectivity would have been very good.

- Fixed a bug: purge could cause a hang in a BLOB table where the primary key index tree was of height 1. Symptom: semaphore waits caused by an X-latch set in btr_free_externally_stored_field().

- Fixed a bug: using `InnoDB` HANDLER commands on a fresh handle crashed mysqld in `ha_innobase::change_active_index()`.

- Fixed a bug: If MySQL estimated a query in the middle of a SELECT statement, `InnoDB` could hang on the adaptive hash index latch in btr0sea.c.

- Fixed a bug: `InnoDB` could report table corruption and assert in page_dir_find_owner_slot() if an adaptive hash index search coincided with purge or an insert.

- Fixed a bug: some filesystem snapshot tool in Windows 2000 could cause an `InnoDB` file write to fail with error 33 ERROR_LOCK_VIOLATION. In synchronous writes `InnoDB` now retries the write 100 times at 1 second intervals.

- Fixed a bug: REPLACE INTO t1 SELECT ... did not work if t1 has an auto-inc column.

- An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in the MySQL replication.

### B.4.22. Changes in MySQL/InnoDB-3.23.55, January 24, 2003

- In INSERT INTO t1 SELECT ... FROM t2 WHERE ... MySQL previously set a table level read lock on t2. This lock is now removed.

- Fixed a bug: If the combined size of `InnoDB` log files was >= 2GB in a 32-bit computer, `InnoDB` would write log in a wrong position. That could make crash recovery and `InnoDB Hot Backup` to fail in log scan.

- Fixed a bug: index cursor restoration could theoretically fail.

- Fixed a bug: an assertion in btr0sea.c, in function btr_search_info_update_slow could theoretically fail in a race of 3 threads.

- Fixed a bug: purge could cause a hang in a BLOB table where the primary key index tree was of height 1. Symptom: semaphore waits caused by an X-latch set in btr_free_externally_stored_field().

- Fixed a bug: If MySQL estimated a query in the middle of a SELECT statement, `InnoDB` could hang on the adaptive hash index latch in btr0sea.c.

- Fixed a bug: `InnoDB` could report table corruption and assert in page_dir_find_owner_slot() if an adaptive hash index search coincided with purge or an insert.

- Fixed a bug: some filesystem snapshot tool in Windows 2000 could cause an `InnoDB` file write to fail with error 33 ERROR_LOCK_VIOLATION. In synchronous writes `InnoDB` now retries the write 100 times at 1 second intervals.

- An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in the MySQL replication. The fix appears in 4.0.11 and probably will not be backported to 3.23.

- Fixed bug in `InnoDB` `page0cur.c` file in function page_cur_search_with_match which caused `InnoDB` to remain on the same page forever. This bug is evident only in tables with more than one page.

### B.4.23. Changes in MySQL/InnoDB-4.0.9, January 14, 2003

- Removed the warning message: 'InnoDB: Out of memory in additional memory pool.'

- Fixed a bug: If the combined size of `InnoDB` log files was >= 2GB in a 32-bit computer, `InnoDB` would write log in a wrong position. That could make crash recovery and `InnoDB Hot Backup` to fail.

- Fixed a bug: index cursor restoration could theoretically fail.

### B.4.24. Changes in MySQL/InnoDB-4.0.8, January 7, 2003

- `InnoDB` now supports also FOREIGN KEY (...) REFERENCES ...(...) [ON UPDATE CASCADE | ON UPDATE SET NULL | ON UPDATE RESTRICT | ON UPDATE NO ACTION].

- Tables and indexes now reserve 4 % less space in the tablespace. Also existing tables reserve less space. By upgrading to 4.0.8 you should see more free space in "InnoDB free" in SHOW TABLE STATUS.

- Fixed bugs: updating the PRIMARY KEY of a row would generate a foreign key error on all FOREIGN KEYs which referenced secondary keys of the row to be updated. Also, if a referencing FOREIGN KEY constraint only referenced the first columns in an index, and there were more columns in that index, updating the additional columns generated a foreign key error.

- Fixed a bug: If an index contains some column twice, and that column is updated, the table becomes corrupt. From now on `InnoDB` prevents creation of such indexes.

- Fixed a bug: removed superfluous error 149 and 150 printouts from the .err log when a locking SELECT caused a deadlock or a lock wait timeout.

- Fixed a bug: an assertion in btr0sea.c, in function btr_search_info_update_slow could theoretically fail in a race of 3 threads.

- Fixed a bug: one could not switch a session transaction isolation level back to REPEATABLE READ after setting it to something else.

### B.4.25. Changes in MySQL/InnoDB-4.0.7, December 26, 2002

- `InnoDB` in 4.0.7 is essentially the same as in 4.0.6.

### B.4.26. Changes in MySQL/InnoDB-4.0.6, December 19, 2002

- Since innodb_log_arch_dir has no relevance under MySQL, there is no need to specify it any more in my.cnf.

- LOAD DATA INFILE in AUTOCOMMIT=1 mode no longer does implicit commits for each 1MB of written binary log.

- Fixed a bug introduced in 4.0.4: LOCK TABLES ... READ LOCAL should not set row locks on the rows read. This caused deadlocks and lock wait timeouts in mysqldump.

- Fixed two bugs introduced in 4.0.4: in AUTO_INCREMENT, REPLACE could cause the counter to be left 1 too low. A deadlock or a lock wait timeout could cause the same problem.

- Fixed a bug: TRUNCATE on a TEMPORARY table crashed `InnoDB`.

- Fixed a bug introduced in 4.0.5: If binary logging was not switched on, INSERT INTO ... SELECT ... or CREATE TABLE ... SELECT ... could cause `InnoDB` to hang on a semaphore created in btr0sea.c, line 128. Workaround: switch binary logging on.

- Fixed a bug: in replication issuing SLAVE STOP in the middle of a multiple-statement transaction could cause that SLAVE START would only perform a part of the transaction. A similar error could occur if the slave crashed and was restarted.

### B.4.27. Changes in MySQL/InnoDB-3.23.54, December 12, 2002

- Fixed a bug: the `InnoDB` range estimator greatly exaggerated the size of a short index range if the paths to the endpoints of the range in the index tree happened to branch in the root. This could cause unnecessary table scans in SQL queries.

- Fixed a bug: ORDER BY could fail if you had not created a primary key to a table, but had defined several indexes of which at least one was a UNIQUE index with all its columns declared as NOT NULL.

- Fixed a bug: a lock wait timeout in connection with ON DELETE CASCADE could cause corruption in indexes.

- Fixed a bug: If a SELECT was done with a unique key from a primary index, and the search matched to a delete-marked record, `InnoDB` could erroneously return the NEXT record.

- Fixed a bug introduced in 3.23.53: LOCK TABLES ... READ LOCAL should not set row locks on the rows read. This caused deadlocks and lock wait timeouts in mysqldump.

- Fixed a bug: If an index contains some column twice, and that column is updated, the table becomes corrupt. From now on `InnoDB` prevents creation of such indexes.

### B.4.28. Changes in MySQL/InnoDB-4.0.5, November 18, 2002

- `InnoDB` now supports also transaction isolation levels READ COMMITTED and READ UNCOMMITTED. READ COMMITTED more closely emulates Oracle and makes porting of applications from Oracle to MySQL easier.

- Deadlock resolution is now selective: we try to pick as victims transactions with less modified or inserted rows.

- FOREIGN KEY definitions are now aware of the lower_case_table_names setting in my.cnf.

- SHOW CREATE TABLE does not output the database name to a FOREIGN KEY definition if the referred table is in the same database as the table.

- `InnoDB` does a consistency check to most index pages before writing them to a data file.

- If you set `innodb_force_recovery` > 0, `InnoDB` tries to jump over corrupt index records and pages when doing SELECT * FROM table. This helps in dumping.

- `InnoDB` now again uses asynchronous unbuffered I/O in Windows 2000 and XP; only unbuffered simulated async I/O in NT, 95/98/ME.

- Fixed a bug: the `InnoDB` range estimator greatly exaggerated the size of a short index range if the paths to the endpoints of the range in the index tree happened to branch in the root. This could cause unnecessary table scans in SQL queries. The fix is also backported to 3.23.54.

- Fixed a bug present in 3.23.52, 4.0.3, 4.0.4: `InnoDB` startup could take very long or even crash on some Windows 95/98/ME computers.

- Fixed a bug: the AUTO-INC lock was held to the end of the transaction if it was granted after a lock wait. This could cause unnecessary deadlocks.

- Fixed a bug: If SHOW INNODB STATUS, innodb_monitor, or innodb_lock_monitor had to print several hundred transactions in one report, and the output became truncated, `InnoDB` would hang, printing to the error log many waits for a mutex created at srv0srv.c, line 1621.

- Fixed a bug: SHOW INNODB STATUS on Unix always reported average file read size as 0 bytes.

- Fixed a potential bug in 4.0.4: `InnoDB` now does ORDER BY ... DESC like `MyISAM`.

- Fixed a bug: DROP TABLE could cause crash or a hang if there was a rollback concurrently running on the table. The fix will be backported to 3.23 only if this appears a real problem for users.

- Fixed a bug: ORDER BY could fail if you had not created a primary key to a table, but had defined several indexes of which at least one was a UNIQUE index with all its columns declared as NOT NULL.

- Fixed a bug: a lock wait timeout in connection with ON DELETE CASCADE could cause corruption in indexes.

- Fixed a bug: If a SELECT was done with a unique key from a primary index, and the search matched to a delete-marked record, `InnoDB` could return the NEXT record.

- Outstanding bugs: in 4.0.4 two bugs were introduced to AUTO_INCREMENT. REPLACE can cause the counter to be left 1 too low. A deadlock or a lock wait timeout can cause the same problem. These are fixed in 4.0.6.

### B.4.29. Changes in MySQL/InnoDB-3.23.53, October 9, 2002

- We again use unbuffered disk I/O to data files in Windows. Windows XP and Windows 2000 read performance seems to be very poor with normal I/O.

- Tuned range estimator so that index range scans are preferred over full index scans.

- Allow dropping and creating a table even if innodb_force_recovery is set. One can use this to drop a table which would cause a crash in rollback or purge, or if a failed table import causes a runaway rollback in recovery.

- Fixed a bug present in 3.23.52, 4.0.3, 4.0.4: `InnoDB` startup could take very long or even crash on some Windows 95/98/ME computers.

- Fixed a bug: fast shutdown (which is the default) sometimes was slowed down by purge and insert buffer merge.

- Fixed a bug: doing a big SELECT from a table where no rows were visible in a consistent read could cause a very long (> 600 seconds) semaphore wait in btr0cur.c line 310.

- Fixed a bug: the AUTO-INC lock was held to the end of the transaction if it was granted after a lock wait. This could cause unnecessary deadlocks.

- Fixed a bug: If you created a temporary table inside LOCK TABLES, and used that temporary table, that caused an assertion failure in ha_innobase.cc.

- Fixed a bug: If SHOW INNODB STATUS, innodb_monitor, or innodb_lock_monitor had to print several hundred transactions in one report, and the output became truncated, `InnoDB` would hang, printing to the error log many waits for a mutex created at srv0srv.c, line 1621.

- Fixed a bug: SHOW INNODB STATUS on Unix always reported average file read size as 0 bytes.

### B.4.30. Changes in MySQL/InnoDB-4.0.4, October 2, 2002

- We again use unbuffered disk I/O in Windows. Windows XP and Windows 2000 read performance seems to be very poor with normal I/O.

- Increased the maximum key length of `InnoDB` tables from 500 to 1024 bytes.

- Increased the table comment field in SHOW TABLE STATUS so that up to 16000 characters of foreign key definitions can be printed there.

- The auto-increment counter is no longer incremented if an insert of a row immediately fails in an error.

- Allow dropping and creating a table even if innodb_force_recovery is set. One can use this to drop a table which would cause a crash in rollback or purge, or if a failed table import causes a runaway rollback in recovery.

- Fixed a bug: Using ORDER BY primarykey DESC in 4.0.3 causes an assertion failure in btr0pcur.c, line 203.

- Fixed a bug: fast shutdown (which is the default) sometimes was slowed down by purge and insert buffer merge.

- Fixed a bug: doing a big SELECT from a table where no rows were visible in a consistent read could cause a very long (> 600 seconds) semaphore wait in btr0cur.c line 310.

- Fixed a bug: If the MySQL query cache was used, it did not get invalidated by a modification done by ON DELETE CASCADE or ...SET NULL.

- Fixed a bug: If you created a temporary table inside LOCK TABLES, and used that temporary table, that caused an assertion failure in ha_innodb.cc.

- Fixed a bug: If you set innodb_flush_log_at_trx_commit to 1, SHOW VARIABLES would show its value as 16 million.

### B.4.31. Changes in MySQL/InnoDB-4.0.3, August 28, 2002

- Removed unnecessary deadlocks when inserts have to wait for a locking read, update, or delete to release its next-key lock.

- The MySQL `HANDLER` SQL statements now work also for `InnoDB` type tables. `InnoDB` does the `HANDLER` reads always as consistent reads. `HANDLER` is a direct access path to read individual indexes of tables. In some cases, `HANDLER` can be used as a substitute of server-side cursors.

- Fixed a bug in 4.0.2: even a simple insert could crash the AIX version.

- Fixed a bug: If you used in a table name characters whose code is > 127, in DROP TABLE `InnoDB` could assert on line 155 of pars0sym.c.

- Compilation from source now provides a working version both on HP-UX-11 and HP-UX-10.20. The source of 4.0.2 worked only on 11, and the source of 3.23.52 only on 10.20.

- Fixed a bug: If compiled on 64-bit Solaris, `InnoDB` produced a bus error at startup.

### B.4.32. Changes in MySQL/InnoDB-3.23.52, August 16, 2002

- The feature set of 3.23 is frozen from this version on. New features go the 4.0 branch, and only bugfixes are made to the 3.23 branch.

- Many CPU-bound join queries now run faster. On Windows also many other CPU-bound queries run faster.

- A new SQL statement SHOW INNODB STATUS returns the output of the `InnoDB` Monitor to the client. The `InnoDB` Monitor now prints detailed information on the latest detected deadlock.

- `InnoDB` made the SQL query optimizer to avoid too much index-only range scans and choose full table scans instead. This is now fixed.

- `BEGIN` and `COMMIT` are now added in the binary log around transactions. The MySQL replication now respects transaction borders: a user no longer sees half transactions in replication slaves.

- A replication slave now prints in crash recovery the last master binary log position it was able to recover to.

- A new setting `innodb_flush_log_at_trx_commit=2` makes `InnoDB` to write the log to the operating system file cache at each commit. This is almost as fast as the setting innodb_flush_log_at_trx_commit=0, and the setting 2 also has the nice feature that in a crash where the operating system does not crash, no committed transaction is lost. If the operating system crashes or there is a power outage, then the setting 2 is no safer than the setting 0.

- Added checksum fields to log blocks.

- SET FOREIGN_KEY_CHECKS=0 helps in importing tables in an arbitrary order which does not respect the foreign key rules.

- SET UNIQUE_CHECKS=0 speeds up table imports into `InnoDB` if you have UNIQUE constraints on secondary indexes. This flag should be used only if you are certain that the input records contain no UNIQUE constraint violations.

- SHOW TABLE STATUS now lists also possible ON DELETE CASCADE or ON DELETE SET NULL in the comment field of the table.

- When CHECK TABLE is run on any `InnoDB` type table, it now checks also the adaptive hash index for all tables.

- If you defined ON DELETE CASCADE or SET NULL and updated the referenced key in the parent row, `InnoDB` deleted or updated the child row. This is now changed to conform to standard SQL: you get the error 'Cannot delete parent row'.

- Improved the auto-increment algorithm: now the first insert or SHOW TABLE STATUS initializes the auto-increment counter for the table. This removes almost all surprising deadlocks caused by SHOW TABLE STATUS.

- Aligned some buffers used in reading and writing to data files. This allows using unbuffered raw devices as data files in Linux.

- Fixed a bug: If you updated the primary key of a table so that only the case of characters changed, that could cause assertion failures, mostly in page0page.ic line 515.

- Fixed a bug: If you delete or update a row referenced in a foreign key constraint and the foreign key check has to wait for a lock, then the check may report an erroneous result. This affects also the ON DELETE... operation.

- Fixed a bug: A deadlock or a lock wait timeout error in `InnoDB` causes `InnoDB` to roll back the whole transaction, but MySQL could still write the earlier SQL statements to the binary log, even though `InnoDB` rolled them back. This could, for example, cause replicated databases to get out-of-sync.

- Fixed a bug: If the database happened to crash in the middle of a commit, then the recovery might leak tablespace pages.

- Fixed a bug: If you specified a non-latin1 character set in my.cnf, then, in contrary to what is stated in the manual, in a foreign key constraint a string type column had to have the same length specification in the referencing table and the referenced table.

- Fixed a bug: DROP TABLE or DROP DATABASE could fail if there simultaneously was a CREATE TABLE running.

- Fixed a bug: If you configured the buffer pool bigger than 2GB in a 32-bit computer, `InnoDB` would assert in buf0buf.ic line 214.

- Fixed a bug: on 64-bit computers updating rows which contained the SQL NULL in some column could cause the undo log and the ordinary log to become corrupt.

- Fixed a bug: innodb_log_monitor caused a hang if it suppressed lock prints for a page.

- Fixed a bug: in the HP-UX-10.20 version mutexes would leak and cause race conditions and crashes in any part of `InnoDB` code.

- Fixed a bug: If you ran in the AUTOCOMMIT mode, executed a SELECT, and immediately after that a RENAME TABLE, then RENAME would fail and MySQL would complain about error 1192.

- Fixed a bug: If compiled on 64-bit Solaris, `InnoDB` produced a bus error at startup.

### B.4.33. Changes in MySQL/InnoDB-4.0.2, July 10, 2002

- `InnoDB` is essentially the same as InnoDB-3.23.51.

- If no innodb_data_file_path is specified, `InnoDB` at the database creation now creates a 10MB auto-extending data file ibdata1 to the datadir of MySQL. In 4.0.1 the file was 64MB and not auto-extending.

### B.4.34. Changes in MySQL/InnoDB-3.23.51, June 12, 2002

- Fixed a bug: a join could result in a segmentation fault in copying of a BLOB or TEXT column if some of the BLOB or TEXT columns in the table contained SQL NULL values.

- Fixed a bug: If you added self-referential foreign key constraints with ON DELETE CASCADE to tables and a row deletion caused `InnoDB` to attempt the deletion of the same row twice because of a cascading delete, then you got an assertion failure.

- Fixed a bug: If you use MySQL 'user-level locks' and close a connection, then `InnoDB` may assert in ha_innobase.cc, line 302.

### B.4.35. Changes in MySQL/InnoDB-3.23.50, April 23, 2002

- `InnoDB` now supports an auto-extending last data file. You do not need to preallocate the whole data file at the database startup.

- Made several changes to facilitate the use of the `InnoDB Hot Backup` tool. It is a separate non-free tool you can use to take online backups of your database without shutting down the server or setting any locks.

- If you want to run the `InnoDB Hot Backup` tool on an auto-extending data file you have to upgrade it to version ibbackup-0.35.

- The log scan phase in crash recovery now runs much faster.

- Starting from this server version, the hot backup tool truncates unused ends in the backup `InnoDB` data files.

- To allow the hot backup tool to work, on Windows we no longer use unbuffered I/O or native async I/O; instead we use the same simulated async I/O as on Unix.

- You can now define the ON DELETE CASCADE or ON DELETE SET NULL clause on foreign keys.

- FOREIGN KEY constraints now survive ALTER TABLE and CREATE INDEX.

- We suppress the FOREIGN KEY check if any of the column values in the foreign key or referenced key to be checked is the SQL NULL. This is compatible with Oracle, for example.

- SHOW CREATE TABLE now lists also foreign key constraints. Also mysqldump no longer forgets about foreign keys in table definitions.

- You can now add a new foreign key constraint with ALTER TABLE ... ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...).

- FOREIGN KEY definitions now allow backticks around table and column names.

- MySQL command SET TRANSACTION ISOLATION LEVEL ... has now the following effect on `InnoDB` tables: If a transaction is defined as SERIALIZABLE then `InnoDB` conceptually adds LOCK IN SHARE MODE to all consistent reads. If a transaction is defined to have any other isolation level, then `InnoDB` obeys its default locking strategy which is REPEATABLE READ.

- SHOW TABLE STATUS no longer sets an x-lock at the end of an auto-increment index if the auto-increment counter has been initialized. This removes in almost all cases the surprising deadlocks caused by SHOW TABLE STATUS.

- Fixed a bug: in a CREATE TABLE statement the string 'foreign' followed by a non-space character confused the FOREIGN KEY parser and caused table creation to fail with errno 150.

### B.4.36. Changes in MySQL/InnoDB-3.23.49, February 17, 2002

- Fixed a bug: If you called DROP DATABASE for a database on which there simultaneously were running queries, the MySQL server could crash or hang. Crashes fixed, but a full fix has to wait some changes in the MySQL layer of code.

- Fixed a bug: on Windows one had to put the database name in lowercase for `DROP DATABASE` to work. Fixed in 3.23.49: case no longer matters on Windows. On Unix, the database name remains case sensitive.

- Fixed a bug: If one defined a non-latin1 character set as the default character set, then definition of foreign key constraints could fail in an assertion failure in dict0crea.c, reporting an internal error 17.

### B.4.37. Changes in MySQL/InnoDB-3.23.48, February 9, 2002

- Tuned the SQL optimizer to favor more often index searches over table scans.

- Fixed a performance problem when several large SELECT queries are run concurrently on a multiprocessor Linux computer. Large CPU-bound SELECT queries now also generally run faster on all platforms.

- If MySQL binary logging is used, `InnoDB` now prints after crash recovery the latest MySQL binary log file name and the position in that file (= byte offset) `InnoDB` was able to recover to. This is useful, for example, when resynchronizing a master and a slave database in replication.

- Added better error messages to help in installation problems.

- One can now recover also MySQL temporary tables which have become orphaned inside the `InnoDB` tablespace.

- `InnoDB` now prevents a FOREIGN KEY declaration where the signedness is not the same in the referencing and referenced integer columns.

- Fixed a bug: calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory corruption and make mysqld to crash. Especially at risk was mysqldump, because it calls frequently SHOW CREATE TABLE.

- Fixed a bug: If on Unix you did an ALTER TABLE to an `InnoDB` table and simultaneously did queries to it, mysqld could crash with an assertion failure in row0row.c, line 474.

- Fixed a bug: If inserts to several tables containing an auto-inc column were wrapped inside one LOCK TABLES, `InnoDB` asserted in lock0lock.c.

- In 3.23.47 we allowed several NULLS in a UNIQUE secondary index. But CHECK TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no longer complains in this situation.

- Fixed a bug: on Sparc and other high-endian processors SHOW VARIABLES showed innodb_flush_log_at_trx_commit and other boolean-valued startup parameters always OFF even if they were switched on.

- Fixed a bug: If you ran mysqld-max-nt as a service on Windows NT/2000, the service shutdown did not always wait long enough for the `InnoDB` shutdown to finish.

### B.4.38. Changes in MySQL/InnoDB-3.23.47, December 28, 2001

- Recovery happens now faster, especially in a lightly loaded system, because background checkpointing has been made more frequent.

- `InnoDB` allows now several similar key values in a UNIQUE secondary index if those values contain SQL NULLs. Thus the convention is now the same as in `MyISAM` tables.

- `InnoDB` gives a better row count estimate for a table which contains BLOBs.

- In a FOREIGN KEY constraint `InnoDB` is now case-insensitive to column names, and in Windows also to table names.

- `InnoDB` allows a FOREIGN KEY column of CHAR type to refer to a column of VARCHAR type, and vice versa. MySQL silently changes the type of some columns between CHAR and VARCHAR, and these silent changes do not hinder FOREIGN KEY declaration any more.

- Recovery has been made more resilient to corruption of log files.

- Unnecessary statistics calculation has been removed from queries which generate a temporary table. Some ORDER BY and DISTINCT queries now run much faster.

- MySQL now knows that the table scan of an `InnoDB` table is done through the primary key. This saves a sort in some ORDER BY queries.

- The maximum key length of `InnoDB` tables is again restricted to 500 bytes. The MySQL interpreter is not able to handle longer keys.

- The default value of innodb_lock_wait_timeout was changed from infinite to 50 seconds, the default value of innodb_file_io_threads from 9 to 4.

### B.4.39. Changes in MySQL/InnoDB-4.0.1, December 23, 2001

- `InnoDB` is the same as in 3.23.47.

- In 4.0.0 the MySQL interpreter did not know the syntax LOCK IN SHARE MODE. This has been fixed.

- In 4.0.0 multiple-table delete did not work for transactional tables. This has been fixed.

### B.4.40. Changes in MySQL/InnoDB-3.23.46, November 30, 2001

- This is the same as 3.23.45.

### B.4.41. Changes in MySQL/InnoDB-3.23.45, November 23, 2001

- This is a bugfix release.

- In versions 3.23.42-.44 when creating a table on Windows, you have to use lowercase letters in the database name to be able to access the table. Fixed in 3.23.45.

- `InnoDB` now flushes stdout and stderr every 10 seconds: If these are redirected to files, the file contents can be better viewed with an editor.

- Fixed an assertion failure in .44, in trx0trx.c, line 178 when you drop a table which has the .frm file but does not exist inside `InnoDB`.

- Fixed a bug in the insert buffer. The insert buffer tree could get into an inconsistent state, causing a crash, and also crashing the recovery. This bug could appear especially in large table imports or alterations.

- Fixed a bug in recovery: `InnoDB` could go into an infinite loop constantly printing a warning message that it cannot find free blocks from the buffer pool.

- Fixed a bug: when you created a temporary table of the `InnoDB` type, and then used ALTER TABLE to it, the MySQL server could crash.

- Prevented creation of MySQL system tables 'mysql.user', 'mysql.host', or 'mysql.db', in the `InnoDB` type.

- Fixed a bug which can cause an assertion failure in 3.23.44 in srv0srv.c, line 1728.

### B.4.42. Changes in MySQL/InnoDB-3.23.44, November 2, 2001

- You can define foreign key constraints on `InnoDB` tables. An example: FOREIGN KEY (col1) REFERENCES table2(col2).

- You can create data files larger than 4GB in those filesystems that allow it.

- Improved `InnoDB` monitors, including a new innodb_table_monitor which allows you to print the contents of the `InnoDB` internal data dictionary.

- DROP DATABASE now works also for `InnoDB` tables.

- Accent characters in the default character set latin1 are ordered according to the MySQL ordering.

  NOTE: If you are using latin1 and have inserted characters whose code is > 127 to an indexed CHAR column, you should run CHECK TABLE on your table when you upgrade to 3.23.43, and drop and reimport the table if CHECK TABLE reports an error!

- `InnoDB` calculates better table cardinality estimates.

- Change in deadlock resolution: in .43 a deadlock rolls back only the SQL statement, in .44 it rolls back the whole transaction.

- Deadlock, lock wait timeout, and foreign key constraint violations (no parent row, child rows exist) now return native MySQL error codes 1213, 1205, 1216, 1217, respectively.

- A new my.cnf parameter innodb_thread_concurrency helps in performance tuning in high concurrency environments.

- A new my.cnf option innodb_force_recovery helps you in dumping tables from a corrupted database.

- A new my.cnf option innodb_fast_shutdown speeds up shutdown. Normally `InnoDB` does a full purge and an insert buffer merge at shutdown.

- Raised maximum key length to 7000 bytes from a previous limit of 500 bytes.

- Fixed a bug in replication of auto-inc columns with multiline inserts.

- Fixed a bug when the case of letters changes in an update of an indexed secondary column.

- Fixed a hang when there are more than 24 data files.

- Fixed a crash when `MAX(`col`)` is selected from an empty table, and `col` is a not the first column in a multi-column index.

- Fixed a bug in purge which could cause crashes.

### B.4.43. Changes in MySQL/InnoDB-3.23.43, October 4, 2001

- This is essentially the same as InnoDB-3.23.42.

### B.4.44. Changes in MySQL/InnoDB-3.23.42, September 9, 2001

- Fixed a bug which corrupted the table if the primary key of a > 8000-byte row was updated.

- There are now 3 types of `InnoDB` Monitors: innodb_monitor, innodb_lock_monitor, and innodb_tablespace_monitor. innodb_monitor now prints also buffer pool hit rate and the total number of rows inserted, updated, deleted, read.

- Fixed a bug in RENAME TABLE.

- Fixed a bug in replication with an auto-increment column.

### B.4.45. Changes in MySQL/InnoDB-3.23.41, August 13, 2001

- Support for < 4GB rows. The previous limit was 8000 bytes.

- Use the doublewrite file flush method.

- Raw disk partitions supported as data files.

- `InnoDB` Monitor.

- Several hang bugs fixed and an `ORDER BY` bug (“Sort aborted”) fixed.

### B.4.46. Changes in MySQL/InnoDB-3.23.40, July 16, 2001

- Only a few rare bugs fixed.

### B.4.47. Changes in MySQL/InnoDB-3.23.39, June 13, 2001

- `CHECK TABLE` now works for `InnoDB` tables.

- A new `my.cnf` parameter `innodb_unix_file_flush_method` introduced. It can be used to tune disk write performance.

- An auto-increment column now gets new values past the transaction mechanism. This saves CPU time and eliminates transaction deadlocks in new value assignment.

- Several bugfixes, most notably the rollback bug in 3.23.38.

### B.4.48. Changes in MySQL/InnoDB-3.23.38, May 12, 2001

- The new syntax `SELECT ... LOCK IN SHARE MODE` is introduced.

- `InnoDB` now calls `fsync()` after every disk write and calculates a checksum for every database page it writes or reads, which reveals disk defects.

- Several bugfixes.

## B.5. Changes in MySQL Cluster

Starting from 4.1.13 and 5.0.7, all Cluster changes are included in the MySQL Change History, and this manual section is no longer separately maintained.

### B.5.1. Changes in MySQL Cluster-5.0.7 (10 June 2005)

### Note

Starting with version 5.0.8, changes for MySQL Cluster can be found in the combined MySQL Change History.

Functionality added or changed:

Bugs fixed:

- (Bug#11019) mgmapi start backup in some cases returns wrong backupid

- (Bug#10190) Backup from cluster wih NoOfReplica=1 is corrupt

- (Bug#9246) Condition pushdown and left join, wrong result

- (Bug#10956) More than 7 node restarts with `--initial` caused cluster to fail.

- (Bug#9945) `ALTER TABLE` caused server crash. (Linux/390)

- (Bug#9826) (Bug#10948) Schema change (`DROP TABLE`, `ALTER TABLE`) crashed HPUX and PPC32.

- (Bug#10711) (Bug#9363) (Bug#8918) (Bug#10058) (Bug#9025) Cluster would time out and crash after first query; setting DataMemory to more than 2GB prevented cluster from starting; calling `ndb_select_count()` crashed the cluster. (64-bit Unix OSes)

### B.5.2. Changes in MySQL Cluster-5.0.6 (26 May 2005)

Functionality added or changed:

- Limit on number of metadata objects (number of tables, indexes and BLOBs) now increased to 20,320

Bugs fixed:

- The server would hang on successive calls to an `INSERT ... ON DUPLICATE KEY UPDATE` query. (Bug#9725)

- (Bug#10193) Invalid DataDir in config causes ndbd segmentation fault

- (Bug#10813) Build with SCI Transporter fails

- (Bug#10831) ndb mgmd LogDestination maxfiles does not rotate logs properly

### B.5.3. Changes in MySQL Cluster-5.0.5 (Not released)

Functionality added or changed:

- Decreased IndexMemory Usage

- Parallel key lookup (read-multi-range) for queries like `SELECT * FROM t1 WHERE primary_key IN (1,2,3,4,5,6,7,8,9,10);`

Bugs fixed:

Patches merged from versions 4.1.11 and 4.1.12

- (Bug#8315) NdbScanFilter cmp method only works for strings of exact word boundary length

- (Bug#8103) Configuration handling error

- (Bug#8035) mysqld signal 10 when ndbd is shutdown

- (Bug#7631) NDB$EVENT contains unreadable event and table names

- (Bug#7628) Filtered event types are ignored

- (Bug#7627) Drop Event operation fails

- (Bug#7424) create index on datetime fails

### B.5.4. Changes in MySQL Cluster-5.0.4 (16 April 2005)

Functionality added or changed:

- Condition pushdown to storage engine now works for update and delete as well

Bugs fixed:

- (Bug#9675) Auto-increment not working with INSERT..SELECT and NDB storage

- (Bug#9517) Condition pushdown to storage engine does not work for update/delete

- (Bug#9282) API Node Crashes/Reloads on 'DELETE FROM'

- (Bug#9280) Memory leak in cluster when dependent sub-queries are used

- (Bug#8585) ndb_cache2 fails on aix52

### B.5.5. Changes in MySQL Cluster-5.0.3 (23 March 2005: Beta)

Functionality added or changed:

- Condition pushdown to storage engine

- Query cache enabled for cluster

Bugs fixed:

- Patches merged from version 4.1.10

### B.5.6. Changes in MySQL Cluster-5.0.1 (27 July 2004)

Functionality added or changed:

- This was the first MySQL Cluster release in the 5.0 series. As nearly all attention was still focused on getting 4.1 stable, it is not recommended to use MySQL 5.0.1 for MySQL Cluster.

Bugs fixed:

- N/A

### B.5.7. Changes in MySQL Cluster-4.1.13 (15 July 2005)

Functionality added or changed:

Bugs fixed:

- (Bug#11132) Connections between data nodes and management nodes were not being closed following shutdown of `ndb_mgmd`.

- (Bug#11050) `ndb_mgm> show` printed incorrectly after master data node failure.

- (Bug#10956) More than 7 node restarts with `--initial` caused cluster to fail.

- (Bug#9826) (Bug#10948) Schema change (`DROP TABLE`, `ALTER TABLE`) crashed HPUX and PPC32.

- (Bug#9025) Data nodes failed to restart on 64-bit Solaris.

- (Bug#11166) Insert records were incorrectly applied by `ndb_restore`, thus making restoration from backup inconsistent if the binlog contained inserts.

- (Bug#8918) (Bug#9363) (Bug#10711) (Bug#10058) (Bug#9025) Cluster would time out and crash after first query; setting DataMemory to more than 2GB prevented cluster from starting; calling `ndb_select_count()` crashed the cluster. (64-bit Unix OSes)

- (Bug#10190) When making a backup of a cluster where `NumberOfReplicas` was equal to 1, the backup's metadata was corrupted. (Linux)

- (Bug#9945) `ALTER TABLE` caused server crash. (Linux/390)

- (Bug#11133) A delete operation performed as part of a transaction caused an erroneous result.

- (Bug#10294) Not allowing sufficient parallelism in cluster configuration (for example, `NoOfTransactions` too small) caused `ndb_restore` to fail without generating any error messages.

- (Bug#11290) Setting TransactionInactiveTimeout= 0 did not result in an infinite timeout.

### B.5.8. Changes in MySQL Cluster-4.1.12 (13 May 2005)

Functionality added or changed:

Bugs fixed:

- (Bug#10471) Backup can become inconsistent with certain combinations of multiple-row updates

- (Bug#10287) ndb_select_all "delimiter" option non functional

- (Bug#10142) Unhandled resource shortage in UNIQUE index code

- (Bug#10029) crash in ordered index scan after db full

- (Bug#10001) 2 NDB nodes get signal 6 (abort) in DBTC

- (Bug#9969) 4012 - has misleading error message

- (Bug#9960) START BACKUP reports failure albeit succeeding

- (Bug#9924) ABORT BACKUP 1 crashes 4 node cluster

- (Bug#9892) Index activation file during node recovery

- (Bug#9891) Crash in DBACC (line 7004) during commit

- (Bug#9865) SELECT does not function properly

- (Bug#9839) Column with AUTOINC contains -1 Value on node stop

- (Bug#9757) Uncompleted node failure after gracefully stopping node

- (Bug#9749) Transactions causes deadlock in ACC

- (Bug#9724) Node fails to start: Message: File has already been opened

- (Bug#9691) UPDATE fails on attempt to update primary key

- (Bug#9675) Auto-increment not working with INSERT..SELECT and NDB storage

- (Bug#9318) drop database does not drop ndb tables

- (Bug#9280) Memory leak in cluster when dependent sub-queries are used

- (Bug#8928) create table with keys will shutdown the cluster

- Creating a table did not work for a cluster with 6 nodes. (Bug#8928) Databases with 1, 2, 4, 8, ... (2`n` nodes) did not have the problem. After a rolling upgrade, restart each node manually by restarting it with the `--initial` option. Otherwise, use dump and restore after an upgrade.

### B.5.9. Changes in MySQL Cluster-4.1.11 (01 April 2005)

Functionality added or changed:

Bugs fixed:

- (Bug#9916) DbaccMain.cpp / DBACC (Line: 4876) / Pointer too large

- (Bug#9435) TIMESTAMP columns don't update

- (Bug#9052) Uninitialized data during unique index build, potential cluster crash

- (Bug#8876) Timeout when committing aborted transaction after node failure

- (Bug#8786) ndb_autodiscover, drop index can fail, wait 2 minutes timeout

- (Bug#8853) Transaction aborted after long time during node failure (4012)

- (Bug#8753) Invalid schema object version after dropping index (crash fixed, currently retry required)

- (Bug#8645) Assertion failure with multiple management servers

- (Bug#8557) ndbd does not get same nodeid on restart

- (Bug#8556) corrupt ndb_mgm show printout for certain configurations

- (Bug#8167) cluster shared memory and mysqld signal usage clash

### B.5.10. Changes in MySQL Cluster-4.1.10 (12 February 2005)

Bugs fixed:

- (Bug#8284) Out of fragment memory in DBACC

- (Bug#8262) Node crash due to bug in DBLQH

- (Bug#8208) node restart fails on Aix 5.2

- (Bug#8167) cluster shared memory and mysqld signal usage clash

- (Bug#8101) unique index and error 4209 while selecting

- (Bug#8070) (Bug#7937) (Bug#6716) various ndb_restore core dumps on HP-UX

- (Bug#8010) 4006 forces MySQL Node Restart

- (Bug#7928) out of connection objects

- (Bug#7898) mysqld crash with ndb (solaris)

- (Bug#7864) Not possible to have more than 4.5G data memory

### B.5.11. Changes in MySQL Cluster-4.1.9 (13 January 2005)

Functionality added or changed:

- New implementation of shared memory transporter.

- Cluster automatically configures shared memory transporter if possible.

- Cluster prioritizes usage of transporters with shared memory and localhost TCP

- Added switches to control the above functions, `ndb-shm` and `ndb-optimized-node-selection`.

Bugs fixed:

- (Bug#7805) config.ini parsing error

- (Bug#7798) Running range scan after alter table in different thread causes node failure

- (Bug#7761) Alter table does not autocommit

- (Bug#7725) Indexed DATETIME Columns Return Random Results

- (Bug#7660) START BACKUP does not increment BACKUP-ID (Big Endian machines)

- (Bug#7593) Cannot Create A Large NDB Data Warehouse

- (Bug#7480) Mysqld crash in ha_ndbcluster using Query Browser

- (Bug#7470) shared memory transporter does not connect

- (Bug#7396) Primary Key not working in NDB Mysql Clustered table (solaris)

- (Bug#7379) ndb restore fails to handle blobs and multiple databases

- (Bug#7346) ndb_restore enters infinite loop

- (Bug#7340) Problem for inserting data into the Text field on utf8

- (Bug#7124) ndb_mgmd is aborted on startup when using SHM connection

### B.5.12. Changes in MySQL Cluster-4.1.8 (14 December 2004)

Functionality added or changed:

- Default port for ndb_mgmd was changed to 1186 (from 2200) as this port number was officially assigned to MySQL Cluster by IANA.

- New command in ndb_mgm, PURGE STALE SESSIONS, as a workaround for cases where nodes fail to allocate a node id even if it is free to use.

- New command in ndb_mgm, CONNECT.

- The ndb executables have been changed to make use of the regular MySQL command line option parsing features. See Section 14.5.5, “Command Options for MySQL Cluster Processes”, for notes on changes.

- As bonus of the above you can now specify all command line options in `my.cnf` using the executable names as sections, that is, `[ndbd]`, `[ndb_mgmd]`, `[ndb_mgm]`, `[ndb_restore]`, and so forth.

            [ndbd]
            ndb-connectstring=myhost.domain.com:1234
            [ndb_mgm]
            ndb-connectstring=myhost.domain.com:1234

- Added use of section `[mysql_cluster]` in `my.cnf`. All cluster executables, including mysqld, parse this section. For example, this is a convenient place to put `ndb-connectstring` so that it need be specified only once.

- Added cluster log info events on allocation and deallocation of nodeid's.

- Added cluster log info events on connection refuse as a result of version mismatch.

- Extended connectstring syntax to allow for leaving the port number out. For example, `ndb-connectstring|connect-string=myhost1,myhost2,myhost3` is a valid connectstring and connect occurs on default port 1186.

- Clear text ndb error messages provided also for error codes that are mapped to corresponding mysql error codes, by executing `SHOW WARNINGS` after an error has occurred which relates to the ndb storage engine.

- Significant performance improvements done for read performance, especially for blobs.

- Added some variables for performance tuning, `ndb_force_send` and `ndb_use_exact_count`. Do `show variables like 'ndb%';` in mysql client for listing. Use `set` command to alter variables.

- Added variables to set some options, `ndb_use_transactions` and `ndb_autoincrement_prefetch_sz`.

Bugs fixed:

- (Bug#7303) ndb_mgm: Trying to set CLUSTERLOG for a specific node id core dumps

- (Bug#7193) start backup gives false error printout

- (Bug#7153) Cluster nodes don't report error on endianness mismatch

- (Bug#7152) ndb_mgmd segmentation fault on incorrect HostName in configuration

- (Bug#7104) clusterlog filtering and level setting broken

- (Bug#6995) ndb_recover on varchar fields results in changing case of data

- (Bug#6919) all status only shows 2 nodes on a 8-node cluster

- (Bug#6871) DBD execute failed: Got error 897 'Unknown error code' from ndbcluster

- (Bug#6794) Wrong outcome of update operation of ndb table

- (Bug#6791) Segmentation fault when config.ini is not correctly set

- (Bug#6775) failure in acc when running many mysql clients

- (Bug#6696) ndb_mgm command line options inconsistent with behavior

- (Bug#6684) ndb_restore doesn't give error messages if improper command given

- (Bug#6677) ndb_mgm can crash on "ALL CLUSTERLOG"

- (Bug#6538) Error code returned when select max() on empty table with index

- (Bug#6451) failing create table givers "ghost" tables which are impossible to remove

- (Bug#6435) strange behavior of left join

- (Bug#6426) update with long pk fails

- (Bug#6398) update of primary key fails

- (Bug#6354) mysql does not complain about --ndbcluster option when NDB is not compiled in

- (Bug#6331) INSERT IGNORE .. SELECT breaks subsequent inserts

- (Bug#6288) cluster nodes crash on data import

- (Bug#6031) To drop database you have to execute DROP DATABASE command twice

- (Bug#6020) LOCK TABLE + delete returns error 208

- (Bug#6018) REPLACE does not work for BLOBs + NDB

- (Bug#6016) Strange crash with blobs + different DATABASES

- (Bug#5973) ndb table belonging to different database shows up in show tables

- (Bug#5872) ALTER TABLE with blob from ndb table to myisam fails

- (Bug#5844) Failing mysql-test-run leaves stray NDB processes behind

- (Bug#5824) HELP text messed up in ndb_mgm

- (Bug#5786) Duplicate key error after restore

- (Bug#5785) lock timeout during concurrent update

- (Bug#5782) Unknown error when using LIMIT with ndb table

- (Bug#5756) RESTART node from ndb_mgm fails

- A few more not reported bugs fixed

### B.5.13. Changes in MySQL Cluster-4.1.7 (23 October 2004)

Functionality added or changed:

- Optimization 1: Improved performance on index scans. Measured 30% performance increase on query which do large amounts of index scans.

- Optimization 2: Improved performance on primary key lookups. Around double performance for autocommitted primary key lookups.

- Optimization 3: Improved performance when using blobs by avoiding usage of exclusive locks for blobs.

Bugs fixed:

- A few bugs fixed.

### B.5.14. Changes in MySQL Cluster-4.1.6 (10 October 2004)

Functionality added or changed:

- Limited character set support for storage engine NDBCLUSTER:

  Char set | Collation
  big5 | big5_chinese_ci
  | big5_bin
  binary | binary
  euckr | euckr_korean_ci
  | euckr_bin
  gb2312 | gb2312_chinese_ci
  | gb2312_bin
  gbk | gbk_chinese_ci
  | gbk_bin
  latin1 | latin1_swedish_ci
  | latin1_bin
  sjis | sjis_japanese_ci
  | sjis_bin
  tis620 | tis620_bin
  ucs2 | ucs2_general_ci
  | ucs2_bin
  ujis | ujis_japanese_ci
  | ujis_bin
  utf8 | utf8_general_ci
  | utf8_bin

- The SCI Transporter has been brought up-to-date with all changes and now works and has been documented as well.

- Optimizations when several clients to a MySQL Server access ndb tables.

- Added more checks and warnings for erroneous and inappropriate cluster configurations.

- `SHOW TABLES` now directly shows ndb tables created on a different MySQL server, that is, without a prior table access.

- Enhanced support for starting MySQL Server independently of ndbd and ndb_mgmd.

- Clear text ndb error messages provided by executing `SHOW WARNINGS` after an error has occurred which relates to the ndb storage engine.

Bugs fixed:

- Quite a few bugs fixed.

### B.5.15. Changes in MySQL Cluster-4.1.5 (16 September 2004)

Functionality added or changed:

- Many queries in MySQL Cluster are executed as range scans or full table scans. All queries that don't use a unique hash index or the primary hash index use this access method. In a distributed system it is crucial that batching is properly performed.

  In previous versions, the batch size was fixed to 16 per data node. In this version it is configurable per MySQL Server. So for queries using lots of large scans it is appropriate to set this parameter rather large and for queries using many small scans only fetching a small amount of records it is appropriate to set it low.

  The performance of queries can easily change as much as 40% based on how this variable is set.

  In future versions more logic will be implemented for assessing the batch size on a per-query basis. Thus, the semantics of the new configuration variable `ScanBatchSize` are likely to change.

- The fixed size overhead of the ndbd process has been greatly decreased. This is also true for the overhead per operation record as well as overhead per table and index.

  A number of new configuration variables have been introduced to enable configuration of system buffers. Configuration variables for specifying the numbers of tables, unique hash indexes, and ordered indexes have also been introduced.

  New configuration variables: `MaxNoOfOrderedIndexes`, `MaxNoOfUniqueHashIndexes`

  Configuration variables no longer used: `MaxNoOfIndexes` (split into the two above).

- In previous versions `ALTER TABLE`, `TRUNCATE TABLE`, and `LOAD DATA` were performed as one big transaction. In this version, all of these statements are automatically separated into several distinct transactions.

  This removes the limitation that one could not change very large tables due to the `MaxNoOfConcurrentOperations` parameter.

- MySQL CLuster's online backup feature now backs up indexes so that both data and indexes are restored.

- In previous versions it was not possible to use `NULL` in indexes. This is now possible for all supported index types.

- Much work has been put onto making `AUTO_INCREMENT` features work as for other table handlers. Autoincrements as a partial key is still only supported by `MyISAM`.

- In earlier versions, mysqld would crash if the cluster wasn't started with the `--ndbcluster` option. Now mysqld handles cluster crashes and starts without crashing.

- The `-i` option for initial startup of ndbd has been removed. Initial startup still can be specified by using the `--initial` option. The reason for this is to ensure that it is clear what takes place when using `--initial`: this option completely removes all data from the disk and should only be used at initial start, in certain software upgrade cases, and in some cases as a workaround when nodes cannot be restarted successfully.

- The management client (ndb_mgm) now has additional commands and more information is printed for some commands such as `show`.

- In previous versions, the files were called `ndb_0..` when it wasn't possible to allocate a node ID when starting the node. To ensure that files are not so easily overwritten, these files are now named `ndb_pid..`, where pid is the process ID assigned by the OS.

- The default parameters have changed for ndb_mgmd and ndbd. In particular, they are now started as daemons by default. The `-n` option has been removed since it could cause confusion as to its meaning (nostart or nodaemon).

- In the configuration file, you can now use `[NDBD]` as an alias for `[DB]`, `[MYSQLD]` as an alias for `[API]`, and `[NDB_MGMD]` as an alias for `[MGM]`.

  ### Note

  In fact, `[NDBD]`, `[MYSQLD]`, and `[NDB_MGMD]` are now the preferred designations, although the older ones will continue to be supported for some time to come in order to maintain backward compatibility.

- Many more checks for consistency in configuration have been introduced to in order to provide quicker feedback on configuration errors.

- In the connect string, it is now possible to use both “`;`” and “`,`” as the separator between entries. Thus, "nodeid=2,host=localhost:2200" is equivalent to "nodeid=2;host=localhost:2200".

  In the configuration file, it is also possible to use “`:`” or “`=`” for assignment values. For example, `MaxNoOfOrderedIndexes : 128` and `MaxNoOfOrderedIndexes = 128` are equivalent expressions.

- The configuration variable names are now case insensitive, so `MaxNoOfOrderedIndexes: 128` is equivalent to `MAXNOOFORDEREDINDEXES = 128`.

- It is possible now to set the backup directory separately from the `FileSystemPath` by using the `BackupDir` configuration variable.

  Log files and trace files can now be placed in any directory by setting the `DataDir` configuration variable.

  `FileSystemPath` is no longer mandatory and defaults to `DataDir`.

- Queries involving tables from different databases are now supported.

- It is now possible to update the primary key.

- The performance of ordered indexes has been greatly improved, particularly the maintenance of indexes on updates, inserts and deletes.

Bugs fixed:

- Quite a few bugs fixed.

### B.5.16. Changes in MySQL Cluster-4.1.4 (31 August 2004)

Functionality added or changed:

- The names of the log files and trace files created by the ndbd and ndb_mgmd processes have changed.

- Support for the many `BLOB` data types was introduced in this version.

Bugs fixed:

- Quite a few bugs were fixed in the 4.1.4 release.

### B.5.17. Changes in MySQL Cluster-4.1.3 (28 June 2004)

Functionality added or changed:

- This was the first MySQL Cluster release so all functionality was new.

Bugs fixed:

- Various bugs fixed in the development process leading up to 4.1.3.

## B.6. MySQL Connector/ODBC (MyODBC) Change History

### B.6.1. Changes in MySQL Connector/ODBC 5.1.2 (Not yet released)

Functionality added or changed:

- A full implementation of SQLForeignKeys based on the information available from INFORMATION_SCHEMA in 5.0 and later versions of the server has been implemented.

Bugs fixed:

- `SQLGetInfo()` reported characters for `SQL_SPECIAL_CHARACTERS` that were not encoded correctly. (Bug#33130)

- Renaming an existing DSN entry would create a new entry with the new name without deleting the old entry. (Bug#31165)

- Reading a `TEXT` column that had been used to store UTF8 data would result in the wrong information being returned during a query. (Bug#28617)

- `SQLForeignKeys` would return an empty string for the schema columns instead of `NULL`. (Bug#19923)

- Evaluating a simple numeric expression when using the OLEDB for ODBC provider and ADO would return an error, instead of the result. (Bug#10128)

- Adding or updating a row using `SQLSetPos()` on a result set with aliased columns would fail. (Bug#6157)

### B.6.2. Changes in MySQL Connector/ODBC 5.1.1 (13 December 2007)

MySQL Connector/ODBC 5.1.1-beta, a new version of the ODBC driver for the MySQL database management system, has been released. This release is the first beta (feature-complete) release of the new 5.1 series and is suitable for use with any MySQL server version since MySQL 4.1, including MySQL 5.0, 5.1, and 6.0. (It will not work with 4.0 or earlier releases.)

Keep in mind that this is a beta release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data.

Includes changes from Connector/ODBC 3.51.21 and 3.51.22.

Built using MySQL 5.0.52.

Platform specific notes:

- The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

- There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

- The installer for 64-bit Windows installs both the 32-bit and 64-bit driver. Please note that Microsoft does not yet supply a 64-bit bridge from ADO to ODBC.

Functionality added or changed:

- Incompatible Change: Replaced myodbc3i (now myodbc-installer) with Connector/ODBC 5.0 version.

- Incompatible Change: Removed monitor (myodbc3m) and dsn-editor (myodbc3c).

- Incompatible Change: Disallow `SET NAMES` in initial statement and in executed statements.

- A wrapper for the `SQLGetPrivateProfileStringW()` function, which is required for Unicode support, has been created. This function is missing from the unixODBC driver manager. (Bug#32685)

- Added MSI installer for Windows 64-bit. (Bug#31510)

- Implemented support for `SQLCancel()`. (Bug#15601)

- Added support for `SQL_NUMERIC_STRUCT`. (Bug#3028, Bug#24920)

- Removed non-threadsafe configuration of the driver. The driver is now always built against the threadsafe version of libmysql.

- Implemented native Windows setup library

- Replaced the internal library which handles creation and loading of DSN information. The new library, which was originally a part of Connector/ODBC 5.0, supports Unicode option values.

- The Windows installer now places files in a subdirectory of the `Program Files` directory instead of the Windows system directory.

Bugs fixed:

- The `SET NAMES` statement has been disabled because it causes problems in the ODBC driver when determining the current client character set. (Bug#32596)

- `SQLDescribeColW` returned UTF-8 column as `SQL_VARCHAR` instead of `SQL_WVARCHAR`. (Bug#32161)

- ADO was unable to open record set using dynamic cursor. (Bug#32014)

- ADO applications would not open a `RecordSet` that contained a `DECIMAL` field. (Bug#31720)

- Memory usage would increase considerably. (Bug#31115)

- SQL statements are limited to 64KB. (Bug#30983, Bug#30984)

- `SQLSetPos` with `SQL_DELETE` advances dynamic cursor incorrectly. (Bug#29765)

- Using an ODBC prepared statement with bound columns would produce an empty result set when called immediately after inserting a row into a table. (Bug#29239)

- ADO Not possible to update a client side cursor. (Bug#27961)

- Recordset `Update()` fails when using `adUseClient` cursor. (Bug#26985)

- Connector/ODBC would fail to connect to the server if the password contained certain characters, including the semicolon and other punctuation marks. (Bug#16178)

- Fixed `SQL_ATTR_PARAM_BIND_OFFSET`, and fixed row offsets to work with updatable cursors.

- `SQLSetConnectAttr()` did not clear previous errors, possibly confusing `SQLError()`.

- `SQLError()` incorrectly cleared the error information, making it unavailable from subsequent calls to `SQLGetDiagRec()`.

- NULL pointers passed to `SQLGetInfo()` could result in a crash.

- `SQL_ODBC_SQL_CONFORMANCE` was not handled by `SQLGetInfo()`.

- `SQLCopyDesc()` did not correctly copy all records.

- Diagnostics were not correctly cleared on connection and environment handles.

### B.6.3. Changes in MySQL Connector/ODBC 5.1.0 (10 September 2007)

This release is the first of the new 5.1 series and is suitable for use with any MySQL server version since MySQL 4.1, including MySQL 5.0, 5.1, and 6.0. (It will not work with 4.0 or earlier releases.)

Keep in mind that this is a alpha release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. Not all of the features planned for the final Connector/ODBC 5.1 release are implemented.

Functionality is based on Connector/ODBC 3.51.20.

Platform specific notes:

- The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

- There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

- There are no installer packages for Microsoft Windows x64 Edition.

Functionality added or changed:

- Added support for Unicode functions (`SQLConnectW`, etc).

- Added descriptor support (`SQLGetDescField`, `SQLGetDescRec`, etc).

- Added support for `SQL_C_WCHAR`.

### B.6.4. Changes in MySQL Connector/ODBC 5.0.12 (Never released)

### Note

Development on Connector/ODBC 5.0.x has ceased. New features and functionality will be incorporated into Connector/ODBC 5.1. See Section 17.1.2.1, “Connector/ODBC Roadmap”.

Bugs fixed:

- Inserting `NULL` values into a `DATETIME` column from Access reports an error. (Bug#27896)

- Tables with `TEXT` columns would be incorrectly identified, returning an `Unknown SQL type - 65535` error. (Bug#20127)

### B.6.5. Changes in MySQL Connector/ODBC 5.0.11 (31 January 2007)

Functionality added or changed:

- Added support for ODBC v2 statement options using attributes.

- Driver now builds and is partially tested under Linux with the iODBC driver manager.

Bugs fixed:

- Connection string parsing for DSN-less connections could fail to identify some parameters. (Bug#25316)

- Updates of `MEMO` or `TEXT` columns from within Microsoft Access would fail. (Bug#25263)

- Transaction support has been added and tested. (Bug#25045)

- Internal function, `my_setpos_delete_ignore()` could cause a crash. (Bug#22796)

- Fixed occasional mis-handling of the `SQL_NUMERIC_C` type.

- Fixed the binding of certain integer types.

### B.6.6. Changes in MySQL Connector/ODBC 5.0.10 (14 December 2006)

Connector/ODBC 5.0.10 is the sixth BETA release.

Functionality added or changed:

- Significant performance improvement when retrieving large text fields in pieces using `SQLGetData()` with a buffer smaller than the whole data. Mainly used in Access when fetching very large text fields. (Bug#24876)

- Added initial unicode support in data and metadata. (Bug#24837)

- Added initial support for removing braces when calling stored procedures and retrieving result sets from procedure calls. (Bug#24485)

- Added loose handling of retrieving some diagnostic data. (Bug#15782)

- Added wide-string type info for `SQLGetTypeInfo()`.

Bugs fixed:

- Editing DSN no longer crashes ODBC data source administrator. (Bug#24675)

- String query parameters are new escaped correctly. (Bug#19078)

### B.6.7. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)

Connector/ODBC 5.0.9 is the fifth BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Functionality added or changed:

- Added support for column binding as SQL_NUMBERIC_STRUCT.

- Added recognition of `SQL_C_SHORT` and `SQL_C_TINYINT` as C types.

Bugs fixed:

- Fixed wildcard handling of and listing of catalogs and tables in `SQLTables`.

- Added limit of display size when requested via `SQLColAttribute`/`SQL_DESC_DISPLAY_SIZE`.

- Fixed buffer length return for SQLDriverConnect.

- ODBC v2 behaviour in driver now supports ODBC v3 date/time types (since DriverManager maps them).

- Catch use of `SQL_ATTR_PARAMSET_SIZE` and report error until we fully support.

- Fixed statistics to fail if it couldn't be completed.

- Corrected retrieval multiple field types bit and blob/text.

- Fixed SQLGetData to clear the NULL indicator correctly during multiple calls.

### B.6.8. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)

Connector/ODBC 5.0.8 is the fourth BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Functionality added or changed:

- Also made `SQL_DESC_NAME` only fill in the name if there was a data pointer given, otherwise just the length.

- Fixed display size to be length if max length isn’t available.

- Made distinction between `CHAR`/`BINARY` (and VAR versions).

- Wildcards now support escaped chars and underscore matching (needed to link tables with underscores in access).

Bugs fixed:

- Fixed binding using `SQL_C_LONG`.

- Fixed using wrong pointer for `SQL_MAX_DRIVER_CONNECTIONS` in `SQLGetInfo`.

- Set default return to `SQL_SUCCESS` if nothing is done for `SQLSpecialColumns`.

- Fixed MDiagnostic to use correct v2/v3 error codes.

- Allow SQLDescribeCol to be called to retrieve the length of the column name, but not the name itself.

- Length now used when handling bind parameter (needed in particular for `SQL_WCHAR`) - this enables updating char data in MS Access.

- Updated retrieval of descriptor fields to use the right pointer types.

- Fixed hanlding of numeric pointers in SQLColAttribute.

- Fixed type returned for `MYSQL_TYPE_LONG` to `SQL_INTEGER` instead of `SQL_TINYINT`.

- Fix size return from `SQLDescribeCol`.

- Fixed string length to chars, not bytes, returned by SQLGetDiagRec.

### B.6.9. Changes in MySQL Connector/ODBC 5.0.7 (08 November 2006)

Connector/ODBC 5.0.7 is the third BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Functionality added or changed:

- Added support for `SQLStatistics` to `MYODBCShell`.

- Improved trace/log.

Bugs fixed:

- SQLBindParameter now handles `SQL_C_DEFAULT`.

- Corrected incorrect column index within `SQLStatistics`. Many more tables can now be linked into MS Access.

- Fixed `SQLDescribeCol` returning column name length in bytes rather than chars.

### B.6.10. Changes in MySQL Connector/ODBC 5.0.6 (03 November 2006)

Connector/ODBC 5.0.6 is the second BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Features, limitations and notes on this release

- Connector/ODBC supports both `User` and `System` DSNs.

- Installation is provided in the form of a standard Microsoft System Installer (MSI).

- You no longer have to have Connector/ODBC 3.51 installed before installing this version.

Bugs fixed:

- You no longer have to have Connector/ODBC 3.51 installed before installing this version.

- Connector/ODBC supports both `User` and `System` DSNs.

- Installation is provided in the form of a standard Microsoft System Installer (MSI).

### B.6.11. Changes in MySQL Connector/ODBC 5.0.5 (17 October 2006)

Connector/ODBC 5.0.5 is the first BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

You no longer have to have Connector/ODBC 3.51 installed before installing this version.

Bugs fixed:

- You no longer have to have Connector/ODBC 3.51 installed before installing this version.

### B.6.12. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)

This is an implementation and testing release, and is not designed for use within a production environment.

Features, limitations and notes on this release:

- The following ODBC API functions have been added in this release:

  - `SQLBindParameter`

  - `SQLBindCol`

### B.6.13. Changes in Connector/ODBC 5.0.2 (Never released)

Connector/ODBC 5.0.2 was an internal implementation and testing release.

### B.6.14. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)

Features, limitations and notes on this release:

- Connector/ODBC 5.0 is Unicode aware.

- Connector/ODBC is currently limited to basic applications. ADO applications and Microsoft Office are not supported.

- Connector/ODBC must be used with a Driver Manager.

- The following ODBC API functions are implemented:

  - `SQLAllocHandle`

  - `SQLCloseCursor`

  - `SQLColAttribute`

  - `SQLColumns`

  - `SQLConnect`

  - `SQLCopyDesc`

  - `SQLDisconnect`

  - `SQLExecDirect`

  - `SQLExecute`

  - `SQLFetch`

  - `SQLFreeHandle`

  - `SQLFreeStmt`

  - `SQLGetConnectAttr`

  - `SQLGetData`

  - `SQLGetDescField`

  - `SQLGetDescRec`

  - `SQLGetDiagField`

  - `SQLGetDiagRec`

  - `SQLGetEnvAttr`

  - `SQLGetFunctions`

  - `SQLGetStmtAttr`

  - `SQLGetTypeInfo`

  - `SQLNumResultCols`

  - `SQLPrepare`

  - `SQLRowcount`

  - `SQLTables`

  The following ODBC API function are implemented, but not yet support all the available attributes/options:

  - `SQLSetConnectAttr`

  - `SQLSetDescField`

  - `SQLSetDescRec`

  - `SQLSetEnvAttr`

  - `SQLSetStmtAttr`

### B.6.15. Changes in MySQL Connector/ODBC 3.51.23 (Not yet released)

Platform specific notes:

- The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

- There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

- There are no installer packages for Microsoft Windows x64 Edition.

Bugs fixed:

- Connector/ODBC would incorrectly return `SQL_SUCCESS` when checking for distributed transaction support. (Bug#32727)

- When using unixODBC or directly linked applications where the thread level is set to less than 3 (within `odbcinst.ini`), a thread synchronization issue would lead to an application crash. This was because `SQLAllocStmt()` and `SQLFreeStmt()` did not synchronize access to the list of statements associated with a connection. (Bug#32587)

- Cleaning up environment handles in multithread environments could result in a five (or more) second delay. (Bug#32366)

- Renaming an existing DSN entry would create a new entry with the new name without deleting the old entry. (Bug#31165)

- Setting the default database using the `DefaultDatabase` property of an ADO `Connection` object would fail with the error `Provider does not support this property`. The `SQLGetInfo()` returned the wrong value for `SQL_DATABASE_NAME` when no database was selected. (Bug#3780)

### B.6.16. Changes in MySQL Connector/ODBC 3.51.22 (13 November 2007)

Functionality added or changed:

- The workaround for this bug was removed due to the fixes in MySQL Server 5.0.48 and 5.1.21.

  This regression was introduced by Bug#10491

Bugs fixed:

- The `English` locale would be used when formatting floating point values. The `C` locale is now used for these values. (Bug#32294)

- When accessing information about supported operations, the driver would return incorrect information about the support for `UNION`. (Bug#32253)

- Unsigned integer values greater than the maximum value of a signed integer would be handled incorrectly. (Bug#32171)

- The wrong result was returned by `SQLGetData()` when the data was an empty string and a zero-sized buffer was specified. (Bug#30958)

- Added the `FLAG_COLUMN_SIZE_S32` option to limit the reported column size to a signed 32-bit integer. This option is automatically enabled for ADO applications to provide a work around for a bug in ADO. (Bug#13776)

### B.6.17. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)

Bugs fixed:

- When using a rowset/cursor and add a new row with a number of fields, subsequent rows with fewer fields will include the original fields from the previous row in the final `INSERT` statement. (Bug#31246)

- Uninitiated memory could be used when C/ODBC internally calls `SQLGetFunctions()`. (Bug#31055)

- The wrong `SQL_DESC_LITERAL_PREFIX` would be returned for date/time types. (Bug#31009)

- The wrong `COLUMN_SIZE` would be returned by `SQLGetTypeInfo` for the TIME columns (`SQL_TYPE_TIME`). (Bug#30939)

- Clicking outside the character set selection box when configuring a new DSN could cause the wrong character set to be selected. (Bug#30568)

- Not specifying a user in the DSN dialog would raise a warning even though the parameter is optional. (Bug#30499)

- `SQLSetParam()` caused memory allocation errors due to driver manager's mapping of deprecated functions (buffer length -1). (Bug#29871)

- When using ADO, a column marked as `AUTO_INCREMENT` could incorrectly report that the column allowed `NULL` values. This was dur to an issue with `NULLABLE` and `IS_NULLABLE` return values from the call to `SQLColumns()`. (Bug#26108)

- Connector/ODBC would return the wrong the error code when the server disconnects the active connection because the configured `wait_timeout` has expired. Previously it would return `HY000`. Connector/ODBC now correctly returns an `SQLSTATE` of `08S01`. (Bug#3456)

### B.6.18. Changes in MySQL Connector/ODBC 3.51.20 (10 September 2007)

Bugs fixed:

- Using `FLAG_NO_PROMPT` doesn't suppress the dialogs normally handled by `SQLDriverConnect`. (Bug#30840)

- The specified length of the username and authentication parameters to `SQLConnect()` were not being honored. (Bug#30774)

- The wrong column size was returned for binary data. (Bug#30547)

- `SQLGetData()` will now always return `SQL_NO_DATA_FOUND` on second call when no data left, even if requested size is 0. (Bug#30520)

- `SQLGetConnectAttr()` did not reflect the connection state correctly. (Bug#14639)

- Removed checkbox in setup dialog for `FLAG_FIELD_LENGTH` (identified as `Don't Optimize Column Width` within the GUI dialog), which was removed from the driver in 3.51.18.

### B.6.19. Changes in MySQL Connector/ODBC 3.51.19 (10 August 2007)

Connector/ODBC 3.51.19 fixes a specific issue with the 3.51.18 release. For a list of changes in the 3.51.18 release, see Section B.6.20, “Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)”.

Functionality added or changed:

- Because of Bug#10491 in the server, character string results were sometimes incorrectly identified as `SQL_VARBINARY`. Until this server bug is corrected, the driver will identify all variable-length strings as `SQL_VARCHAR`.

### B.6.20. Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)

Platform specific notes:

- The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

- There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

- Binary packages for Sun Solaris are now available as `PKG` packages.

- Binary packages as disk images with installers are now available for Mac OS X.

- A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.

Functionality added or changed:

- When connecting to a specific database when using a DSN, the system tables from the `mysql` database are no longer also available. Previously, tables from the mysql database (catalog) were listed as `SYSTEM TABLES` by `SQLTables()` even when a different catalog was being queried. (Bug#28662)

- Installed for Mac OS X has been re-instated. The installer registers the driver at a system (not user) level and makes it possible to create both user and system DSNs using the Connector/ODBC driver. The installer also fixes the situation where the necessary drivers would bge installed local to the user, not globally. (Bug#15326, Bug#10444)

- Connector/ODBC now supports batched statements. In order to enable cached statement support you must switch enable the batched statement option (`FLAG_MULTI_STATEMENTS`, 67108864, or Allow multiple statements within a GUI configuration). Be aware that batched statements create an increased chance of SQL injection attacks and you must ensure that your application protects against this scenario. (Bug#7445)

- The `SQL_ATTR_ROW_BIND_OFFSET_PTR` is now supported for row bind offsets. (Bug#6741)

- The `TRACE` and `TRACEFILE` DSN options have been removed. Use the ODBC driver manager trace options instead.

Bugs fixed:

- When using a table with multiple `TIMESTAMP` columns, the final `TIMESTAMP` column within the table definition would not be updateable. Note that there is still a limitation in MySQL server regarding multiple `TIMESTAMP` columns . (Bug#9927) (Bug#30081)

- Fixed an issue where the myodbc3i would update the the user ODBC configuration file (`~/Library/ODBC/odbcinst.ini`) instead of the system `/Library/ODBC/odbcinst.ini`. This was caused because myodbc3i was not honouring the `s` and `u` modifiers for the `-d` command line option. (Bug#29964)

- Getting table metadata (through the `SQLColumns()` would fail, returning a bad table definition to calling applications. (Bug#29888)

- `DATETIME` column types would return `FALSE` in place of `SQL_SUCCESS` when requesting the column type information. (Bug#28657)

- The `SQL_COLUMN_TYPE`, `SQL_COLUMN_DISPLAY` and `SQL_COLUMN_PRECISION` values would be returned incorrectly by `SQLColumns()`, `SQLDescribeCol()` and `SQLColAttribute()` when accessing character columns, especially those generated through `concat()`. The lengths returned should now conform to the ODBC specification. The `FLAG_FIELD_LENGTH` option no longer has any affect on the results returned. (Bug#27862)

- Obtaining the length of a column when using a character set for the connection of `utf8` would result in the length being returned incorrectly. (Bug#19345)

- The `SQLColumns()` function could return incorrect information about `TIMESTAMP` columns, indicating that the field was not nullable. (Bug#14414)

- The `SQLColumns()` function could return incorrect information about `AUTO_INCREMENT` columns, indicating that the field was not nullable. (Bug#14407)

- A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.

- There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

- `BIT(n)` columns are now treated as `SQL_BIT` data where `n = 1` and binary data where `n > 1`.

- The wrong value from `SQL_DESC_LITERAL_SUFFIX` was returned for binary fields.

- The `SQL_DATETIME_SUB` column in SQLColumns() was not correctly set for date and time types.

- The value for `SQL_DESC_FIXED_PREC_SCALE` was not returned correctly for values in MySQL 5.0 and later.

- The wrong value for `SQL_DESC_TYPE` was returned for date and time types.

- `SQLConnect()` and `SQLDriverConnect()` were rewritten to eliminate duplicate code and ensure all options were supported using both connection methods. `SQLDriverConnect()` now only requires the setup library to be present when the call requires it.

- The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

- Binary packages as disk images with installers are now available for Mac OS X.

- Binary packages for Sun Solaris are now available as `PKG` packages.

- The wrong value for `DECIMAL_DIGITS` in `SQLColumns()` was reported for `FLOAT` and `DOUBLE` fields, as well as the wrong value for the scale parameter to `SQLDescribeCol()`, and the `SQL_DESC_SCALE` attribute from `SQLColAttribute()`.

- The `SQL_DATA_TYPE` column in `SQLColumns()` results did not report the correct value for date and time types.

### B.6.21. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)

Platform specific notes:

- The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

- There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

- Binary packages for Sun Solaris are now available as `PKG` packages.

- Binary packages as disk images with installers are now available for Mac OS X.

- A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.

Functionality added or changed:

- It is now possible to specify a different character set as part of the DSN or connection string. This must be used instead of the `SET NAMES` statement. You can also configure the character set value from the GUI configuration. (Bug#9498, Bug#6667)

- Fixed calling convention ptr and wrong free in myodbc3i, and fixed the null terminating (was only one, not two) when writing DSN to string.

- Dis-allow NULL ptr for null indicator when calling SQLGetData() if value is null. Now returns SQL_ERROR w/state 22002.

- The setup library has been split into its own RPM package, to allow installing the driver itself with no GUI dependencies.

Bugs fixed:

- `myodbc3i` did not correctly format driver info, which could cause the installation to fail. (Bug#29709)

- Connector/ODBC crashed with Crystal Reports due to a rproblem with `SQLProcedures()`. (Bug#28316)

- Fixed a problem where the GUI would crash when configuring or removing a System or User DSN. (Bug#27315)

- Fixed error handling of out-of-memory and bad connections in catalog functions. This might raise errors in code paths that had ignored them in the past. (Bug#26934)

- For a stored procedure that returns multiple result sets, Connector/ODBC returned only the first result set. (Bug#16817)

- Calling `SQLGetDiagField` with `RecNumber 0, DiagIdentifier NOT 0` returned `SQL_ERROR`, preventing access to diagnostic header fields. (Bug#16224)

- Added a new DSN option (`FLAG_ZERO_DATE_TO_MIN`) to retrieve `XXXX-00-00` dates as the minimum allowed ODBC date (`XXXX-01-01`). Added another option (`FLAG_MIN_DATE_TO_ZERO`) to mirror this but for bound parameters. `FLAG_MIN_DATE_TO_ZERO` only changes `0000-01-01` to `0000-00-00`. (Bug#13766)

- If there was more than one unique key on a table, the correct fields were not used in handling `SQLSetPos()`. (Bug#10563)

- When inserting a large `BLOB` field, Connector/ODBC would crash due to a memory allocation error. (Bug#10562)

- The driver was using `mysql_odbc_escape_string()`, which does not handle the `NO_BACKSLASH_ESCAPES` SQL mode. Now it uses `mysql_real_escape_string()`, which does. (Bug#9498)

- `SQLColumns()` did not handle many of its parameters correctly, which could lead to incorrect results. The table name argument was not handled as a pattern value, and most arguments were not escaped correctly when they contained non-alphanumeric characters. (Bug#8860)

- There are no binary packages for Microsoft Windows x64 Edition.

- There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

- Correctly return error if `SQLBindCol` is called with an invalid column.

- Fixed possible crash if `SQLBindCol()` was not called before `SQLSetPos()`.

- The Mac OS X binary packages are only provided as tarballs, there is no installer.

- The binary packages for Sun Solaris are only provided as tarballs, not the PKG format.

- The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

### B.6.22. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)

Functionality added or changed:

- Connector/ODBC now supports using SSL for communication. This is not yet exposed in the setup GUI, but must be enabled through configuration files or the DSN. (Bug#12918)

Bugs fixed:

- Calls to SQLNativeSql() could cause stack corruption due to an incorrect pointer cast. (Bug#28758)

- Using curors on results sets with multi-column keys could select the wrong value. (Bug#28255)

- `SQLForeignKeys` does not escape `_` and `%` in the table name arguments. (Bug#27723)

- When using stored procedures, making a `SELECT` or second stored procedure call after an initial stored procedure call, the second statement will fail. (Bug#27544)

- SQLTables() did not distinguish tables from views. (Bug#23031)

- Data in `TEXT` columns would fail to be read correctly. (Bug#16917)

- Specifying strings as parameters using the `adBSTR` or `adVarWChar` types, (`SQL_WVARCHAR` and `SQL_WLONGVARCHAR`) would be incorrectly quoted. (Bug#16235)

- SQL_WVARCHAR and SQL_WLONGVARCHAR parameters were not properly quoted and escaped. (Bug#16235)

- Using `BETWEEN` with date values, the wrong results could be returned. (Bug#15773)

- When using the `Don't Cache Results` (option value `1048576`) with Microsoft Access, the connection will fail using DAO/VisualBasic. (Bug#4657)

- Return values from `SQLTables()` may be truncated. (Bugs #22797)

### B.6.23. Changes in MySQL Connector/ODBC 3.51.15 (7 May 2007)

Bugs fixed:

- Connector/ODBC would incorrectly claim to support `SQLProcedureColumns` (by returning true when queried about `SQLPROCEDURECOLUMNS` with `SQLGetFunctions`), but this functionality is not supported. (Bug#27591)

- An incorrect transaction isolation level may not be returned when accessing the connection attributes. (Bug#27589)

- Adding a new DSN with the `myodbc3i` utility under AIX would fail. (Bug#27220)

- When inserting data using bulk statements (through `SQLBulkOperations`), the indicators for all rows within the insert would not updated correctly. (Bug#24306)

- Using `SQLProcedures` does not return the database name within the returned resultset. (Bug#23033)

- The `SQLTransact()` function did not support an empty connection handle. (Bug#21588)

- Using `SQLDriverConnect` instead of `SQLConnect` could cause later operations to fail. (Bug#7912)

- When using blobs and parameter replacement in a statement with `WHERE CURSOR OF`, the SQL is truncated. (Bug#5853)

- Connector/ODBC would return too many foreign key results when accessing tables with similar names. (Bug#4518)

### B.6.24. Changes in MySQL Connector/ODBC 3.51.14 (08 March 2007)

Functionality added or changed:

- Use of `SQL_ATTR_CONNECTION_TIMEOUT` on the server has now been disabled. If you attempt to set this attribute on your connection the `SQL_SUCCESS_WITH_INFO` will be returned, with an error number/string of `HYC00: Optional feature not supported`. (Bug#19823)

- Added auto is null option to Connector/ODBC option parameters. (Bug#10910)

- Added auto-reconnect option to Connector/ODBC option parameters.

- Added support for the `HENV` handlers in `SQLEndTran()`.

Bugs fixed:

- On 64-bit systems, some types would be incorrectly returned. (Bug#26024)

- When retrieving `TIME` columns, C/ODBC would incorrectly interpret the type of the string and could interpret it as a `DATE` type instead. (Bug#25846)

- Connector/ODBC may insert the wrong parameter values when using prepared statements under 64-bit Linux. (Bug#22446)

- Using Connector/ODBC, with `SQLBindCol` and binding the length to the return value from `SQL_LEN_DATA_AT_EXEC` fails with a memory allocation error. (Bug#20547)

- Using `DataAdapter`, Connector/ODBC may continually consume memory when reading the same records within a loop (Windows Server 2003 SP1/SP2 only). (Bug#20459)

- When retrieving data from columns that have been compressed using `COMPRESS()`, the retrieved data would be truncated to 8KB. (Bug#20208)

- The ODBC driver name and version number were incorrectly reported by the driver. (Bug#19740)

- A string format exception would be raised when using iODBC, Connector/ODBC and the embedded MySQL server. (Bug#16535)

- The `SQLDriverConnect()` ODBC method did not work with recent Connector/ODBC releases. (Bug#12393)

### B.6.25. Changes in MySQL Connector/ODBC 3.51.13 (Never released)

Connector/ODBC 3.51.13 was an internal implementation and testing release.

### B.6.26. Changes in MySQL Connector/ODBC 3.51.12 (11 Febrauary 2005)

Functionality added or changed:

- N/A

Bugs fixed:

- Using stored procedures with ADO, where the `CommantType` has been set correctly to `adCmdStoredProc`, calls to stored procedures would fail. (Bug#15635)

- File DSNs could not be saved. (Bug#12019)

- `SQLColumns()` returned no information for tables that had a column named using a reserved word. (Bug#9539)

### B.6.27. Changes in MySQL Connector/ODBC 3.51.11 (28 January 2005)

Bugs fixed:

- `mysql_list_dbcolumns()` and `insert_fields()` were retrieving all rows from a table. Fixed the queries generated by these functions to return no rows. (Bug#8198)

- `SQLGetTypoInfo()` returned `tinyblob` for `SQL_VARBINARY` and nothing for `SQL_BINARY`. Fixed to return `varbinary` for `SQL_VARBINARY`, `binary` for `SQL_BINARY`, and `longblob` for `SQL_LONGVARBINARY`. (Bug#8138)

## B.7. MySQL Connector/NET Change History

### B.7.1. Changes in MySQL Connector/NET 5.2.0 (Not yet released)

Functionality added or changed:

- Added support for `DbDataAdapter` `UpdateBatchSize`. Batching is fully supported including collapsing inserts down into the multi-value form if possible.

- DDEX provider now works under Visual Studio 2008 beta 2.

- Added ClearPool and ClearAllPools features.

Bugs fixed:

- Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug#31433)

- Column name metadata was not using the character set as deifned within the connection string being used. (Bug#31185)

- Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)

- Commands executed from within the state change handeler would fail with a `NULL` exception. (Bug#30964)

- When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug#30116)

- Using compression in the MySQL connection with Connector/NET would be slower than using native (uncompressed) communication. (Bug#27865)

- The `MySqlDbType.Datetime` has been replaced with `MySqlDbType.DateTime`. The old format has been obsoleted. (Bug#26344)

### B.7.2. Changes in MySQL Connector/NET 5.1.4 (20 November 2007)

Bugs fixed:

- Setting the size of a string parameter after the value could cause an exception. (Bug#32094)

- Creation of parameter objects with non-input direction using a constructor would fail. This was cause by some old legacy code preventing their use. (Bug#32093)

- A date string could be returned incorrectly by `MySqlDataTime.ToString()` when the date returned by MySQL was `0000-00-00 00:00:00`. (Bug#32010)

- A syntax error in a set of batch statements could leave the data adapter in a state that appears hung. (Bug#31930)

- Installing over a failed uninstall of a previous version could result in multiple clients being registered in the `machine.config`. This would prevent certain aspects of the MySQL connection within Visual Studio to work properly. (Bug#31731)

- Connector/NET would incorrectly report success when enlisting in a distributed transaction, although distributed transactions are not supported. (Bug#31703)

- Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug#31433)

- Trying to use a connection that was not open could return an ambiguous and misleading error message. (Bug#31262)

- Column name metadata was not using the character set as deifned within the connection string being used. (Bug#31185)

- Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)

- Commands executed from within the state change handeler would fail with a `NULL` exception. (Bug#30964)

- Extracting data through XML functions within a query returns the data as `System.Byte[]`. This was due to Connector/NET incorrectly identifying `BLOB` fields as binary, rather than text. (Bug#30233)

- When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug#30116)

- Column types with only 1-bit (such as `BOOLEAN` and `TINYINT(1)` were not returned as boolean fields. (Bug#27959)

- When accessing certain statements, the command would timeout before the command completed. Because this cannot always be controlled through the individual command timeout options, a `default command timeout` has been added to the connection string options. (Bug#27958)

- The server error code was not updated in the `Data[]` hash, which prevented `DbProviderFactory` users from accessing the server error code. (Bug#27436)

- The `MySqlDbType.Datetime` has been replaced with `MySqlDbType.DateTime`. The old format has been obsoleted. (Bug#26344)

- Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug#13991)

### B.7.3. Changes in MySQL Connector/NET 5.1.3 (21 September 2007)

This is a new Beta development release, fixing recently discovered bugs.

Bugs fixed:

- An incorrect `ConstraintException` could be raised on an `INSERT` when adding rows to a table with a multiple-column unique key index. (Bug#30204)

- A `DATE` field would be updated with a date/time value, causing a `MySqlDataAdapter.Update()` exception. (Bug#30077)

- The Saudi Hijri calendar was not supported. (Bug#29931)

- Calling `SHOW CREATE PROCEDURE` for routines with a hyphen in the catalog name produced a syntax error. (Bug#29526)

- Connecting to a MySQL server earlier than version 4.1 would raise a `NullException`. (Bug#29476)

- The availability of a MySQL server would not be reset when using pooled connections (`pooling=true`). This would lead to the server being reported as unavailable, even if the server become available while the application was still running. (Bug#29409)

- A `FormatException` error would be raised if a parameter had not been found, instead of `Resources.ParameterMustBeDefined`. (Bug#29312)

- An exception would be thrown when using the Manage Role functionality within the web administrator to assign a role to a user. (Bug#29236)

- Using the membership/role providers when `validationKey` or `decryptionKey` parameters are set to `AutoGenerate`, an exception would be raised when accessing the corresponding values. (Bug#29235)

- Certain operations would not check the `UsageAdvisor` setting, causing log messages from the Usage Advisor even when it was disabled. (Bug#29124)

- Using the same connection string multiple times would result in `Database=`dbname`` appearing multiple times in the resulting string. (Bug#29123)

- Visual Studio Plugin: Adding a new query based on a stored procedure that uses the `SELECT` statement would terminate the query/TableAdapter wizard. (Bug#29098)

- Using `TransactionScope` would cause an `InvalidOperationException`. (Bug#28709)

### B.7.4. Changes in MySQL Connector/NET 5.1.2 (18 June 2007)

This is a new Beta development release, fixing recently discovered bugs.

Bugs fixed:

- Log messages would be truncated to 300 bytes. (Bug#28706)

- Creating a user would fail due to the application name being set incorrectly. (Bug#28648)

- Visual Studio Plugin: Adding a new query based on a stored procedure that used a `UPDATE`, `INSERT` or `DELETE` statement would terminate the query/TableAdapter wizard. (Bug#28536)

- Visual Studio Plugin: Query Builder would fail to show `TINYTEXT` columns, and any columns listed after a `TINYTEXT` column correctly. (Bug#28437)

- Accessing the results from a large query when using data compression in the connection would fail to return all the data. (Bug#28204)

- Visual Studio Plugin: Update commands would not be generated correctly when using the TableAdapter wizard. (Bug#26347)

### B.7.5. Changes in MySQL Connector/NET 5.1.1 (23 May 2007)

Bugs fixed:

- Running the statement `SHOW PROCESSLIST` would return columns as byte arrays instead of native columns. (Bug#28448)

- Installation of the Connector/NET on Windows would fail if VisualStudio had not already been installed. (Bug#28260)

- Connector/NET would look for the wrong table when executing `User.IsRole().` (Bug#28251)

- Building a connection string within a tight loop would show slow peformance. (Bug#28167)

- The `UNSIGNED` flag for parameters in a stored procedure would be ignored when using `MySqlCommandBuilder` to obtain the parameter information. (Bug#27679)

- Using `MySQLDataAdapter.FillSchema()` on a stored procedure would raise an exception: `Invalid attempt to access a field before calling Read()`. (Bug#27668)

- `DATETIME` fields from versions of MySQL bgefore 4.1 would be incorrectly parsed, resulting in a exception. (Bug#23342)

- Fixed password property on `MySqlConnectionStringBuilder` to use `PasswordPropertyText` attribute. This causes dots to show instead of actual password text.

### B.7.6. Changes in MySQL Connector/NET 5.1.0 (01 May 2007)

Functionality added or changed:

- Now compiles for .NET CF 2.0.

- Rewrote stored procedure parsing code using a new SQL tokenizer. Really nasty procedures including nested comments are now supported.

- GetSchema will now report objects relative to the currently selected database. What this means is that passing in null as a database restriction will report objects on the currently selected database only.

- Added Membership and Role provider contributed by Sean Wright (thanks!).

### B.7.7. Changes in MySQL Connector/NET 5.0.9 (Not yet released)

Bugs fixed:

- Setting the size of a string parameter after the value could cause an exception. (Bug#32094)

- Creation of parameter objects with non-input direction using a constructor would fail. This was cause by some old legacy code preventing their use. (Bug#32093)

- A date string could be returned incorrectly by `MySqlDataTime.ToString()` when the date returned by MySQL was `0000-00-00 00:00:00`. (Bug#32010)

- A syntax error in a set of batch statements could leave the data adapter in a state that appears hung. (Bug#31930)

- Installing over a failed uninstall of a previous version could result in multiple clients being registered in the `machine.config`. This would prevent certain aspects of the MySQL connection within Visual Studio to work properly. (Bug#31731)

- Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug#31433)

- Column name metadata was not using the character set as deifned within the connection string being used. (Bug#31185)

- Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)

- Commands executed from within the state change handeler would fail with a `NULL` exception. (Bug#30964)

- When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug#30116)

- The server error code was not updated in the `Data[]` hash, which prevented `DbProviderFactory` users from accessing the server error code. (Bug#27436)

- Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug#13991)

### B.7.8. Changes in MySQL Connector/NET 5.0.8 (21 August 2007)

### Note

This version introduces a new installer technology.

Bugs fixed:

- Extracting data through XML functions within a query returns the data as `System.Byte[]`. This was due to Connector/NET incorrectly identifying `BLOB` fields as binary, rather than text. (Bug#30233)

- An incorrect `ConstraintException` could be raised on an `INSERT` when adding rows to a table with a multiple-column unique key index. (Bug#30204)

- A `DATE` field would be updated with a date/time value, causing a `MySqlDataAdapter.Update()` exception. (Bug#30077)

- Fixed bug where Connector/Net was hand building some date time patterns rather than using the patterns provided under CultureInfo. This caused problems with some calendars that do not support the same ranges as Gregorian.. (Bug#29931)

- Calling `SHOW CREATE PROCEDURE` for routines with a hyphen in the catalog name produced a syntax error. (Bug#29526)

- The availability of a MySQL server would not be reset when using pooled connections (`pooling=true`). This would lead to the server being reported as unavailable, even if the server become available while the application was still running. (Bug#29409)

- A `FormatException` error would be raised if a parameter had not been found, instead of `Resources.ParameterMustBeDefined`. (Bug#29312)

- Certain operations would not check the `UsageAdvisor` setting, causing log messages from the Usage Advisor even when it was disabled. (Bug#29124)

- Using the same connection string multiple times would result in `Database=`dbname`` appearing multiple times in the resulting string. (Bug#29123)

- Log messages would be truncated to 300 bytes. (Bug#28706)

- Accessing the results from a large query when using data compression in the connection will fail to return all the data. (Bug#28204)

- Fixed problem where `MySqlConnection.BeginTransaction` checked the drivers status var before checking if the connection was open. The result was that the driver could report an invalid condition on a previously opened connection.

- Fixed problem where we were not closing prepared statement handles when commands are disposed. This could lead to using up all prepared statement handles on the server.

- Fixed the database schema collection so that it works on servers that are not properly respecting the `lower_case_table_names` setting.

- Fixed problem where any attempt to not read all the records returned from a select where each row of the select is greater than 1024 bytes would hang the driver.

- Fixed problem where a command timing out just after it actually finished would cause an exception to be thrown on the command timeout thread which would then be seen as an unhandled exception.

- Fixed some serious issues with command timeout and cancel that could present as exceptions about thread ownership. The issue was that not all queries cancel the same. Some produce resultsets while others don't. ExecuteReader had to be changed to check for this.

### B.7.9. Changes in MySQL Connector/NET 5.0.7 (18 May 2007)

Bugs fixed:

- Running the statement `SHOW PROCESSLIST` would return columns as byte arrays instead of native columns. (Bug#28448)

- Building a connection string within a tight loop would show slow peformance. (Bug#28167)

- Using logging (with the `logging=true` parameter to the connection string) would not generate a log file. (Bug#27765)

- The `UNSIGNED` flag for parameters in a stored procedure would be ignored when using `MySqlCommandBuilder` to obtain the parameter information. (Bug#27679)

- Using `MySQLDataAdapter.FillSchema()` on a stored procedure would raise an exception: `Invalid attempt to access a field before calling Read()`. (Bug#27668)

- If you close an open connection with an active transaction, the transaction is not automatically rolled back. (Bug#27289)

- When cloning an open `MySqlClient.MySqlConnection` with the `Persist Security Info=False` option set, the cloned connection is not usable because the security information has not been cloned. (Bug#27269)

- Enlisting a null transaction would affect the current connection object, such that further enlistment operations to the transaction are not possible. (Bug#26754)

- Attempting to change the the `Connection Protocol` property within a `PropertyGrid` control would raise an exception. (Bug#26472)

- The `characterset` property would not be identified during a connection (also affected Visual Studion Plugin). (Bug#26147, Bug#27240)

- The `CreateFormat` column of the `DataTypes` collection did not contain a format specification for creating a new column type. (Bug#25947)

- `DATETIME` fields from versions of MySQL bgefore 4.1 would be incorrectly parsed, resulting in a exception. (Bug#23342)

### B.7.10. Changes in MySQL Connector/NET 5.0.6 (22 March 2007)

Bugs fixed:

- Publisher listed in "Add/Remove Programs" is not consistent with other MySQL products. (Bug#27253)

- `DESCRIBE ....` SQL statement returns byte arrays rather than data on MySQL versions older than 4.1.15. (Bug#27221)

- `cmd.Parameters.RemoveAt("Id")` will cause an error if the last item is requested. (Bug#27187)

- `MySqlParameterCollection` and parameters added with `Insert` method can not be retrieved later using `ParameterName`. (Bug#27135)

- Exception thrown when using large values in `UInt64` parameters. (Bug#27093)

- MySQL Visual Studio Plugin 1.1.2 does not work with Connector/Net 5.0.5. (Bug#26960)

### B.7.11. Changes in MySQL Connector/NET 5.0.5 (07 March 2007)

Functionality added or changed:

- Reverted behavior that required parameter names to start with the parameter marker. We apologize for this back and forth but we mistakenly changed the behavior to not match what `SqlClient` supports. We now support using either syntax for adding parameters however we also respond exactly like `SqlClient` in that if you ask for the index of a parameter using a syntax different from when you added the parameter, the result will be -1.

- Assembly now properly appears in the Visual Studio 2005 Add/Remove Reference dialog.

- Fixed problem that prevented use of `SchemaOnly` or `SingleRow` command behaviors with stored procedures or prepared statements.

- Added `MySqlParameterCollection.AddWithValue` and marked the `Add(name, value)` method as obsolete.

- Return parameters created with DeriveParameters now have the name `RETURN_VALUE`.

- Fixed problem with parameter name hashing where the hashes were not getting updated when parameters were removed from the collection.

- Fixed problem with calling stored functions when a return parameter was not given.

- Added `Use Procedure Bodies` connection string option to allow calling procedures without using procedure metadata.

Bugs fixed:

- `MySqlConnection.GetSchema` fails with `NullReferenceException` for Foreign Keys. (Bug#26660)

- Connector/NET would fail to install under Windows Vista. (Bug#26430)

- Opening a connection would be slow due to hostname lookup. (Bug#26152)

- Incorrect values/formats would be applied when the `OldSyntax` connection string option was used. (Bug#25950)

- Registry would be incorrectly populated with installation locations. (Bug#25928)

- Times with negative values would be returned incorrectly. (Bug#25912)

- Returned data types of a `DataTypes` collection do not contain the right correctl CLR Datatype. (Bug#25907)

- `GetSchema` and `DataTypes` would throw an exception due to an incorrect table name. (Bug#25906)

- `MySqlConnection` throws an exception when connecting to MySQL v4.1.7. (Bug#25726)

- `SELECT` did not work correctly when using a `WHERE` clause containing a UTF-8 string. (Bug#25651)

- When closing and then re-opening a connection to a database, the character set specification is lost. (Bug#25614)

- Filling a table schema through a stored procedure triggers a runtime error. (Bug#25609)

- `BINARY` and `VARBINARY` columns would be returned as a string, not binary, datatype. (Bug#25605)

- A critical `ConnectionPool` error would result in repeated `System.NullReferenceException`. (Bug#25603)

- The `UpdateRowSource.FirstReturnedRecord` method does not work. (Bug#25569)

- When connecting to a MySQL Server earlier than version 4.1, the connection would hang when reading data. (Bug#25458)

- Using `ExecuteScalar()` with more than one query, where one query fails, will hang the connection. (Bug#25443)

- When a `MySqlConversionException` is raised on a remote object, the client application would receive a `SerializationException` instead. (Bug#24957)

- When connecting to a server, the return code from the connection could be zero, even though the hostname was incorrect. (Bug#24802)

- High CPU utilization would be experienced when there is no idle connection waiting when using pooled connections through `MySqlPool.GetConnection`. (Bug#24373)

- Connector/NET would not compile properly when used with Mono 1.2. (Bug#24263)

- Applications would crash when calling with `CommandType` set to `StoredProcedure`.

### B.7.12. Changes in MySQL Connector/NET 5.0.4 (Not released)

This is a new Beta development release, fixing recently discovered bugs.

### B.7.13. Changes in MySQL Connector/NET 5.0.3 (05 January 2007)

Functionality added or changed:

- Usage Advisor has been implemented. The Usage Advisor checks your queries and will report if you are using the connection inefficiently.

- PerfMon hooks have been added to monitor the stored procedure cache hits and misses.

- The `MySqlCommand` object now supports asynchronous query methods. This is implemented useg the `BeginExecuteNonQuery` and `EndExecuteNonQuery` methods.

- Metadata from storaed procedures and stored function execution are cached.

- The `CommandBuilder.DeriveParameters` function has been updated to the procedure cache.

- The `ViewColumns` `GetSchema` collection has been updated.

- Improved speed and performance by re-architecting certain sections of the code.

- Support for the embedded server and client library have been removed from this release. Support will be added back to a later release.

- The ShapZipLib library has been replaced with the deflate support provided within .NET 2.0.

- SSL support has been updated.

Bugs fixed:

- Additional text added to error message (Bug#25178)

- An exception would be raised, or the process would hang, if `SELECT` privileges on a database were not granted and a stored procedure was used. (Bug#25033)

- When adding parameter objects to a command object, if the parameter direction is set to `ReturnValue` before the parameter is added to the command object then when the command is executed it throws an error. (Bug#25013)

- Using `Driver.IsTooOld()` would return the wrong value. (Bug#24661)

- When using a `DbNull.Value` as the value for a parameter value, and then later setting a specific value type, the command would fail with an exception because the wrong type was implied from the `DbNull.Value`. (Bug#24565)

- Stored procedure executions are not thread safe. (Bug#23905)

- Deleting a connection to a disconnected server when using the Visual Studio Plugin would cause an assertion failure. (Bug#23687)

- Nested transactions (which are unsupported)do not raise an error or warning. (Bug#22400)

### B.7.14. Changes in MySQL Connector/NET 5.0.2 (06 November 2006)

Functionality added or changed:

- An `Ignore Prepare` option has been added to the connection string options. If enabled, prepared statements will be disabled application-wide. The default for this option is true.

- Implemented a stored procedure cache. By default, the connector caches the metadata for the last 25 procedures that are seen. You can change the numbver of procedures that are cacheds by using the `procedure cache` connection string.

- Important change: Due to a number of issues with the use of server-side prepared statements, Connector/NET 5.0.2 has disabled their use by default. The disabling of server-side prepared statements does not affect the operation of the connector in any way.

  To enable server-side prepared statements you must add the following configuration property to your connector string properties:

      ignore prepare=false

  The default value of this property is true.

Bugs fixed:

- One system where IPv6 was enabled, Connector/NET would incorrectly resolve hostnames. (Bug#23758)

- Column names with accented characters were not parsed properly causing malformed column names in result sets. (Bug#23657)

- An exception would be thrown when calling `GetSchemaTable` and `fields` was null. (Bug#23538)

- A `System.FormatException` exception would be raised when invoking a stored procedure with an `ENUM` input parameter. (Bug#23268)

- During installation, an antivirus error message would be raised (indicating a malicious script problem). (Bug#23245)

- Creating a connection through the Server Explorer when using the Visual Studio Plugin would fail. The installer for the Visual Studio Plugin has been updated to ensure that Connector/NET 5.0.2 must be installed. (Bug#23071)

- Using Windows Vista (RC2) as a non-privileged user would raise a `Registry key 'Global' access denied`. (Bug#22882)

- Within Mono, using the `PreparedStatement` interface could result in an error due to a `BitArray` copying error. (Bug#18186)

- Connector/NET did not work as a data source for the `SqlDataSource` object used by ASP.NET 2.0. (Bug#16126)

### B.7.15. Changes in MySQL Connector/NET 5.0.1 (01 October 2006)

Bugs fixed:

- Connector/NET on a Tukish operating system, may fail to execute certain SQL statements correctly. (Bug#22452)

- Starting a transaction on a connection created by `MySql.Data.MySqlClient.MySqlClientFactory`, using `BeginTransaction` without specifying an isolation level, causes the SQL statement to fail with a syntax error. (Bug#22042)

- The `MySqlexception` class is now derived from the `DbException` class. (Bug#21874)

- The `#` would not be accepted within column/table names, even though it was valid. (Bug#21521)

- You can now install the Connector/NET MSI package from the command line using the `/passive`, `/quiet`, `/q` options. (Bug#19994)

- Submitting an empty string to a command object through `prepare` raises an `System.IndexOutOfRangeException`, rather than a Connector/Net exception. (Bug#18391)

- Using `ExecuteScalar` with a datetime field, where the value of the field is "0000-00-00 00:00:00", a `MySqlConversionException` exception would be raised. (Bug#11991)

- An `MySql.Data.Types.MySqlConversionException` would be raised when trying to update a row that contained a date field, where the date field contained a zero value (0000-00-00 00:00:00). (Bug#9619)

- Executing multiple queries as part of a transaction returns `There is already an openDataReader associated with this Connection which must be closed first`. (Bug#7248)

- Incorrect field/data lengths could be returned for `VARCHAR` UTF8 columns. Bug (#14592)

### B.7.16. Changes in MySQL Connector/NET 5.0.0 (08 August 2006)

Functionality added or changed:

- Replaced use of ICSharpCode with .NET 2.0 internal deflate support.

- Refactored test suite to test all protocols in a single pass.

- Added usage advisor warnings for requesting column values by the wrong type.

- Reimplemented PacketReader/PacketWriter support into `MySqlStream` class.

- Reworked connection string classes to be simpler and faster.

- Added procedure metadata caching.

- Added internal implemention of SHA1 so we don't have to distribute the OpenNetCF on mobile devices.

- Implemented `MySqlClientFactory` class.

- Added perfmon hooks for stored procedure cache hits and misses.

- Implemented classes and interfaces for ADO.Net 2.0 support.

- Added Async query methods.

- Implemented Usage Advisor.

- Completely refactored how column values are handled to avoid boxing in some cases.

- Implemented `MySqlConnectionBuilder` class.

Bugs fixed:

- CommandText: Question mark in comment line is being parsed as a parameter. (Bug#6214)

### B.7.17. Changes in MySQL Connector/NET 1.0.11 (Not yet released)

Bugs fixed:

- Setting the size of a string parameter after the value could cause an exception. (Bug#32094)

- Creation of parameter objects with non-input direction using a constructor would fail. This was cause by some old legacy code preventing their use. (Bug#32093)

- Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)

- Commands executed from within the state change handeler would fail with a `NULL` exception. (Bug#30964)

- Extracting data through XML functions within a query returns the data as `System.Byte[]`. This was due to Connector/NET incorrectly identifying `BLOB` fields as binary, rather than text. (Bug#30233)

- Using compression in the MySQL connection with Connector/NET would be slower than using native (uncompressed) communication. (Bug#27865)

- Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug#13991)

### B.7.18. Changes in MySQL Connector/NET 1.0.10 (24 August 2007)

Bugs fixed:

- An incorrect `ConstraintException` could be raised on an `INSERT` when adding rows to a table with a multiple-column unique key index. (Bug#30204)

- The availability of a MySQL server would not be reset when using pooled connections (`pooling=true`). This would lead to the server being reported as unavailable, even if the server become available while the application was still running. (Bug#29409)

- Publisher listed in "Add/Remove Programs" is not consistent with other MySQL products. (Bug#27253)

- `MySqlParameterCollection` and parameters added with `Insert` method can not be retrieved later using `ParameterName`. (Bug#27135)

- `BINARY` and `VARBINARY` columns would be returned as a string, not binary, datatype. (Bug#25605)

- A critical `ConnectionPool` error would result in repeated `System.NullReferenceException`. (Bug#25603)

- When a `MySqlConversionException` is raised on a remote object, the client application would receive a `SerializationException` instead. (Bug#24957)

- High CPU utilization would be experienced when there is no idle connection waiting when using pooled connections through `MySqlPool.GetConnection`. (Bug#24373)

### B.7.19. Changes in MySQL Connector/NET 1.0.9 (02 February 2007)

Functionality added or changed:

- The ICSharpCode ZipLib is no longer used by the Connector, and is no longer distributed with it.

- Important change: Binaries for .NET 1.0 are no longer supplied with this release. If you need support for .NET 1.0, you must build from source.

- Improved `CommandBuilder.DeriveParameters` to first try and use the procedure cache before querying for the stored procedure metadata. Return parameters created with `DeriveParameters` now have the name `RETURN_VALUE`.

- An `Ignore Prepare` option has been added to the connection string options. If enabled, prepared statements will be disabled application-wide. The default for this option is true.

- Implemented a stored procedure cache. By default, the connector caches the metadata for the last 25 procedures that are seen. You can change the numbver of procedures that are cacheds by using the `procedure cache` connection string.

- Important change: Due to a number of issues with the use of server-side prepared statements, Connector/NET 5.0.2 has disabled their use by default. The disabling of server-side prepared statements does not affect the operation of the connector in any way.

  To enable server-side prepared statements you must add the following configuration property to your connector string properties:

      ignore prepare=false

  The default value of this property is true.

Bugs fixed:

- Times with negative values would be returned incorrectly. (Bug#25912)

- `MySqlConnection` throws a `NullReferenceException` and `ArgumentNullException` when connecting to MySQL v4.1.7. (Bug#25726)

- `SELECT` did not work correctly when using a `WHERE` clause containing a UTF-8 string. (Bug#25651)

- When closing and then re-opening a connection to a database, the character set specification is lost. (Bug#25614)

- Trying to fill a table schema through a stored procedure triggers a runtime error. (Bug#25609)

- Using `ExecuteScalar()` with more than one query, where one query fails, will hang the connection. (Bug#25443)

- Additional text added to error message. (Bug#25178)

- When adding parameter objects to a command object, if the parameter direction is set to `ReturnValue` before the parameter is added to the command object then when the command is executed it throws an error. (Bug#25013)

- When connecting to a server, the return code from the connection could be zero, even though the hostname was incorrect. (Bug#24802)

- Using `Driver.IsTooOld()` would return the wrong value. (Bug#24661)

- When using a `DbNull.Value` as the value for a parameter value, and then later setting a specific value type, the command would fail with an exception because the wrong type was implied from the `DbNull.Value`. (Bug#24565)

- Stored procedure executions are not thread safe. (Bug#23905)

- The `CommandBuilder` would mistakenly add insert parameters for a table column with auto incrementation enabled. (Bug#23862)

- One system where IPv6 was enabled, Connector/NET would incorrectly resolve hostnames. (Bug#23758)

- Nested transactions do not raise an error or warning. (Bug#22400)

- An `System.OverflowException` would be raised when accessing a varchar field over 255 bytes. Bug (#23749)

- Within Mono, using the `PreparedStatement` interface could result in an error due to a `BitArray` copying error. (Bug 18186)

### B.7.20. Changes in MySQL Connector/NET 1.0.8 (20 October 2006)

Functionality added or changed:

- Stored procedures are now cached.

- The method for retrieving stored procedured metadata has been changed so that users without `SELECT` privileges on the `mysql.proc` table can use a stored procedure.

Bugs fixed:

- Connector/NET on a Tukish operating system, may fail to execute certain SQL statements correctly. (Bug#22452)

- The `#` would not be accepted within column/table names, even though it was valid. (Bug#21521)

- Calling `Close` on a connection after calling a stored procedure would trigger a `NullReferenceException`. (Bug#20581)

- You can now install the Connector/NET MSI package from the command line using the `/passive`, `/quiet`, `/q` options. (Bug#19994)

- The DiscoverParameters function would fail when a stored procedure used a `NUMERIC` parameter type. (Bug#19515)

- When running a query that included a date comparison, a DateReader error would be raised. (Bug#19481)

- `IDataRecord.GetString` would raise `NullPointerException` for null values in returned rows. Method now throws `SqlNullValueException`. (Bug#19294)

- Parameter substitution in queries where the order of parameters and table fields did not match would substitute incorrect values. (Bug#19261)

- Submitting an empty string to a command object through `prepare` raises an `System.IndexOutOfRangeException`, rather than a Connector/Net exception. (Bug#18391)

- An exception would be raised when using an output parameter to a `System.String` value. (Bug#17814)

- CHAR type added to MySqlDbType. (Bug#17749)

- A `SELECT` query on a table with a date with a value of `'0000-00-00'` would hang the application. (Bug#17736)

- The CommandBuilder ignored Unsigned flag at Parameter creation. (Bug#17375)

- When working with multiple threads, character set initialization would generate errors. (Bug#17106)

- When using an unsigned 64-bit integer in a stored procedure, the unsigned bit would be lost stored. (Bug#16934)

- `DataReader` would show the value of the previous row (or last row with non-null data) if the current row contained a `datetime` field with a null value. (Bug#16884)

- Unsigned data types were not properly supported. (Bug#16788)

- The connection string parser did not allow single or double quotes in the password. (Bug#16659)

- The `MySqlDateTime` class did not contain constructors. (Bug#15112)

- Called `MySqlCommandBuilder.DeriveParameters` for a stored procedure that has no paramers would cause an application crash. (Bug#15077)

- Using `ExecuteScalar` with a datetime field, where the value of the field is "0000-00-00 00:00:00", a `MySqlConversionException` exception would be raised. (Bug#11991)

- An `MySql.Data.Types.MySqlConversionException` would be raised when trying to update a row that contained a date field, where the date field contained a zero value (0000-00-00 00:00:00). (Bug#9619)

- When using `MySqlDataAdapter`, connections to a MySQL server may remain open and active, even though the use of the connection has been completed and the data received. (Bug#8131)

- Executing multiple queries as part of a transaction returns `There is already an openDataReader associated with this Connection which must be closed first`. (Bug#7248)

- Incorrect field/data lengths could be returned for `VARCHAR` UTF8 columns. Bug (#14592)

### B.7.21. Changes in MySQL Connector/NET 1.0.7 (21 November 2005)

Bugs fixed:

- Unsigned `tinyint` (NET byte) would lead to and incorrectly determined parameter type from the parameter value. (Bug#18570)

- A `#42000Query was empty` exception occurred when executing a query built with `MySqlCommandBuilder`, if the query string ended with a semicolon. (Bug#14631)

- The parameter collection object's `Add()` method added parameters to the list without first checking to see whether they already existed. Now it updates the value of the existing parameter object if it exists. (Bug#13927)

- Added support for the `cp932` character set. (Bug#13806)

- Calling a stored procedure where a parameter contained special characters (such as `'@'`) would produce an exception. Note that `ANSI_QUOTES` had to be enabled to make this possible. (Bug#13753)

- The `Ping()` method did not update the `State` property of the `Connection` object. (Bug#13658)

- Implemented the `MySqlCommandBuilder.DeriveParameters` method that is used to discover the parameters for a stored procedure. (Bug#13632)

- A statement that contained multiple references to the same parameter could not be prepared. (Bug#13541)

### B.7.22. Changes in MySQL Connector/NET 1.0.6 (03 October 2005)

Bugs fixed:

- Connector/NET 1.0.5 could not connect on Mono. (Bug#13345)

- Serializing a parameter failed if the first value passed in was `NULL`. (Bug#13276)

- Field names that contained the following characters caused errors: `()%<>/` (Bug#13036)

- The `nant` build sequence had problems. (Bug#12978)

- The Connector/NET 1.0.5 installer would not install alongside Connector/NET 1.0.4. (Bug#12835)

### B.7.23. Changes in MySQL Connector/NET 1.0.5 (29 August 2005)

Bugs fixed:

- Connector/NET could not connect to MySQL 4.1.14. (Bug#12771)

- With multiple hosts in the connection string, Connector/NET would not connect to the last host in the list. (Bug#12628)

- The `ConnectionString` property could not be set when a `MySqlConnection` object was added with the designer. (Bug#12551, Bug#8724)

- The `cp1250` character set was not supported. (Bug#11621)

- A call to a stored procedure caused an exception if the stored procedure had no parameters. (Bug#11542)

- Certain malformed queries would trigger a `Connection must be valid and open` error message. (Bug#11490)

- Trying to use a stored procedure when `Connection.Database` was not populated generated an exception. (Bug#11450)

- Connector/NET interpreted the new decimal data type as a byte array. (Bug#11294)

- Added support to call a stored function from Connector/NET. (Bug#10644)

- Connection could fail when .NET thread pool had no available worker threads. (Bug#10637)

- Calling `MySqlConnection.clone` when a connection string had not yet been set on the original connection would generate an error. (Bug#10281)

- Decimal parameters caused syntax errors. (Bug#10152, Bug#11550, Bug#10486)

- Parameters were not recognized when they were separated by linefeeds. (Bug#9722)

- The `MySqlCommandBuilder` class could not handle queries that referenced tables in a database other than the default database. (Bug#8382)

- Trying to read a `TIMESTAMP` column generated an exception. (Bug#7951)

- Connector/NET could not work properly with certain regional settings. (WL#8228)

### B.7.24. Changes in MySQL Connector/NET 1.0.4 (20 January 2005)

Bugs fixed:

- `MySqlReader.GetInt32` throws exception if column is unsigned. (Bug#7755)

- Quote character \222 not quoted in `EscapeString`. (Bug#7724)

- GetBytes is working no more. (Bug#7704)

- `MySqlDataReader.GetString(index)` returns non-Null value when field is `Null`. (Bug#7612)

- Clone method bug in `MySqlCommand`. (Bug#7478)

- Problem with Multiple resultsets. (Bug#7436)

- `MySqlAdapter.Fill` method throws error message `Non-negative number required`. (Bug#7345)

- `MySqlCommand.Connection` returns an IDbConnection. (Bug#7258)

- Calling prepare causing exception. (Bug#7243)

- Fixed problem with shared memory connections.

- Added or filled out several more topics in the API reference documentation.

- Fixed another small problem with prepared statements.

- Fixed problem that causes named pipes to not work with some blob functionality.

### B.7.25. Changes in MySQL Connector/NET 1.0.3 (12 October 2004)

Bugs fixed:

- Invalid query string when using inout parameters (Bug#7133)

- Inserting `DateTime` causes `System.InvalidCastException` to be thrown. (Bug#7132)

- `MySqlDateTime` in Datatables sorting by Text, not Date. (Bug#7032)

- Exception stack trace lost when re-throwing exceptions. (Bug#6983)

- Errors in parsing stored procedure parameters. (Bug#6902)

- InvalidCast when using `DATE_ADD`-function. (Bug#6879)

- Int64 Support in `MySqlCommand` Parameters. (Bug#6863)

- Test suite fails with MySQL 4.0 because of case sensitivity of table names. (Bug#6831)

- `MySqlDataReader.GetChar(int i)` throws `IndexOutOfRange` exception. (Bug#6770)

- Integer "out" parameter from stored procedure returned as string. (Bug#6668)

- An Open Connection has been Closed by the Host System. (Bug#6634)

- Fixed Invalid character set index: 200. (Bug#6547)

- Connections now do not have to give a database on the connection string.

- Installer now includes options to install into GAC and create Start Menu items.

- Fixed major problem with detecting null values when using prepared statements.

- Fixed problem where multiple resultsets having different numbers of columns would cause a problem.

- Added `ServerThread` property to `MySqlConnection` to expose server thread id.

- Added Ping method to `MySqlConnection`.

- Changed the name of the test suite to `MySql.Data.Tests.dll`.

- Now `SHOW COLLATION` is used upon connection to retrieve the full list of charset ids.

- Made MySQL the default named pipe name.

### B.7.26. Changes in MySQL Connector/NET 1.0.2 (15 November 2004)

Bugs fixed:

- Fixed Objects not being disposed (Bug#6649)

- Fixed Charset-map for UCS-2 (Bug#6541)

- Fixed Zero date "0000-00-00" is returned wrong when filling Dataset (Bug#6429)

- Fixed double type handling in MySqlParameter(string parameterName, object value) (Bug#6428)

- Fixed Installation directory ignored using custom installation (Bug#6329)

- Fixed #HY000 Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ (Bug#6322)

- Added the TableEditor CS and VB sample

- Added charset connection string option

- Fixed problem with MySqlBinary where string values could not be used to update extended text columns

- Provider is now using character set specified by server as default

- Updated the installer to include the new samples

- Fixed problem where setting command text leaves the command in a prepared state

- Fixed Long inserts take very long time (Bu #5453)

- Fixed problem where calling stored procedures might cause an "Illegal mix of collations" problem.

### B.7.27. Changes in MySQL Connector/NET 1.0.1 (27 October 2004)

Bugs fixed:

- Fixed IndexOutOfBounds when reading BLOB with DataReader with GetString(index) (Bug#6230)

- Fixed GetBoolean returns wrong values (Bug#6227)

- Fixed Method TokenizeSql() uses only a limited set of valid characters for parameters (Bug#6217)

- Fixed NET Connector source missing resx files (Bug#6216)

- Fixed System.OverflowException when using YEAR datatype (Bug#6036)

- Fixed MySqlDateTime sets IsZero property on all subseq.records after first zero found (Bug#6006)

- Fixed serializing of floating point parameters (double, numeric, single, decimal) (Bug#5900)

- Fixed missing Reference in DbType setter (Bug#5897)

- Fixed Parsing the ';' char (Bug#5876)

- Fixed DBNull Values causing problems with retrieving/updating queries. (Bug#5798)

- IsNullable error (Bug#5796)

- Fixed problem where MySqlParameterCollection.Add() would throw unclear exception when given a null value (Bug#5621)

- Fixed construtor initialize problems in MySqlCommand() (Bug#5613)

- Fixed Yet Another "object reference not set to an instance of an object" (Bug#5496)

- Fixed Can't display Chinese correctly (Bug#5288)

- Fixed MySqlDataReader and 'show tables from ...' behavior (Bug#5256)

- Fixed problem in PacketReader where it could try to allocate the wrong buffer size in EnsureCapacity

- Fixed problem where using old syntax while using the interfaces caused problems

- Fixed Bug#5458 Calling GetChars on a longtext column throws an exception

- Added test case for resetting the command text on a prepared command

- Fixed Bug#5388 DataReader reports all rows as NULL if one row is NULL

- Fixed problem where connection lifetime on the connect string was not being respected

- Fixed Bug#5602 Possible bug in MySqlParameter(string, object) constructor

- Field buffers being reused to decrease memory allocations and increase speed

- Fixed Bug#5392 MySqlCommand sees "?" as parameters in string literals

- Added Aggregate function test (wasn't really a bug)

- Using PacketWriter instead of Packet for writing to streams

- Implemented SequentialAccess

- Fixed problem with ConnectionInternal where a key might be added more than once

- Fixed Russian character support as well

- Fixed Bug#5474 cannot run a stored procedure populating mysqlcommand.parameters

- Fixed problem where connector was not issuing a CMD_QUIT before closing the socket

- Fixed problem where Min Pool Size was not being respected

- Refactored compression code into CompressedStream to clean up NativeDriver

- CP1252 is now used for Latin1 only when the server is 4.1.2 and later

- Fixed Bug#5469 Setting DbType throws NullReferenceException

- Virtualized driver subsystem so future releases could easily support client or embedded server support

### B.7.28. Changes in MySQL Connector/NET 1.0.0 (01 September 2004)

Bugs fixed:

- Thai encoding not correctly supported. (Bug#3889)

- Bumped version number to 1.0.0 for beta 1 release.

- Removed all of the XML comment warnings.

- Added `COPYING.rtf` file for use in installer.

- Updated many of the test cases.

- Fixed problem with using compression.

- Removed some last references to ByteFX.

### B.7.29. Changes in MySQL Connector/NET Version 0.9.0 (30 August 2004)

- Added test fixture for prepared statements.

- All type classes now implement a `SerializeBinary` method for sending their data to a `PacketWriter`.

- Added `PacketWriter` class that will enable future low-memory large object handling.

- Fixed many small bugs in running prepared statements and stored procedures.

- Changed command so that an exception will not be thrown in executing a stored procedure with parameters in old syntax mode.

- `SingleRow` behavior now working right even with limit.

- `GetBytes` now only works on binary columns.

- Logger now truncates long sql commands so blob columns don't blow out our log.

- host and database now have a default value of "" unless otherwise set.

- Connection Timeout seems to be ignored. (Bug#5214)

- Added test case for bug# 5051: GetSchema not working correctly.

- Fixed problem where `GetSchema` would return false for `IsUnique` when the column is key.

- `MySqlDataReader GetXXX` methods now using the field level `MySqlValue` object and not performing conversions.

- `DataReader` returning `NULL` for time column. (Bug#5097)

- Added test case for `LOAD DATA LOCAL INFILE`.

- Added replacetext custom nant task.

- Added `CommandBuilderTest` fixture.

- Added Last One Wins feature to `CommandBuilder`.

- Fixed persist security info case problem.

- Fixed `GetBool` so that 1, true, "true", and "yes" all count as true.

- Make parameter mark configurable.

- Added the "old syntax" connection string parameter to allow use of @ parameter marker.

- `MySqlCommandBuilder`. (Bug#4658)

- `ByteFX.MySqlClient` caches passwords if `Persist Security Info` is false. (Bug#4864)

- Updated license banner in all source files to include FLOSS exception.

- Added new .Types namespace and implementations for most current MySql types.

- Added `MySqlField41` as a subclass of `MySqlField`.

- Changed many classes to now use the new .Types types.

- Changed type `enum int` to `Int32`, `short` to `Int16`, and `bigint` to `Int64`.

- Added dummy types `UInt16`, `UInt32`, and `UInt64` to allow an unsigned parameter to be made.

- Connections are now reset when they are pulled from the connection pool.

- Refactored auth code in driver so it can be used for both auth and reset.

- Added `UserReset` test in `PoolingTests.cs`.

- Connections are now reset using `COM_CHANGE_USER` when pulled from the pool.

- Implemented `SingleResultSet` behavior.

- Implemented support of unicode.

- Added char set mappings for utf-8 and ucs-2.

- Time fields overflow using bytefx .net mysql driver (Bug#4520)

- Modified time test in data type test fixture to check for time spans where hours > 24.

- Wrong string with backslash escaping in `ByteFx.Data.MySqlClient.MySqlParameter`. (Bug#4505)

- Added code to Parameter test case TestQuoting to test for backslashes.

- `MySqlCommandBuilder` fails with multi-word column names. (Bug#4486)

- Fixed bug in `TokenizeSql` where underscore would terminate character capture in parameter name.

- Added test case for spaces in column names.

- `MySqlDataReader.GetBytes` don't works correctly. (Bug#4324)

- Added `GetBytes()` test case to `DataReader` test fixture.

- Now reading all server variables in `InternalConnection.Configure` into `Hashtable`.

- Now using `string[]` for index map in `CharSetMap`.

- Added CRInSQL test case for carriage returns in SQL.

- Setting maxPacketSize to default value in `Driver.ctor`.

- Setting `MySqlDbType` on a parameter doesn't set generic type. (Bug#4442)

- Removed obsolete data types `Long` and `LongLong`.

- Overflow exception thrown when using "use pipe" on connection string. (Bug#4071)

- Changed "use pipe" keyword to "pipe name" or just "pipe".

- Allow reading multiple resultsets from a single query.

- Added flags attribute to `ServerStatusFlags` enum.

- Changed name of `ServerStatus` enum to `ServerStatusFlags`.

- Inserted data row doesn't update properly.

- Error processing show create table. (Bug#4074)

- Change `Packet.ReadLenInteger` to `ReadPackedLong` and added `packet.ReadPackedInteger` that always reads integers packed with 2,3,4.

- Added `syntax.cs` test fixture to test various SQL syntax bugs.

- Improper handling of time values. Now time value of 00:00:00 is not treated as null. (Bug#4149)

- Moved all test suite files into `TestSuite` folder.

- Fixed bug where null column would move the result packet pointer backward.

- Added new nant build script.

- Clear tablename so it will be regen'ed properly during the next `GenerateSchema`. (Bug#3917)

- `GetValues` was always returning zero and was also always trying to copy all fields rather than respecting the size of the array passed in. (Bug#3915)

- Implemented shared memory access protocol.

- Implemented prepared statements for MySQL 4.1.

- Implemented stored procedures for MySQL 5.0.

- Renamed `MySqlInternalConnection` to `InternalConnection`.

- SQL is now parsed as chars, fixes problems with other languages.

- Added logging and allow batch connection string options.

- `RowUpdating` event not set when setting the `DataAdapter` property. (Bug#3888)

- Fixed bug in char set mapping.

- Implemented 4.1 authentication.

- Improved open/auth code in driver.

- Improved how connection bits are set during connection.

- Database name is now passed to server during initial handshake.

- Changed namespace for client to `MySql.Data.MySqlClient`.

- Changed assembly name of client to `MySql.Data.dll`.

- Changed license text in all source files to GPL.

- Added the `MySqlClient.build` Nant file.

- Removed the mono batch files.

- Moved some of the unused files into notused folder so nant build file can use wildcards.

- Implemented shared memory access.

- Major revamp in code structure.

- Prepared statements now working for MySql 4.1.1 and later.

- Finished implementing auth for 4.0, 4.1.0, and 4.1.1.

- Changed namespace from `MySQL.Data.MySQLClient` back to `MySql.Data.MySqlClient`.

- Fixed bug in `CharSetMapping` where it was trying to use text names as ints.

- Changed namespace to `MySQL.Data.MySQLClient`.

- Integrated auth changes from UC2004.

- Fixed bug where calling any of the GetXXX methods on a datareader before or after reading data would not throw the appropriate exception (thanks Luca Morelli).

- Added `TimeSpan` code in parameter.cs to properly serialize a timespan object to mysql time format (thanks Gianluca Colombo).

- Added `TimeStamp` to parameter serialization code. Prevented `DataAdatper` updates from working right (thanks Michael King).

- Fixed a misspelling in `MySqlHelper.cs` (thanks Patrick Kristiansen).

### B.7.30. Changes in MySQL Connector/NET Version 0.76

- Driver now using charset number given in handshake to create encoding.

- Changed command editor to point to `MySqlClient.Design`.

- Fixed bug in `Version.isAtLeast`.

- Changed `DBConnectionString` to support changes done to `MySqlConnectionString`.

- Removed `SqlCommandEditor` and `DataAdapterPreviewDialog`.

- Using new long return values in many places.

- Integrated new `CompressedStream` class.

- Changed `ConnectionString` and added attributes to allow it to be used in `MySqlClient.Design`.

- Changed `packet.cs` to support newer lengths in `ReadLenInteger`.

- Changed other classes to use new properties and fields of `MySqlConnectionString`.

- `ConnectionInternal` is now using PING to see whether the server is alive.

- Moved toolbox bitmaps into resource folder.

- Changed `field.cs` to allow values to come directly from row buffer.

- Changed to use the new driver.Send syntax.

- Using a new packet queueing system.

- Started work handling the "broken" compression packet handling.

- Fixed bug in `StreamCreator` where failure to connect to a host would continue to loop infinitly (thanks Kevin Casella).

- Improved connectstring handling.

- Moved designers into Pro product.

- Removed some old commented out code from `command.cs`.

- Fixed a problem with compression.

- Fixed connection object where an exception throw prior to the connection opening would not leave the connection in the connecting state (thanks Chris Cline).

- Added GUID support.

- Fixed sequence out of order bug (thanks Mark Reay).

### B.7.31. Changes in MySQL Connector/NET Version 0.75

- Enum values now supported as parameter values (thanks Philipp Sumi).

- Year datatype now supported.

- Fixed compression.

- Fixed bug where a parameter with a `TimeSpan` as the value would not serialize properly.

- Fixed bug where default constructor would not set default connection string values.

- Added some XML comments to some members.

- Work to fix/improve compression handling.

- Improved `ConnectionString` handling so that it better matches the standard set by `SqlClient`.

- A `MySqlException` is now thrown if a username is not included in the connection string.

- Localhost is now used as the default if not specified on the connection string.

- An exception is now thrown if an attempt is made to set the connection string while the connection is open.

- Small changes to `ConnectionString` docs.

- Removed `MultiHostStream` and `MySqlStream`. Replaced it with `Common/StreamCreator`.

- Added support for Use Pipe connection string value.

- Added Platform class for easier access to platform utility functions.

- Fixed small pooling bug where new connection was not getting created after `IsAlive` fails.

- Added `Platform.cs` and `StreamCreator.cs`.

- Fixed `Field.cs` to properly handle 4.1 style timestamps.

- Changed `Common.Version` to `Common.DBVersion` to avoid name conflict.

- Fixed `field.cs` so that text columns return the right field type.

- Added `MySqlError` class to provide some reference for error codes (thanks Geert Veenstra).

### B.7.32. Changes in MySQL Connector/NET Version 0.74

- Added Unix socket support (thanks Mohammad DAMT).

- Only calling `Thread.Sleep` when no data is available.

- Improved escaping of quote characters in parameter data.

- Removed misleading comments from `parameter.cs`.

- Fixed pooling bug.

- Fixed `ConnectionString` editor dialog (thanks marco p (pomarc)).

- `UserId` now supported in connection strings (thanks Jeff Neeley).

- Attempting to create a parameter that is not input throws an exception (thanks Ryan Gregg).

- Added much documentation.

- Checked in new `MultiHostStream` capability. Big thanks to Dan Guisinger for this. he originally submitted the code and idea of supporting multiple machines on the connect string.

- Added a lot of documentation.

- Fixed speed issue with 0.73.

- Changed to Thread.Sleep(0) in MySqlDataStream to help optimize the case where it doesn't need to wait (thanks Todd German).

- Prepopulating the idlepools to `MinPoolSize`.

- Fixed `MySqlPool` deadlock condition as well as stupid bug where CreateNewPooledConnection was not ever adding new connections to the pool. Also fixed `MySqlStream.ReadBytes` and `ReadByte` to not use `TicksPerSecond` which does not appear to always be right. (thanks Matthew J. Peddlesden)

- Fix for precision and scale (thanks Matthew J. Peddlesden).

- Added `Thread.Sleep(1)` to stream reading methods to be more cpu friendly (thanks Sean McGinnis).

- Fixed problem where `ExecuteReader` would sometime return null (thanks Lloyd Dupont).

- Fixed major bug with null field handling (thanks Naucki).

- Enclosed queries for `max_allowed_packet` and `characterset` inside try catch (and set defaults).

- Fixed problem where socket was not getting closed properly (thanks Steve!).

- Fixed problem where `ExecuteNonQuery` was not always returning the right value.

- Fixed `InternalConnection` to not use `@@session.max_allowed_packet` but use `@@max_allowed_packet`. (Thanks Miguel)

- Added many new XML doc lines.

- Fixed sql parsing to not send empty queries (thanks Rory).

- Fixed problem where the reader was not unpeeking the packet on close.

- Fixed problem where user variables were not being handled (thanks Sami Vaaraniemi).

- Fixed loop checking in the MySqlPool (thanks Steve M. Brown)

- Fixed `ParameterCollection.Add` method to match `SqlClient` (thanks Joshua Mouch).

- Fixed `ConnectionString` parsing to handle no and yes for boolean and not lowercase values (thanks Naucki).

- Added `InternalConnection` class, changes to pooling.

- Implemented Persist Security Info.

- Added `security.cs` and `version.cs` to project

- Fixed `DateTime` handling in `Parameter.cs` (thanks Burkhard Perkens-Golomb).

- Fixed parameter serialization where some types would throw a cast exception.

- Fixed `DataReader` to convert all returned values to prevent casting errors (thanks Keith Murray).

- Added code to `Command.ExecuteReader` to return null if the initial SQL statement throws an exception (thanks Burkhard Perkens-Golomb).

- Fixed `ExecuteScalar` bug introduced with restructure.

- Restructure to allow for `LOCAL DATA INFILE` and better sequencing of packets.

- Fixed several bugs related to restructure.

- Early work done to support more secure passwords in Mysql 4.1. Old passwords in 4.1 not supported yet.

- Parameters appearing after system parameters are now handled correctly (Adam M. (adammil)).

- Strings can now be assigned directly to blob fields (Adam M.).

- Fixed float parameters (thanks Pent).

- Improved Parameter constructor and `ParameterCollection.Add` methods to better match SqlClient (thanks Joshua Mouch).

- Corrected `Connection.CreateCommand` to return a `MySqlCommand` type.

- Fixed connection string designer dialog box problem (thanks Abraham Guyt).

- Fixed problem with sending commands not always reading the response packet (thanks Joshua Mouch).

- Fixed parameter serialization where some blobs types were not being handled (thanks Sean McGinnis).

- Removed spurious `MessageBox.show` from `DataReader` code (thanks Joshua Mouch).

- Fixed a nasty bug in the split sql code (thanks everyone!).

### B.7.33. Changes in MySQL Connector/NET Version 0.71

- Fixed bug in `MySqlStream` where too much data could attempt to be read (thanks Peter Belbin)

- Implemented `HasRows` (thanks Nash Pherson).

- Fixed bug where tables with more than 252 columns cause an exception (thanks Joshua Kessler).

- Fixed bug where SQL statements ending in ; would cause a problem (thanks Shane Krueger).

- Fixed bug in driver where error messages were getting truncated by 1 character (thanks Shane Krueger).

- Made `MySqlException` serializable (thanks Mathias Hasselmann).

### B.7.34. Changes in MySQL Connector/NET Version 0.70

- Updated some of the character code pages to be more accurate.

- Fixed problem where readers could be opened on connections that had readers open.

- Moved test to separate assembly `MySqlClientTests`.

- Fixed stupid problem in driver with sequence out of order (Thanks Peter Belbin).

- Added some pipe tests.

- Increased default max pool size to 50.

- Compiles with Mono 0-24.

- Fixed connection and data reader dispose problems.

- Added `String` datatype handling to parameter serialization.

- Fixed sequence problem in driver that occurred after thrown exception (thanks Burkhard Perkens-Golomb).

- Added support for `CommandBehavior.SingleRow` to `DataReader`.

- Fixed command sql processing so quotes are better handled (thanks Theo Spears).

- Fixed parsing of double, single, and decimal values to account for non-English separators. You still have to use the right syntax if you using hard coded sql, but if you use parameters the code will convert floating point types to use '.' appropriately internal both into the server and out.

- Added `MySqlStream` class to simplify timeouts and driver coding.

- Fixed `DataReader` so that it is closed properly when the associated connection is closed. [thanks smishra]

- Made client more SqlClient compliant so that DataReaders have to be closed before the connection can be used to run another command.

- Improved `DBNull.Value` handling in the fields.

- Added several unit tests.

- Fixed `MySqlException` base class.

- Improved driver coding

- Fixed bug where NextResult was returning false on the last resultset.

- Added more tests for MySQL.

- Improved casting problems by equating unsigned 32bit values to Int64 and unsigned 16bit values to Int32, and so forth.

- Added new constructor for `MySqlParameter` for (name, type, size, srccol)

- Fixed bug in `MySqlDataReader` where it didn't check for null fieldlist before returning field count.

- Started adding `MySqlClient` unit tests (added `MySqlClient/Tests` folder and some test cases).

- Fixed some things in Connection String handling.

- Moved `INIT_DB` to `MySqlPool`. I may move it again, this is in preparation of the conference.

- Fixed bug inside `CommandBuilder` that prevented inserts from happening properly.

- Reworked some of the internals so that all three execute methods of Command worked properly.

- Fixed many small bugs found during benchmarking.

- The first cut of `CoonectionPooling` is working. "min pool size" and "max pool size" are respected.

- Work to enable multiple resultsets to be returned.

- Character sets are handled much more intelligently now. The driver queries MySQL at startup for the default character set. That character set is then used for conversions if that code page can be loaded. If not, then the default code page for the current OS is used.

- Added code to save the inferred type in the name,value constructor of `Parameter`.

- Also, inferred type if value of null parameter is changed using `Value` property.

- Converted all files to use proper Camel case. MySQL is now MySql in all files. PgSQL is now PgSql.

- Added attribute to PgSql code to prevent designer from trying to show.

- Added `MySQLDbType` property to Parameter object and added proper conversion code to convert from `DbType` to `MySQLDbType`).

- Removed unused `ObjectToString` method from `MySQLParameter.cs`.

- Fixed `Add(..)` method in `ParameterCollection` so that it doesn't use `Add(name, value)` instead.

- Fixed `IndexOf` and `Contains` in `ParameterCollection` to be aware that parameter names are now stored without @.

- Fixed `Command.ConvertSQLToBytes` so it only allows characters that can be in MySQL variable names.

- Fixed `DataReader` and `Field` so that blob fields read their data from `Field.cs` and `GetBytes` works right.

- Added simple query builder editor to `CommandText` property of `MySQLCommand`.

- Fixed `CommandBuilder` and `Parameter` serialization to account for Parameters not storing @ in their names.

- Removed `MySQLFieldType` enum from Field.cs. Now using `MySQLDbType` enum.

- Added `Designer` attribute to several classes to prevent designer view when using VS.Net.

- Fixed Initial catalog typo in `ConnectionString` designer.

- Removed 3 parameter constructor for `MySQLParameter` that conflicted with (name, type, value).

- Changed `MySQLParameter` so `paramName` is now stored without leading @ (this fixed null inserts when using designer).

- Changed `TypeConverter` for `MySQLParameter` to use the constructor with all properties.

### B.7.35. Changes in MySQL Connector/NET Version 0.68

- Fixed sequence issue in driver.

- Added `DbParametersEditor` to make parameter editing more like `SqlClient`.

- Fixed `Command` class so that parameters can be edited using the designer

- Update connection string designer to support `Use Compression` flag.

- Fixed string encoding so that European characters like ä will work correctly.

- Creating base classes to aid in building new data providers.

- Added support for UID key in connection string.

- Field, parameter, command now using DBNull.Value instead of null.

- `CommandBuilder` using `DBNull.Value`.

- `CommandBuilder` now builds insert command correctly when an auto_insert field is not present.

- Field now uses typeof keyword to return `System.Types` (performance).

### B.7.36. Changes in MySQL Connector/NET Version 0.65

- `MySQLCommandBuilder` now implemented.

- Transaction support now implemented (not all table types support this).

- `GetSchemaTable` fixed to not use xsd (for Mono).

- Driver is now Mono-compatible.

- TIME data type now supported.

- More work to improve Timestamp data type handling.

- Changed signatures of all classes to match corresponding `SqlClient` classes.

### B.7.37. Changes in MySQL Connector/NET Version 0.60

- Protocol compression using SharpZipLib (www.icsharpcode.net).

- Named pipes on Windows now working properly.

- Work done to improve `Timestamp` data type handling.

- Implemented `IEnumerable` on `DataReader` so `DataGrid` would work.

### B.7.38. Changes in MySQL Connector/NET Version 0.50

- Speed increased dramatically by removing bugging network sync code.

- Driver no longer buffers rows of data (more ADO.Net compliant).

- Conversion bugs related to `TIMESTAMP` and `DATETIME` fields fixed.

## B.8. MySQL Connector/J Change History

### B.8.1. Changes in MySQL Connector/J 5.1.x

#### B.8.1.1. Changes in MySQL Connector/J 5.1.6 (Not yet released)

Functionality added or changed:

- XAConnections and datasources have been updated to the JDBC-4.0 standard.

- The profiler event handling has been made extensible via the `profilerEventHandler` connection property.

- Add the `verifyServerCertificate` propery. If set to "false" the driver will not verify the server's certificate when `useSSL` is set to "true"

  When using this feature, the keystore parameters should be specified by the `clientCertificateKeyStore*` properties, rather than system properties, as the JSSE doesn't it straightforward to have a non-verifying trust store and the "default" key store.

Bugs fixed:

- During a Daylight Savings Time (DST) switchover, there was no way to store two timestamp/datetime values , as the hours end up being the same when sent as the literal that MySQL requires.

  Note that to get this scenario to work with MySQL (since it doesn't support per-value timezones), you need to configure your server (or session) to be in UTC, and tell the driver not to use the legacy date/time code by setting `useLegacyDatetimeCode` to "false". This will cause the driver to always convert to/from the server and client timezone consistently.

  This bug fix also fixes Bug#15604, by adding entirely new date/time handling code that can be switched on by `useLegacyDatetimeCode` being set to "false" as a JDBC configuration property. For Connector/J 5.1.x, the default is "true", in trunk and beyond it will be "false" (i.e. the old date/time handling code will be deprecated) (Bug#32577, Bug#15604)

- When unpacking rows directly, we don't hand off error message packets to the internal method which decodes them correctly, so no exception is raised, and the driver than hangs trying to read rows that aren't there. This tends to happen when calling stored procedures, as normal SELECTs won't have an error in this spot in the protocol unless an I/O error occurs. (Bug#32246)

- When using a connection from `ConnectionPoolDataSource`, some `Connection.prepareStatement()` methods would return null instead of the prepared statement. (Bug#32101)

- Using `CallableStatement.setNull()` on a stored function would throw an `ArrayIndexOutOfBounds` exception when setting the last parameter to null. (Bug#31823)

- `MysqlValidConnectionChecker` doesn't properly handle connections created using `ReplicationConnection`. (Bug#31790)

- `DatabaseMetadata.getColumns()` doesn't return the correct column names if the connection character isn't UTF-8. A bug in MySQL server compounded the issue, but was fixed within the MySQL 5.0 release cycle. The fix includes changes to all the sections of the code that access the server metadata. (Bug#20491)

- Fixed `ResultSetMetadata.getColumnName()` for result sets returned from `Statement.getGeneratedKeys()` - it was returning null instead of "GENERATED_KEY" as in 5.0.x.

#### B.8.1.2. Changes in MySQL Connector/J 5.1.5 (09 October 2007)

The following features are new, compared to the 5.0 series of Connector/J

- Support for JDBC-4.0 `NCHAR`, `NVARCHAR` and `NCLOB` types.

- JDBC-4.0 support for setting per-connection client information (which can be viewed in the comments section of a query via `SHOW PROCESSLIST` on a MySQL server, or can be extended to support custom persistence of the information via a public interface).

- Support for JDBC-4.0 XML processing via JAXP interfaces to DOM, SAX and StAX.

- JDBC-4.0 standardized unwrapping to interfaces that include vendor extensions.

Functionality added or changed:

- Added `autoSlowLog` configuration property, overrides `slowQueryThreshold*` properties, driver determines slow queries by those that are slower than 5 * stddev of the mean query time (outside the 96% percentile).

Bugs fixed:

- When a connection is in read-only mode, queries that are wrapped in parentheses were incorrectly identified DML statements. (Bug#28256)

#### B.8.1.3. Changes in MySQL Connector/J 5.1.4 (Not Released)

Only released internally.

#### B.8.1.4. Changes in MySQL Connector/J 5.1.3 (10 September 2007)

The following features are new, compared to the 5.0 series of Connector/J

- Support for JDBC-4.0 `NCHAR`, `NVARCHAR` and `NCLOB` types.

- JDBC-4.0 support for setting per-connection client information (which can be viewed in the comments section of a query via `SHOW PROCESSLIST` on a MySQL server, or can be extended to support custom persistence of the information via a public interface).

- Support for JDBC-4.0 XML processing via JAXP interfaces to DOM, SAX and StAX.

- JDBC-4.0 standardized unwrapping to interfaces that include vendor extensions.

Functionality added or changed:

- Connector/J now connects using an initial character set of `utf-8` solely for the purpose of authentication to allow user names or database names in any character set to be used in the JDBC connection URL. (Bug#29853)

- Added two configuration parameters:

  - `blobsAreStrings` — Should the driver always treat BLOBs as Strings. Added specifically to work around dubious metadata returned by the server for `GROUP BY` clauses. Defaults to false.

  - `functionsNeverReturnBlobs` — Should the driver always treat data from functions returning `BLOBs` as Strings. Added specifically to work around dubious metadata returned by the server for `GROUP BY` clauses. Defaults to false.

- Setting `rewriteBatchedStatements` to `true` now causes CallableStatements with batched arguments to be re-written in the form "CALL (...); CALL (...); ..." to send the batch in as few client-server round trips as possible.

- The driver now picks appropriate internal row representation (whole row in one buffer, or individual byte[]s for each column value) depending on heuristics, including whether or not the row has `BLOB` or `TEXT` types and the overall row-size. The threshold for row size that will cause the driver to use a buffer rather than individual byte[]s is configured by the configuration property `largeRowSizeThreshold`, which has a default value of 2KB.

- The data (and how it's stored) for `ResultSet` rows are now behind an interface which allows us (in some cases) to allocate less memory per row, in that for "streaming" result sets, we re-use the packet used to read rows, since only one row at a time is ever active.

- Added experimental support for statement "interceptors" via the `com.mysql.jdbc.StatementInterceptor` interface, examples are in `com/mysql/jdbc/interceptors`. Implement this interface to be placed "in between" query execution, so that it can be influenced (currently experimental).

- The driver will automatically adjust the server session variable `net_write_timeout` when it determines its been asked for a "streaming" result, and resets it to the previous value when the result set has been consumed. (The configuration property is named `netTimeoutForStreamingResults`, with a unit of seconds, the value '0' means the driver will not try and adjust this value).

- JDBC-4.0 ease-of-development features including auto-registration with the `DriverManager` via the service provider mechanism, standardized Connection validity checks and categorized `SQLExceptions` based on recoverability/retry-ability and class of the underlying error.

- `Statement.setQueryTimeout()`s now affect the entire batch for batched statements, rather than the individual statements that make up the batch.

- Errors encountered during `Statement`/`PreparedStatement`/`CallableStatement.executeBatch()` when `rewriteBatchStatements` has been set to `true` now return `BatchUpdateExceptions` according to the setting of `continueBatchOnError`.

  If `continueBatchOnError` is set to `true`, the update counts for the "chunk" that were sent as one unit will all be set to `EXECUTE_FAILED`, but the driver will attempt to process the remainder of the batch. You can determine which "chunk" failed by looking at the update counts returned in the `BatchUpdateException`.

  If `continueBatchOnError` is set to "false", the update counts returned will contain all updates up-to and including the failed "chunk", with all counts for the failed "chunk" set to `EXECUTE_FAILED`.

  Since MySQL doesn't return multiple error codes for multiple-statements, or for multi-value `INSERT`/`REPLACE`, it is the application's responsibility to handle determining which item(s) in the "chunk" actually failed.

- New methods on com.mysql.jdbc.Statement: `setLocalInfileInputStream()` and `getLocalInfileInputStream()`:

  - `setLocalInfileInputStream()` sets an `InputStream` instance that will be used to send data to the MySQL server for a `LOAD DATA LOCAL INFILE` statement rather than a `FileInputStream` or `URLInputStream` that represents the path given as an argument to the statement.

    This stream will be read to completion upon execution of a `LOAD DATA LOCAL INFILE` statement, and will automatically be closed by the driver, so it needs to be reset before each call to `execute*()` that would cause the MySQL server to request data to fulfill the request for `LOAD DATA LOCAL INFILE`.

    If this value is set to `NULL`, the driver will revert to using a `FileInputStream` or `URLInputStream` as required.

  - `getLocalInfileInputStream()` returns the `InputStream` instance that will be used to send data in response to a `LOAD DATA LOCAL INFILE` statement.

    This method returns `NULL` if no such stream has been set via `setLocalInfileInputStream()`.

- Setting `useBlobToStoreUTF8OutsideBMP` to `true` tells the driver to treat `[MEDIUM/LONG]BLOB` columns as `[LONG]VARCHAR` columns holding text encoded in UTF-8 that has characters outside the BMP (4-byte encodings), which MySQL server can't handle natively.

  Set `utf8OutsideBmpExcludedColumnNamePattern` to a regex so that column names matching the given regex will still be treated as `BLOBs` The regex must follow the patterns used for the `java.util.regex` package. The default is to exclude no columns, and include all columns.

  Set `utf8OutsideBmpIncludedColumnNamePattern` to specify exclusion rules to utf8OutsideBmpExcludedColumnNamePattern". The regex must follow the patterns used for the `java.util.regex` package.

Bugs fixed:

- `setObject(int, Object, int, int)` delegate in PreparedStatmentWrapper delegates to wrong method. (Bug#30892)

- NPE with null column values when `padCharsWithSpace` is set to true. (Bug#30851)

- Collation on `VARBINARY` column types would be misidentified. A fix has been added, but this fix only works for MySQL server versions 5.0.25 and newer, since earlier versions didn't consistently return correct metadata for functions, and thus results from subqueries and functions were indistinguishable from each other, leading to type-related bugs. (Bug#30664)

- An `ArithmeticException` or `NullPointerException` would be raised when the batch had zero members and `rewriteBatchedStatements=true` when `addBatch()` was never called, or `executeBatch()` was called immediately after `clearBatch()`. (Bug#30550)

- Closing a load-balanced connection would cause a `ClassCastException`. (Bug#29852)

- Connection checker for JBoss didn't use same method parameters via reflection, causing connections to always seem "bad". (Bug#29106)

- `DatabaseMetaData.getTypeInfo()` for the types `DECIMAL` and `NUMERIC` will return a precision of 254 for server versions older than 5.0.3, 64 for versions 5.0.3-5.0.5 and 65 for versions newer than 5.0.5. (Bug#28972)

- `CallableStatement.executeBatch()` doesn't work when connection property `noAccessToProcedureBodies` has been set to `true`.

  The fix involves changing the behavior of `noAccessToProcedureBodies`,in that the driver will now report all paramters as "IN" paramters but allow callers to call registerOutParameter() on them without throwing an exception. (Bug#28689)

- `DatabaseMetaData.getColumns()` doesn't contain `SCOPE_*` or `IS_AUTOINCREMENT` columns. (Bug#27915)

- Schema objects with identifiers other than the connection character aren't retrieved correctly in `ResultSetMetadata`. (Bug#27867)

- `Connection.getServerCharacterEncoding()` doesn't work for servers with version >= 4.1. (Bug#27182)

- The automated SVN revisions in `DBMD.getDriverVersion()`. The SVN revision of the directory is now inserted into the version information during the build. (Bug#21116)

- Specifying a "validation query" in your connection pool that starts with "/* ping */" _exactly_ will cause the driver to instead send a ping to the server and return a fake result set (much lighter weight), and when using a ReplicationConnection or a LoadBalancedConnection, will send the ping across all active connections.

#### B.8.1.5. Changes in MySQL Connector/J 5.1.2 (29 June 2007)

This is a new Beta development release, fixing recently discovered bugs.

Functionality added or changed:

- Setting the configuration property `rewriteBatchedStatements` to `true` will now cause the driver to rewrite batched prepared statements with more than 3 parameter sets in a batch into multi-statements (separated by ";") if they are not plain `(i.e. without `SELECT` or `ON DUPLICATE KEY UPDATE` clauses) INSERT` or `REPLACE` statements.

#### B.8.1.6. Changes in MySQL Connector/J 5.1.1 (22 June 2007)

This is a new Alpha development release, adding new features and fixing recently discovered bugs.

Functionality added or changed:

- Incompatible Change: Pulled vendor-extension methods of `Connection` implementation out into an interface to support `java.sql.Wrapper` functionality from `ConnectionPoolDataSource`. The vendor extensions are javadoc'd in the `com.mysql.jdbc.Connection` interface.

  For those looking further into the driver implementation, it is not an API that is used for plugability of implementations inside our driver (which is why there are still references to `ConnectionImpl` throughout the code).

  We've also added server and client `prepareStatement()` methods that cover all of the variants in the JDBC API.

  `Connection.serverPrepare(String)` has been re-named to `Connection.serverPrepareStatement()` for consistency with `Connection.clientPrepareStatement()`.

- Row navigation now causes any streams/readers open on the result set to be closed, as in some cases we're reading directly from a shared network packet and it will be overwritten by the "next" row.

- Made it possible to retrieve prepared statement parameter bindings (to be used in `StatementInterceptors`, primarily).

- Externalized the descriptions of connection properties.

- The data (and how it's stored) for `ResultSet` rows are now behind an interface which allows us (in some cases) to allocate less memory per row, in that for "streaming" result sets, we re-use the packet used to read rows, since only one row at a time is ever active.

- Similar to `Connection`, we pulled out vendor extensions to `Statement` into an interface named `com.mysql.Statement`, and moved the `Statement` class into `com.mysql.StatementImpl`. The two methods (javadoc'd in `com.mysql.Statement` are `enableStreamingResults()`, which already existed, and `disableStreamingResults()` which sets the statement instance back to the fetch size and result set type it had before `enableStreamingResults()` was called.

- Driver now picks appropriate internal row representation (whole row in one buffer, or individual byte[]s for each column value) depending on heuristics, including whether or not the row has `BLOB` or `TEXT` types and the overall row-size. The threshold for row size that will cause the driver to use a buffer rather than individual byte[]s is configured by the configuration property `largeRowSizeThreshold`, which has a default value of 2KB.

- Added experimental support for statement "interceptors" via the `com.mysql.jdbc.StatementInterceptor` interface, examples are in `com/mysql/jdbc/interceptors`.

  Implement this interface to be placed "in between" query execution, so that you can influence it. (currently experimental).

  `StatementInterceptors` are "chainable" when configured by the user, the results returned by the "current" interceptor will be passed on to the next on in the chain, from left-to-right order, as specified by the user in the JDBC configuration property `statementInterceptors`.

- See the sources (fully javadoc'd) for `com.mysql.jdbc.StatementInterceptor` for more details until we iron out the API and get it documented in the manual.

- Setting `rewriteBatchedStatements` to `true` now causes `CallableStatements` with batched arguments to be re-written in the form `CALL (...); CALL (...); ...` to send the batch in as few client-server round trips as possible.

#### B.8.1.7. Changes in MySQL Connector/J 5.1.0 (11 April 2007)

This is the first public alpha release of the current Connector/J 5.1 development branch, providing an insight to upcoming features. Although some of these are still under development, this release includes the following new features and changes (in comparison to the current Connector/J 5.0 production release):

Important change: Due to a number of issues with the use of server-side prepared statements, Connector/J 5.0.5 has disabled their use by default. The disabling of server-side prepared statements does not affect the operation of the connector in any way.

To enable server-side prepared statements you must add the following configuration property to your connector string:

    useServerPrepStmts=true

The default value of this property is `false` (that is, Connector/J does not use server-side prepared statements).

### Note

The disabling of server-side prepared statements does not affect the operation of the connector. However, if you use the `useTimezone=true` connection option and use client-side prepared statements (instead of server-side prepared statements) you should also set `useSSPSCompatibleTimezoneShift=true`.

Functionality added or changed:

- Refactored `CommunicationsException` into a JDBC-3.0 version, and a JDBC-4.0 version (which extends `SQLRecoverableException`, now that it exists).

  ### Note

  This change means that if you were catching `com.mysql.jdbc.CommunicationsException` in your applications instead of looking at the SQLState class of `08`, and are moving to Java 6 (or newer), you need to change your imports to that exception to be `com.mysql.jdbc.exceptions.jdbc4.CommunicationsException`, as the old class will not be instantiated for communications link-related errors under Java 6.

- Added support for JDBC-4.0 categorized `SQLExceptions`.

- Added support for JDBC-4.0's `NCLOB`, and `NCHAR`/`NVARCHAR` types.

- `com.mysql.jdbc.java6.javac` — full path to your Java-6 javac executable

- Added support for JDBC-4.0's SQLXML interfaces.

- Re-worked Ant buildfile to build JDBC-4.0 classes separately, as well as support building under Eclipse (since Eclipse can't mix/match JDKs).

  To build, you must set `JAVA_HOME` to J2SDK-1.4.2 or Java-5, and set the following properties on your Ant command line:

  - `com.mysql.jdbc.java6.javac` — full path to your Java-6 javac executable

  - `com.mysql.jdbc.java6.rtjar` — full path to your Java-6 `rt.jar` file

- New feature — driver will automatically adjust session variable `net_write_timeout` when it determines it has been asked for a "streaming" result, and resets it to the previous value when the result set has been consumed. (configuration property is named `netTimeoutForStreamingResults` value and has a unit of seconds, the value `0` means the driver will not try and adjust this value).

- Added support for JDBC-4.0's client information. The backend storage of information provided via `Connection.setClientInfo()` and retrieved by `Connection.getClientInfo()` is pluggable by any class that implements the `com.mysql.jdbc.JDBC4ClientInfoProvider` interface and has a no-args constructor.

  The implementation used by the driver is configured using the `clientInfoProvider` configuration property (with a default of value of `com.mysql.jdbc.JDBC4CommentClientInfoProvider`, an implementation which lists the client information as a comment prepended to every query sent to the server).

  This functionality is only available when using Java-6 or newer.

- `com.mysql.jdbc.java6.rtjar` — full path to your Java-6 `rt.jar` file

- Added support for JDBC-4.0's `Wrapper` interface.

### B.8.2. Changes in MySQL Connector/J 5.0.x

#### B.8.2.1. Changes in MySQL Connector/J 5.0.8 (09 October 2007)

Functionality added or changed:

- `blobsAreStrings` — Should the driver always treat BLOBs as Strings. Added specifically to work around dubious metadata returned by the server for `GROUP BY` clauses. Defaults to false.

- Added two configuration parameters:

  - `blobsAreStrings` — Should the driver always treat BLOBs as Strings. Added specifically to work around dubious metadata returned by the server for `GROUP BY` clauses. Defaults to false.

  - `functionsNeverReturnBlobs` — Should the driver always treat data from functions returning `BLOBs` as Strings. Added specifically to work around dubious metadata returned by the server for `GROUP BY` clauses. Defaults to false.

- `functionsNeverReturnBlobs` — Should the driver always treat data from functions returning `BLOBs` as Strings. Added specifically to work around dubious metadata returned by the server for `GROUP BY` clauses. Defaults to false.

- XAConnections now start in auto-commit mode (as per JDBC-4.0 specification clarification).

- Driver will now fall back to sane defaults for `max_allowed_packet` and `net_buffer_length` if the server reports them incorrectly (and will log this situation at `WARN` level, since it's actually an error condition).

Bugs fixed:

- Connections established using URLs of the form `jdbc:mysql:loadbalance://` weren't doing failover if they tried to connect to a MySQL server that was down. The driver now attempts connections to the next "best" (depending on the load balance strategy in use) server, and continues to attempt connecting to the next "best" server every 250 milliseconds until one is found that is up and running or 5 minutes has passed.

  If the driver gives up, it will throw the last-received `SQLException`. (Bug#31053)

- `setObject(int, Object, int, int)` delegate in PreparedStatmentWrapper delegates to wrong method. (Bug#30892)

- NPE with null column values when `padCharsWithSpace` is set to true. (Bug#30851)

- Collation on `VARBINARY` column types would be misidentified. A fix has been added, but this fix only works for MySQL server versions 5.0.25 and newer, since earlier versions didn't consistently return correct metadata for functions, and thus results from subqueries and functions were indistinguishable from each other, leading to type-related bugs. (Bug#30664)

- An `ArithmeticException` or `NullPointerException` would be raised when the batch had zero members and `rewriteBatchedStatements=true` when `addBatch()` was never called, or `executeBatch()` was called immediately after `clearBatch()`. (Bug#30550)

- Closing a load-balanced connection would cause a `ClassCastException`. (Bug#29852)

- Connection checker for JBoss didn't use same method parameters via reflection, causing connections to always seem "bad". (Bug#29106)

- `DatabaseMetaData.getTypeInfo()` for the types `DECIMAL` and `NUMERIC` will return a precision of 254 for server versions older than 5.0.3, 64 for versions 5.0.3-5.0.5 and 65 for versions newer than 5.0.5. (Bug#28972)

- `CallableStatement.executeBatch()` doesn't work when connection property `noAccessToProcedureBodies` has been set to `true`.

  The fix involves changing the behavior of `noAccessToProcedureBodies`,in that the driver will now report all paramters as "IN" paramters but allow callers to call registerOutParameter() on them without throwing an exception. (Bug#28689)

- When a connection is in read-only mode, queries that are wrapped in parentheses were incorrectly identified DML statements. (Bug#28256)

- `UNSIGNED` types not reported via `DBMD.getTypeInfo()`, and capitalization of type names is not consistent between `DBMD.getColumns()`, `RSMD.getColumnTypeName()` and `DBMD.getTypeInfo()`.

  This fix also ensures that the precision of `UNSIGNED MEDIUMINT` and `UNSIGNED BIGINT` is reported correctly via `DBMD.getColumns()`. (Bug#27916)

- `DatabaseMetaData.getColumns()` doesn't contain `SCOPE_*` or `IS_AUTOINCREMENT` columns. (Bug#27915)

- Schema objects with identifiers other than the connection character aren't retrieved correctly in `ResultSetMetadata`. (Bug#27867)

- Cached metadata with `PreparedStatement.execute()` throws `NullPointerException`. (Bug#27412)

- `Connection.getServerCharacterEncoding()` doesn't work for servers with version >= 4.1. (Bug#27182)

- The automated SVN revisions in `DBMD.getDriverVersion()`. The SVN revision of the directory is now inserted into the version information during the build. (Bug#21116)

- Specifying a "validation query" in your connection pool that starts with "/* ping */" _exactly_ will cause the driver to instead send a ping to the server and return a fake result set (much lighter weight), and when using a ReplicationConnection or a LoadBalancedConnection, will send the ping across all active connections.

#### B.8.2.2. Changes in MySQL Connector/J 5.0.7 (20 July 2007)

Functionality added or changed:

- The driver will now automatically set `useServerPrepStmts` to `true` when `useCursorFetch` has been set to `true`, since the feature requires server-side prepared statements in order to function.

- `tcpKeepAlive` - Should the driver set SO_KEEPALIVE (default `true`)?

- Give more information in EOFExceptions thrown out of MysqlIO (how many bytes the driver expected to read, how many it actually read, say that communications with the server were unexpectedly lost).

- Driver detects when it is running in a ColdFusion MX server (tested with version 7), and uses the configuration bundle `coldFusion`, which sets `useDynamicCharsetInfo` to `false` (see previous entry), and sets `useLocalSessionState` and autoReconnect to `true`.

- `tcpNoDelay` - Should the driver set SO_TCP_NODELAY (disabling the Nagle Algorithm, default `true`)?

- Added configuration property `slowQueryThresholdNanos` - if `useNanosForElapsedTime` is set to `true`, and this property is set to a non-zero value the driver will use this threshold (in nanosecond units) to determine if a query was slow, instead of using millisecond units.

- `tcpRcvBuf` - Should the driver set SO_RCV_BUF to the given value? The default value of '0', means use the platform default value for this property.

- Setting `useDynamicCharsetInfo` to `false` now causes driver to use static lookups for collations as well (makes ResultSetMetadata.isCaseSensitive() much more efficient, which leads to performance increase for ColdFusion, which calls this method for every column on every table it sees, it appears).

- Added configuration properties to allow tuning of TCP/IP socket parameters:

  - `tcpNoDelay` - Should the driver set SO_TCP_NODELAY (disabling the Nagle Algorithm, default `true`)?

  - `tcpKeepAlive` - Should the driver set SO_KEEPALIVE (default `true`)?

  - `tcpRcvBuf` - Should the driver set SO_RCV_BUF to the given value? The default value of '0', means use the platform default value for this property.

  - `tcpSndBuf` - Should the driver set SO_SND_BUF to the given value? The default value of '0', means use the platform default value for this property.

  - `tcpTrafficClass` - Should the driver set traffic class or type-of-service fields? See the documentation for java.net.Socket.setTrafficClass() for more information.

- Setting the configuration parameter `useCursorFetch` to `true` for MySQL-5.0+ enables the use of cursors that allow Connector/J to save memory by fetching result set rows in chunks (where the chunk size is set by calling setFetchSize() on a Statement or ResultSet) by using fully-materialized cursors on the server.

- `tcpSndBuf` - Should the driver set SO_SND_BUF to the given value? The default value of '0', means use the platform default value for this property.

- `tcpTrafficClass` - Should the driver set traffic class or type-of-service fields? See the documentation for java.net.Socket.setTrafficClass() for more information.

- Added new debugging functionality - Setting configuration property `includeInnodbStatusInDeadlockExceptions` to `true` will cause the driver to append the output of `SHOW ENGINE INNODB STATUS` to deadlock-related exceptions, which will enumerate the current locks held inside InnoDB.

- Added configuration property `useNanosForElapsedTime` - for profiling/debugging functionality that measures elapsed time, should the driver try to use nanoseconds resolution if available (requires JDK >= 1.5)?

  ### Note

  If `useNanosForElapsedTime` is set to `true`, and this property is set to "0" (or left default), then elapsed times will still be measured in nanoseconds (if possible), but the slow query threshold will be converted from milliseconds to nanoseconds, and thus have an upper bound of approximately 2000 milliseconds (as that threshold is represented as an integer, not a long).

Bugs fixed:

- Don't send any file data in response to LOAD DATA LOCAL INFILE if the feature is disabled at the client side. This is to prevent a malicious server or man-in-the-middle from asking the client for data that the client is not expecting. Thanks to Jan Kneschke for discovering the exploit and Andrey "Poohie" Hristov, Konstantin Osipov and Sergei Golubchik for discussions about implications and possible fixes. (Bug#29605)

- Parser in client-side prepared statements runs to end of statement, rather than end-of-line for '#' comments. Also added support for '--' single-line comments. (Bug#28956)

- Parser in client-side prepared statements eats character following '/' if it's not a multi-line comment. (Bug#28851)

- PreparedStatement.getMetaData() for statements containing leading one-line comments is not returned correctly.

  As part of this fix, we also overhauled detection of DML for `executeQuery()` and `SELECT`s for `executeUpdate()` in plain and prepared statements to be aware of the same types of comments. (Bug#28469)

#### B.8.2.3. Changes in MySQL Connector/J 5.0.6 (15 May 2007)

Functionality added or changed:

- Added an experimental load-balanced connection designed for use with SQL nodes in a MySQL Cluster/NDB environment (This is not for master-slave replication. For that, we suggest you look at `ReplicationConnection` or `lbpool`).

  If the JDBC URL starts with `jdbc:mysql:loadbalance://host-1,host-2,...host-n`, the driver will create an implementation of `java.sql.Connection` that load balances requests across a series of MySQL JDBC connections to the given hosts, where the balancing takes place after transaction commit.

  Therefore, for this to work (at all), you must use transactions, even if only reading data.

  Physical connections to the given hosts will not be created until needed.

  The driver will invalidate connections that it detects have had communication errors when processing a request. A new connection to the problematic host will be attempted the next time it is selected by the load balancing algorithm.

  There are two choices for load balancing algorithms, which may be specified by the `loadBalanceStrategy` JDBC URL configuration property:

  - `random` — the driver will pick a random host for each request. This tends to work better than round-robin, as the randomness will somewhat account for spreading loads where requests vary in response time, while round-robin can sometimes lead to overloaded nodes if there are variations in response times across the workload.

  - `bestResponseTime` — the driver will route the request to the host that had the best response time for the previous transaction.

- `bestResponseTime` — the driver will route the request to the host that had the best response time for the previous transaction.

- Added configuration property `padCharsWithSpace` (defaults to `false`). If set to `true`, and a result set column has the `CHAR` type and the value does not fill the amount of characters specified in the DDL for the column, the driver will pad the remaining characters with space (for ANSI compliance).

- When `useLocalSessionState` is set to `true` and connected to a MySQL-5.0 or later server, the JDBC driver will now determine whether an actual `commit` or `rollback` statement needs to be sent to the database when `Connection.commit()` or `Connection.rollback()` is called.

  This is especially helpful for high-load situations with connection pools that always call `Connection.rollback()` on connection check-in/check-out because it avoids a round-trip to the server.

- Added configuration property `useDynamicCharsetInfo`. If set to `false` (the default), the driver will use a per-connection cache of character set information queried from the server when necessary, or when set to `true`, use a built-in static mapping that is more efficient, but isn't aware of custom character sets or character sets implemented after the release of the JDBC driver.

  ### Note

  This only affects the `padCharsWithSpace` configuration property and the `ResultSetMetaData.getColumnDisplayWidth()` method.

- New configuration property, `enableQueryTimeouts` (default `true`).

  When enabled, query timeouts set via `Statement.setQueryTimeout()` use a shared `java.util.Timer` instance for scheduling. Even if the timeout doesn't expire before the query is processed, there will be memory used by the `TimerTask` for the given timeout which won't be reclaimed until the time the timeout would have expired if it hadn't been cancelled by the driver. High-load environments might want to consider disabling this functionality. (this configuration property is part of the `maxPerformance` configuration bundle).

- Give better error message when "streaming" result sets, and the connection gets clobbered because of exceeding `net_write_timeout` on the server.

- `random` — the driver will pick a random host for each request. This tends to work better than round-robin, as the randomness will somewhat account for spreading loads where requests vary in response time, while round-robin can sometimes lead to overloaded nodes if there are variations in response times across the workload.

- `com.mysql.jdbc.[NonRegistering]Driver` now understands URLs of the format `jdbc:mysql:replication://` and `jdbc:mysql:loadbalance://` which will create a ReplicationConnection (exactly like when using `[NonRegistering]ReplicationDriver`) and an experimental load-balanced connection designed for use with SQL nodes in a MySQL Cluster/NDB environment, respectively.

  In an effort to simplify things, we're working on deprecating multiple drivers, and instead specifying different core behavior based upon JDBC URL prefixes, so watch for `[NonRegistering]ReplicationDriver` to eventually disappear, to be replaced with `com.mysql.jdbc[NonRegistering]Driver` with the new URL prefix.

- Fixed issue where a failed-over connection would let an application call `setReadOnly(false)`, when that call should be ignored until the connection is reconnected to a writable master unless `failoverReadOnly` had been set to `false`.

- Driver will now use `INSERT INTO ... VALUES (DEFAULT)` form of statement for updatable result sets for `ResultSet.insertRow()`, rather than pre-populating the insert row with values from `DatabaseMetaData.getColumns()` (which results in a `SHOW FULL COLUMNS` on the server for every result set). If an application requires access to the default values before `insertRow()` has been called, the JDBC URL should be configured with `populateInsertRowWithDefaultValues` set to `true`.

  This fix specifically targets performance issues with ColdFusion and the fact that it seems to ask for updatable result sets no matter what the application does with them.

- More intelligent initial packet sizes for the "shared" packets are used (512 bytes, rather than 16K), and initial packets used during handshake are now sized appropriately as to not require reallocation.

Bugs fixed:

- More useful error messages are generated when the driver thinks a result set is not updatable. (Thanks to Ashley Martens for the patch). (Bug#28085)

- `Connection.getTransactionIsolation()` uses "`SHOW VARIABLES LIKE`" which is very inefficient on MySQL-5.0+ servers. (Bug#27655)

- Fixed issue where calling `getGeneratedKeys()` on a prepared statement after calling `execute()` didn't always return the generated keys (`executeUpdate()` worked fine however). (Bug#27655)

- `CALL /* ... */ `some_proc`()` doesn't work. As a side effect of this fix, you can now use `/* */` and `#` comments when preparing statements using client-side prepared statement emulation.

  If the comments happen to contain parameter markers (`?`), they will be treated as belonging to the comment (that is, not recognized) rather than being a parameter of the statement.

  ### Note

  The statement when sent to the server will contain the comments as-is, they're not stripped during the process of preparing the `PreparedStatement` or `CallableStatement`.

  (Bug#27400)

- `ResultSet.get*()` with a column index < 1 returns misleading error message. (Bug#27317)

- Using `ResultSet.get*()` with a column index less than 1 returns a misleading error message. (Bug#27317)

- Comments in DDL of stored procedures/functions confuse procedure parser, and thus metadata about them can not be created, leading to inability to retrieve said metadata, or execute procedures that have certain comments in them. (Bug#26959)

- Fast date/time parsing doesn't take into account `00:00:00` as a legal value. (Bug#26789)

- `PreparedStatement` is not closed in `BlobFromLocator.getBytes()`. (Bug#26592)

- When the configuration property `useCursorFetch` was set to `true`, sometimes server would return new, more exact metadata during the execution of the server-side prepared statement that enables this functionality, which the driver ignored (using the original metadata returned during `prepare()`), causing corrupt reading of data due to type mismatch when the actual rows were returned. (Bug#26173)

- `CallableStatements` with `OUT/INOUT` parameters that are "binary" (`BLOB`, `BIT`, `(VAR)BINARY`, `JAVA_OBJECT`) have extra 7 bytes. (Bug#25715)

- Whitespace surrounding storage/size specifiers in stored procedure parameters declaration causes `NumberFormatException` to be thrown when calling stored procedure on JDK-1.5 or newer, as the Number classes in JDK-1.5+ are whitespace intolerant. (Bug#25624)

- Client options not sent correctly when using SSL, leading to stored procedures not being able to return results. Thanks to Don Cohen for the bug report, testcase and patch. (Bug#25545)

- `Statement.setMaxRows()` is not effective on result sets materialized from cursors. (Bug#25517)

- `BIT(> 1)` is returned as `java.lang.String` from `ResultSet.getObject()` rather than `byte[]`. (Bug#25328)

#### B.8.2.4. Changes in MySQL Connector/J 5.0.5 (02 March 2007)

Functionality added or changed:

- Usage Advisor will now issue warnings for result sets with large numbers of rows. You can configure the trigger value by using the `resultSetSizeThreshold` parameter, which has a default value of 100.

- The `rewriteBatchedStatements` feature can now be used with server-side prepared statements.

- Important change: Due to a number of issues with the use of server-side prepared statements, Connector/J 5.0.5 has disabled their use by default. The disabling of server-side prepared statements does not affect the operation of the connector in any way.

  To enable server-side prepared statements you must add the following configuration property to your connector string:

      useServerPrepStmts=true

  The default value of this property is `false` (that is, Connector/J does not use server-side prepared statements).

- Improved speed of `datetime` parsing for ResultSets that come from plain or non-server-side prepared statements. You can enable old implementation with `useFastDateParsing=false` as a configuration parameter.

- Usage Advisor now detects empty results sets and does not report on columns not referenced in those empty sets.

- Fixed logging of XA commands sent to server, it's now configurable via `logXaCommands` property (defaults to `false`).

- Added configuration property `localSocketAddress`,which is the hostname or IP address given to explicitly configure the interface that the driver will bind the client side of the TCP/IP connection to when connecting.

- We've added a new configuration option `treatUtilDateAsTimestamp`, which is `false` by default, as (1) We already had specific behavior to treat java.util.Date as a java.sql.Timestamp because it's useful to many folks, and (2) that behavior will very likely be required for drivers JDBC-post-4.0.

Bugs fixed:

- Connection property `socketFactory` wasn't exposed via correctly named mutator/accessor, causing data source implementations that use JavaBean naming conventions to set properties to fail to set the property (and in the case of SJAS, fail silently when trying to set this parameter). (Bug#26326)

- A query execution which timed out did not always throw a `MySQLTimeoutException`. (Bug#25836)

- Storing a `java.util.Date` object in a `BLOB` column would not be serialized correctly during `setObject`. (Bug#25787)

- Timer instance used for `Statement.setQueryTimeout()` created per-connection, rather than per-VM, causing memory leak. (Bug#25514)

- `EscapeProcessor` gets confused by multiple backslashes. We now push the responsibility of syntax errors back on to the server for most escape sequences. (Bug#25399)

- `INOUT` parameters in `CallableStatements` get doubly-escaped. (Bug#25379)

- When using the `rewriteBatchedStatements` connection option with `PreparedState.executeBatch()` an internal memory leak would occur. (Bug#25073)

- Fixed issue where field-level for metadata from `DatabaseMetaData` when using `INFORMATION_SCHEMA` didn't have references to current connections, sometimes leading to Null Pointer Exceptions (NPEs) when introspecting them via `ResultSetMetaData`. (Bug#25073)

- `StringUtils.indexOfIgnoreCaseRespectQuotes()` isn't case-insensitive on the first character of the target. This bug also affected `rewriteBatchedStatements` functionality when prepared statements did not use uppercase for the `VALUES` clause. (Bug#25047)

- Client-side prepared statement parser gets confused by in-line comments `/*...*/` and therefore cannot rewrite batch statements or reliably detect the type of statements when they are used. (Bug#25025)

- Results sets from `UPDATE` statements that are part of multi-statement queries would cause an `SQLException` error, "Result is from UPDATE". (Bug#25009)

- Specifying `US-ASCII` as the character set in a connection to a MySQL 4.1 or newer server does not map correctly. (Bug#24840)

- Using `DatabaseMetaData.getSQLKeywords()` does not return a all of the of the reserved keywords for the current MySQL version. Current implementation returns the list of reserved words for MySQL 5.1, and does not distinguish between versions. (Bug#24794)

- Calling `Statement.cancel()` could result in a Null Pointer Exception (NPE). (Bug#24721)

- Using `setFetchSize()` breaks prepared `SHOW` and other commands. (Bug#24360)

- Calendars and timezones are now lazily instantiated when required. (Bug#24351)

- Using `DATETIME` columns would result in time shifts when `useServerPrepStmts` was true. The reason was due to different behavior when using client-side compared to server-side prepared statements and the `useJDBCCompliantTimezoneShift` option. This is now fixed if moving from server-side prepared statements to client-side prepared statements by setting `useSSPSCompatibleTimezoneShift` to `true`, as the driver can't tell if this is a new deployment that never used server-side prepared statements, or if it is an existing deployment that is switching to client-side prepared statements from server-side prepared statements. (Bug#24344)

- Connector/J now returns a better error message when server doesn't return enough information to determine stored procedure/function parameter types. (Bug#24065)

- A connection error would occur when connecting to a MySQL server with certain character sets. Some collations/character sets reported as "unknown" (specifically `cias` variants of existing character sets), and inability to override the detected server character set. (Bug#23645)

- Inconsistency between `getSchemas` and `INFORMATION_SCHEMA`. (Bug#23304)

- `DatabaseMetaData.getSchemas()` doesn't return a `TABLE_CATALOG` column. (Bug#23303)

- When using a JDBC connection URL that is malformed, the `NonRegisteringDriver.getPropertyInfo` method will throw a Null Pointer Exception (NPE). (Bug#22628)

- Some exceptions thrown out of `StandardSocketFactory` were needlessly wrapped, obscuring their true cause, especially when using socket timeouts. (Bug#21480)

- When using a server-side prepared statement the driver would send timestamps to the server using nanoseconds instead of milliseconds. (Bug#21438)

- When using server-side prepared statements and timestamp columns, value would be incorrectly populated (with nanoseconds, not microseconds). (Bug#21438)

- `ParameterMetaData` throws `NullPointerException` when prepared SQL has a syntax error. Added `generateSimpleParameterMetadata` configuration property, which when set to `true` will generate metadata reflecting `VARCHAR` for every parameter (the default is `false`, which will cause an exception to be thrown if no parameter metadata for the statement is actually available). (Bug#21267)

- Fixed an issue where `XADataSources` couldn't be bound into JNDI, as the `DataSourceFactory` didn't know how to create instances of them.

Other changes:

- Avoid static synchronized code in JVM class libraries for dealing with default timezones.

- Performance enhancement of initial character set configuration, driver will only send commands required to configure connection character set session variables if the current values on the server do not match what is required.

- Re-worked stored procedure parameter parser to be more robust. Driver no longer requires `BEGIN` in stored procedure definition, but does have requirement that if a stored function begins with a label directly after the "returns" clause, that the label is not a quoted identifier.

- Throw exceptions encountered during timeout to thread calling `Statement.execute*()`, rather than `RuntimeException`.

- Changed cached result set metadata (when using `cacheResultSetMetadata=true`) to be cached per-connection rather than per-statement as previously implemented.

- Reverted back to internal character conversion routines for single-byte character sets, as the ones internal to the JVM are using much more CPU time than our internal implementation.

- When extracting foreign key information from `SHOW CREATE TABLE` in `DatabaseMetaData`, ignore exceptions relating to tables being missing (which could happen for cross-reference or imported-key requests, as the list of tables is generated first, then iterated).

- Fixed some Null Pointer Exceptions (NPEs) when cached metadata was used with `UpdatableResultSets`.

- Take `localSocketAddress` property into account when creating instances of `CommunicationsException` when the underyling exception is a `java.net.BindException`, so that a friendlier error message is given with a little internal diagnostics.

- Fixed cases where `ServerPreparedStatements` weren't using cached metadata when `cacheResultSetMetadata=true` was used.

- Use a `java.util.TreeMap` to map column names to ordinal indexes for `ResultSet.findColumn()` instead of a HashMap. This allows us to have case-insensitive lookups (required by the JDBC specification) without resorting to the many transient object instances needed to support this requirement with a normal `HashMap` with either case-adjusted keys, or case-insensitive keys. (In the worst case scenario for lookups of a 1000 column result set, TreeMaps are about half as fast wall-clock time as a HashMap, however in normal applications their use gives many orders of magnitude reduction in transient object instance creation which pays off later for CPU usage in garbage collection).

- When using cached metadata, skip field-level metadata packets coming from the server, rather than reading them and discarding them without creating `com.mysql.jdbc.Field` instances.

#### B.8.2.5. Changes in MySQL Connector/J 5.0.4 (20 October 2006)

Bugs fixed:

- DBMD.getColumns() does not return expected COLUMN_SIZE for the SET type, now returns length of largest possible set disregarding whitespace or the "," delimitters to be consistent with the ODBC driver. (Bug#22613)

- Added new _ci collations to CharsetMapping - utf8_unicode_ci not working. (Bug#22456)

- Driver was using milliseconds for Statement.setQueryTimeout() when specification says argument is to be in seconds. (Bug#22359)

- Workaround for server crash when calling stored procedures via a server-side prepared statement (driver now detects prepare(stored procedure) and substitutes client-side prepared statement). (Bug#22297)

- Driver issues truncation on write exception when it shouldn't (due to sending big decimal incorrectly to server with server-side prepared statement). (Bug#22290)

- Newlines causing whitespace to span confuse procedure parser when getting parameter metadata for stored procedures. (Bug#22024)

- When using information_schema for metadata, COLUMN_SIZE for getColumns() is not clamped to range of java.lang.Integer as is the case when not using information_schema, thus leading to a truncation exception that isn't present when not using information_schema. (Bug#21544)

- Column names don't match metadata in cases where server doesn't return original column names (column functions) thus breaking compatibility with applications that expect 1-1 mappings between findColumn() and rsmd.getColumnName(), usually manifests itself as "Can't find column ('')" exceptions. (Bug#21379)

- Driver now sends numeric 1 or 0 for client-prepared statement `setBoolean()` calls instead of '1' or '0'.

- Fixed configuration property `jdbcCompliantTruncation` was not being used for reads of result set values.

- DatabaseMetaData correctly reports `true` for `supportsCatalog*()` methods.

- Driver now supports `{call sp}` (without "()" if procedure has no arguments).

#### B.8.2.6. Changes in MySQL Connector/J 5.0.3 (26 July 2006)

Functionality added or changed:

- Added configuration option `noAccessToProcedureBodies` which will cause the driver to create basic parameter metadata for `CallableStatements` when the user does not have access to procedure bodies via `SHOW CREATE PROCEDURE` or selecting from `mysql.proc` instead of throwing an exception. The default value for this option is `false`

Bugs fixed:

- Fixed `Statement.cancel()` causes `NullPointerException` if underlying connection has been closed due to server failure. (Bug#20650)

- If the connection to the server has been closed due to a server failure, then the cleanup process will call `Statement.cancel()`, triggering a `NullPointerException`, even though there is no active connection. (Bug#20650)

#### B.8.2.7. Changes in MySQL Connector/J 5.0.2 (11 July 2006)

Bugs fixed:

- `MysqlXaConnection.recover(int flags)` now allows combinations of `XAResource.TMSTARTRSCAN` and `TMENDRSCAN`. To simulate the “scanning” nature of the interface, we return all prepared XIDs for `TMSTARTRSCAN`, and no new XIDs for calls with `TMNOFLAGS`, or `TMENDRSCAN` when not in combination with `TMSTARTRSCAN`. This change was made for API compliance, as well as integration with IBM WebSphere's transaction manager. (Bug#20242)

- Fixed `MysqlValidConnectionChecker` for JBoss doesn't work with `MySQLXADataSources`. (Bug#20242)

- Added connection/datasource property `pinGlobalTxToPhysicalConnection` (defaults to `false`). When set to `true`, when using `XAConnections`, the driver ensures that operations on a given XID are always routed to the same physical connection. This allows the `XAConnection` to support `XA START ... JOIN` after `XA END` has been called, and is also a workaround for transaction managers that don't maintain thread affinity for a global transaction (most either always maintain thread affinity, or have it as a configuration option). (Bug#20242)

- Better caching of character set converters (per-connection) to remove a bottleneck for multibyte character sets. (Bug#20242)

- Fixed `ConnectionProperties` (and thus some subclasses) are not serializable, even though some J2EE containers expect them to be. (Bug#19169)

- Fixed driver fails on non-ASCII platforms. The driver was assuming that the platform character set would be a superset of MySQL's `latin1` when doing the handshake for authentication, and when reading error messages. We now use Cp1252 for all strings sent to the server during the handshake phase, and a hard-coded mapping of the `language` systtem variable to the character set that is used for error messages. (Bug#18086)

- Fixed can't use `XAConnection` for local transactions when no global transaction is in progress. (Bug#17401)

#### B.8.2.8. Changes in MySQL Connector/J 5.0.1 (Not Released)

Not released due to a packaging error

#### B.8.2.9. Changes in MySQL Connector/J 5.0.0 (22 December 2005)

Bugs fixed:

- Added support for Connector/MXJ integration via url subprotocol `jdbc:mysql:mxj://...`. (Bug#14729)

- Idle timeouts cause `XAConnections` to whine about rolling themselves back. (Bug#14729)

- When fix for Bug#14562 was merged from 3.1.12, added functionality for `CallableStatement`'s parameter metadata to return correct information for `.getParameterClassName()`. (Bug#14729)

- Added service-provider entry to `META-INF/services/java.sql.Driver` for JDBC-4.0 support. (Bug#14729)

- Fuller synchronization of `Connection` to avoid deadlocks when using multithreaded frameworks that multithread a single connection (usually not recommended, but the JDBC spec allows it anyways), part of fix to Bug#14972). (Bug#14729)

- Moved all `SQLException` constructor usage to a factory in `SQLError` (ground-work for JDBC-4.0 `SQLState`-based exception classes). (Bug#14729)

- Removed Java5-specific calls to `BigDecimal` constructor (when result set value is `''`, `(int)0` was being used as an argument indirectly via method return value. This signature doesn't exist prior to Java5.) (Bug#14729)

- Implementation of `Statement.cancel()` and `Statement.setQueryTimeout()`. Both require MySQL-5.0.0 or newer server, require a separate connection to issue the `KILL QUERY` statement, and in the case of `setQueryTimeout()` creates an additional thread to handle the timeout functionality.

  Note: Failures to cancel the statement for `setQueryTimeout()` may manifest themselves as `RuntimeExceptions` rather than failing silently, as there is currently no way to unblock the thread that is executing the query being cancelled due to timeout expiration and have it throw the exception instead. (Bug#14729)

- Return "[VAR]BINARY" for `RSMD.getColumnTypeName()` when that is actually the type, and it can be distinguished (MySQL-4.1 and newer). (Bug#14729)

- Attempt detection of the MySQL type `BINARY` (it's an alias, so this isn't always reliable), and use the `java.sql.Types.BINARY` type mapping for it.

- Added unit tests for `XADatasource`, as well as friendlier exceptions for XA failures compared to the "stock" `XAException` (which has no messages).

- If the connection `useTimezone` is set to `true`, then also respect time zone conversions in escape-processed string literals (for example, `"{ts ...}"` and `"{t ...}"`).

- Don't allow `.setAutoCommit(true)`, or `.commit()` or `.rollback()` on an XA-managed connection as per the JDBC specification.

- `XADataSource` implemented (ported from 3.2 branch which won't be released as a product). Use `com.mysql.jdbc.jdbc2.optional.MysqlXADataSource` as your datasource class name in your application server to utilize XA transactions in MySQL-5.0.10 and newer.

- Moved `-bin-g.jar` file into separate `debug` subdirectory to avoid confusion.

- Return original column name for `RSMD.getColumnName()` if the column was aliased, alias name for `.getColumnLabel()` (if aliased), and original table name for `.getTableName()`. Note this only works for MySQL-4.1 and newer, as older servers don't make this information available to clients.

- Setting `useJDBCCompliantTimezoneShift=true` (it's not the default) causes the driver to use GMT for all `TIMESTAMP`/`DATETIME` time zones, and the current VM time zone for any other type that refers to time zones. This feature can not be used when `useTimezone=true` to convert between server and client time zones.

- `PreparedStatement.setString()` didn't work correctly when `sql_mode` on server contained `NO_BACKSLASH_ESCAPES` and no characters that needed escaping were present in the string.

- Add one level of indirection of internal representation of `CallableStatement` parameter metadata to avoid class not found issues on JDK-1.3 for `ParameterMetadata` interface (which doesn't exist prior to JDBC-3.0).

### B.8.3. Changes in MySQL Connector/J 3.1.x

#### B.8.3.1. Changes in MySQL Connector/J 3.1.15 (Not yet released)

Important change: Due to a number of issues with the use of server-side prepared statements, Connector/J 5.0.5 has disabled their use by default. The disabling of server-side prepared statements does not affect the operation of the connector in any way.

To enable server-side prepared statements you must add the following configuration property to your connector string:

    useServerPrepStmts=true

The default value of this property is `false` (that is, Connector/J does not use server-side prepared statements).

Bugs fixed:

- Specifying `US-ASCII` as the character set in a connection to a MySQL 4.1 or newer server does not map correctly. (Bug#24840)

#### B.8.3.2. Changes in MySQL Connector/J 3.1.14 (10-19-2006)

Bugs fixed:

- Check and store value for continueBatchOnError property in constructor of Statements, rather than when executing batches, so that Connections closed out from underneath statements don't cause NullPointerExceptions when it's required to check this property. (Bug#22290)

- Fixed Bug#18258 - DatabaseMetaData.getTables(), columns() with bad catalog parameter threw exception rather than return empty result set (as required by spec). (Bug#22290)

- Driver now sends numeric 1 or 0 for client-prepared statement setBoolean() calls instead of '1' or '0'. (Bug#22290)

- Fixed bug where driver would not advance to next host if roundRobinLoadBalance=true and the last host in the list is down. (Bug#22290)

- Driver issues truncation on write exception when it shouldn't (due to sending big decimal incorrectly to server with server-side prepared statement). (Bug#22290)

- Fixed bug when calling stored functions, where parameters weren't numbered correctly (first parameter is now the return value, subsequent parameters if specified start at index "2"). (Bug#22290)

- Removed logger autodetection altogether, must now specify logger explicitly if you want to use a logger other than one that logs to STDERR. (Bug#21207)

- DDriver throws NPE when tracing prepared statements that have been closed (in asSQL()). (Bug#21207)

- ResultSet.getSomeInteger() doesn't work for BIT(>1). (Bug#21062)

- Escape of quotes in client-side prepared statements parsing not respected. Patch covers more than bug report, including NO_BACKSLASH_ESCAPES being set, and stacked quote characters forms of escaping (that is, '' or ""). (Bug#20888)

- Fixed can't pool server-side prepared statements, exception raised when re-using them. (Bug#20687)

- Fixed Updatable result set that contains a BIT column fails when server-side prepared statements are used. (Bug#20485)

- Fixed updatable result set throws ClassCastException when there is row data and moveToInsertRow() is called. (Bug#20479)

- Fixed ResultSet.getShort() for UNSIGNED TINYINT returns incorrect values when using server-side prepared statements. (Bug#20306)

- ReplicationDriver does not always round-robin load balance depending on URL used for slaves list. (Bug#19993)

- Fixed calling toString() on ResultSetMetaData for driver-generated (that is, from DatabaseMetaData method calls, or from getGeneratedKeys()) result sets would raise a NullPointerException. (Bug#19993)

- Connection fails to localhost when using timeout and IPv6 is configured. (Bug#19726)

- ResultSet.getFloatFromString() can't retrieve values near Float.MIN/MAX_VALUE. (Bug#18880)

- Fixed memory leak with profileSQL=true. (Bug#16987)

- Fixed NullPointerException in MysqlDataSourceFactory due to Reference containing RefAddrs with null content. (Bug#16791)

#### B.8.3.3. Changes in MySQL Connector/J 3.1.13 (26 May 2006)

Bugs fixed:

- `Fixed PreparedStatement.setObject(int, Object, int)` doesn't respect scale of BigDecimals. (Bug#19615)

- Fixed `ResultSet.wasNull()` returns incorrect value when extracting native string from server-side prepared statement generated result set. (Bug#19282)

- Fixed invalid classname returned for `ResultSetMetaData.getColumnClassName()` for `BIGINT type`. (Bug#19282)

- Fixed case where driver wasn't reading server status correctly when fetching server-side prepared statement rows, which in some cases could cause warning counts to be off, or multiple result sets to not be read off the wire. (Bug#19282)

- Fixed data truncation and `getWarnings()` only returns last warning in set. (Bug#18740)

- Fixed aliased column names where length of name > 251 are corrupted. (Bug#18554)

- Improved performance of retrieving `BigDecimal`, `Time`, `Timestamp` and `Date` values from server-side prepared statements by creating fewer short-lived instances of `Strings` when the native type is not an exact match for the requested type. (Bug#18496)

- Added performance feature, re-writing of batched executes for `Statement.executeBatch()` (for all DML statements) and `PreparedStatement.executeBatch()` (for INSERTs with VALUE clauses only). Enable by using "rewriteBatchedStatements=true" in your JDBC URL. (Bug#18041)

- Fixed issue where server-side prepared statements don't cause truncation exceptions to be thrown when truncation happens. (Bug#18041)

- Fixed `CallableStatement.registerOutParameter()` not working when some parameters pre-populated. Still waiting for feedback from JDBC experts group to determine what correct parameter count from `getMetaData()` should be, however. (Bug#17898)

- Fixed calling `clearParameters()` on a closed prepared statement causes NPE. (Bug#17587)

- Map "latin1" on MySQL server to CP1252 for MySQL > 4.1.0. (Bug#17587)

- Added additional accessor and mutator methods on ConnectionProperties so that DataSource users can use same naming as regular URL properties. (Bug#17587)

- Fixed `ResultSet.wasNull()` not always reset correctly for booleans when done via conversion for server-side prepared statements. (Bug#17450)

- Fixed `Statement.getGeneratedKeys()` throws `NullPointerException` when no query has been processed. (Bug#17099)

- Fixed updatable result set doesn't return `AUTO_INCREMENT` values for `insertRow()` when multiple column primary keys are used. (the driver was checking for the existence of single-column primary keys and an autoincrement value > 0 instead of a straightforward `isAutoIncrement()` check). (Bug#16841)

- `DBMD.getColumns()` returns wrong type for `BIT`. (Bug#15854)

- `lib-nodist` directory missing from package breaks out-of-box build. (Bug#15676)

- Fixed issue with `ReplicationConnection` incorrectly copying state, doesn't transfer connection context correctly when transitioning between the same read-only states. (Bug#15570)

- No "dos" character set in MySQL > 4.1.0. (Bug#15544)

- `INOUT` parameter does not store `IN` value. (Bug#15464)

- `PreparedStatement.setObject()` serializes `BigInteger` as object, rather than sending as numeric value (and is thus not complementary to `.getObject()` on an `UNSIGNED LONG` type). (Bug#15383)

- Fixed issue where driver was unable to initialize character set mapping tables. Removed reliance on `.properties` files to hold this information, as it turns out to be too problematic to code around class loader hierarchies that change depending on how an application is deployed. Moved information back into the `CharsetMapping` class. (Bug#14938)

- Exception thrown for new decimal type when using updatable result sets. (Bug#14609)

- Driver now aware of fix for `BIT` type metadata that went into MySQL-5.0.21 for server not reporting length consistently . (Bug#13601)

- Added support for Apache Commons logging, use "com.mysql.jdbc.log.CommonsLogger" as the value for the "logger" configuration property. (Bug#13469)

- Fixed driver trying to call methods that don't exist on older and newer versions of Log4j. The fix is not trying to auto-detect presence of log4j, too many different incompatible versions out there in the wild to do this reliably.

  If you relied on autodetection before, you will need to add "logger=com.mysql.jdbc.log.Log4JLogger" to your JDBC URL to enable Log4J usage, or alternatively use the new "CommonsLogger" class to take care of this. (Bug#13469)

- LogFactory now prepends "com.mysql.jdbc.log" to log class name if it can't be found as-specified. This allows you to use "short names" for the built-in log factories, for example "logger=CommonsLogger" instead of "logger=com.mysql.jdbc.log.CommonsLogger". (Bug#13469)

- `ResultSet.getShort()` for `UNSIGNED TINYINT` returned wrong values. (Bug#11874)

#### B.8.3.4. Changes in MySQL Connector/J 3.1.12 (30 November 2005)

Bugs fixed:

- Process escape tokens in `Connection.prepareStatement(...)`. You can disable this behavior by setting the JDBC URL configuration property `processEscapeCodesForPrepStmts` to `false`. (Bug#15141)

- Usage advisor complains about unreferenced columns, even though they've been referenced. (Bug#15065)

- Driver incorrectly closes streams passed as arguments to `PreparedStatements`. Reverts to legacy behavior by setting the JDBC configuration property `autoClosePStmtStreams` to `true` (also included in the 3-0-Compat configuration “bundle”). (Bug#15024)

- Deadlock while closing server-side prepared statements from multiple threads sharing one connection. (Bug#14972)

- Unable to initialize character set mapping tables (due to J2EE classloader differences). (Bug#14938)

- Escape processor replaces quote character in quoted string with string delimiter. (Bug#14909)

- `DatabaseMetaData.getColumns()` doesn't return `TABLE_NAME` correctly. (Bug#14815)

- `storesMixedCaseIdentifiers()` returns `false` (Bug#14562)

- `storesLowerCaseIdentifiers()` returns `true` (Bug#14562)

- `storesMixedCaseQuotedIdentifiers()` returns `false` (Bug#14562)

- `storesMixedCaseQuotedIdentifiers()` returns `true` (Bug#14562)

- If `lower_case_table_names=0` (on server):

  - `storesLowerCaseIdentifiers()` returns `false`

  - `storesLowerCaseQuotedIdentifiers()` returns `false`

  - `storesMixedCaseIdentifiers()` returns `true`

  - `storesMixedCaseQuotedIdentifiers()` returns `true`

  - `storesUpperCaseIdentifiers()` returns `false`

  - `storesUpperCaseQuotedIdentifiers()` returns `true`

  (Bug#14562)

- `storesUpperCaseIdentifiers()` returns `false` (Bug#14562)

- `storesUpperCaseQuotedIdentifiers()` returns `true` (Bug#14562)

- If `lower_case_table_names=1` (on server):

  - `storesLowerCaseIdentifiers()` returns `true`

  - `storesLowerCaseQuotedIdentifiers()` returns `true`

  - `storesMixedCaseIdentifiers()` returns `false`

  - `storesMixedCaseQuotedIdentifiers()` returns `false`

  - `storesUpperCaseIdentifiers()` returns `false`

  - `storesUpperCaseQuotedIdentifiers()` returns `true`

  (Bug#14562)

- `storesLowerCaseQuotedIdentifiers()` returns `true` (Bug#14562)

- Fixed `DatabaseMetaData.stores*Identifiers()`:

  - If `lower_case_table_names=0` (on server):

    - `storesLowerCaseIdentifiers()` returns `false`

    - `storesLowerCaseQuotedIdentifiers()` returns `false`

    - `storesMixedCaseIdentifiers()` returns `true`

    - `storesMixedCaseQuotedIdentifiers()` returns `true`

    - `storesUpperCaseIdentifiers()` returns `false`

    - `storesUpperCaseQuotedIdentifiers()` returns `true`

  - If `lower_case_table_names=1` (on server):

    - `storesLowerCaseIdentifiers()` returns `true`

    - `storesLowerCaseQuotedIdentifiers()` returns `true`

    - `storesMixedCaseIdentifiers()` returns `false`

    - `storesMixedCaseQuotedIdentifiers()` returns `false`

    - `storesUpperCaseIdentifiers()` returns `false`

    - `storesUpperCaseQuotedIdentifiers()` returns `true`

  (Bug#14562)

- `storesMixedCaseIdentifiers()` returns `true` (Bug#14562)

- `storesLowerCaseQuotedIdentifiers()` returns `false` (Bug#14562)

- Java type conversion may be incorrect for `MEDIUMINT`. (Bug#14562)

- `storesLowerCaseIdentifiers()` returns `false` (Bug#14562)

- Added configuration property `useGmtMillisForDatetimes` which when set to `true` causes `ResultSet.getDate()`, `.getTimestamp()` to return correct millis-since GMT when `.getTime()` is called on the return value (currently default is `false` for legacy behavior). (Bug#14562)

- Extraneous sleep on `autoReconnect`. (Bug#13775)

- Reconnect during middle of `executeBatch()` should not occur if `autoReconnect` is enabled. (Bug#13255)

- `maxQuerySizeToLog` is not respected. Added logging of bound values for `execute()` phase of server-side prepared statements when `profileSQL=true` as well. (Bug#13048)

- OpenOffice expects `DBMD.supportsIntegrityEnhancementFacility()` to return `true` if foreign keys are supported by the datasource, even though this method also covers support for check constraints, which MySQL doesn't have. Setting the configuration property `overrideSupportsIntegrityEnhancementFacility` to `true` causes the driver to return `true` for this method. (Bug#12975)

- Added `com.mysql.jdbc.testsuite.url.default` system property to set default JDBC url for testsuite (to speed up bug resolution when I'm working in Eclipse). (Bug#12975)

- `logSlowQueries` should give better info. (Bug#12230)

- Don't increase timeout for failover/reconnect. (Bug#6577)

- Fixed client-side prepared statement bug with embedded `?` characters inside quoted identifiers (it was recognized as a placeholder, when it was not).

- Don't allow `executeBatch()` for `CallableStatements` with registered `OUT`/`INOUT` parameters (JDBC compliance).

- Fall back to platform-encoding for `URLDecoder.decode()` when parsing driver URL properties if the platform doesn't have a two-argument version of this method.

#### B.8.3.5. Changes in MySQL Connector/J 3.1.11 (07 October 2005)

Bugs fixed:

- The configuration property `sessionVariables` now allows you to specify variables that start with the “`@`” sign. (Bug#13453)

- URL configuration parameters don't allow “`&`” or “`=`” in their values. The JDBC driver now parses configuration parameters as if they are encoded using the application/x-www-form-urlencoded format as specified by `java.net.URLDecoder` (http://java.sun.com/j2se/1.5.0/docs/api/java/net/URLDecoder.html).

  If the “`%`” character is present in a configuration property, it must now be represented as `%25`, which is the encoded form of “`%`” when using application/x-www-form-urlencoded encoding. (Bug#13453)

- Workaround for Bug#13374: `ResultSet.getStatement()` on closed result set returns `NULL` (as per JDBC 4.0 spec, but not backward-compatible). Set the connection property `retainStatementAfterResultSetClose` to `true` to be able to retrieve a `ResultSet`'s statement after the `ResultSet` has been closed via `.getStatement()` (the default is `false`, to be JDBC-compliant and to reduce the chance that code using JDBC leaks `Statement` instances). (Bug#13277)

- `ResultSetMetaData` from `Statement.getGeneratedKeys()` caused a `NullPointerException` to be thrown whenever a method that required a connection reference was called. (Bug#13277)

- Backport of `VAR[BINARY|CHAR] [BINARY]` types detection from 5.0 branch. (Bug#13277)

- Fixed `NullPointerException` when converting `catalog` parameter in many `DatabaseMetaDataMethods` to `byte[]`s (for the result set) when the parameter is `null`. (`null` isn't technically allowed by the JDBC specification, but we've historically allowed it). (Bug#13277)

- Backport of `Field` class, `ResultSetMetaData.getColumnClassName()`, and `ResultSet.getObject(int)` changes from 5.0 branch to fix behavior surrounding `VARCHAR BINARY`/`VARBINARY` and related types. (Bug#13277)

- Read response in `MysqlIO.sendFileToServer()`, even if the local file can't be opened, otherwise next query issued will fail, because it's reading the response to the empty `LOAD DATA INFILE` packet sent to the server. (Bug#13277)

- When `gatherPerfMetrics` is enabled for servers older than 4.1.0, a `NullPointerException` is thrown from the constructor of `ResultSet` if the query doesn't use any tables. (Bug#13043)

- `java.sql.Types.OTHER` returned for `BINARY` and `VARBINARY` columns when using `DatabaseMetaData.getColumns()`. (Bug#12970)

- `ServerPreparedStatement.getBinding()` now checks if the statement is closed before attempting to reference the list of parameter bindings, to avoid throwing a `NullPointerException`. (Bug#12970)

- Tokenizer for `=` in URL properties was causing `sessionVariables=....` to be parameterized incorrectly. (Bug#12753)

- `cp1251` incorrectly mapped to `win1251` for servers newer than 4.0.x. (Bug#12752)

- `getExportedKeys()` (Bug#12541)

- Specifying a catalog works as stated in the API docs. (Bug#12541)

- Specifying `NULL` means that catalog will not be used to filter the results (thus all databases will be searched), unless you've set `nullCatalogMeansCurrent=true` in your JDBC URL properties. (Bug#12541)

- `getIndexInfo()` (Bug#12541)

- `getProcedures()` (and thus indirectly `getProcedureColumns()`) (Bug#12541)

- `getImportedKeys()` (Bug#12541)

- Specifying `""` means “current” catalog, even though this isn't quite JDBC spec compliant, it's there for legacy users. (Bug#12541)

- `getCrossReference()` (Bug#12541)

- Added `Connection.isMasterConnection()` for clients to be able to determine if a multi-host master/slave connection is connected to the first host in the list. (Bug#12541)

- `getColumns()` (Bug#12541)

- Handling of catalog argument in `DatabaseMetaData.getIndexInfo()`, which also means changes to the following methods in `DatabaseMetaData`:

  - `getBestRowIdentifier()`

  - `getColumns()`

  - `getCrossReference()`

  - `getExportedKeys()`

  - `getImportedKeys()`

  - `getIndexInfo()`

  - `getPrimaryKeys()`

  - `getProcedures()` (and thus indirectly `getProcedureColumns()`)

  - `getTables()`

  The `catalog` argument in all of these methods now behaves in the following way:

  - Specifying `NULL` means that catalog will not be used to filter the results (thus all databases will be searched), unless you've set `nullCatalogMeansCurrent=true` in your JDBC URL properties.

  - Specifying `""` means “current” catalog, even though this isn't quite JDBC spec compliant, it's there for legacy users.

  - Specifying a catalog works as stated in the API docs.

  - Made `Connection.clientPrepare()` available from “wrapped” connections in the `jdbc2.optional` package (connections built by `ConnectionPoolDataSource` instances).

  (Bug#12541)

- `getBestRowIdentifier()` (Bug#12541)

- Made `Connection.clientPrepare()` available from “wrapped” connections in the `jdbc2.optional` package (connections built by `ConnectionPoolDataSource` instances). (Bug#12541)

- `getTables()` (Bug#12541)

- `getPrimaryKeys()` (Bug#12541)

- `Connection.prepareCall()` is database name case-sensitive (on Windows systems). (Bug#12417)

- `explainSlowQueries` hangs with server-side prepared statements. (Bug#12229)

- Properties shared between master and slave with replication connection. (Bug#12218)

- Geometry types not handled with server-side prepared statements. (Bug#12104)

- `maxPerformance.properties` mis-spells “elideSetAutoCommits”. (Bug#11976)

- `ReplicationConnection` won't switch to slave, throws “Catalog can't be null” exception. (Bug#11879)

- `Pstmt.setObject(...., Types.BOOLEAN)` throws exception. (Bug#11798)

- Escape tokenizer doesn't respect stacked single quotes for escapes. (Bug#11797)

- `GEOMETRY` type not recognized when using server-side prepared statements. (Bug#11797)

- Foreign key information that is quoted is parsed incorrectly when `DatabaseMetaData` methods use that information. (Bug#11781)

- The `sendBlobChunkSize` property is now clamped to `max_allowed_packet` with consideration of stream buffer size and packet headers to avoid `PacketTooBigExceptions` when `max_allowed_packet` is similar in size to the default `sendBlobChunkSize` which is 1M. (Bug#11781)

- `CallableStatement.clearParameters()` now clears resources associated with `INOUT`/`OUTPUT` parameters as well as `INPUT` parameters. (Bug#11781)

- Fixed regression caused by fix for Bug#11552 that caused driver to return incorrect values for unsigned integers when those integers where within the range of the positive signed type. (Bug#11663)

- Moved source code to Subversion repository. (Bug#11663)

- Incorrect generation of testcase scripts for server-side prepared statements. (Bug#11663)

- Fixed statements generated for testcases missing `;` for “plain” statements. (Bug#11629)

- Spurious `!` on console when character encoding is `utf8`. (Bug#11629)

- `StringUtils.getBytes()` doesn't work when using multi-byte character encodings and a length in characters is specified. (Bug#11614)

- `DBMD.storesLower/Mixed/UpperIdentifiers()` reports incorrect values for servers deployed on Windows. (Bug#11575)

- Reworked `Field` class, `*Buffer`, and `MysqlIO` to be aware of field lengths > `Integer.MAX_VALUE`. (Bug#11498)

- Escape processor didn't honor strings demarcated with double quotes. (Bug#11498)

- Updated `DBMD.supportsCorrelatedQueries()` to return `true` for versions > 4.1, `supportsGroupByUnrelated()` to return `true` and `getResultSetHoldability()` to return `HOLD_CURSORS_OVER_COMMIT`. (Bug#11498)

- Lifted restriction of changing streaming parameters with server-side prepared statements. As long as `all` streaming parameters were set before execution, `.clearParameters()` does not have to be called. (due to limitation of client/server protocol, prepared statements can not reset individual stream data on the server side). (Bug#11498)

- `ResultSet.moveToCurrentRow()` fails to work when preceded by a call to `ResultSet.moveToInsertRow()`. (Bug#11190)

- `VARBINARY` data corrupted when using server-side prepared statements and `.setBytes()`. (Bug#11115)

- `Statement.getWarnings()` fails with NPE if statement has been closed. (Bug#10630)

- Only get `char[]` from SQL in `PreparedStatement.ParseInfo()` when needed. (Bug#10630)

#### B.8.3.6. Changes in MySQL Connector/J 3.1.10 (23 June 2005)

Bugs fixed:

- Initial implemention of `ParameterMetadata` for `PreparedStatement.getParameterMetadata()`. Only works fully for `CallableStatements`, as current server-side prepared statements return every parameter as a `VARCHAR` type.

- Fixed connecting without a database specified raised an exception in `MysqlIO.changeDatabaseTo()`.

#### B.8.3.7. Changes in MySQL Connector/J 3.1.9 (22 June 2005)

Bugs fixed:

- Production package doesn't include JBoss integration classes. (Bug#11411)

- Removed nonsensical “costly type conversion” warnings when using usage advisor. (Bug#11411)

- Fixed `PreparedStatement.setClob()` not accepting `null` as a parameter. (Bug#11360)

- Connector/J dumping query into `SQLException` twice. (Bug#11360)

- `autoReconnect` ping causes exception on connection startup. (Bug#11259)

- `Connection.setCatalog()` is now aware of the `useLocalSessionState` configuration property, which when set to `true` will prevent the driver from sending `USE ...` to the server if the requested catalog is the same as the current catalog. (Bug#11115)

- `3-0-Compat` — Compatibility with Connector/J 3.0.x functionality (Bug#11115)

- `maxPerformance` — maximum performance without being reckless (Bug#11115)

- `solarisMaxPerformance` — maximum performance for Solaris, avoids syscalls where it can (Bug#11115)

- Added `maintainTimeStats` configuration property (defaults to `true`), which tells the driver whether or not to keep track of the last query time and the last successful packet sent to the server's time. If set to `false`, removes two syscalls per query. (Bug#11115)

- `VARBINARY` data corrupted when using server-side prepared statements and `ResultSet.getBytes()`. (Bug#11115)

- Added the following configuration bundles, use one or many via the `useConfigs` configuration property:

  - `maxPerformance` — maximum performance without being reckless

  - `solarisMaxPerformance` — maximum performance for Solaris, avoids syscalls where it can

  - `3-0-Compat` — Compatibility with Connector/J 3.0.x functionality

  (Bug#11115)

- Try to handle `OutOfMemoryErrors` more gracefully. Although not much can be done, they will in most cases close the connection they happened on so that further operations don't run into a connection in some unknown state. When an OOM has happened, any further operations on the connection will fail with a “Connection closed” exception that will also list the OOM exception as the reason for the implicit connection close event. (Bug#10850)

- Setting `cachePrepStmts=true` now causes the `Connection` to also cache the check the driver performs to determine if a prepared statement can be server-side or not, as well as caches server-side prepared statements for the lifetime of a connection. As before, the `prepStmtCacheSize` parameter controls the size of these caches. (Bug#10850)

- Don't send `COM_RESET_STMT` for each execution of a server-side prepared statement if it isn't required. (Bug#10850)

- 0-length streams not sent to server when using server-side prepared statements. (Bug#10850)

- Driver detects if you're running MySQL-5.0.7 or later, and does not scan for `LIMIT ?[,?]` in statements being prepared, as the server supports those types of queries now. (Bug#10850)

- Reorganized directory layout. Sources now are in `src` folder. Don't pollute parent directory when building, now output goes to `./build`, distribution goes to `./dist`. (Bug#10496)

- Added support/bug hunting feature that generates `.sql` test scripts to `STDERR` when `autoGenerateTestcaseScript` is set to `true`. (Bug#10496)

- `SQLException` is thrown when using property `characterSetResults` with `cp932` or `eucjpms`. (Bug#10496)

- The datatype returned for `TINYINT(1)` columns when `tinyInt1isBit=true` (the default) can be switched between `Types.BOOLEAN` and `Types.BIT` using the new configuration property `transformedBitIsBoolean`, which defaults to `false`. If set to `false` (the default), `DatabaseMetaData.getColumns()` and `ResultSetMetaData.getColumnType()` will return `Types.BOOLEAN` for `TINYINT(1)` columns. If `true`, `Types.BOOLEAN` will be returned instead. Regardless of this configuration property, if `tinyInt1isBit` is enabled, columns with the type `TINYINT(1)` will be returned as `java.lang.Boolean` instances from `ResultSet.getObject(...)`, and `ResultSetMetaData.getColumnClassName()` will return `java.lang.Boolean`. (Bug#10485)

- `SQLException` thrown when retrieving `YEAR(2)` with `ResultSet.getString()`. The driver will now always treat `YEAR` types as `java.sql.Dates` and return the correct values for `getString()`. Alternatively, the `yearIsDateType` connection property can be set to `false` and the values will be treated as `SHORT`s. (Bug#10485)

- Driver doesn't support `{?=CALL(...)}` for calling stored functions. This involved adding support for function retrieval to `DatabaseMetaData.getProcedures()` and `getProcedureColumns()` as well. (Bug#10310)

- Unsigned `SMALLINT` treated as signed for `ResultSet.getInt()`, fixed all cases for `UNSIGNED` integer values and server-side prepared statements, as well as `ResultSet.getObject()` for `UNSIGNED TINYINT`. (Bug#10156)

- Made `ServerPreparedStatement.asSql()` work correctly so auto-explain functionality would work with server-side prepared statements. (Bug#10155)

- Double quotes not recognized when parsing client-side prepared statements. (Bug#10155)

- Made JDBC2-compliant wrappers public in order to allow access to vendor extensions. (Bug#10155)

- `DatabaseMetaData.supportsMultipleOpenResults()` now returns `true`. The driver has supported this for some time, DBMD just missed that fact. (Bug#10155)

- Cleaned up logging of profiler events, moved code to dump a profiler event as a string to `com.mysql.jdbc.log.LogUtils` so that third parties can use it. (Bug#10155)

- Made `enableStreamingResults()` visible on `com.mysql.jdbc.jdbc2.optional.StatementWrapper`. (Bug#10155)

- Actually write manifest file to correct place so it ends up in the binary jar file. (Bug#10144)

- Added `createDatabaseIfNotExist` property (default is `false`), which will cause the driver to ask the server to create the database specified in the URL if it doesn't exist. You must have the appropriate privileges for database creation for this to work. (Bug#10144)

- Memory leak in `ServerPreparedStatement` if `serverPrepare()` fails. (Bug#10144)

- `com.mysql.jdbc.PreparedStatement.ParseInfo` does unnecessary call to `toCharArray()`. (Bug#9064)

- Driver now correctly uses CP932 if available on the server for Windows-31J, CP932 and MS932 java encoding names, otherwise it resorts to SJIS, which is only a close approximation. Currently only MySQL-5.0.3 and newer (and MySQL-4.1.12 or .13, depending on when the character set gets backported) can reliably support any variant of CP932.

- Overhaul of character set configuration, everything now lives in a properties file.

#### B.8.3.8. Changes in MySQL Connector/J 3.1.8 (14 April 2005)

Bugs fixed:

- Should accept `null` for catalog (meaning use current) in DBMD methods, even though it's not JDBC-compliant for legacy's sake. Disable by setting connection property `nullCatalogMeansCurrent` to `false` (which will be the default value in C/J 3.2.x). (Bug#9917)

- Fixed driver not returning `true` for `-1` when `ResultSet.getBoolean()` was called on result sets returned from server-side prepared statements. (Bug#9778)

- Added a `Manifest.MF` file with implementation information to the `.jar` file. (Bug#9778)

- More tests in `Field.isOpaqueBinary()` to distinguish opaque binary (that is, fields with type `CHAR(n)` and `CHARACTER SET BINARY`) from output of various scalar and aggregate functions that return strings. (Bug#9778)

- `DBMD.getTables()` shouldn't return tables if views are asked for, even if the database version doesn't support views. (Bug#9778)

- Should accept `null` for name patterns in DBMD (meaning “`%`”), even though it isn't JDBC compliant, for legacy's sake. Disable by setting connection property `nullNamePatternMatchesAll` to `false` (which will be the default value in C/J 3.2.x). (Bug#9769)

- Then fallback to our `STDERR` logging. (Bug#9704)

- The performance metrics feature now gathers information about number of tables referenced in a SELECT. (Bug#9704)

- The logging system is now automatically configured. If the value has been set by the user, via the URL property `logger` or the system property `com.mysql.jdbc.logger`, then use that, otherwise, autodetect it using the following steps:

  1. Log4j, if it's available,

  2. Then JDK1.4 logging,

  3. Then fallback to our `STDERR` logging.

  (Bug#9704)

- Then JDK1.4 logging, (Bug#9704)

- Log4j, if it's available, (Bug#9704)

- `Statement.getMoreResults()` could throw NPE when existing result set was `.close()`d. (Bug#9704)

- Stored procedures with `DECIMAL` parameters with storage specifications that contained “`,`” in them would fail. (Bug#9682)

- `PreparedStatement.setObject(int, Object, int type, int scale)` now uses scale value for `BigDecimal` instances. (Bug#9682)

- Added support for the c3p0 connection pool's (http://c3p0.sf.net/) validation/connection checker interface which uses the lightweight `COM_PING` call to the server if available. To use it, configure your c3p0 connection pool's `connectionTesterClassName` property to use `com.mysql.jdbc.integration.c3p0.MysqlConnectionTester`. (Bug#9320)

- `PreparedStatement.getMetaData()` inserts blank row in database under certain conditions when not using server-side prepared statements. (Bug#9320)

- Better detection of `LIMIT` inside/outside of quoted strings so that the driver can more correctly determine whether a prepared statement can be prepared on the server or not. (Bug#9320)

- `Connection.canHandleAsPreparedStatement()` now makes “best effort” to distinguish `LIMIT` clauses with placeholders in them from ones without in order to have fewer false positives when generating work-arounds for statements the server cannot currently handle as server-side prepared statements. (Bug#9320)

- Fixed `build.xml` to not compile `log4j` logging if `log4j` not available. (Bug#9320)

- Added finalizers to `ResultSet` and `Statement` implementations to be JDBC spec-compliant, which requires that if not explicitly closed, these resources should be closed upon garbage collection. (Bug#9319)

- Stored procedures with same name in different databases confuse the driver when it tries to determine parameter counts/types. (Bug#9319)

- A continuation of Bug#8868, where functions used in queries that should return non-string types when resolved by temporary tables suddenly become opaque binary strings (work-around for server limitation). Also fixed fields with type of `CHAR(n) CHARACTER SET BINARY` to return correct/matching classes for `RSMD.getColumnClassName()` and `ResultSet.getObject()`. (Bug#9236)

- Cannot use `UTF-8` for characterSetResults configuration property. (Bug#9206)

- `PreparedStatement.addBatch()` doesn't work with server-side prepared statements and streaming `BINARY` data. (Bug#9040)

- `ServerPreparedStatements` now correctly “stream” `BLOB`/`CLOB` data to the server. You can configure the threshold chunk size using the JDBC URL property `blobSendChunkSize` (the default is 1MB). (Bug#8868)

- `DATE_FORMAT()` queries returned as `BLOB`s from `getObject()`. (Bug#8868)

- Server-side session variables can be preset at connection time by passing them as a comma-delimited list for the connection property `sessionVariables`. (Bug#8868)

- `BlobFromLocator` now uses correct identifier quoting when generating prepared statements. (Bug#8868)

- Fixed regression in `ping()` for users using `autoReconnect=true`. (Bug#8868)

- Check for empty strings (`''`) when converting `CHAR`/`VARCHAR` column data to numbers, throw exception if `emptyStringsConvertToZero` configuration property is set to `false` (for backward-compatibility with 3.0, it is now set to `true` by default, but will most likely default to `false` in 3.2). (Bug#8803)

- `DATA_TYPE` column from `DBMD.getBestRowIdentifier()` causes `ArrayIndexOutOfBoundsException` when accessed (and in fact, didn't return any value). (Bug#8803)

- `DBMD.supportsMixedCase*Identifiers()` returns wrong value on servers running on case-sensitive filesystems. (Bug#8800)

- `DBMD.supportsResultSetConcurrency()` not returning `true` for forward-only/read-only result sets (we obviously support this). (Bug#8792)

- Fixed `ResultSet.getTime()` on a `NULL` value for server-side prepared statements throws NPE.

- Made `Connection.ping()` a public method.

- Added support for new precision-math `DECIMAL` type in MySQL 5.0.3 and up.

- Fixed `DatabaseMetaData.getTables()` returning views when they were not asked for as one of the requested table types.

#### B.8.3.9. Changes in MySQL Connector/J 3.1.7 (18 February 2005)

Bugs fixed:

- `PreparedStatements` not creating streaming result sets. (Bug#8487)

- Don't pass `NULL` to `String.valueOf()` in `ResultSet.getNativeConvertToString()`, as it stringifies it (that is, returns `null`), which is not correct for the method in question. (Bug#8487)

- Fixed NPE in `ResultSet.realClose()` when using usage advisor and result set was already closed. (Bug#8428)

- `ResultSet.getString()` doesn't maintain format stored on server, bug fix only enabled when `noDatetimeStringSync` property is set to `true` (the default is `false`). (Bug#8428)

- Added support for `BIT` type in MySQL-5.0.3. The driver will treat `BIT(1-8)` as the JDBC standard `BIT` type (which maps to `java.lang.Boolean`), as the server does not currently send enough information to determine the size of a bitfield when < 9 bits are declared. `BIT(>9)` will be treated as `VARBINARY`, and will return `byte[]` when `getObject()` is called. (Bug#8424)

- Added `useLocalSessionState` configuration property, when set to `true` the JDBC driver trusts that the application is well-behaved and only sets autocommit and transaction isolation levels using the methods provided on `java.sql.Connection`, and therefore can manipulate these values in many cases without incurring round-trips to the database server. (Bug#8424)

- Added `enableStreamingResults()` to `Statement` for connection pool implementations that check `Statement.setFetchSize()` for specification-compliant values. Call `Statement.setFetchSize(>=0)` to disable the streaming results for that statement. (Bug#8424)

- `ResultSet.getBigDecimal()` throws exception when rounding would need to occur to set scale. The driver now chooses a rounding mode of “half up” if non-rounding `BigDecimal.setScale()` fails. (Bug#8424)

- Fixed synchronization issue with `ServerPreparedStatement.serverPrepare()` that could cause deadlocks/crashes if connection was shared between threads. (Bug#8096)

- Emulated locators corrupt binary data when using server-side prepared statements. (Bug#8096)

- Infinite recursion when “falling back” to master in failover configuration. (Bug#7952)

- Disable multi-statements (if enabled) for MySQL-4.1 versions prior to version 4.1.10 if the query cache is enabled, as the server returns wrong results in this configuration. (Bug#7952)

- Removed `dontUnpackBinaryResults` functionality, the driver now always stores results from server-side prepared statements as is from the server and unpacks them on demand. (Bug#7952)

- Fixed duplicated code in `configureClientCharset()` that prevented `useOldUTF8Behavior=true` from working properly. (Bug#7952)

- Added `holdResultsOpenOverStatementClose` property (default is `false`), that keeps result sets open over statement.close() or new execution on same statement (suggested by Kevin Burton). (Bug#7715)

- Detect new `sql_mode` variable in string form (it used to be integer) and adjust quoting method for strings appropriately. (Bug#7715)

- Timestamps converted incorrectly to strings with server-side prepared statements and updatable result sets. (Bug#7715)

- Timestamp key column data needed `_binary` stripped for `UpdatableResultSet.refreshRow()`. (Bug#7686)

- Choose correct “direction” to apply time adjustments when both client and server are in GMT time zone when using `ResultSet.get(..., cal)` and `PreparedStatement.set(...., cal)`. (Bug#4718)

- Remove `_binary` introducer from parameters used as in/out parameters in `CallableStatement`. (Bug#4718)

- Always return `byte[]`s for output parameters registered as `*BINARY`. (Bug#4718)

- By default, the driver now scans SQL you are preparing via all variants of `Connection.prepareStatement()` to determine if it is a supported type of statement to prepare on the server side, and if it is not supported by the server, it instead prepares it as a client-side emulated prepared statement. You can disable this by passing `emulateUnsupportedPstmts=false` in your JDBC URL. (Bug#4718)

- Added `dontTrackOpenResources` option (default is `false`, to be JDBC compliant), which helps with memory use for non-well-behaved apps (that is, applications that don't close `Statement` objects when they should). (Bug#4718)

- Send correct value for “boolean” `true` to server for `PreparedStatement.setObject(n, "true", Types.BIT)`. (Bug#4718)

- Fixed bug with Connection not caching statements from `prepareStatement()` when the statement wasn't a server-side prepared statement. (Bug#4718)

#### B.8.3.10. Changes in MySQL Connector/J 3.1.6 (23 December 2004)

Bugs fixed:

- `DBMD.getProcedures()` doesn't respect catalog parameter. (Bug#7026)

- Fixed hang on `SocketInputStream.read()` with `Statement.setMaxRows()` and multiple result sets when driver has to truncate result set directly, rather than tacking a `LIMIT `n`` on the end of it.

#### B.8.3.11. Changes in MySQL Connector/J 3.1.5 (02 December 2004)

Bugs fixed:

- Use 1MB packet for sending file for `LOAD DATA LOCAL INFILE` if that is < `max_allowed_packet` on server. (Bug#6537)

- `SUM()` on `DECIMAL` with server-side prepared statement ignores scale if zero-padding is needed (this ends up being due to conversion to `DOUBLE` by server, which when converted to a string to parse into `BigDecimal`, loses all “padding” zeros). (Bug#6537)

- Use `DatabaseMetaData.getIdentifierQuoteString()` when building DBMD queries. (Bug#6537)

- Use our own implementation of buffered input streams to get around blocking behavior of `java.io.BufferedInputStream`. Disable this with `useReadAheadInput=false`. (Bug#6399)

- Make auto-deserialization of `java.lang.Objects` stored in `BLOB` columns configurable via `autoDeserialize` property (defaults to `false`). (Bug#6399)

- `ResultSetMetaData.getColumnDisplaySize()` returns incorrect values for multi-byte charsets. (Bug#6399)

- Re-work `Field.isOpaqueBinary()` to detect `CHAR(`n`) CHARACTER SET BINARY` to support fixed-length binary fields for `ResultSet.getObject()`. (Bug#6399)

- Failing to connect to the server when one of the addresses for the given host name is IPV6 (which the server does not yet bind on). The driver now loops through all IP addresses for a given host, and stops on the first one that `accepts()` a `socket.connect()`. (Bug#6348)

- Removed unwanted new `Throwable()` in `ResultSet` constructor due to bad merge (caused a new object instance that was never used for every result set created). Found while profiling for Bug#6359. (Bug#6225)

- `ServerSidePreparedStatement` allocating short-lived objects unnecessarily. (Bug#6225)

- Use null-safe-equals for key comparisons in updatable result sets. (Bug#6225)

- Fixed too-early creation of `StringBuffer` in `EscapeProcessor.escapeSQL()`, also return `String` when escaping not needed (to avoid unnecessary object allocations). Found while profiling for Bug#6359. (Bug#6225)

- `UNSIGNED BIGINT` unpacked incorrectly from server-side prepared statement result sets. (Bug#5729)

- Added experimental configuration property `dontUnpackBinaryResults`, which delays unpacking binary result set values until they're asked for, and only creates object instances for non-numerical values (it is set to `false` by default). For some usecase/jvm combinations, this is friendlier on the garbage collector. (Bug#5706)

- Don't throw exceptions for `Connection.releaseSavepoint()`. (Bug#5706)

- Inefficient detection of pre-existing string instances in `ResultSet.getNativeString()`. (Bug#5706)

- Use a per-session `Calendar` instance by default when decoding dates from `ServerPreparedStatements` (set to old, less performant behavior by setting property `dynamicCalendars=true`). (Bug#5706)

- Fixed batched updates with server prepared statements weren't looking if the types had changed for a given batched set of parameters compared to the previous set, causing the server to return the error “Wrong arguments to mysql_stmt_execute()”. (Bug#5235)

- Handle case when string representation of timestamp contains trailing “`.`” with no numbers following it. (Bug#5235)

- Server-side prepared statements did not honor `zeroDateTimeBehavior` property, and would cause class-cast exceptions when using `ResultSet.getObject()`, as the all-zero string was always returned. (Bug#5235)

- Fix comparisons made between string constants and dynamic strings that are converted with either `toUpperCase()` or `toLowerCase()` to use `Locale.ENGLISH`, as some locales “override” case rules for English. Also use `StringUtils.indexOfIgnoreCase()` instead of `.toUpperCase().indexOf()`, avoids creating a very short-lived transient `String` instance.

#### B.8.3.12. Changes in MySQL Connector/J 3.1.4 (04 September 2004)

Bugs fixed:

- Fixed `ServerPreparedStatement` to read prepared statement metadata off the wire, even though it's currently a placeholder instead of using `MysqlIO.clearInputStream()` which didn't work at various times because data wasn't available to read from the server yet. This fixes sporadic errors users were having with `ServerPreparedStatements` throwing `ArrayIndexOutOfBoundExceptions`. (Bug#5032)

- Added three ways to deal with all-zero datetimes when reading them from a `ResultSet`: `exception` (the default), which throws an `SQLException` with an SQLState of `S1009`; `convertToNull`, which returns `NULL` instead of the date; and `round`, which rounds the date to the nearest closest value which is `'0001-01-01'`. (Bug#5032)

- The driver is more strict about truncation of numerics on `ResultSet.get*()`, and will throw an `SQLException` when truncation is detected. You can disable this by setting `jdbcCompliantTruncation` to `false` (it is enabled by default, as this functionality is required for JDBC compliance). (Bug#5032)

- You can now use URLs in `LOAD DATA LOCAL INFILE` statements, and the driver will use Java's built-in handlers for retreiving the data and sending it to the server. This feature is not enabled by default, you must set the `allowUrlInLocalInfile` connection property to `true`. (Bug#5032)

- `ResultSet.getObject()` doesn't return type `Boolean` for pseudo-bit types from prepared statements on 4.1.x (shortcut for avoiding extra type conversion when using binary-encoded result sets obscured test in `getObject()` for “pseudo” bit type). (Bug#5032)

- Use `com.mysql.jdbc.Message`'s classloader when loading resource bundle, should fix sporadic issues when the caller's classloader can't locate the resource bundle. (Bug#5032)

- `ServerPreparedStatements` dealing with return of `DECIMAL` type don't work. (Bug#5012)

- Track packet sequence numbers if `enablePacketDebug=true`, and throw an exception if packets received out-of-order. (Bug#4689)

- `ResultSet.wasNull()` does not work for primatives if a previous `null` was returned. (Bug#4689)

- Optimized integer number parsing, enable “old” slower integer parsing using JDK classes via `useFastIntParsing=false` property. (Bug#4642)

- Added `useOnlyServerErrorMessages` property, which causes message text in exceptions generated by the server to only contain the text sent by the server (as opposed to the SQLState's “standard” description, followed by the server's error message). This property is set to `true` by default. (Bug#4642)

- `ServerPreparedStatement.execute*()` sometimes threw `ArrayIndexOutOfBoundsException` when unpacking field metadata. (Bug#4642)

- Connector/J 3.1.3 beta does not handle integers correctly (caused by changes to support unsigned reads in `Buffer.readInt()` -> `Buffer.readShort()`). (Bug#4510)

- Added support in `DatabaseMetaData.getTables()` and `getTableTypes()` for views, which are now available in MySQL server 5.0.x. (Bug#4510)

- `ResultSet.getObject()` returns wrong type for strings when using prepared statements. (Bug#4482)

- Calling `MysqlPooledConnection.close()` twice (even though an application error), caused NPE. Fixed. (Bug#4482)

#### B.8.3.13. Changes in MySQL Connector/J 3.1.3 (07 July 2004)

Bugs fixed:

- Support new time zone variables in MySQL-4.1.3 when `useTimezone=true`. (Bug#4311)

- Error in retrieval of `mediumint` column with prepared statements and binary protocol. (Bug#4311)

- Support for unsigned numerics as return types from prepared statements. This also causes a change in `ResultSet.getObject()` for the `bigint unsigned` type, which used to return `BigDecimal` instances, it now returns instances of `java.lang.BigInteger`. (Bug#4311)

- Externalized more messages (on-going effort). (Bug#4119)

- Null bitmask sent for server-side prepared statements was incorrect. (Bug#4119)

- Added constants for MySQL error numbers (publicly accessible, see `com.mysql.jdbc.MysqlErrorNumbers`), and the ability to generate the mappings of vendor error codes to SQLStates that the driver uses (for documentation purposes). (Bug#4119)

- Added packet debuging code (see the `enablePacketDebug` property documentation). (Bug#4119)

- Use SQL Standard SQL states by default, unless `useSqlStateCodes` property is set to `false`. (Bug#4119)

- Mangle output parameter names for `CallableStatements` so they will not clash with user variable names.

- Added support for `INOUT` parameters in `CallableStatements`.

#### B.8.3.14. Changes in MySQL Connector/J 3.1.2 (09 June 2004)

Bugs fixed:

- Don't enable server-side prepared statements for server version 5.0.0 or 5.0.1, as they aren't compatible with the '4.1.2+' style that the driver uses (the driver expects information to come back that isn't there, so it hangs). (Bug#3804)

- `getWarnings()` returns `SQLWarning` instead of `DataTruncation`. (Bug#3804)

- `getProcedureColumns()` doesn't work with wildcards for procedure name. (Bug#3540)

- `getProcedures()` does not return any procedures in result set. (Bug#3539)

- Fixed `DatabaseMetaData.getProcedures()` when run on MySQL-5.0.0 (output of `SHOW PROCEDURE STATUS` changed between 5.0.0 and 5.0.1. (Bug#3520)

- Added `connectionCollation` property to cause driver to issue `set collation_connection=...` query on connection init if default collation for given charset is not appropriate. (Bug#3520)

- `DBMD.getSQLStateType()` returns incorrect value. (Bug#3520)

- Correctly map output parameters to position given in `prepareCall()` versus. order implied during `registerOutParameter()`. (Bug#3146)

- Cleaned up detection of server properties. (Bug#3146)

- Correctly detect initial character set for servers >= 4.1.0. (Bug#3146)

- Support placeholder for parameter metadata for server >= 4.1.2. (Bug#3146)

- Added `gatherPerformanceMetrics` property, along with properties to control when/where this info gets logged (see docs for more info).

- Fixed case when no parameters could cause a `NullPointerException` in `CallableStatement.setOutputParameters()`.

- Enabled callable statement caching via `cacheCallableStmts` property.

- Fixed sending of split packets for large queries, enabled nio ability to send large packets as well.

- Added `.toString()` functionality to `ServerPreparedStatement`, which should help if you're trying to debug a query that is a prepared statement (it shows SQL as the server would process).

- Added `logSlowQueries` property, along with `slowQueriesThresholdMillis` property to control when a query should be considered “slow.”

- Removed wrapping of exceptions in `MysqlIO.changeUser()`.

- Fixed stored procedure parameter parsing info when size was specified for a parameter (for example, `char()`, `varchar()`).

- `ServerPreparedStatements` weren't actually de-allocating server-side resources when `.close()` was called.

- Fixed case when no output parameters specified for a stored procedure caused a bogus query to be issued to retrieve out parameters, leading to a syntax error from the server.

#### B.8.3.15. Changes in MySQL Connector/J 3.1.1 (14 February 2004)

Bugs fixed:

- Use DocBook version of docs for shipped versions of drivers. (Bug#2671)

- `NULL` fields were not being encoded correctly in all cases in server-side prepared statements. (Bug#2671)

- Fixed rare buffer underflow when writing numbers into buffers for sending prepared statement execution requests. (Bug#2671)

- Fixed `ConnectionProperties` that weren't properly exposed via accessors, cleaned up `ConnectionProperties` code. (Bug#2623)

- Class-cast exception when using scrolling result sets and server-side prepared statements. (Bug#2623)

- Merged unbuffered input code from 3.0. (Bug#2623)

- Enabled streaming of result sets from server-side prepared statements. (Bug#2606)

- Server-side prepared statements were not returning datatype `YEAR` correctly. (Bug#2606)

- Fixed charset conversion issue in `getTables()`. (Bug#2502)

- Implemented multiple result sets returned from a statement or stored procedure. (Bug#2502)

- Implemented `Connection.prepareCall()`, and `DatabaseMetaData`. `getProcedures()` and `getProcedureColumns()`. (Bug#2359)

- Merged prepared statement caching, and `.getMetaData()` support from 3.0 branch. (Bug#2359)

- Fixed off-by-1900 error in some cases for years in `TimeUtil.fastDate`/`TimeCreate()` when unpacking results from server-side prepared statements. (Bug#2359)

- Reset `long binary` parameters in `ServerPreparedStatement` when `clearParameters()` is called, by sending `COM_RESET_STMT` to the server. (Bug#2359)

- `NULL` values for numeric types in binary encoded result sets causing `NullPointerExceptions`. (Bug#2359)

- Display where/why a connection was implicitly closed (to aid debugging). (Bug#1673)

- `DatabaseMetaData.getColumns()` is not returning correct column ordinal info for non-`'%'` column name patterns. (Bug#1673)

- Fixed `NullPointerException` in `ServerPreparedStatement.setTimestamp()`, as well as year and month descrepencies in `ServerPreparedStatement.setTimestamp()`, `setDate()`. (Bug#1673)

- Added ability to have multiple database/JVM targets for compliance and regression/unit tests in `build.xml`. (Bug#1673)

- Fixed sending of queries larger than 16M. (Bug#1673)

- Merged fix of datatype mapping from MySQL type `FLOAT` to `java.sql.Types.REAL` from 3.0 branch. (Bug#1673)

- Fixed NPE and year/month bad conversions when accessing some datetime functionality in `ServerPreparedStatements` and their resultant result sets. (Bug#1673)

- Added named and indexed input/output parameter support to `CallableStatement`. MySQL-5.0.x or newer. (Bug#1673)

- `CommunicationsException` implemented, that tries to determine why communications was lost with a server, and displays possible reasons when `.getMessage()` is called. (Bug#1673)

- Detect collation of column for `RSMD.isCaseSensitive()`. (Bug#1673)

- Optimized `Buffer.readLenByteArray()` to return shared empty byte array when length is 0.

- Fix support for table aliases when checking for all primary keys in `UpdatableResultSet`.

- Unpack “unknown” data types from server prepared statements as `Strings`.

- Implemented `Statement.getWarnings()` for MySQL-4.1 and newer (using `SHOW WARNINGS`).

- Ensure that warnings are cleared before executing queries on prepared statements, as-per JDBC spec (now that we support warnings).

- Correctly initialize datasource properties from JNDI Refs, including explicitly specified URLs.

- Implemented long data (Blobs, Clobs, InputStreams, Readers) for server prepared statements.

- Deal with 0-length tokens in `EscapeProcessor` (caused by callable statement escape syntax).

- `DatabaseMetaData` now reports `supportsStoredProcedures()` for MySQL versions >= 5.0.0

- Support for `mysql_change_user()`. See the `changeUser()` method in `com.mysql.jdbc.Connection`.

- Removed `useFastDates` connection property.

- Support for NIO. Use `useNIO=true` on platforms that support NIO.

- Check for closed connection on delete/update/insert row operations in `UpdatableResultSet`.

- Support for transaction savepoints (MySQL >= 4.0.14 or 4.1.1).

- Support “old” `profileSql` capitalization in `ConnectionProperties`. This property is deprecated, you should use `profileSQL` if possible.

- Fixed character encoding issues when converting bytes to ASCII when MySQL doesn't provide the character set, and the JVM is set to a multi-byte encoding (usually affecting retrieval of numeric values).

- Centralized setting of result set type and concurrency.

- Fixed bug with `UpdatableResultSets` not using client-side prepared statements.

- Default result set type changed to `TYPE_FORWARD_ONLY` (JDBC compliance).

- Fixed `IllegalAccessError` to `Calendar.getTimeInMillis()` in `DateTimeValue` (for JDK < 1.4).

- Allow contents of `PreparedStatement.setBlob()` to be retained between calls to `.execute*()`.

- Fixed stack overflow in `Connection.prepareCall()` (bad merge).

- Refactored how connection properties are set and exposed as `DriverPropertyInfo` as well as `Connection` and `DataSource` properties.

- Reduced number of methods called in average query to be more efficient.

- Prepared `Statements` will be re-prepared on auto-reconnect. Any errors encountered are postponed until first attempt to re-execute the re-prepared statement.

#### B.8.3.16. Changes in MySQL Connector/J 3.1.0 (18 February 2003)

Bugs fixed:

- Added `useServerPrepStmts` property (default `false`). The driver will use server-side prepared statements when the server version supports them (4.1 and newer) when this property is set to `true`. It is currently set to `false` by default until all bind/fetch functionality has been implemented. Currently only DML prepared statements are implemented for 4.1 server-side prepared statements.

- Added `requireSSL` property.

- Track open `Statements`, close all when `Connection.close()` is called (JDBC compliance).

### B.8.4. Changes in MySQL Connector/J 3.0.x

#### B.8.4.1. Changes in MySQL Connector/J 3.0.17 (23 June 2005)

Bugs fixed:

- Workaround for server Bug#9098: Default values of `CURRENT_*` for `DATE`, `TIME`, `DATETIME`, and `TIMESTAMP` columns can't be distinguished from `string` values, so `UpdatableResultSet.moveToInsertRow()` generates bad SQL for inserting default values. (Bug#8812)

- `NON_UNIQUE` column from `DBMD.getIndexInfo()` returned inverted value. (Bug#8812)

- `EUCKR` charset is sent as `SET NAMES euc_kr` which MySQL-4.1 and newer doesn't understand. (Bug#8629)

- Added support for the `EUC_JP_Solaris` character encoding, which maps to a MySQL encoding of `eucjpms` (backported from 3.1 branch). This only works on servers that support `eucjpms`, namely 5.0.3 or later. (Bug#8629)

- Use hex escapes for `PreparedStatement.setBytes()` for double-byte charsets including “aliases” `Windows-31J`, `CP934`, `MS932`. (Bug#8629)

- `DatabaseMetaData.supportsSelectForUpdate()` returns correct value based on server version. (Bug#8629)

- Which requires hex escaping of binary data when using multi-byte charsets with prepared statements. (Bug#8064)

- Fixed duplicated code in `configureClientCharset()` that prevented `useOldUTF8Behavior=true` from working properly. (Bug#7952)

- Backported SQLState codes mapping from Connector/J 3.1, enable with `useSqlStateCodes=true` as a connection property, it defaults to `false` in this release, so that we don't break legacy applications (it defaults to `true` starting with Connector/J 3.1). (Bug#7686)

- Timestamp key column data needed `_binary` stripped for `UpdatableResultSet.refreshRow()`. (Bug#7686)

- `MS932`, `SHIFT_JIS`, and `Windows_31J` not recognized as aliases for `sjis`. (Bug#7607)

- Handle streaming result sets with more than 2 billion rows properly by fixing wraparound of row number counter. (Bug#7601)

- `PreparedStatement.fixDecimalExponent()` adding extra `+`, making number unparseable by MySQL server. (Bug#7601)

- Escape sequence {fn convert(..., type)} now supports ODBC-style types that are prepended by `SQL_`. (Bug#7601)

- Statements created from a pooled connection were returning physical connection instead of logical connection when `getConnection()` was called. (Bug#7316)

- Support new protocol type `MYSQL_TYPE_VARCHAR`. (Bug#7081)

- Added `useOldUTF8Behavior`' configuration property, which causes JDBC driver to act like it did with MySQL-4.0.x and earlier when the character encoding is `utf-8` when connected to MySQL-4.1 or newer. (Bug#7081)

- `DatabaseMetaData.getIndexInfo()` ignored `unique` parameter. (Bug#7081)

- `PreparedStatement.fixDecimalExponent()` adding extra `+`, making number unparseable by MySQL server. (Bug#7061)

- `PreparedStatements` don't encode Big5 (and other multi-byte) character sets correctly in static SQL strings. (Bug#7033)

- Connections starting up failed-over (due to down master) never retry master. (Bug#6966)

- Adding `CP943` to aliases for `sjis`. (Bug#6549, Bug#7607)

- `Timestamp`/`Time` conversion goes in the wrong “direction” when `useTimeZone=true` and server time zone differs from client time zone. (Bug#5874)

#### B.8.4.2. Changes in MySQL Connector/J 3.0.16 (15 November 2004)

Bugs fixed:

- Made `TINYINT(1)` -> `BIT`/`Boolean` conversion configurable via `tinyInt1isBit` property (default `true` to be JDBC compliant out of the box). (Bug#5664)

- Off-by-one bug in `Buffer.readString(`string`)`. (Bug#5664)

- `ResultSet.updateByte()` when on insert row throws `ArrayOutOfBoundsException`. (Bug#5664)

- Fixed regression where `useUnbufferedInput` was defaulting to `false`. (Bug#5664)

- `ResultSet.getTimestamp()` on a column with `TIME` in it fails. (Bug#5664)

- Fixed `DatabaseMetaData.getTypes()` returning incorrect (this is, non-negative) scale for the `NUMERIC` type. (Bug#5664)

- Only set `character_set_results` during connection establishment if server version >= 4.1.1. (Bug#5664)

- Fixed `ResultSetMetaData.isReadOnly()` to detect non-writable columns when connected to MySQL-4.1 or newer, based on existence of “original” table and column names.

- Re-issue character set configuration commands when re-using pooled connections and/or `Connection.changeUser()` when connected to MySQL-4.1 or newer.

#### B.8.4.3. Changes in MySQL Connector/J 3.0.15 (04 September 2004)

Bugs fixed:

- `ResultSet.getMetaData()` should not return incorrectly initialized metadata if the result set has been closed, but should instead throw an `SQLException`. Also fixed for `getRow()` and `getWarnings()` and traversal methods by calling `checkClosed()` before operating on instance-level fields that are nullified during `.close()`. (Bug#5069)

- Use `_binary` introducer for `PreparedStatement.setBytes()` and `set*Stream()` when connected to MySQL-4.1.x or newer to avoid misinterpretation during character conversion. (Bug#5069)

- Parse new time zone variables from 4.1.x servers. (Bug#5069)

- `ResultSet` should release `Field[]` instance in `.close()`. (Bug#5022)

- `RSMD.getPrecision()` returning 0 for non-numeric types (should return max length in chars for non-binary types, max length in bytes for binary types). This fix also fixes mapping of `RSMD.getColumnType()` and `RSMD.getColumnTypeName()` for the `BLOB` types based on the length sent from the server (the server doesn't distinguish between `TINYBLOB`, `BLOB`, `MEDIUMBLOB` or `LONGBLOB` at the network protocol level). (Bug#4880)

- “Production” is now “GA” (General Availability) in naming scheme of distributions. (Bug#4860, Bug#4138)

- `DBMD.getColumns()` returns incorrect JDBC type for unsigned columns. This affects type mappings for all numeric types in the `RSMD.getColumnType()` and `RSMD.getColumnTypeNames()` methods as well, to ensure that “like” types from `DBMD.getColumns()` match up with what `RSMD.getColumnType()` and `getColumnTypeNames()` return. (Bug#4860, Bug#4138)

- Calling `.close()` twice on a `PooledConnection` causes NPE. (Bug#4808)

- `DOUBLE` mapped twice in `DBMD.getTypeInfo()`. (Bug#4742)

- Added FLOSS license exemption. (Bug#4742)

- Removed redundant calls to `checkRowPos()` in `ResultSet`. (Bug#4334)

- Failover for `autoReconnect` not using port numbers for any hosts, and not retrying all hosts.

  ### Warning

  This required a change to the `SocketFactory` `connect()` method signature, which is now `public Socket connect(String host, int portNumber, Properties props)`; therefore, any third-party socket factories will have to be changed to support this signature.

  (Bug#4334)

- Logical connections created by `MysqlConnectionPoolDataSource` will now issue a `rollback()` when they are closed and sent back to the pool. If your application server/connection pool already does this for you, you can set the `rollbackOnPooledClose` property to `false` to avoid the overhead of an extra `rollback()`. (Bug#4334)

- `StringUtils.escapeEasternUnicodeByteStream` was still broken for GBK. (Bug#4010)

#### B.8.4.4. Changes in MySQL Connector/J 3.0.14 (28 May 2004)

Bugs fixed:

- Fixed URL parsing error.

#### B.8.4.5. Changes in MySQL Connector/J 3.0.13 (27 May 2004)

Bugs fixed:

- `No Database Selected` when using `MysqlConnectionPoolDataSource`. (Bug#3920)

- `PreparedStatement.getGeneratedKeys()` method returns only 1 result for batched insertions. (Bug#3873)

- Using a `MySQLDatasource` without server name fails. (Bug#3848)

#### B.8.4.6. Changes in MySQL Connector/J 3.0.12 (18 May 2004)

Bugs fixed:

- Inconsistent reporting of data type. The server still doesn't return all types for *BLOBs *TEXT correctly, so the driver won't return those correctly. (Bug#3570)

- `UpdatableResultSet` not picking up default values for `moveToInsertRow()`. (Bug#3557)

- Not specifying database in URL caused `MalformedURL` exception. (Bug#3554)

- Auto-convert MySQL encoding names to Java encoding names if used for `characterEncoding` property. (Bug#3554)

- Use `junit.textui.TestRunner` for all unit tests (to allow them to be run from the command line outside of Ant or Eclipse). (Bug#3554)

- Added encoding names that are recognized on some JVMs to fix case where they were reverse-mapped to MySQL encoding names incorrectly. (Bug#3554)

- Made `StringRegressionTest` 4.1-unicode aware. (Bug#3520)

- Fixed regression in `PreparedStatement.setString()` and eastern character encodings. (Bug#3520)

- `DBMD.getSQLStateType()` returns incorrect value. (Bug#3520)

- Renamed `StringUtils.escapeSJISByteStream()` to more appropriate `escapeEasternUnicodeByteStream()`. (Bug#3511)

- `StringUtils.escapeSJISByteStream()` not covering all eastern double-byte charsets correctly. (Bug#3511)

- Return creating statement for `ResultSets` created by `getGeneratedKeys()`. (Bug#2957)

- Use `SET character_set_results` during initialization to allow any charset to be returned to the driver for result sets. (Bug#2670)

- Don't truncate `BLOB` or `CLOB` values when using `setBytes()` and/or `setBinary/CharacterStream()`. . (Bug#2670)

- Dynamically configure character set mappings for field-level character sets on MySQL-4.1.0 and newer using `SHOW COLLATION` when connecting. (Bug#2670)

- Map `binary` character set to `US-ASCII` to support `DATETIME` charset recognition for servers >= 4.1.2. (Bug#2670)

- Use `charsetnr` returned during connect to encode queries before issuing `SET NAMES` on MySQL >= 4.1.0. (Bug#2670)

- Add helper methods to `ResultSetMetaData` (`getColumnCharacterEncoding()` and `getColumnCharacterSet()`) to allow end-users to see what charset the driver thinks it should be using for the column. (Bug#2670)

- Only set `character_set_results` for MySQL >= 4.1.0. (Bug#2670)

- Allow `url` parameter for `MysqlDataSource` and `MysqlConnectionPool` `DataSource` so that passing of other properties is possible from inside appservers.

- Don't escape SJIS/GBK/BIG5 when using MySQL-4.1 or newer.

- Backport documentation tooling from 3.1 branch.

- Added `failOverReadOnly` property, to allow end-user to configure state of connection (read-only/writable) when failed over.

- Allow `java.util.Date` to be sent in as parameter to `PreparedStatement.setObject()`, converting it to a `Timestamp` to maintain full precision. . (Bug#103)

- Add unsigned attribute to `DatabaseMetaData.getColumns()` output in the `TYPE_NAME` column.

- Map duplicate key and foreign key errors to SQLState of `23000`.

- Backported “change user” and “reset server state” functionality from 3.1 branch, to allow clients of `MysqlConnectionPoolDataSource` to reset server state on `getConnection()` on a pooled connection.

#### B.8.4.7. Changes in MySQL Connector/J 3.0.11 (19 February 2004)

Bugs fixed:

- Return `java.lang.Double` for `FLOAT` type from `ResultSetMetaData.getColumnClassName()`. (Bug#2855)

- Return `[B` instead of `java.lang.Object` for `BINARY`, `VARBINARY` and `LONGVARBINARY` types from `ResultSetMetaData.getColumnClassName()` (JDBC compliance). (Bug#2855)

- Issue connection events on all instances created from a `ConnectionPoolDataSource`. (Bug#2855)

- Return `java.lang.Integer` for `TINYINT` and `SMALLINT` types from `ResultSetMetaData.getColumnClassName()`. (Bug#2852)

- Added `useUnbufferedInput` parameter, and now use it by default (due to JVM issue http://developer.java.sun.com/developer/bugParade/bugs/4401235.html) (Bug#2578)

- Fixed failover always going to last host in list. (Bug#2578)

- Detect `on`/`off` or `1`, `2`, `3` form of `lower_case_table_names` value on server. (Bug#2578)

- `AutoReconnect` time was growing faster than exponentially. (Bug#2447)

- Trigger a `SET NAMES utf8` when encoding is forced to `utf8` or `utf-8` via the `characterEncoding` property. Previously, only the Java-style encoding name of `utf-8` would trigger this.

#### B.8.4.8. Changes in MySQL Connector/J 3.0.10 (13 January 2004)

Bugs fixed:

- Enable caching of the parsing stage of prepared statements via the `cachePrepStmts`, `prepStmtCacheSize`, and `prepStmtCacheSqlLimit` properties (disabled by default). (Bug#2006)

- Fixed security exception when used in Applets (applets can't read the system property `file.encoding` which is needed for `LOAD DATA LOCAL INFILE`). (Bug#2006)

- Speed up parsing of `PreparedStatements`, try to use one-pass whenever possible. (Bug#2006)

- Fixed exception `Unknown character set 'danish'` on connect with JDK-1.4.0 (Bug#2006)

- Fixed mappings in SQLError to report deadlocks with SQLStates of `41000`. (Bug#2006)

- Removed static synchronization bottleneck from instance factory method of `SingleByteCharsetConverter`. (Bug#2006)

- Removed static synchronization bottleneck from `PreparedStatement.setTimestamp()`. (Bug#2006)

- `ResultSet.findColumn()` should use first matching column name when there are duplicate column names in `SELECT` query (JDBC-compliance). (Bug#2006)

- `maxRows` property would affect internal statements, so check it for all statement creation internal to the driver, and set to 0 when it is not. (Bug#2006)

- Use constants for SQLStates. (Bug#2006)

- Map charset `ko18_ru` to `ko18r` when connected to MySQL-4.1.0 or newer. (Bug#2006)

- Ensure that `Buffer.writeString()` saves room for the `\0`. (Bug#2006)

- `ArrayIndexOutOfBounds` when parameter number == number of parameters + 1. (Bug#1958)

- Connection property `maxRows` not honored. (Bug#1933)

- Statements being created too many times in `DBMD.extractForeignKeyFromCreateTable()`. (Bug#1925)

- Support escape sequence {fn convert ... }. (Bug#1914)

- Implement `ResultSet.updateClob()`. (Bug#1913)

- Autoreconnect code didn't set catalog upon reconnect if it had been changed. (Bug#1913)

- `ResultSet.getObject()` on `TINYINT` and `SMALLINT` columns should return Java type `Integer`. (Bug#1913)

- Added more descriptive error message `Server Configuration Denies Access to DataSource`, as well as retrieval of message from server. (Bug#1913)

- `ResultSetMetaData.isCaseSensitive()` returned wrong value for `CHAR`/`VARCHAR` columns. (Bug#1913)

- Added `alwaysClearStream` connection property, which causes the driver to always empty any remaining data on the input stream before each query. (Bug#1913)

- `DatabaseMetaData.getSystemFunction()` returning bad function `VResultsSion`. (Bug#1775)

- Foreign Keys column sequence is not consistent in `DatabaseMetaData.getImported/Exported/CrossReference()`. (Bug#1731)

- Fix for `ArrayIndexOutOfBounds` exception when using `Statement.setMaxRows()`. (Bug#1695)

- Subsequent call to `ResultSet.updateFoo()` causes NPE if result set is not updatable. (Bug#1630)

- Fix for 4.1.1-style authentication with no password. (Bug#1630)

- Cross-database updatable result sets are not checked for updatability correctly. (Bug#1592)

- `DatabaseMetaData.getColumns()` should return `Types.LONGVARCHAR` for MySQL `LONGTEXT` type. (Bug#1592)

- Fixed regression of `Statement.getGeneratedKeys()` and `REPLACE` statements. (Bug#1576)

- Barge blobs and split packets not being read correctly. (Bug#1576)

- Backported fix for aliased tables and `UpdatableResultSets` in `checkUpdatability()` method from 3.1 branch. (Bug#1534)

- “Friendlier” exception message for `PacketTooLargeException`. (Bug#1534)

- Don't count quoted IDs when inside a 'string' in `PreparedStatement` parsing. (Bug#1511)

#### B.8.4.9. Changes in MySQL Connector/J 3.0.9 (07 October 2003)

Bugs fixed:

- `ResultSet.get/setString` mashing char 127. (Bug#1247)

- Added property to “clobber” streaming results, by setting the `clobberStreamingResults` property to `true` (the default is `false`). This will cause a “streaming” `ResultSet` to be automatically closed, and any oustanding data still streaming from the server to be discarded if another query is executed before all the data has been read from the server. (Bug#1247)

- Added `com.mysql.jdbc.util.BaseBugReport` to help creation of testcases for bug reports. (Bug#1247)

- Backported authentication changes for 4.1.1 and newer from 3.1 branch. (Bug#1247)

- Made `databaseName`, `portNumber`, and `serverName` optional parameters for `MysqlDataSourceFactory`. (Bug#1246)

- Optimized `CLOB.setChracterStream()`. (Bug#1131)

- Fixed `CLOB.truncate()`. (Bug#1130)

- Fixed deadlock issue with `Statement.setMaxRows()`. (Bug#1099)

- `DatabaseMetaData.getColumns()` getting confused about the keyword “set” in character columns. (Bug#1099)

- Clip +/- INF (to smallest and largest representative values for the type in MySQL) and NaN (to 0) for `setDouble`/`setFloat()`, and issue a warning on the statement when the server does not support +/- INF or NaN. (Bug#884)

- Don't fire connection closed events when closing pooled connections, or on `PooledConnection.getConnection()` with already open connections. (Bug#884)

- Double-escaping of `'\'` when charset is SJIS or GBK and `'\'` appears in non-escaped input. (Bug#879)

- When emptying input stream of unused rows for “streaming” result sets, have the current thread `yield()` every 100 rows in order to not monopolize CPU time. (Bug#879)

- Issue exception on `ResultSet.get`XXX`()` on empty result set (wasn't caught in some cases). (Bug#848)

- Don't hide messages from exceptions thrown in I/O layers. (Bug#848)

- Fixed regression in large split-packet handling. (Bug#848)

- Better diagnostic error messages in exceptions for “streaming” result sets. (Bug#848)

- Don't change timestamp TZ twice if `useTimezone==true`. (Bug#774)

- Don't wrap `SQLExceptions` in `RowDataDynamic`. (Bug#688)

- Don't try and reset isolation level on reconnect if MySQL doesn't support them. (Bug#688)

- The `insertRow` in an `UpdatableResultSet` is now loaded with the default column values when `moveToInsertRow()` is called. (Bug#688)

- `DatabaseMetaData.getColumns()` wasn't returning `NULL` for default values that are specified as `NULL`. (Bug#688)

- Change default statement type/concurrency to `TYPE_FORWARD_ONLY` and `CONCUR_READ_ONLY` (spec compliance). (Bug#688)

- Fix `UpdatableResultSet` to return values for `get`XXX`()` when on insert row. (Bug#675)

- Support `InnoDB` contraint names when extracting foreign key information in `DatabaseMetaData` (implementing ideas from Parwinder Sekhon). (Bug#664, Bug#517)

- Backported 4.1 protocol changes from 3.1 branch (server-side SQL states, new field information, larger client capability flags, connect-with-database, and so forth). (Bug#664, Bug#517)

- `refreshRow` didn't work when primary key values contained values that needed to be escaped (they ended up being doubly escaped). (Bug#661)

- Fixed `ResultSet.previous()` behavior to move current position to before result set when on first row of result set. (Bug#496)

- Fixed `Statement` and `PreparedStatement` issuing bogus queries when `setMaxRows()` had been used and a `LIMIT` clause was present in the query. (Bug#496)

- Faster date handling code in `ResultSet` and `PreparedStatement` (no longer uses `Date` methods that synchronize on static calendars).

- Fixed test for end of buffer in `Buffer.readString()`.

#### B.8.4.10. Changes in MySQL Connector/J 3.0.8 (23 May 2003)

Bugs fixed:

- Fixed SJIS encoding bug, thanks to Naoto Sato. (Bug#378)

- Fix problem detecting server character set in some cases. (Bug#378)

- Allow multiple calls to `Statement.close()`. (Bug#378)

- Return correct number of generated keys when using `REPLACE` statements. (Bug#378)

- Unicode character 0xFFFF in a string would cause the driver to throw an `ArrayOutOfBoundsException`. . (Bug#378)

- Fix row data decoding error when using very large packets. (Bug#378)

- Optimized row data decoding. (Bug#378)

- Issue exception when operating on an already closed prepared statement. (Bug#378)

- Optimized usage of `EscapeProcessor`. (Bug#378)

- Use JVM charset with filenames and `LOAD DATA [LOCAL] INFILE`.

- Fix infinite loop with `Connection.cleanup()`.

- Changed Ant target `compile-core` to `compile-driver`, and made testsuite compilation a separate target.

- Fixed result set not getting set for `Statement.executeUpdate()`, which affected `getGeneratedKeys()` and `getUpdateCount()` in some cases.

- Return list of generated keys when using multi-value `INSERTS` with `Statement.getGeneratedKeys()`.

- Allow bogus URLs in `Driver.getPropertyInfo()`.

#### B.8.4.11. Changes in MySQL Connector/J 3.0.7 (08 April 2003)

Bugs fixed:

- Fixed charset issues with database metadata (charset was not getting set correctly).

- You can now toggle profiling on/off using `Connection.setProfileSql(boolean)`.

- 4.1 Column Metadata fixes.

- Fixed `MysqlPooledConnection.close()` calling wrong event type.

- Fixed `StringIndexOutOfBoundsException` in `PreparedStatement.setClob()`.

- `IOExceptions` during a transaction now cause the `Connection` to be closed.

- Remove synchronization from `Driver.connect()` and `Driver.acceptsUrl()`.

- Fixed missing conversion for `YEAR` type in `ResultSetMetaData.getColumnTypeName()`.

- Updatable `ResultSets` can now be created for aliased tables/columns when connected to MySQL-4.1 or newer.

- Fixed `LOAD DATA LOCAL INFILE` bug when file > `max_allowed_packet`.

- Don't pick up indexes that start with `pri` as primary keys for `DBMD.getPrimaryKeys()`.

- Ensure that packet size from `alignPacketSize()` does not exceed `max_allowed_packet` (JVM bug)

- Don't reset `Connection.isReadOnly()` when autoReconnecting.

- Fixed escaping of 0x5c (`'\'`) character for GBK and Big5 charsets.

- Fixed `ResultSet.getTimestamp()` when underlying field is of type `DATE`.

- Throw `SQLExceptions` when trying to do operations on a forcefully closed `Connection` (that is, when a communication link failure occurs).

#### B.8.4.12. Changes in MySQL Connector/J 3.0.6 (18 February 2003)

Bugs fixed:

- Backported 4.1 charset field info changes from Connector/J 3.1.

- Fixed `Statement.setMaxRows()` to stop sending `LIMIT` type queries when not needed (performance).

- Fixed `DBMD.getTypeInfo()` and `DBMD.getColumns()` returning different value for precision in `TEXT` and `BLOB` types.

- Fixed `SQLExceptions` getting swallowed on initial connect.

- Fixed `ResultSetMetaData` to return `""` when catalog not known. Fixes `NullPointerExceptions` with Sun's `CachedRowSet`.

- Allow ignoring of warning for “non transactional tables” during rollback (compliance/usability) by setting `ignoreNonTxTables` property to `true`.

- Clean up `Statement` query/method mismatch tests (that is, `INSERT` not allowed with `.executeQuery()`).

- Fixed `ResultSetMetaData.isWritable()` to return correct value.

- More checks added in `ResultSet` traversal method to catch when in closed state.

- Implemented `Blob.setBytes()`. You still need to pass the resultant `Blob` back into an updatable `ResultSet` or `PreparedStatement` to persist the changes, because MySQL does not support “locators”.

- Add “window” of different `NULL` sorting behavior to `DBMD.nullsAreSortedAtStart` (4.0.2 to 4.0.10, true; otherwise, no).

#### B.8.4.13. Changes in MySQL Connector/J 3.0.5 (22 January 2003)

Bugs fixed:

- Fixed `ResultSet.isBeforeFirst()` for empty result sets.

- Added missing `LONGTEXT` type to `DBMD.getColumns()`.

- Implemented an empty `TypeMap` for `Connection.getTypeMap()` so that some third-party apps work with MySQL (IBM WebSphere 5.0 Connection pool).

- Added update options for foreign key metadata.

- Fixed `Buffer.fastSkipLenString()` causing `ArrayIndexOutOfBounds` exceptions with some queries when unpacking fields.

- Quote table names in `DatabaseMetaData.getColumns()`, `getPrimaryKeys()`, `getIndexInfo()`, `getBestRowIdentifier()`.

- Retrieve `TX_ISOLATION` from database for `Connection.getTransactionIsolation()` when the MySQL version supports it, instead of an instance variable.

- Greatly reduce memory required for `setBinaryStream()` in `PreparedStatements`.

#### B.8.4.14. Changes in MySQL Connector/J 3.0.4 (06 January 2003)

Bugs fixed:

- Streamlined character conversion and `byte[]` handling in `PreparedStatements` for `setByte()`.

- Fixed `PreparedStatement.executeBatch()` parameter overwriting.

- Added quoted identifiers to database names for `Connection.setCatalog`.

- Added support for 4.0.8-style large packets.

- Reduce memory footprint of `PreparedStatements` by sharing outbound packet with `MysqlIO`.

- Added `strictUpdates` property to allow control of amount of checking for “correctness” of updatable result sets. Set this to `false` if you want faster updatable result sets and you know that you create them from `SELECT` statements on tables with primary keys and that you have selected all primary keys in your query.

- Added support for quoted identifiers in `PreparedStatement` parser.

#### B.8.4.15. Changes in MySQL Connector/J 3.0.3 (17 December 2002)

Bugs fixed:

- Allow user to alter behavior of `Statement`/ `PreparedStatement.executeBatch()` via `continueBatchOnError` property (defaults to `true`).

- More robust escape tokenizer: Recognize `--` comments, and allow nested escape sequences (see `testsuite.EscapeProcessingTest`).

- Fixed `Buffer.isLastDataPacket()` for 4.1 and newer servers.

- `NamedPipeSocketFactory` now works (only intended for Windows), see `README` for instructions.

- Changed `charsToByte` in `SingleByteCharConverter` to be non-static.

- Use non-aliased table/column names and database names to fully qualify tables and columns in `UpdatableResultSet` (requires MySQL-4.1 or newer).

- `LOAD DATA LOCAL INFILE ...` now works, if your server is configured to allow it. Can be turned off with the `allowLoadLocalInfile` property (see the `README`).

- Implemented `Connection.nativeSQL()`.

- Fixed `ResultSetMetaData.getColumnTypeName()` returning `BLOB` for `TEXT` and `TEXT` for `BLOB` types.

- Fixed charset handling in `Fields.java`.

- Because of above, implemented `ResultSetMetaData.isAutoIncrement()` to use `Field.isAutoIncrement()`.

- Substitute `'?'` for unknown character conversions in single-byte character sets instead of `'\0'`.

- Added `CLIENT_LONG_FLAG` to be able to get more column flags (`isAutoIncrement()` being the most important).

- Honor `lower_case_table_names` when enabled in the server when doing table name comparisons in `DatabaseMetaData` methods.

- `DBMD.getImported/ExportedKeys()` now handles multiple foreign keys per table.

- More robust implementation of updatable result sets. Checks that all primary keys of the table have been selected.

- Some MySQL-4.1 protocol support (extended field info from selects).

- Check for connection closed in more `Connection` methods (`createStatement`, `prepareStatement`, `setTransactionIsolation`, `setAutoCommit`).

- Fixed `ResultSetMetaData.getPrecision()` returning incorrect values for some floating-point types.

- Changed `SingleByteCharConverter` to use lazy initialization of each converter.

#### B.8.4.16. Changes in MySQL Connector/J 3.0.2 (08 November 2002)

Bugs fixed:

- Implemented `Clob.setString()`.

- Added `com.mysql.jdbc.MiniAdmin` class, which allows you to send `shutdown` command to MySQL server. This is intended to be used when “embedding” Java and MySQL server together in an end-user application.

- Added SSL support. See `README` for information on how to use it.

- All `DBMD` result set columns describing schemas now return `NULL` to be more compliant with the behavior of other JDBC drivers for other database systems (MySQL does not support schemas).

- Use `SHOW CREATE TABLE` when possible for determining foreign key information for `DatabaseMetaData`. Also allows cascade options for `DELETE` information to be returned.

- Implemented `Clob.setCharacterStream()`.

- Failover and `autoReconnect` work only when the connection is in an `autoCommit(false)` state, in order to stay transaction-safe.

- Fixed `DBMD.supportsResultSetConcurrency()` so that it returns `true` for `ResultSet.TYPE_SCROLL_INSENSITIVE` and `ResultSet.CONCUR_READ_ONLY` or `ResultSet.CONCUR_UPDATABLE`.

- Implemented `Clob.setAsciiStream()`.

- Removed duplicate code from `UpdatableResultSet` (it can be inherited from `ResultSet`, the extra code for each method to handle updatability I thought might someday be necessary has not been needed).

- Fixed `UnsupportedEncodingException` thrown when “forcing” a character encoding via properties.

- Fixed incorrect conversion in `ResultSet.getLong()`.

- Implemented `ResultSet.updateBlob()`.

- Removed some not-needed temporary object creation by smarter use of `Strings` in `EscapeProcessor`, `Connection` and `DatabaseMetaData` classes.

- Escape `0x5c` character in strings for the SJIS charset.

- `PreparedStatement` now honors stream lengths in setBinary/Ascii/Character Stream() unless you set the connection property `useStreamLengthsInPrepStmts` to `false`.

- Fixed issue with updatable result sets and `PreparedStatements` not working.

- Fixed start position off-by-1 error in `Clob.getSubString()`.

- Added `connectTimeout` parameter that allows users of JDK-1.4 and newer to specify a maximum time to wait to establish a connection.

- Fixed various non-ASCII character encoding issues.

- Fixed `ResultSet.isLast()` for empty result sets (should return `false`).

- Added driver property `useHostsInPrivileges`. Defaults to `true`. Affects whether or not `@hostname` will be used in `DBMD.getColumn/TablePrivileges`.

- Fixed `ResultSet.setFetchDirection(FETCH_UNKNOWN)`.

- Added `queriesBeforeRetryMaster` property that specifies how many queries to issue when failed over before attempting to reconnect to the master (defaults to 50).

- Fixed issue when calling `Statement.setFetchSize()` when using arbitrary values.

- Properly restore connection properties when autoReconnecting or failing-over, including `autoCommit` state, and isolation level.

- Implemented `Clob.truncate()`.

#### B.8.4.17. Changes in MySQL Connector/J 3.0.1 (21 September 2002)

Bugs fixed:

- Charsets now automatically detected. Optimized code for single-byte character set conversion.

- Fixed `ResultSetMetaData.isSigned()` for `TINYINT` and `BIGINT`.

- Fixed `RowDataStatic.getAt()` off-by-one bug.

- Fixed `ResultSet.getRow()` off-by-one bug.

- Massive code clean-up to follow Java coding conventions (the time had come).

- Implemented `ResultSet.getCharacterStream()`.

- Added limited `Clob` functionality (`ResultSet.getClob()`, `PreparedStatemtent.setClob()`, `PreparedStatement.setObject(Clob)`.

- `Connection.isClosed()` no longer “pings” the server.

- `Connection.close()` issues `rollback()` when `getAutoCommit()` is `false`.

- Added `socketTimeout` parameter to URL.

- Added `LOCAL TEMPORARY` to table types in `DatabaseMetaData.getTableTypes()`.

- Added `paranoid` parameter, which sanitizes error messages by removing “sensitive” information from them (such as hostnames, ports, or usernames), as well as clearing “sensitive” data structures when possible.

#### B.8.4.18. Changes in MySQL Connector/J 3.0.0 (31 July 2002)

Bugs fixed:

- General source-code cleanup.

- The driver now only works with JDK-1.2 or newer.

- Fix and sort primary key names in `DBMetaData` (SF bugs 582086 and 582086).

- `ResultSet.getTimestamp()` now works for `DATE` types (SF bug 559134).

- Float types now reported as `java.sql.Types.FLOAT` (SF bug 579573).

- Support for streaming (row-by-row) result sets (see `README`) Thanks to Doron.

- Testsuite now uses Junit (which you can get from http://www.junit.org.

- JDBC Compliance: Passes all tests besides stored procedure tests.

- `ResultSet.getDate/Time/Timestamp` now recognizes all forms of invalid values that have been set to all zeros by MySQL (SF bug 586058).

- Added multi-host failover support (see `README`).

- Repackaging: New driver name is `com.mysql.jdbc.Driver`, old name still works, though (the driver is now provided by MySQL-AB).

- Support for large packets (new addition to MySQL-4.0 protocol), see `README` for more information.

- Better checking for closed connections in `Statement` and `PreparedStatement`.

- Performance improvements in string handling and field metadata creation (lazily instantiated) contributed by Alex Twisleton-Wykeham-Fiennes.

- JDBC-3.0 functionality including `Statement/PreparedStatement.getGeneratedKeys()` and `ResultSet.getURL()`.

- Overall speed improvements via controlling transient object creation in `MysqlIO` class when reading packets.

- !!! LICENSE CHANGE !!! The driver is now GPL. If you need non-GPL licenses, please contact me `<mark@mysql.com>`.

- Performance enchancements: Driver is now 50–100% faster in most situations, and creates fewer temporary objects.

### B.8.5. Changes in MySQL Connector/J 2.0.x

#### B.8.5.1. Changes in MySQL Connector/J 2.0.14 (16 May 2002)

Bugs fixed:

- `ResultSet.getDouble()` now uses code built into JDK to be more precise (but slower).

- Fixed typo for `relaxAutoCommit` parameter.

- `LogicalHandle.isClosed()` calls through to physical connection.

- Added SQL profiling (to `STDERR`). Set `profileSql=true` in your JDBC URL. See `README` for more information.

- `PreparedStatement` now releases resources on `.close()`. (SF bug 553268)

- More code cleanup.

- Quoted identifiers not used if server version does not support them. Also, if server started with `--ansi` or `--sql-mode=ANSI_QUOTES`, “`"`” will be used as an identifier quote character, otherwise “`'`” will be used.

#### B.8.5.2. Changes in MySQL Connector/J 2.0.13 (24 April 2002)

Bugs fixed:

- Fixed unicode chars being read incorrectly. (SF bug 541088)

- Faster blob escaping for `PrepStmt`.

- Added `setURL()` to `MySQLXADataSource`. (SF bug 546019)

- Added `set`/`getPortNumber()` to `DataSource(s)`. (SF bug 548167)

- `PreparedStatement.toString()` fixed. (SF bug 534026)

- More code cleanup.

- Rudimentary version of `Statement.getGeneratedKeys()` from JDBC-3.0 now implemented (you need to be using JDK-1.4 for this to work, I believe).

- `DBMetaData.getIndexInfo()` - bad PAGES fixed. (SF BUG 542201)

- `ResultSetMetaData.getColumnClassName()` now implemented.

#### B.8.5.3. Changes in MySQL Connector/J 2.0.12 (07 April 2002)

Bugs fixed:

- Fixed `testsuite.Traversal` `afterLast()` bug, thanks to Igor Lastric.

- Added new types to `getTypeInfo()`, fixed existing types thanks to Al Davis and Kid Kalanon.

- Fixed time zone off-by-1-hour bug in `PreparedStatement` (538286, 528785).

- Added identifier quoting to all `DatabaseMetaData` methods that need them (should fix 518108).

- Added support for `BIT` types (51870) to `PreparedStatement`.

- `ResultSet.insertRow()` should now detect auto_increment fields in most cases and use that value in the new row. This detection will not work in multi-valued keys, however, due to the fact that the MySQL protocol does not return this information.

- Relaxed synchronization in all classes, should fix 520615 and 520393.

- `DataSources` - fixed `setUrl` bug (511614, 525565), wrong datasource class name (532816, 528767).

- Added support for `YEAR` type (533556).

- Fixes for `ResultSet` updatability in `PreparedStatement`.

- `ResultSet`: Fixed updatability (values being set to `null` if not updated).

- Added `getTable/ColumnPrivileges()` to DBMD (fixes 484502).

- Added `getIdleFor()` method to `Connection` and `MysqlLogicalHandle`.

- `ResultSet.refreshRow()` implemented.

- Fixed `getRow()` bug (527165) in `ResultSet`.

- General code cleanup.

#### B.8.5.4. Changes in MySQL Connector/J 2.0.11 (27 January 2002)

Bugs fixed:

- Full synchronization of `Statement.java`.

- Fixed missing `DELETE_RULE` value in `DBMD.getImported/ExportedKeys()` and `getCrossReference()`.

- More changes to fix `Unexpected end of input stream` errors when reading `BLOB` values. This should be the last fix.

#### B.8.5.5. Changes in MySQL Connector/J 2.0.10 (24 January 2002)

Bugs fixed:

- Fixed null-pointer-exceptions when using `MysqlConnectionPoolDataSource` with Websphere 4 (bug 505839).

- Fixed spurious `Unexpected end of input stream` errors in `MysqlIO` (bug 507456).

#### B.8.5.6. Changes in MySQL Connector/J 2.0.9 (13 January 2002)

Bugs fixed:

- Fixed extra memory allocation in `MysqlIO.readPacket()` (bug 488663).

- Added detection of network connection being closed when reading packets (thanks to Todd Lizambri).

- Fixed casting bug in `PreparedStatement` (bug 488663).

- `DataSource` implementations moved to `org.gjt.mm.mysql.jdbc2.optional` package, and (initial) implementations of `PooledConnectionDataSource` and `XADataSource` are in place (thanks to Todd Wolff for the implementation and testing of `PooledConnectionDataSource` with IBM WebSphere 4).

- Fixed quoting error with escape processor (bug 486265).

- Removed concatenation support from driver (the `||` operator), as older versions of VisualAge seem to be the only thing that use it, and it conflicts with the logical `||` operator. You will need to start mysqld with the `--ansi` flag to use the `||` operator as concatenation (bug 491680).

- Ant build was corrupting included `jar` files, fixed (bug 487669).

- Report batch update support through `DatabaseMetaData` (bug 495101).

- Implementation of `DatabaseMetaData.getExported/ImportedKeys()` and `getCrossReference()`.

- Fixed off-by-one-hour error in `PreparedStatement.setTimestamp()` (bug 491577).

- Full synchronization on methods modifying instance and class-shared references, driver should be entirely thread-safe now (please let me know if you have problems).

#### B.8.5.7. Changes in MySQL Connector/J 2.0.8 (25 November 2001)

Bugs fixed:

- `XADataSource`/`ConnectionPoolDataSource` code (experimental)

- `DatabaseMetaData.getPrimaryKeys()` and `getBestRowIdentifier()` are now more robust in identifying primary keys (matches regardless of case or abbreviation/full spelling of `Primary Key` in `Key_type` column).

- Batch updates now supported (thanks to some inspiration from Daniel Rall).

- `PreparedStatement.setAnyNumericType()` now handles positive exponents correctly (adds `+` so MySQL can understand it).

#### B.8.5.8. Changes in MySQL Connector/J 2.0.7 (24 October 2001)

Bugs fixed:

- Character sets read from database if `useUnicode=true` and `characterEncoding` is not set. (thanks to Dmitry Vereshchagin)

- Initial transaction isolation level read from database (if avaialable). (thanks to Dmitry Vereshchagin)

- Fixed `PreparedStatement` generating SQL that would end up with syntax errors for some queries.

- `PreparedStatement.setCharacterStream()` now implemented

- Captialize type names when `captializeTypeNames=true` is passed in URL or properties (for WebObjects. (thanks to Anjo Krank)

- `ResultSet.getBlob()` now returns `null` if column value was `null`.

- Fixed `ResultSetMetaData.getPrecision()` returning one less than actual on newer versions of MySQL.

- Fixed dangling socket problem when in high availability (`autoReconnect=true`) mode, and finalizer for `Connection` will close any dangling sockets on GC.

- Fixed time zone issue in `PreparedStatement.setTimestamp()`. (thanks to Erik Olofsson)

- PreparedStatement.setDouble() now uses full-precision doubles (reverting a fix made earlier to truncate them).

- Fixed `DatabaseMetaData.supportsTransactions()`, and `supportsTransactionIsolationLevel()` and `getTypeInfo()` `SQL_DATETIME_SUB` and `SQL_DATA_TYPE` fields not being readable.

- Updatable result sets now correctly handle `NULL` values in fields.

- PreparedStatement.setBoolean() will use 1/0 for values if your MySQL version is 3.21.23 or higher.

- Fixed `ResultSet.isAfterLast()` always returning `false`.

#### B.8.5.9. Changes in MySQL Connector/J 2.0.6 (16 June 2001)

Bugs fixed:

- Fixed `PreparedStatement` parameter checking.

- Fixed case-sensitive column names in `ResultSet.java`.

#### B.8.5.10. Changes in MySQL Connector/J 2.0.5 (13 June 2001)

Bugs fixed:

- `ResultSet.insertRow()` works now, even if not all columns are set (they will be set to `NULL`).

- Added `Byte` to `PreparedStatement.setObject()`.

- Fixed data parsing of `TIMESTAMP` values with 2-digit years.

- Added `ISOLATION` level support to `Connection.setIsolationLevel()`

- `DataBaseMetaData.getCrossReference()` no longer `ArrayIndexOOB`.

- `ResultSet.getBoolean()` now recognizes `-1` as `true`.

- `ResultSet` has +/-Inf/inf support.

- `getObject()` on `ResultSet` correctly does `TINYINT`->`Byte` and `SMALLINT`->`Short`.

- Fixed `ResultSetMetaData.getColumnTypeName` for `TEXT`/`BLOB`.

- Fixed `ArrayIndexOutOfBounds` when sending large `BLOB` queries. (Max size packet was not being set)

- Fixed NPE on `PreparedStatement.executeUpdate()` when all columns have not been set.

- Fixed `ResultSet.getBlob()` `ArrayIndex` out-of-bounds.

#### B.8.5.11. Changes in MySQL Connector/J 2.0.3 (03 December 2000)

Bugs fixed:

- Fixed composite key problem with updatable result sets.

- Faster ASCII string operations.

- Fixed off-by-one error in `java.sql.Blob` implementation code.

- Fixed incorrect detection of `MAX_ALLOWED_PACKET`, so sending large blobs should work now.

- Added detection of -/+INF for doubles.

- Added `ultraDevHack` URL parameter, set to `true` to allow (broken) Macromedia UltraDev to use the driver.

- Implemented `getBigDecimal()` without scale component for JDBC2.

#### B.8.5.12. Changes in MySQL Connector/J 2.0.1 (06 April 2000)

Bugs fixed:

- Columns that are of type `TEXT` now return as `Strings` when you use `getObject()`.

- Cleaned up exception handling when driver connects.

- Fixed `RSMD.isWritable()` returning wrong value. Thanks to Moritz Maass.

- `DatabaseMetaData.getPrimaryKeys()` now works correctly with respect to `key_seq`. Thanks to Brian Slesinsky.

- Fixed many JDBC-2.0 traversal, positioning bugs, especially with respect to empty result sets. Thanks to Ron Smits, Nick Brook, Cessar Garcia and Carlos Martinez.

- No escape processing is done on `PreparedStatements` anymore per JDBC spec.

- Fixed some issues with updatability support in `ResultSet` when using multiple primary keys.

#### B.8.5.13. Changes in MySQL Connector/J 2.0.0pre5 (21 February 2000)

- Fixed Bad Handshake problem.

#### B.8.5.14. Changes in MySQL Connector/J 2.0.0pre4 (10 January 2000)

- Fixes to ResultSet for insertRow() - Thanks to Cesar Garcia

- Fix to Driver to recognize JDBC-2.0 by loading a JDBC-2.0 class, instead of relying on JDK version numbers. Thanks to John Baker.

- Fixed ResultSet to return correct row numbers

- Statement.getUpdateCount() now returns rows matched, instead of rows actually updated, which is more SQL-92 like.

10-29-99

- Statement/PreparedStatement.getMoreResults() bug fixed. Thanks to Noel J. Bergman.

- Added Short as a type to PreparedStatement.setObject(). Thanks to Jeff Crowder

- Driver now automagically configures maximum/preferred packet sizes by querying server.

- Autoreconnect code uses fast ping command if server supports it.

- Fixed various bugs with respect to packet sizing when reading from the server and when alloc'ing to write to the server.

#### B.8.5.15. Changes in MySQL Connector/J 2.0.0pre (17 August 1999)

- Now compiles under JDK-1.2. The driver supports both JDK-1.1 and JDK-1.2 at the same time through a core set of classes. The driver will load the appropriate interface classes at runtime by figuring out which JVM version you are using.

- Fixes for result sets with all nulls in the first row. (Pointed out by Tim Endres)

- Fixes to column numbers in SQLExceptions in ResultSet (Thanks to Blas Rodriguez Somoza)

- The database no longer needs to specified to connect. (Thanks to Christian Motschke)

### B.8.6. Changes in MySQL Connector/J 1.2b (04 July 1999)

- Better Documentation (in progress), in doc/mm.doc/book1.html

- DBMD now allows null for a column name pattern (not in spec), which it changes to '%'.

- DBMD now has correct types/lengths for getXXX().

- ResultSet.getDate(), getTime(), and getTimestamp() fixes. (contributed by Alan Wilken)

- EscapeProcessor now handles \{ \} and { or } inside quotes correctly. (thanks to Alik for some ideas on how to fix it)

- Fixes to properties handling in Connection. (contributed by Juho Tikkala)

- ResultSet.getObject() now returns null for NULL columns in the table, rather than bombing out. (thanks to Ben Grosman)

- ResultSet.getObject() now returns Strings for types from MySQL that it doesn't know about. (Suggested by Chris Perdue)

- Removed DataInput/Output streams, not needed, 1/2 number of method calls per IO operation.

- Use default character encoding if one is not specified. This is a work-around for broken JVMs, because according to spec, EVERY JVM must support "ISO8859_1", but they don't.

- Fixed Connection to use the platform character encoding instead of "ISO8859_1" if one isn't explicitly set. This fixes problems people were having loading the character- converter classes that didn't always exist (JVM bug). (thanks to Fritz Elfert for pointing out this problem)

- Changed MysqlIO to re-use packets where possible to reduce memory usage.

- Fixed escape-processor bugs pertaining to {} inside quotes.

### B.8.7. Changes in MySQL Connector/J 1.2.x and lower

#### B.8.7.1. Changes in MySQL Connector/J 1.2a (14 April 1999)

- Fixed character-set support for non-Javasoft JVMs (thanks to many people for pointing it out)

- Fixed ResultSet.getBoolean() to recognize 'y' & 'n' as well as '1' & '0' as boolean flags. (thanks to Tim Pizey)

- Fixed ResultSet.getTimestamp() to give better performance. (thanks to Richard Swift)

- Fixed getByte() for numeric types. (thanks to Ray Bellis)

- Fixed DatabaseMetaData.getTypeInfo() for DATE type. (thanks to Paul Johnston)

- Fixed EscapeProcessor for "fn" calls. (thanks to Piyush Shah at locomotive.org)

- Fixed EscapeProcessor to not do extraneous work if there are no escape codes. (thanks to Ryan Gustafson)

- Fixed Driver to parse URLs of the form "jdbc:mysql://host:port" (thanks to Richard Lobb)

#### B.8.7.2. Changes in MySQL Connector/J 1.1i (24 March 1999)

- Fixed Timestamps for PreparedStatements

- Fixed null pointer exceptions in RSMD and RS

- Re-compiled with jikes for valid class files (thanks ms!)

#### B.8.7.3. Changes in MySQL Connector/J 1.1h (08 March 1999)

- Fixed escape processor to deal with unmatched { and } (thanks to Craig Coles)

- Fixed escape processor to create more portable (between DATETIME and TIMESTAMP types) representations so that it will work with BETWEEN clauses. (thanks to Craig Longman)

- MysqlIO.quit() now closes the socket connection. Before, after many failed connections some OS's would run out of file descriptors. (thanks to Michael Brinkman)

- Fixed NullPointerException in Driver.getPropertyInfo. (thanks to Dave Potts)

- Fixes to MysqlDefs to allow all *text fields to be retrieved as Strings. (thanks to Chris at Leverage)

- Fixed setDouble in PreparedStatement for large numbers to avoid sending scientific notation to the database. (thanks to J.S. Ferguson)

- Fixed getScale() and getPrecision() in RSMD. (contrib'd by James Klicman)

- Fixed getObject() when field was DECIMAL or NUMERIC (thanks to Bert Hobbs)

- DBMD.getTables() bombed when passed a null table-name pattern. Fixed. (thanks to Richard Lobb)

- Added check for "client not authorized" errors during connect. (thanks to Hannes Wallnoefer)

#### B.8.7.4. Changes in MySQL Connector/J 1.1g (19 February 1999)

- Result set rows are now byte arrays. Blobs and Unicode work bidriectonally now. The useUnicode and encoding options are implemented now.

- Fixes to PreparedStatement to send binary set by setXXXStream to be sent untouched to the MySQL server.

- Fixes to getDriverPropertyInfo().

#### B.8.7.5. Changes in MySQL Connector/J 1.1f (31 December 1998)

- Changed all ResultSet fields to Strings, this should allow Unicode to work, but your JVM must be able to convert between the character sets. This should also make reading data from the server be a bit quicker, because there is now no conversion from StringBuffer to String.

- Changed PreparedStatement.streamToString() to be more efficient (code from Uwe Schaefer).

- URL parsing is more robust (throws SQL exceptions on errors rather than NullPointerExceptions)

- PreparedStatement now can convert Strings to Time/Date values via setObject() (code from Robert Currey).

- IO no longer hangs in Buffer.readInt(), that bug was introduced in 1.1d when changing to all byte-arrays for result sets. (Pointed out by Samo Login)

#### B.8.7.6. Changes in MySQL Connector/J 1.1b (03 November 1998)

- Fixes to DatabaseMetaData to allow both IBM VA and J-Builder to work. Let me know how it goes. (thanks to Jac Kersing)

- Fix to ResultSet.getBoolean() for NULL strings (thanks to Barry Lagerweij)

- Beginning of code cleanup, and formatting. Getting ready to branch this off to a parallel JDBC-2.0 source tree.

- Added "final" modifier to critical sections in MysqlIO and Buffer to allow compiler to inline methods for speed.

9-29-98

- If object references passed to setXXX() in PreparedStatement are null, setNull() is automatically called for you. (Thanks for the suggestion goes to Erik Ostrom)

- setObject() in PreparedStatement will now attempt to write a serialized representation of the object to the database for objects of Types.OTHER and objects of unknown type.

- Util now has a static method readObject() which given a ResultSet and a column index will re-instantiate an object serialized in the above manner.

#### B.8.7.7. Changes in MySQL Connector/J 1.1 (02 September 1998)

- Got rid of "ugly hack" in MysqlIO.nextRow(). Rather than catch an exception, Buffer.isLastDataPacket() was fixed.

- Connection.getCatalog() and Connection.setCatalog() should work now.

- Statement.setMaxRows() works, as well as setting by property maxRows. Statement.setMaxRows() overrides maxRows set via properties or url parameters.

- Automatic re-connection is available. Because it has to "ping" the database before each query, it is turned off by default. To use it, pass in "autoReconnect=true" in the connection URL. You may also change the number of reconnect tries, and the initial timeout value via "maxReconnects=n" (default 3) and "initialTimeout=n" (seconds, default 2) parameters. The timeout is an exponential backoff type of timeout; for example, if you have initial timeout of 2 seconds, and maxReconnects of 3, then the driver will timeout 2 seconds, 4 seconds, then 16 seconds between each re-connection attempt.

#### B.8.7.8. Changes in MySQL Connector/J 1.0 (24 August 1998)

- Fixed handling of blob data in Buffer.java

- Fixed bug with authentication packet being sized too small.

- The JDBC Driver is now under the LPGL

8-14-98

- Fixed Buffer.readLenString() to correctly read data for BLOBS.

- Fixed PreparedStatement.stringToStream to correctly read data for BLOBS.

- Fixed PreparedStatement.setDate() to not add a day. (above fixes thanks to Vincent Partington)

- Added URL parameter parsing (?user=... and so forth).

#### B.8.7.9. Changes in MySQL Connector/J 0.9d (04 August 1998)

- Big news! New package name. Tim Endres from ICE Engineering is starting a new source tree for GNU GPL'd Java software. He's graciously given me the org.gjt.mm package directory to use, so now the driver is in the org.gjt.mm.mysql package scheme. I'm "legal" now. Look for more information on Tim's project soon.

- Now using dynamically sized packets to reduce memory usage when sending commands to the DB.

- Small fixes to getTypeInfo() for parameters, and so forth.

- DatabaseMetaData is now fully implemented. Let me know if these drivers work with the various IDEs out there. I've heard that they're working with JBuilder right now.

- Added JavaDoc documentation to the package.

- Package now available in .zip or .tar.gz.

#### B.8.7.10. Changes in MySQL Connector/J 0.9 (28 July 1998)

- Implemented getTypeInfo(). Connection.rollback() now throws an SQLException per the JDBC spec.

- Added PreparedStatement that supports all JDBC API methods for PreparedStatement including InputStreams. Please check this out and let me know if anything is broken.

- Fixed a bug in ResultSet that would break some queries that only returned 1 row.

- Fixed bugs in DatabaseMetaData.getTables(), DatabaseMetaData.getColumns() and DatabaseMetaData.getCatalogs().

- Added functionality to Statement that allows executeUpdate() to store values for IDs that are automatically generated for AUTO_INCREMENT fields. Basically, after an executeUpdate(), look at the SQLWarnings for warnings like "LAST_INSERTED_ID = 'some number', COMMAND = 'your SQL query'". If you are using AUTO_INCREMENT fields in your tables and are executing a lot of executeUpdate()s on one Statement, be sure to clearWarnings() every so often to save memory.

#### B.8.7.11. Changes in MySQL Connector/J 0.8 (06 July 1998)

- Split MysqlIO and Buffer to separate classes. Some ClassLoaders gave an IllegalAccess error for some fields in those two classes. Now mm.mysql works in applets and all classloaders. Thanks to Joe Ennis <jce@mail.boone.com> for pointing out the problem and working on a fix with me.

#### B.8.7.12. Changes in MySQL Connector/J 0.7 (01 July 1998)

- Fixed DatabaseMetadata problems in getColumns() and bug in switch statement in the Field constructor. Thanks to Costin Manolache <costin@tdiinc.com> for pointing these out.

#### B.8.7.13. Changes in MySQL Connector/J 0.6 (21 May 1998)

- Incorporated efficiency changes from Richard Swift <Richard.Swift@kanatek.ca> in `MysqlIO.java` and `ResultSet.java`:

- We're now 15% faster than gwe's driver.

- Started working on `DatabaseMetaData`.

- The following methods are implemented:

  - `getTables()`

  - `getTableTypes()`

  - `getColumns()`

  - `getCatalogs()`

## B.9. MySQL Connector/MXJ Change History

### B.9.1. Changes in MySQL Connector/MXJ 5.0.6 (04 May 2007)

Bugs fixed:

- Changed tests to shutdown mysqld prior to deleting files.

- Fixed port file to always be writen to datadir.

- Added os.name-os.arch to resource directory mapping properties file.

- Swapped out commercial binaries for v5.0.40.

- Delete `portFile` on shutdown.

- Moved `platform-map.properties` into `db-files.jar`.

- Clarified the startup max wait numbers.

- Updated `build.xml` in preperation for next beta build.

- Removed `use-default-architecture` property replaced.

### B.9.2. Changes in MySQL Connector/MXJ 5.0.5 (14 March 2007)

Bugs fixed:

- Moved `MysqldFactory` to main package.

- Reformatting: Added newlines some files which did not end in them.

- Swapped out commercial binaries for v5.0.36.

- Found and removed dynamic linking in mysql_kill; updated solution.

- Changed protected constructor of `SimpleMysqldDynamicMBean` from taking a `MysqldResource` to taking a `MysqldFactory`, in order to lay groundwork for addressing BUG discovered by Andrew Rubinger. See: MySQL Forums (Actual testing with JBoss, and filing a bug, is still required.)

- `build.xml`: `usage` now slightly more verbose; some reformatting.

- Now incoporates Reggie Bernett's `SafeTerminateProcess` and only calls the unsafe TerminateProcess as a final last resort.

- New windows `kill.exe` fixes bug where mysqld was being force terminated. Issue reported by bruno haleblian and others, see: MySQL Forums.

- Replaced `Boolean.parseBoolean` with JDK 1.4 compliant `valueOf`.

- Changed `connector-mxj.properties` default mysql version to 5.0.37.

- In testing so far mysqld reliably shuts down cleanly much faster.

- Added testcase to `com.mysql.management.jmx.AcceptanceTest` which demonstrats that `dataDir` is a mutable MBean property.

- Updated `build.xml` in prep for next release.

- Changed `SimpleMysqldDynamicMBean` to create `MysqldResource` on demand in order to allow setting of `datadir`. (Rubinger bug groundwork).

- Clarified the synchronization of `MysqldResource` methods.

- `SIGHUP` is replaced with `MySQLShutdown<PID>` event.

- Clarified the immutability of `baseDir`, `dataDir`, `pidFile`, `portFile`.

- Added 5.1.15 binaries to the repository.

- Removed 5.1.14 binaries from the repository.

- Added `getDataDir()` to interface `MysqldResourceI`.

- Added 5.1.14 binaries to repository.

- Replaced windows kill.exe resource with re-written version specific to mysqld.

- Added Patched `StandardSocketFactory` from Connector/J 5-0 HEAD.

- Ensured 5.1.14 compatibility.

- Swapped out gpl binaries for v5.0.37.

- Removed 5.0.22 binaries from the repository.

### B.9.3. Changes in MySQL Connector/MXJ 5.0.4 (28 January 2007)

Bugs fixed:

- Allow multiple calls to start server from URL connection on non-3306 port. (Bug#24004)

- Updated `build.xml` to build to handle with different gpl and commercial mysld version numbers.

- Only populate the options map from the help text if specifically requested or in the MBean case.

- Introduced property for Linux & WinXX to default to 32bit versions.

- Swapped out gpl binaries for v5.0.27.

- Swapped out commercial binaries for v5.0.32.

- Moved mysqld binary resourced into separate jar file NOTICE: `CLASSPATH` will now need to `connector-mxj-db-files.jar`.

- Minor test robustness improvements.

- Moved default version string out of java class into a text editable properties file (`connector-mxj.properties`) in the resources directory.

- Fixed test to be tollerant of `/tmp` being a symlink to `/foo/tmp`.

### B.9.4. Changes in MySQL Connector/MXJ 5.0.3 (24 June 2006)

Bugs fixed:

- Removed unused imports, formatted code, made minor edits to tests.

- Removed "TeeOutputStream" - no longer needed.

- Swapped out the mysqld binaries for MySQL v5.0.22.

### B.9.5. Changes in MySQL Connector/MXJ 5.0.2 (15 June 2006)

Bugs fixed:

- Replaced string parsing with JDBC connection attempt for determining if a mysqld is "ready for connections" `CLASSPATH` will now need to include Connector/J jar.

- "platform" directories replace spaces with underscores

- extracted array and list printing to ListToString utility class

- Swapped out the mysqld binaries for MySQL v5.0.21

- Added trace level logging with Aspect/J. `CLASSPATH` will now need to include `lib/aspectjrt.jar`

- reformatted code

- altered to be "basedir" rather than "port" oriented.

- help parsing test reflects current help options

- insulated users from problems with "." in basedir

- swapped out the mysqld binaries for MySQL v5.0.18

- Made tests more robust be deleting the /tmp/test-c.mxj directory before running tests.

- ServerLauncherSocketFactory.shutdown API change: now takes File parameter (basedir) instead of port.

- socket is now "mysql.sock" in datadir

- added ability to specify "mysql-version" as an url parameter

- Extended timeout for help string parsing, to avoid cases where the help text was getting prematurely flushed, and thus truncated.

- swapped out the mysqld binaries for MySQL v5.0.19

- MysqldResource now tied to dataDir as well as basedir (API CHANGE)

- moved PID file into datadir

- ServerLauncherSocketFactory.shutdown now works across JVMs.

- extracted splitLines(String) to Str utility class

- ServerLauncherSocketFactory.shutdown(port) no longer throws, only reports to System.err

- ServerLauncherSocketFactory now treats URL parameters in the form of `&server.foo=null` as `serverOptionMap.put("foo", null)`

- ServerLauncherSocketFactory.shutdown API change: now takes 2 File parameters (basedir, datadir)

### B.9.6. Changes in MySQL Connector/MXJ 5.0.1 (Never released)

This was an internal only release.

### B.9.7. Changes in MySQL Connector/MXJ 5.0.0 (09 December 2005)

Bugs fixed:

- Removed HelpOptionsParser's need to reference a MysqldResource.

- Reorganized utils into a single "Utils" collaborator.

- Minor test tweaks

- Altered examples and tests to use new Connector/J 5.0 URL syntax for for launching Connector/MXJ ("jdbc:mysql:mxj://")

- Swapped out the mysqld binaries for MySQL v5.0.16.

- Ditched "ClassUtil" (merged with Str).

- Minor refactorings for type casting and exception handling.

## B.10. MySQL Proxy Change History

### B.10.1. Changes in MySQL Proxy 0.6.0 (Not yet released)

Functionality added or changed:

- When using read/write splitting and the `rw-splitting.lua` example script, connecting a second user to the proxy returns an error message. (Bug#30867)

- Added support in `read_query_result()` to overwrite the result-set.

- Added `--no-daemon` and `--pid-file`.

- Added hooks for `read_auth()`, `read_handshake()` and `read_auth_result()`.

- Added handling of `proxy.connection.backend_ndx` in `connect_server()` and `read_query()` to support read/write splitting.

- Added support for `proxy.response.packets`.

- Added testcases.

- Added `--no-proxy` to disable the proxy.

- Added support for listening UNIX sockets.

- Added a global lua-scope `proxy.global.*`.

- Added connection pooling.

Bugs fixed:

- Fixed assertion on `COM_BINLOG_DUMP`. (Bug#29764)

- Fixed assertion on result-packets like `[ field-len | fields | EOF | ERR ]`. (Bug#29732)

- Fixed assertion at login with empty password + empty default db. (Bug#29719)

- Fixed assertion at `COM_SHUTDOWN`. (Bug#29719)

- Fixed crash if `proxy.connection` is used in `connect_server()`.

- Fixed check for `glib2` to require at least 2.6.0.

- Fixed assertion when all backends are down and we try to connect.

- Fixed connection-stalling if `read_query_result()` throws an `assert()`ion.

- Fixed len-encoding on `proxy.resulsets`.

- Fixed compilation on win32.

- Fixed assertion when connecting to the MySQL 6.0.1.

- Fixed decoding of len-encoded ints for 3-byte notation.

- Fixed `inj.resultset.affected_rows` on `SELECT` queries.

- Fixed handling of (SQL) `NULL` in result-sets.

- Fixed mem-leak with `proxy.response.*` is used.

### B.10.2. Changes in MySQL Proxy 0.5.1 (30 June 2007)

Functionality added or changed:

- Added `resultset.affected_rows` and `resultset.insert_id`.

- Changed `--proxy.profiling` to `--proxy-skip-profiling`.

- Added missing dependency to `libmysqlclient-dev` to the INSTALL file.

- Added `inj.query_time` and `inj.response_time` into the lua scripts.

- Added support for pre-4.1 passwords in a 4.1 connection.

- Added script examples for rewriting and injection.

- Added `proxy.VERSION`.

- Added support for UNIX sockets.

- Added protection against duplicate resultsets from a script.

Bugs fixed:

- Fixed mysql check in configure to die when mysql.h isn't detected.

- Fixed handling of duplicate ERR on `COM_CHANGE_USER` in MySQL 5.1.18+.

- Fixed compile error with MySQL 4.1.x on missing COM_STMT_*.

- Fixed crash on fields > 250 bytes when the resultset is inspected.

- Fixed warning if `connect_server()` is not provided.

- Fixed assertion when a error occurs at initial script exec time.

- Fixed assertion when `read_query_result()` is not provided when `PROXY_SEND_QUERY` is used.

### B.10.3. Changes in MySQL Proxy 0.5.0 (19 June 2007)

This is the first beta release.

Bugs fixed:

- Added `automake`/`autoconf` support.

- Added `cmake` support.

Prev |  | Next
Appendix A. Errors, Error Codes, and Common Problems | Home | Appendix C. Limits and Restrictions