Appendix D. MySQL Change History

This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 5.6, which is currently MySQL 5.6.4. We offer a version of the Manual for each series of MySQL releases (5.0, 5.1, and so forth). For information about changes in another release series of the MySQL database software, see the corresponding version of this Manual.

We update this section as we add new features in the 5.6 series, so that everybody can follow the development process.

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

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

D.1. Changes in Release 5.6.x (Development)

D.1.1. Changes in MySQL 5.6.3 (Not yet released)
D.1.2. Changes in MySQL 5.6.2 (11 April 2011)
D.1.3. Changes in MySQL 5.6.1 (Not released Milestone 5)
D.1.4. Changes in MySQL 5.6.0 (Not released Milestone 4)

An overview of features added in MySQL 5.6 can be found here: Section 1.5, “What Is New in MySQL 5.6”. For a full list of changes, please refer to the changelog sections for individual 5.6 releases.

For discussion of upgrade issues that you may encounter for upgrades from MySQL 5.5 to MySQL 5.6, see Section 2.11.1.1, “Upgrading from MySQL 5.5 to 5.6”.

D.1.1. Changes in MySQL 5.6.3 (Not yet released)

Performance Schema Notes

The Performance Schema has these additions:
- The Performance Schema now instruments stages and statements. Stages are steps during the statement-execution process, such as parsing a statement, opening a table, or performing a filesort operation. Stages correspond to the thread states displayed by SHOW PROCESSLIST or that are visible in the INFORMATION_SCHEMA.PROCESSLIST table. Stages begin and end when state values change.
  Within the event hierarchy, wait events nest within stage events, which nest within statement events. To reflect this nesting in wait-event tables such as events_waits_current, the NESTING_EVENT_ID column now can be non-NULL to indicate the EVENT_ID value of the event within which an event is nested, and NESTING_EVENT_TYPE is a new column indicating the type of the nesting event.
  The setup_instruments table now contains instruments with names that begin with stage and statement. Corresponding to these instruments, the setup_timers table now contains rows with NAME values of stage and statement that indicate the unit for stage and statement event timing. The default unit for each is NANOSECOND.
  These new tables store stage and statement events:
  - events_stages_current: Current stage events
  - events_stages_history: The most recent stage events for each thread
  - events_stages_history_long: The most recent stage events overall
  - events_statements_current: Current statement events
  - events_statements_history: The most recent statement events for each thread
  - events_statements_history_long: The most recent statement events overall
  The setup_consumers table now contains consumer values with names corresponding to those table names. These consumers may be used to filter collection of stage and statement events.
  There are also summary tables that provide aggregated stage and statement information.
  Application developers can use statement instrumentation to see in detail the statements generated by an application, and how these statements are executed by the server. Stage instrumentation can be used to focus on particular parts of statements. This information may be useful to change how an application issues queries against the database, to minimize the application footprint on the server, and to improve application performance and scalability.
- The Performance Schema now provides statistics about connections to the server. When a client connects, it does so under a particular user name and from a particular host. The Performance Schema tracks connections per account (user name plus host name) and separately per user name and per host name, using these tables:
  - accounts: Connection statistics per client account
  - hosts: Connection statistics per client host name
  - users: Connection statistics per client user name
  There are also summary tables that provide aggregated connection information.
  It is good security practice to define a dedicated account per application, so that an application is given privileges to perform only those actions that it needs during its operation. This also facilitates monitoring because the information in the connection tables can be used by application developers to see load statistics per application when deploying several applications against a given database server.
- Previously, the setup_objects table could be used only to include patterns specifying which objects to instrument. There was no way to explicitly disable object instrumentation, such as to configure instrumention for all tables except those in a particular database. Now the setup_objects table includes an ENABLED column that indicates whether to instrument matching objects. This feature improves the setup_objects table usability because it permits exclusion patterns.
  The default table contents now include a row that disables instrumentation for tables in the mysql database, which is a change from the previous default object instrumentation. This change is chosen assuming that end users want to instrument application objects, not internal server tables. The change reduces the default Performance Schema overhead because I/O and locks on mysql tables are not instrumented.
  The table also includes rows that disable instrumentation for tables in the INFORMATION_SCHEMA and performance_schema databases. This is not a change in behavior because those tables were not instrumented before. Rather, these rows make the full object instrumentation defaults explicit.
- The Performance Schema now instruments sockets. This enables monitoring of network communication to and from the server. Information collected includes network activity such as socket instances, socket operations, and number of bytes transmitted and received.
  The setup_instruments table now contains instruments with names that begin with wait/io/socket. There is also an idle instrument used for idle events when a socket is waiting for the next request from the client. Corresponding to the latter instrument, the setup_timers table now contains a row with a NAME value of idle that indicates the unit for idle event timing. The default unit is MICROSECOND.
  These new tables contain socket information:
  - socket_instances: A real-time snapshot of the active connections to the MySQL server
  - socket_summary_by_instance: Aggregate timer and byte count statistics generated by the wait/io/socket/* instruments for all socket I/O operations, per socket instance
  - socket_summary_by_event_name: Aggregate timer and byte count statistics generated by the wait/io/socket/* instruments for all socket I/O operations, per socket instrument
  The information in the socket tables can be used by application developers, particularly those developing web-based applications, to assess the volume of network traffic directly attributable to queries generated by their application. This can be particularly useful during development of applications intended for large-scale implementations.
If you upgrade to this release of MySQL from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate these changes into the performance_schema database.
For more information, see Chapter 19, MySQL Performance Schema.

Functionality Added or Changed

Incompatible Change: In the audit plugin interface, the event_class member was removed from the mysql_event_general structure and the calling sequence for the notification function changed. Originally, the second argument was a pointer to the event structure. The function now receives this information as two arguments: an event class number and a pointer to the event. Corresponding to these changes, MYSQL_AUDIT_INTERFACE_VERSION was increased to 0x0300.
The plugin_audit.h header file, and the NULL_AUDIT example plugin in the plugin/audit_null directory have been modified per these changes. See Section 21.2.4.8, “Writing Audit Plugins”.
Important Change: Replication: The RESET SLAVE statement has been extended with an ALL keyword. In addition to deleting the master.info, relay-log.info, and all relay log files, RESET SLAVE ALL also clears all connection information otherwise held in memory following execution of RESET SLAVE. (Bug #11809016)
InnoDB Storage Engine: InnoDB now permits concurrent reads while creating a secondary index. (Bug #11853126)
See also Bug #11751388, Bug #11784056, Bug #11815600.
Replication: MySQL 5.6.1 added timestamps to the error messages shown in the Last_IO_Error and Last_SQL_Error columns of the output of SHOW SLAVE STATUS. Now these timestamps are shown in separate columns of their own, named Last_IO_Error_Timestamp and Last_SQL_Error_Timestamp, respectively. (Bug #11765599, Bug #58584)
See also Bug #43535, Bug #11752361.
Several memory allocation calls were removed, resulting in improved performance. (Bug #12552221)
CMake configuration support on Linux now provides a boolean ENABLE_GCOV option to control whether to include support for gcov. (Bug #12549572)
Replication: BEGIN, COMMIT, and ROLLBACK statements are now cached along with the statements instead of being written when the cache is flushed to the binary log. This change does not affect DDL statements—which are written into the statement cache, then immediately flushed—or Incident events (which, along with Rotate events, are still written directly to the binary log).
Previously, Performance Schema instrumentation for both the binary log and the relay log used these instruments:
```
wait/io/file/sql/binlog 
wait/io/file/sql/binlog_index 
wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_index 
wait/synch/cond/sql/MYSQL_BIN_LOG::update_cond 
```
Now instrumentation for the relay log uses these instruments, which makes it possible to distinguish events for the binary log from those for the relay log:
```
wait/io/file/sql/relaylog 
wait/io/file/sql/relaylog_index 
wait/synch/mutex/sql/MYSQL_RELAY_LOG::LOCK_index 
wait/synch/cond/sql/MYSQL_RELAY_LOG::update_cond 
```
(Bug #59658, Bug #11766528)
A new server option, --plugin-load-add, complements the --plugin-load option. --plugin-load-add adds a plugin or plugins to the set of plugins to be loaded at startup. The argument format is the same as for --plugin-load. --plugin-load-add can be used to avoid specifying a large set of plugins as a single long unwieldy --plugin-load argument.
--plugin-load-add can be given in the absence of --plugin-load, but any instance of --plugin-load-add that appears before --plugin-load. has no effect because --plugin-load resets the set of plugins to load.
This change affects the output of mysqld --verbose --help in that a value for plugin-load is no longer printed. (Bug #59026, Bug #11766001)
When invoked with the --auto-generate-sql option, mysqlslap dropped the schema specified with the --create-schema option at the end of the test run, which may have been unexpected by the user. mysqlslap no longer drops the schema, but has a new --create-and-drop-schema option that both creates and drops a schema. (Bug #58090, Bug #11765157)
The server now exposes SSL certificate expiration dates through the Ssl_server_not_before and Ssl_server_not_after status variables. Both variables have values in ANSI time format (for example, Sep 12 16:22:06 2013 GMT), or are blank for non-SSL connections. (Bug #57648, Bug #11764778)
Previously, TEMPORARY tables created with CREATE TEMPORARY TABLES had the default storage engine unless the definition included an explicit ENGINE option. (The default engine is the value of the default_storage_engine system variable.) Since MySQL 5.5.5, when the default storage engine was changed from the nontransactional MyISAM engine to the transactional InnoDB engine, TEMPORARY tables have incurred the overhead of transactional processing.
To permit the default storage engine for TEMPORARY tables to be set independently of the default engine for permanent tables, the server now supports a default_tmp_storage_engine system variable. For example, to create TEMPORARY tables as nontransactional tables by default, start the server with --default_tmp_storage_engine=MyISAM. The storage engine for TEMPORARY tables can still be specified on an individual basis by including an ENGINE option in table definitions. (Bug #49232, Bug #11757216)
For temporary tables created with the CREATE TEMPORARY TABLE statement, the privilege model has changed.
Previously, the CREATE TEMPORARY TABLES privilege enabled users to create temporary tables with the CREATE TEMPORARY TABLE statement. However, other operations on a temporary table, such as INSERT, UPDATE, or SELECT, required additional privileges for those operations for the database containing the temporary table, or for the nontemporary table of the same name.
To keep privileges for temporary and nontemporary tables separate, a common workaround for this situation was to create a database dedicated to the use of temporary tables. Then for that database, a user could be granted the CREATE TEMPORARY TABLES privilege, along with any other privileges required for temporary table operations done by that user.
Now, the CREATE TEMPORARY TABLES privilege enables users to create temporary tables with CREATE TEMPORARY TABLE, as before. However, after a session has created a temporary table, the server performs no further privilege checks on the table. The creating session can perform any operation on the table, such as DROP TABLE, INSERT, UPDATE, or SELECT.
One implication of this change is that a session can manipulate its temporary tables even if the current user has no privilege to create them. Suppose that the current user does not have the CREATE TEMPORARY TABLES privilege but is able to execute a DEFINER-context stored procedure that executes with the privileges of a user who does have CREATE TEMPORARY TABLES and that creates a temporary table. While the procedure executes, the session uses the privileges of the defining user. After the procedure returns, the effective privileges revert to those of the current user, which can still see the temporary table and perform any operation on it. (Bug #27480, Bug #11746602)
Client programs now display more information for SSL errors to aid in diagnosis and debugging of connection problems. (Bug #21287, Bug #11745920)
A new utility, mysql_plugin, enables MySQL administrators to manage which plugins a MySQL server loads. It provides an alternative to manually specifying the --plugin-load option at server startup or using the INSTALL PLUGIN and UNINSTALL PLUGIN statements at runtime. See Section 4.4.5, “mysql_plugin — Configure MySQL Server Plugins”.
The following items are deprecated and will be removed in a future MySQL release. Where alternatives are shown, applications should be updated to use them.
- The innodb_table_monitor table. Similar information can be obtained from InnoDB INFORMATION_SCHEMA tables. See Section 18.29, “INFORMATION_SCHEMA Tables for InnoDB”.
- The innodb_locks_unsafe_for_binlog system variable.
- The innodb_stats_sample_pages system variable. Use innodb_stats_transient_sample_pages instead.
- The innodb_use_sys_malloc and The innodb_additional_mem_pool_size system variables.
The undocumented --all option for perror has been removed. Also, perror no longer displays messages for BDB error codes.
MySQL now includes support for manipulating IPv6 network addresses and for validating IPv4 and IPv6 addresses:
- The INET6_ATON() and INET6_NTOA() functions convert between string and numeric forms of IPv6 addresses. Because numeric-format IPv6 addresses require more bytes than the largest integer type, the representation uses the VARBINARY data type.
- The IS_IPV4() and IS_IPV6() functions test whether a string value represents a valid IPv4 or IPv6 address. The IS_IPV4_COMPAT() and IS_IPV4_MAPPED() functions test whether a numeric-format value represents a valid IPv4-compatible or IPv4-mapped address.
- No changes were made to the INET_ATON() or INET_NTOA() functions that manipulate IPv4 addresses.
IS_IPV4() is more strict than INET_ATON() about what constitutes a valid IPv4 address, so it may be useful for applications that need to perform strong checks against invalid values. Alternatively, use INET6_ATON() to convert IPv4 addresses to internal form and check for a NULL result (which indicates an invalid address). INET6_ATON() is equally strong as IS_IPV4() about checking IPv4 addresses.
The Windows installer now creates an item in the MySQL menu named MySQL command line client - Unicode. This item invokes the mysql client with properties set to communicate through the console to the MySQL server using Unicode. It passes the --default-character-set=utf8 option to mysql and sets the font to the Lucida Console Unicode-compatible font.
The max_allowed_packet system variable now controls the maximum size of parameter values that can be sent with the mysql_stmt_send_long_data() C API function.
The NULL_AUDIT example plugin in the plugin/audit_null directory has been updated to count instances of events in the MYSQL_AUDIT_CONNECTION_CLASS event class. See Section 21.2.4.8, “Writing Audit Plugins”.

Bugs Fixed

Incompatible Change: For socket I/O, an optimization for the case when the server used alarms for timeouts could cause a slowdown when socket timeouts were used instead.
The fix for this issue results in several changes:
- Previously, timeouts applied to entire packet-level send or receive operations. Now timeouts apply to individual I/O operations at a finer level, such as sending 10 bytes of a given packet.
- The handling of packets larger than max_allowed_packet has changed. Previously, if an application sent a packet bigger than the maximum permitted size, or if the server failed to allocate a buffer sufficiently large to hold the packet, the server kept reading the packet until its end, then skipped it and returned an ER_NET_PACKET_TOO_LARGE error. Now the server disconnects the session if it cannot handle such large packets.
- On Windows, the default value for the MYSQL_OPT_CONNECT_TIMEOUT option to mysql_options() is no longer 20 seconds. Now the default is no timeout (infinite), the same as on other platforms.
- Building and running MySQL on POSIX systems now requires support for poll() and O_NONBLOCK. These should be available on any modern POSIX system.
(Bug #54790, Bug #11762221, Bug #36225, Bug #11762221)
InnoDB Storage Engine: Replication: Trying to update a column, previously set to NULL, of an InnoDB table with no primary key caused replication to fail with Can't find record in 'table' on the slave. (Bug #11766865, Bug #60091)
InnoDB Storage Engine: A failed CREATE INDEX operation for an InnoDB table could result in some memory being allocated but not freed. This memory leak could affect tables created with the ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED setting. (Bug #12699505)
InnoDB Storage Engine: Stability is improved when using BLOB values within InnoDB tables in a heavily loaded system, especially for tables using the ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED setting. (Bug #12612184)
InnoDB Storage Engine: The server could halt if InnoDB interpreted a very heavy I/O load for 15 minutes or more as an indication that the server was hung. This change fixes the logic that measures how long InnoDB threads were waiting, which formerly could produce false positives. (Bug #11877216, Bug #11755413, Bug #47183)
InnoDB Storage Engine: With the setting lower_case_table_names=2, inserts into InnoDB tables covered by foreign key constraints could fail after a server restart. (Bug #11831040, Bug #60196, Bug #60909)
InnoDB Storage Engine: If the server crashed while an XA transaction was prepared but not yet committed, the transaction could remain in the system after restart, and cause a subsequent shutdown to hang. (Bug #11766513, Bug #59641)
InnoDB Storage Engine: Improved concurrency for extending InnoDB tablespace files, which could prevent stalls on busy systems with many tables that use that innodb_file_per_table setting. (Bug #11763692, Bug #56433)
InnoDB Storage Engine: With the setting lower_case_table_names=2, inserts into InnoDB tables covered by foreign key constraints could fail after a server restart. This is a similar problem to the foreign key error in Bug #11831040 / Bug #60196 / Bug #60909, but with a different root cause and occurring on Mac OS X.
Partitioning: The internal get_partition_set() function did not take into account the possibility that a key specification could be NULL in some cases. (Bug #12380149)
Partitioning: When executing a row-ordered retrieval index merge, the partitioning handler used memory from that allocated for the table, rather than that allocated to the query, causing table object memory not to be freed until the table was closed. (Bug #11766249, Bug #59316)
Partitioning: Attempting to use ALTER TABLE ... EXCHANGE PARTITION to exchange a view with a (nonexistent) partition of a table that was not partitioned caused the server to crash. (Bug #11766232, Bug #60039)
Partitioning: Auto-increment columns of partitioned tables were checked even when they were not being written to. In debug builds, this could lead to a server crash. (Bug #11765667, Bug #58655)
Partitioning: The UNIX_TIMESTAMP() function was not treated as a monotonic function for purposes of partition pruning. (Bug #11746819, Bug #28928)
Replication: A mistake in thread cleanup could cause a replication master to crash. (Bug #12578441)
Replication: When using row-based replication and attribute promotion or demotion (see Section 15.4.1.6.2, “Replication of Columns Having Different Data Types”), memory allocated internally for conversion of BLOB columns was not freed afterwards. (Bug #12558519)
Replication: A memory leak could occur when re-creating a missing master info repository, because a new I/O cache used for a reference to the repository was re-created when the repository was re-created, but the previous cache was never removed. (Bug #12557307)
Replication: A race condition could occur between a user thread and the SQL thread when both tried to read the same memory before its value was safely set. This issue has now been corrected.
In addition, internal functions relating to creation of and appending to log events, when storing data, used memory local to the functions which was freed when the functions returned. As part of the fix for this problem, the output of SHOW SLAVE STATUS has been modified such that it no longer refers to files or file names in the accompanying status message, but rather contains one of the messages Making temporary file (append) before replaying LOAD DATA INFILE or Making temporary file (create) before replaying LOAD DATA INFILE. (Bug #12416611)
Replication: The name of the Ssl_verify_server_cert column in the mysql.slave_master_info table was misspelled as Ssl_verify_servert_cert. (Bug #12407446, Bug #60988)
Replication: When mysqlbinlog was invoked using --base64-output=decode-row and --start-position=pos, (where pos is a point in the binary log past the format description log event), a spurious error of the type shown here was generated:
```
malformed binlog: it does not contain any Format_description_log_event... 
```
However, since there is nothing unsafe about not printing the format description log event, the error has been removed for this case. (Bug #12354268)
Replication: A failed CREATE USER statement was mistakenly written to the binary log. (Bug #11827392, Bug #60082)
Replication: It is no longer possible to change the storage engine used by the mysql.slave_master_info and mysql.slave_relay_log_info tables while replication is running. This means that, to make replication crash-safe, you must make sure that both of these tables use a transactional storage engine before starting replication.
For more information, see Section 15.2.2, “Replication Relay and Status Logs”, and Options for logging slave status to tables. (Bug #11765887, Bug #58897)
Replication: A transaction was written to the binary log even when it did not update any nontransactional tables. (Bug #11763471, Bug #56184)
See also Bug #11763126, Bug #55789.
Replication: mysqlbinlog using the --raw option did not function correctly with binary logs from MySQL Server versions 5.0.3 and earlier. (Bug #11763265, Bug #55956)
Replication: Retrying a transaction on the slave could insert extra data into nontransactional tables. (Bug #11763126, Bug #55789)
See also Bug #11763471, Bug #56184.
Replication: Typographical errors appeared in the text of several replication error messages. (The word “position” was misspelled as “postion”.) (Bug #11762616, Bug #55229)
Replication: Temporary deadlocks in the slave SQL thread could cause unnecessary Deadlock found when trying to get lock; try restarting transaction error messages to be logged on the slave.
Now in such cases, only a warning is logged unless slave_transaction_retries has been exceeded by the number of such warnings for a given transaction. (Bug #11748510, Bug #36524)
Replication: When a slave requested a binary log file which did not exist on master, the slave continued to request the file regardless. This caused the slave's error log to be flooded with low-level EE_FILENOTFOUND errors (error code 29) from the master. (Bug #11745939, Bug #21437)
Partitioning: A problem with a previous fix for poor performance of INSERT ON DUPLICATE KEY UPDATE statements on tables having many partitions caused the handler function for reading a row from a specific index to fail to store the ID of the partition last used. This caused some statements to fail with Can't find record errors. (Bug #59297, Bug #11766232)
The metadata locking subsystem added too much overhead for INFORMATION_SCHEMA queries that were processed by opening only .frm or .TRG files and had to scan many tables. For example, SELECT COUNT(*) FROM INFORMATION_SCHEMA.TRIGGERS was affected. (Bug #12828477)
Compilation failed on Mac OS X 10.7 (Lion) with a warning: Implicit declaration of function 'pthread_init' (Bug #12779790)
With profiling disabled or not compiled in, set_thd_proc_info() unnecessarily checked file name lengths. (Bug #12756017)
Compiling the server with maintainer mode enabled failed for gcc 4.6 or higher. (Bug #12727287)
For prepared statements, an OK could be sent to the client if the prepare failed due to being killed. (Bug #12661349)
Some Valgrind warnings were corrected:
- For the SUBSTRING(), LEFT(), RIGHT(), LPAD(), RPAD(), and REPEAT() functions, a missing NULL value check was corrected.
- For the LIKE operator, an attempt to use an uninitialized string buffer in the case of an empty wildcard was corrected.
(Bug #12634989, Bug #59851, Bug #11766684)
Adding support for Windows authentication to libmysql introduced a link dependency on the system Secur32 library. The Microsoft Visual C++ link information now pulls in this library automatically. (Bug #12612143)
With index condition pushdown enabled, a crash could occur due to an invalid end-of-range value. (Bug #12601961)
The option-parsing code for empty strings leaked memory. (Bug #12589928)
The server could fail to free allocated memory when INSERT DELAYED was used with binary logging enabled. (Bug #12538873)
A DBUG_ASSERT added by Bug #11792200 was overly aggressive in raising assertions. (Bug #12537160)
In some cases, memory allocated for Query_tables_list::sroutines() was not freed properly. (Bug #12429877)
After the fix for Bug #11889186, MAKEDATE() arguments with a year part greater than 9999 raised an assertion. (Bug #12403504)
An assertion could be raised due to a missing NULL value check in Item_func_round::fix_length_and_dec(). (Bug #12392636)
Assignments to NEW.var_name within triggers, where var_name had a BLOB or TEXT type, were not properly handled and produced incorrect results. (Bug #12362125)
An assertion could be raised if Index Condition Pushdown code pushed down an index condition containing a subquery. (Bug #12355958)
XA COMMIT could fail to clean up the error state if it discovered that the current XA transaction had to be rolled back. Consequently, the next XA transaction could raise an assertion when it checked for proper cleanup of the previous transaction. (Bug #12352846)
An assertion could be raised during two-phase commits if the binary log was used as the transaction coordinator log. (Bug #12346411)
InnoDB could add temporary index information to INFORMATION_SCHEMA, which could raise an assertion. (Bug #12340873)
On Windows, the server rejected client connections if no DNS server was available. (Bug #12325375)
A too-strict assertion could cause a server crash. (Bug #12321461)
mysql_upgrade did not properly upgrade the authentication_string column of the mysql.user table. (Bug #11936829)
The optimizer sometimes chose a forward index scan followed by a filesort to reserve the order rather than scanning the index in reverse order. (Bug #11882131)
Previously, an inappropriate error message was produced if a multiple-table update for an InnoDB table with a clustered primary key would update a table through multiple aliases, and perform an update that may physically move the row in at least one of these aliases. Now the error message is: Primary key/partition key update is not permitted since the table is updated both as 'tbl_name1' and 'tbl_name2' (Bug #11882110)
See also Bug #11764529.
Queries that used STRAIGHT_JOIN on data that included NULL values could return incorrect results if index condition pushdown was enabled. (Bug #11873324)
InnoDB invoked some zlib functions without proper initialization. (Bug #11849231)
Division of large numbers could cause stack corruption. (Bug #11792200)
CHECK TABLE and REPAIR TABLE failed to find problems with MERGE tables that had underlying tables missing or with the wrong storage engine. Issues were reported only for the first underlying table. (Bug #11754210)
Replication: If a LOAD DATA INFILE statement—replicated using statement-based replication—featured a SET clause, the name-value pairs were regenerated using a method (Item::print()) intended primarily for generating output for statements such as EXPLAIN EXTENDED, and which cannot be relied on to return valid SQL. This could in certain cases lead to a crash on the slave.
To fix this problem, the server now names each value in its original, user-supplied form, and uses that to create LOAD DATA INFILE statements for statement-based replication. (Bug #60580, Bug #11902767)
See also Bug #34283, Bug #11752526, Bug #43746.
Replication: Error 1590 (ER_SLAVE_INCIDENT) caused the slave to stop even when it was started with --slave-skip-errors=1590. (Bug #59889, Bug #11768580, Bug #11799671)
Replication: Using the --server-id option with mysqlbinlog could cause format description log events to be filtered from the binary log, leaving mysqlbinlog unable to read the remainder of the log. Now such events are always read without regard to the value of this option.
As part of the the fix for this problem, mysqlbinlog now also reads rotate log events without regard to the value of --server-id. (Bug #59530, Bug #11766427)
Replication: A failed DROP DATABASE statement could break statement-based replication. (Bug #58381, Bug #11765416)
Replication: Processing of corrupted table map events could cause the server to crash. This was especially likely if the events mapped different tables to the same identifier, such as could happen due to Bug#56226.
Now, before applying a table map event, the server checks whether the table has already been mapped with different settings, and if so, an error is raised and the slave SQL thread stops. If it has been mapped with the same settings, or if the table is set to be ignored by filtering rules, there is no change in behavior: the event is skipped and IDs are not checked. (Bug #44360, Bug #11753004)
See also Bug #11763509.
The server failed to compile if partitioning support was disabled. (Bug #61625, Bug #12694147)
ALTER TABLE {MODIFY|CHANGE} ... FIRST did nothing except rename columns if the old and new versions of the table had exactly the same structure with respect to column data types. As a result, the mapping of column name to column data was incorrect. The same thing happened for ALTER TABLE DROP COLUMN ... ADD COLUMN statements intended to produce a new version of the table with exactly the same structure as the old version. (Bug #61493, Bug #12652385)
Incorrect handling of metadata locking for FLUSH TABLES WITH READ LOCK for statements requiring prelocking caused two problems:
- Execution of any data-changing statement that required prelocking (that is, involved a stored function or trigger) as part of a transaction slowed down somewhat all subsequent statements in the transaction. Performance in a transaction that periodically involved such statements gradually degraded over time.
- Execution of any data-changing statement that required prelocking as part of a transaction prevented a concurrent FLUSH TABLES WITH READ LOCK from proceeding until the end of the transaction rather than at the end of the particular statement.
(Bug #61401, Bug #12641342)
A problem introduced in 5.5.11 caused very old (MySQL 4.0) clients to be unable to connect to the server. (Bug #61222, Bug #12563279)
The fractional part of the “Queries per second” value could be displayed incorrectly in MySQL status output (for example, in the output from mysqladmin status or the mysql STATUS command). (Bug #61205, Bug #12565712)
The mysql-log-rotate script was updated because it referred to deprecated MySQL options. (Bug #61038, Bug #12546842)
Using CREATE EVENT IF NOT EXISTS for an event that already existed and was enabled caused multiple instances of the event to run. (Bug #61005, Bug #12546938)
If a statement ended with mismatched quotes, the server accepted the statement and interpreted whatever was after the initial quote as a text string. (Bug #60993, Bug #12546960)
LOAD DATA INFILE incorrectly parsed relative data file path names that ascended more than three levels in the file system and as a consequence was unable to find the file. (Bug #60987, Bug #12403662)
Table I/O for the Performance Schema table_io_waits_summary_by_index_usage table was counted as using no index for UPDATE and DELETE statements, even when an index was used. (Bug #60905, Bug #12370950)
An internal client macro reference was removed from the client_plugin.h header file. This reference made the file unusable. (Bug #60746, Bug #12325444)
Comparison of a DATETIME stored program variable and NOW() led to an “Illegal mix of collations error” when character_set_connection was set to utf8. (Bug #60625, Bug #11926811)

Selecting from a view for which the definition included a HAVING clause failed with an error:

1356: View '...' references invalid table(s) or column(s)
or function(s) or definer/invoker of view lack rights to use them

(Bug #60295, Bug #11829681)

CREATE TABLE syntax permits specification of a STORAGE {DEFAULT|DISK|MEMORY} option. However, this value was not written to the .frm file, so that a subsequent CREATE TABLE ... LIKE for the table did not include that option.
Also, ALTER TABLE of a table that had a tablespace incorrectly destroyed the tablespace. (Bug #60111, Bug #11766883, Bug #34047, Bug #11747789)
The mysql_load_client_plugin() C API function did not clear the previous error. (Bug #60075, Bug #11766854)
For repeated invocation of some stored procedures, the server consumed memory that it did not release until the connection terminated. (Bug #60025, Bug #11848763)
The server permitted max_allowed_packet to be set lower than net_buffer_length, which does not make sense because max_allowed_packet is the upper limit on net_buffer_length values. Now a warning occurs and the value remains unchanged. (Bug #59959, Bug #11766769)
The server did not check for certain invalid out of order sequences of XA statements, and these sequences raised an assertion. (Bug #59936, Bug #11766752, Bug #12348348)
For unknown users, the native password plugin reported incorrectly that no password had been specified even when it had. (Bug #59792, Bug #11766641)
Setting optimizer_join_cache_level to 3 or greater raised an assertion for some queries. (Bug #59651, Bug #11766522)
Previously, Performance Schema table columns that held byte counts were BIGINT UNSIGNED. These were changed to BIGINT (signed). This makes it easier to perform calculations that compute differences between columns. (Bug #59631, Bug #11766504)
A missing variable initialization for Item_func_set_user_var objects could raise an assertion. (Bug #59527, Bug #11766424)
For some queries, the optimizer performed range analysis too many times for the same index. (Bug #59415, Bug #11766327)
With the conversion from GNU autotools to CMake for configuring MySQL, the USE_SYMDIR preprocessor symbol was omitted. This caused failure of symbolic links (described at Section 7.11.3.1, “Using Symbolic Links”). (Bug #59408, Bug #11766320)
When the server was started with the --skip-innodb option, it initialized the have_innodb system variable to YES rather than DISABLED. (Bug #59393, Bug #11766306)
An incorrect max_length value for YEAR values could be used in temporary result tables for UNION, leading to incorrect results. (Bug #59343, Bug #11766270)
In Item_func_in::fix_length_and_dec(), a Valgrind warning for uninitialized values was corrected. (Bug #59270, Bug #11766212)
An invalid pathname argument for the --defaults-extra-file option of MySQL programs caused a program crash. (Bug #59234, Bug #11766184)
In Item_func_month::val_str(), a Valgrind warning for a too-late NULL value check was corrected. (Bug #59166, Bug #11766126)
In Item::get_date, a Valgrind warning for a missing NULL value check was corrected. (Bug #59164, Bug #11766124)
In extract_date_time(), a Valgrind warning for a missing end-of-string check was corrected. (Bug #59151, Bug #11766112)
Some tables were not instrumented by the Performance Schema even though they were listed in the setup_objects table. (Bug #59150, Bug #11766111)
In string context, the MIN() and MAX() functions did not take into account the unsignedness of a BIGINT UNSIGNED argument. (Bug #59132, Bug #11766094)
In Item_func::val_decimal, a Valgrind warning for a missing NULL value check was corrected. (Bug #59125, Bug #11766087)
On Windows, the authentication_string column recently added to the mysql.user table caused the Configuration Wizard to fail. (Bug #59038, Bug #11766011)
In ROUND() calculations, a Valgrind warning for uninitialized memory was corrected. (Bug #58937, Bug #11765923)
The range created by the optimizer when OR-ing two conditions could be incorrect, causing incorrect query results. (Bug #58834, Bug #11765831)
Valgrind warnings caused by comparing index values to an uninitialized field were corrected. (Bug #58705, Bug #11765713)
As a side effect of optimizing condition AND TRUE or condition OR FALSE, MySQL for certain subqueries forgot that the columns used by the condition needed to be read, which raised an assertion in debug builds. (Bug #58690, Bug #11765699)
CREATE TRIGGER and DROP TRIGGER can change the prelocking list of stored routines, but the routine cache did not detect such changes, resulting in routine execution with an inaccurate locking list. (Bug #58674, Bug #11765684)
In Item_func_str_to_date::val_str, a Valgrind warning for an uninitialized variable was corrected. (Bug #58154, Bug #11765216)
The code for PROCEDURE ANALYSE() had a missing DBUG_RETURN statement, which could cause a server crash in debug builds. (Bug #58140, Bug #11765202)
LOAD DATA INFILE errors could leak I/O cache memory. (Bug #58072, Bug #11765141)
For LOAD DATA INFILE, multibyte character sequences could be pushed onto a stack too small to accommodate them. (Bug #58069, Bug #11765139)
The embedded server crashed when argc = 0. (Bug #57931, Bug #12561297)
An assertion could be raised in Item_func_int_val::fix_num_length_and_dec() due to overflow for geometry functions. (Bug #57900, Bug #11764994)
An assertion was raised if a statement tried to upgrade a metadata lock while there was an active FLUSH TABLE tbl_list WITH READ LOCK statement. Now if a statement tries to upgrade a metadata lock in this situation, the server returns an ER_TABLE_NOT_LOCKED_FOR_WRITE error to the client. (Bug #57649, Bug #11764779)
The optimizer sometimes requested ordered access from a storage engine when ordered access was not required. (Bug #57601, Bug #11764737)
An embedded client aborted rather than issuing an error message if it issued a TEE command (\T file_name) and the directory containing the file did not exist. This occurred because the wrong error handler was called. (Bug #57491, Bug #11764633)
For an outer join with a NOT IN subquery in the WHERE clause, a null left operand to the NOT IN returned was treated differently than a literal NULL operand. (Bug #56881, Bug #11764086)
Threads blocked in the waiting for table metadata state were not visible in performance_schema.THREADS or SHOW PROFILE. (Bug #56475, Bug #11763728)
With prepared statements, the server could attempt to send result set metadata after the table had been closed. (Bug #56115, Bug #11763413)
Table objects associated with one session's optimizer structures could be closed after being passed to another session, prematurely ending the second session's table or index scan. (Bug #56080, Bug #11763382)
In some cases, SHOW WARNINGS returned an empty result when the previous statement failed. (Bug #55847, Bug #11763166)
In debug builds, Field_new_decimal::store_value() was subject to buffer overflows. (Bug #55436, Bug #11762799)
For an InnoDB table, dropping and adding an index in a single ALTER TABLE statement could fail. (Bug #54927, Bug #11762345)
For a client connected using SSL, the Ssl_cipher_list status variable was empty and did not show the possible cipher types. (Bug #52596, Bug #11760210)
The mysql client sometimes did not properly close sessions terminated by the user with Control+C. (Bug #52515, Bug #11760134)
CREATE TABLE ... LIKE for a MyISAM table definition that included an DATA DIRECTORY or INDEX DIRECTORY table option failed, instead of creating a table with those option omitted as documented. (Bug #52354, Bug #11759990)
Attempts to grant the EXECUTE or ALTER ROUTINE privilege for a nonexistent stored procedure returned success instead of an error. (Bug #51401, Bug #11759114)
With lower_case_table_names=2, resolution of objects qualified by database names could fail. (Bug #50924, Bug #11758687)
On Linux, the mysql client built using the bundled libedit did not read ~/.editrc. (Bug #49967, Bug #11757855)
For some statements such as DESCRIBE or SHOW, views with too many columns produced errors. (Bug #49437, Bug #11757397)
The optimizer sometimes incorrectly processed HAVING clauses for queries that did not also have an ORDER BY clause. (Bug #48916, Bug #11756928)
PROCEDURE ANALYZE() could leak memory for NULL results, and could return incorrect results if used with a LIMIT clause. (Bug #48137, Bug #11756242)
A race condition between loading a stored routine using the name qualified by the database name and dropping that database resulted in a spurious error message: The table mysql.proc is missing, corrupt, or contains bad data (Bug #47870, Bug #11756013)
When used to upgrade tables, mysqlcheck (and mysql_upgrade, which invokes mysqlcheck) did not upgrade some tables for which table repair was found to be necessary. In particular, it failed to upgrade InnoDB tables that needed repair, leaving them in a nonupgraded state. This occurred because:
- mysqlcheck --check-upgrade ---auto-repair checks for tables that are incompatible with the current version of MySQL. It does this by issuing the CHECK TABLE ... FOR UPGRADE statement and examining the result.
- For any table found to be incompatible, mysqlcheck issues a REPAIR TABLE statement. But this fails for storage engines such as InnoDB that do not support the repair operation. Consequently, the table remained unchanged.
To fix the problem, the following changes were made to CHECK TABLE ... FOR UPGRADE and mysqlcheck. Because mysql_upgrade invokes mysqlcheck, these changes also fix the problem for mysql_upgrade.
- CHECK TABLE ... FOR UPGRADE returns a different error if a table needs repair but its storage engine does not support REPAIR TABLE:
  Previous:
```
Error: ER_TABLE_NEEDS_UPGRADE
Table upgrade required. Please do "REPAIR TABLE `tbl_name`" or
dump/reload to fix it!
```
  Now:
```
Error: ER_TABLE_NEEDS_REBUILD
Table rebuild required. Please do "ALTER TABLE `tbl_name` FORCE" or
dump/reload to fix it!
```
- mysqlcheck recognizes the new error and issues an ALTER TABLE ... FORCE statement. The FORCE option for ALTER TABLE was recognized but did nothing; now it is implemented and acts as a “null” alter operation that rebuilds the table.
(Bug #47205, Bug #11755431)
On some platforms, the Incorrect value: xxx for column yyy at row zzz error produced by LOAD DATA INFILE could have an incorrect value of zzz. (Bug #46895, Bug #11755168)
The mysql_affected_rows() C API function returned 3 (instead of 2) for INSERT ... ON DUPLICATE KEY UPDATE statements where there was a duplicated key value. (Bug #46675, Bug #11754979)
Upgrades using an RPM package recreated the test database, which is undesirable when the DBA had removed it. (Bug #45415, Bug #11753896)
In MySQL 5.1 and up, if a table had triggers that used syntax supported in 5.0 but not 5.1, the table became unavailable. Now the table is marked as having broken triggers. (Bug #45235, Bug #11753738)
An attempt to install nonexistent files during installation was corrected. (Bug #43247, Bug #11752142)
Some status variables rolled over to zero after reaching the maximum 32-bit value. They have been changed to 64-bit values. (Bug #42698, Bug #11751727)
SHOW EVENTS did not always show events from the correct database. (Bug #41907, Bug #11751148)
For queries with many eq_ref joins, the optimizer took excessive time to develop an execution plan. (Bug #41740, Bug #11751026, Bug #58225, Bug #11765274)
On FreeBSD 64-bit builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
With DISTINCT CONCAT(col_name,...) 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 contained 1111.) (Bug #4082)

D.1.2. Changes in MySQL 5.6.2 (11 April 2011)

InnoDB Configurable Data Dictionary Cache

InnoDB Storage Engine: InnoDB now uses the table_cache option value as a guide to remove table metadata from memory when many different InnoDB tables are accessed. InnoDB table metadata is removed using a variation of the LRU algorithm. (Parent and child tables in foreign key relationships are exempted from removal.) (Bug #20877, Bug #11745884)

INFORMATION_SCHEMA Table for InnoDB Metrics

InnoDB Storage Engine: A new INFORMATION_SCHEMA table, INNODB_METRICS, lets you query low-level InnoDB performance information, getting cumulative counts, averages, and min/max values for internal aspects of the storage engine operation. You can start, stop, and reset the metrics counters using the configuration variables innodb_monitor_enable, innodb_monitor_disable, innodb_monitor_reset, and innodb_monitor_reset_all.

INFORMATION_SCHEMA Tables for InnoDB Buffer Pool Information

InnoDB Storage Engine: The new INFORMATION_SCHEMA tables INNODB_BUFFER_PAGE, INNODB_BUFFER_PAGE_LRU, and INNODB_BUFFER_POOL_STATS display InnoDB buffer pool information for tuning on large-memory or highly loaded systems.

INFORMATION_SCHEMA Tables for InnoDB Data Dictionary

InnoDB Storage Engine: The InnoDB data dictionary, containing metadata about InnoDB tables, columns, indexes, and foreign keys, is available for SQL queries through a set of INFORMATION_SCHEMA tables.

Persistent InnoDB Optimizer Statistics

InnoDB Storage Engine: The optimizer statistics for InnoDB tables can now persist across server restarts, producing more stable query performance. You can also control the amount of sampling done to estimate cardinality for each index, resulting in more accurate optimizer statistics.

Explicit Partition Selection

Partitioning: It is now possible to select one or more partitions or subpartitions when querying from a partitioned table. In addition, many data modification statements (DELETE, INSERT, REPLACE, UPDATE, LOAD DATA, and LOAD XML) that act on partitioned tables also now support explicit partition selection. For example, assume we have a table named t with some integer column named c, and t has 4 partitions named p0, p1, p2, and p3. Then the query SELECT * FROM t PARTITION (p0, p1) WHERE c < 5 returns rows only in partitions p0 and p1 that match the WHERE condition, while partitions p2 and p3 are not checked.
For additional information and examples, see Section 16.5, “Partition Selection”, as well as the descriptions of the statements just listed.

Row Image Control

Replication: Added the binlog_row_image server system variable, which can be used to enable row image control for row-based replication. This means that you can potentially save disk space, network resources, and memory usage by the MySQL Server by logging only those columns that are required for uniquely identifying rows, or which are actually changed on each row, as opposed to logging all columns for each and every row change event. In addition, you can use a “noblob” mode where all columns, except for unneeded BLOB or TEXT columns, are logged.
For more information, see System variables used with the binary log. (Bug #47200, Bug #11755426, Bug #47303, Bug #56917, Bug #11755426, Bug #11755513, Bug #11764116)

Crash-Safe Binary Log

Replication: Support for checksums when writing and reading the binary log is added to the MySQL Server. Writing checksums into the binary log is disabled by default; it can be enabled by starting the server with the --binlog-checksum option. To cause the server to read checksums from the binary log, start the server with the --master-verify-checksum option. The --slave-sql-verify-checksum option causes the slave to read checksums from the relay log.
Replication: The MySQL Server now records and reads back only complete events or transactions to and from the binary log. By default, the server now logs the length of the event as well as the event itself and uses this information to verify that the event was written correctly to the log. A master also uses by default this value to verify events when reading from the binary log.
If you enable writing of checksums (using the binlog_checksum system variable), the master can use these instead by enabling the master_verify_checksum system variable. The slave I/O thread also verifies events received from the master. You can cause the slave SQL thread to use checksums (if available) as well, when reading from the relay log, by enabling the slave_sql_verify_checksum system variable on the slave.

Slave Log Tables

Replication: It is now possible to write information about the slave connection to the master and about the slave's execution point within the relay log to tables rather than files. Logging of master connection information and of slave relay log information to tables can be done independently of one another; this is controlled by the --master-info-repository and --relay-log-info-repository server options. When --master-info-repository is set to TABLE, connection information is logged in the slave_master_info table in the mysql system database. When --relay-log-info-repository is set to TABLE, relay log information is logged to the slave_relay_log_info table, also in the mysql database.

Pluggable Authentication Notes

MySQL distributions now include auth_socket, a server-side authentication plugin that authenticates clients that connect from the local host through the Unix socket file. The plugin uses the SO_PEERCRED socket option to obtain information about the user running the client program (and thus can be built only on systems that support this option). For a connection to succeed, the plugin requires a match between the login name of the connecting client user and the MySQL user name presented by the client program. For more information, see Section 5.5.6.4, “The Socket Peer-Credential Authentication Plugin”. (Bug #59017, Bug #11765993)

Optimizer Features

The optimizer now more efficiently handles queries (and subqueries) of the following form:
```
SELECT ... FROM single_table ... ORDER BY non_index_column [DESC] LIMIT [M,]N;
```
That type of query is common in web applications that display only a few rows from a larger result set. For example:
```
SELECT col1, ... FROM t1 ... ORDER BY name LIMIT 10;
SELECT col1, ... FROM t1 ... ORDER BY RAND() LIMIT 15;
```
The sort buffer has a size of sort_buffer_size. If the sort elements for N rows are small enough to fit in the sort buffer (M+N rows if M was specified), the server can avoid using a merge file and perform the sort entirely in memory. For details, see Section 7.2.1.3, “Optimizing LIMIT Queries”.
The optimizer implements Disk-Sweep Multi-Range Read. Reading rows using a range scan on a secondary index can result in many random disk accesses to the base table when the table is large and not stored in the storage engine's cache. With the Disk-Sweep Multi-Range Read (MRR) optimization, MySQL tries to reduce the number of random disk access for range scans by first scanning the index only and collecting the keys for the relevant rows. Then the keys are sorted and finally the rows are retrieved from the base table using the order of the primary key. The motivation for Disk-sweep MRR is to reduce the number of random disk accesses and instead achieve a more sequential scan of the base table data. For more information, see Section 7.13.10, “Multi-Range Read Optimization”.
The optimizer implements Index Condition Pushdown (ICP), an optimization for the case where MySQL retrieves rows from a table using an index. Without ICP, the storage engine traverses the index to locate rows in the base table and returns them to the MySQL server which evaluates the WHERE condition for the rows. With ICP enabled, and if parts of the WHERE condition can be evaluated by using only fields from the index, the MySQL server pushes this part of the WHERE condition down to the storage engine. The storage engine then evaluates the pushed index condition by using the index entry and only if this is satisfied is base row be read. ICP can reduce the number of accesses the storage engine has to do against the base table and the number of accesses the MySQL server has to do against the storage engine. For more information, see Section 7.13.4, “Index Condition Pushdown Optimization”.

Pluggable Authentication Notes

MySQL distributions now include mysql_clear_password, a client-side authentication plugin that sends the password to the server without hashing or encryption. Although this is insecure, and thus appropriate precautions should be taken (such as using an SSL connection), the plugin is useful in conjunction with server-side plugins that must have access to the original password in clear text. For more information, see Section 5.5.6.3, “The Clear Text Client-Side Authentication Plugin”.

Performance Schema Notes

The Performance Schema has these additions:
- The Performance Schema now has tables that contain summaries for table and index I/O wait events, as generated by the wait/io/table/sql/handler instrument:
  - table_io_waits_summary_by_table: Aggregates table I/O wait events. The grouping is by table.
  - table_io_waits_summary_by_index_usage: Aggregates table index I/O wait events. The grouping is by table index.
  The information in these tables can be used to assess the impact of table I/O performed by applications. For example, it is possible to see which tables are used and which indexes are used (or not used), or to identify bottlenecks on a table when multiple applications access it. The results may be useful to change how applications issue queries against a database, to minimize application footprint on the server and to improve application performance and scalability.
  A change that accompanies the new tables is that the events_waits_current table now has an INDEX_NAME column to identify which index was used for that operation that generated the event. The same is true of the event-history tables, events_waits_history, and events_waits_history_long.
- The Performance Schema now has an instrument named wait/lock/table/sql/handler in the setup_instruments table for instrumenting table lock wait events. It differs from wait/io/table/sql/handler, which instruments table I/O. This enables independent instrumentation of table I/O and table locks.
  Accompanying the new instrument, the Performance Schema has a table named table_lock_waits_summary_by_table that aggregates table lock wait events, as generated by the new instrument. The grouping is by table.
  The information in this table may be used to assess the impact of table locking performed by applications. The results may be useful to change how applications issue queries against the database and use table locks, to minimize the application footprint on the server and to improve application performance and scalability. For example, an application locking tables for a long time may negatively affect other applications, and the instrumentation makes this visible.
- To selectively control which tables are instrumented for I/O and locking, use the setup_objects table. See Section 19.2.3.2.1.2, “Pre-Filtering by Object”.
If you upgrade to this release of MySQL from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate these changes into the performance_schema database.
For more information, see Chapter 19, MySQL Performance Schema.

Functionality Added or Changed

Incompatible Change: The following obsolete constructs have been removed. Where alternatives are shown, applications should be updated to use them.
- The FLUSH MASTER and FLUSH SLAVE statements. Use the RESET MASTER and RESET SLAVE statements instead.
Important Change: Replication: Added the --binlog-rows-query-log-events option for mysqld. Using this option causes a server logging in row-based mode to write informational rows query log events (SQL statements, for debugging and other purposes) to the binary log. MySQL server and MySQL programs from MySQL 5.6.2 and later normally ignore such events, so that they do not pose an issue when reading the binary log. mysqld and mysqlbinlog from previous MySQL releases cannot read such events in the binary log, and fail if they attempt to do so. For this reason, you should never prepare logs for a MySQL 5.6.1 or earlier replication slave server (or other reader such as mysqlbinlog) with this option enabled on the master. (Bug #11758695, Bug #50935, Bug #11758695)
InnoDB Storage Engine: A separate InnoDB thread (page_cleaner) now handles the flushing of dirty pages that was formerly done by the InnoDB master thread. (Bug #11762412, Bug #55004)
InnoDB Storage Engine: InnoDB can optionally log details about all deadlocks that occur, to assist with troubleshooting and diagnosis. This feature is controlled by the innodb_print_all_deadlocks configuration option. (Bug #1784, Bug #17572)
InnoDB Storage Engine: The configuration option innodb_purge_threads can now be set to a value higher than 1.
InnoDB Storage Engine: The InnoDB kernel mutex has been split into several mutexes and rw-locks, for improved concurrency.
Replication: On MySQL replication slaves having multiple network interfaces, it is now possible to set which interface to use for connecting to the master using the MASTER_BIND='interface' option in a CHANGE MASTER TO statement.
The value set by this option can be seen in the Master_Bind column of the output from SHOW SLAVE STATUS or the Bind column of the mysql.slave_master_info table. (Bug #25939, Bug #11746389)
Replication: Added the log_bin_basename system variable, which contains the complete file name and path to the binary log file. (The log_bin system variable shows only whether or not binary logging is enabled; log_bin_basename, however, reflects the name set with the --log-bin server option.) Also added relay_log_basename system variable, which shows the file name and complete path to the relay log file.
See also Bug #19614, Bug #11745759.
The mysql_upgrade, mysqlbinlog, mysqlcheck, mysqlimport, mysqlshow, and mysqlslap clients now have --default-auth and --plugin-dir options for specifying which authentication plugin and plugin directory to use. (Bug #58139)
The server now includes the thread ID in rows written to the slow query log. In the slow query log file, the thread ID is the last value in the line. In the mysql.slow_loglog table, there is a new thread_id column.
To update the slow_log table if you are upgrading from an earlier release, run mysql_upgrade and restart the server. See Section 4.4.8, “mysql_upgrade — Check Tables for MySQL Upgrade”. (Bug #53630, Bug #11761166)
The server now writes thread shutdown messages to the error log during the shutdown procedure. (Bug #48388, Bug #11756464)
If the --init-file option is given, the server now writes messages indicating the beginning and end of file execution to the error log. (Bug #48387, Bug #11756463)
Boolean system variables can be enabled at run time by setting them to the value ON or OFF, but previously this did not work at server startup. Now at startup such variables can be enabled by setting them to ON or TRUE, or disabled by setting them to OFF or FALSE. Any other nonnumeric variable is invalid. (Bug #46393)
See also Bug #11754743, Bug #51631.
MySQL distributions now include an INFO_SRC file that contains information about the source distribution, such as the MySQL version from which it was created. MySQL binary distributions additionally include an INFO_BIN file that contains information about how the distribution was built, such as compiler options and feature flags. In RPM packages, these files are located in the /usr/share/doc/packages/MySQL-server directory. In tar.gz and derived packages, they are located in the Docs directory under the location where the distribution is unpacked. (Bug #42969, Bug #11751935)
Previously, for queries that were aborted due to a sort problem, the server wrote the message Sort aborted to the error log. Now the server writes more information to provide a more specific message, such as:
```
Sort aborted: Out of memory (Needed 24 bytes)
Out of sort memory, consider increasing server sort buffer size
Sort aborted: Out of sort memory, consider increasing server sort
  buffer size
Sort aborted: Incorrect number of arguments for FUNCTION test.f1;
  expected 0, got 1
```
In addition, if the server was started with --log-warnings=2, the server write information about the host, user, and query. (Bug #36022, Bug #11748358)
Previously, for queries that were aborted due to a sort problem or terminated with KILL in the middle of a sort, the server wrote the message Sort aborted to the error log. Now the server writes more information about the cause of the error. These causes include:
- Insufficient disk space in the temporary file directory prevented a temp file from being created
- Insufficient memory for sort_buffer_size to be allocated
- Somebody ran KILL id in the middle of a filesort operation
- The server was shut down while some queries were sorting
- A transaction was rolled back or aborted due to a lock wait timeout or deadlock
- Unexpected errors, such as a source table or even temp table was corrupt
- Processing of a subquery failed which was also sorting
(Bug #30771, Bug #11747102)
mysqldump --xml now displays comments from column definitions. (Bug #13618, Bug #11745324)
Windows provides APIs based on UTF-16LE for reading from and writing to the console. MySQL now supports a utf16le character set for UTF-16LE, so the mysql client for Windows has been modified to provide improved Unicode support by using these APIs.
To take advantage of this change, you must run mysql within a console that uses a compatible Unicode font and set the default character set to a Unicode character set that is supported for communication with the server. For instructions, see Section 4.5.1.6.1, “Unicode Support on Windows”.
The undocumented SHOW NEW MASTER statement has been removed.
A new plugin service, my_plugin_log_service, enables plugins to report errors and specify error messages. The server writes the messages to the error log. See Section 21.2.5, “MySQL Services for Plugins”.

Bugs Fixed

Performance: InnoDB Storage Engine: An UPDATE statement for an InnoDB table could be slower than necessary if it changed a column covered by a prefix index, but did not change the prefix portion of the value. The fix improves performance for InnoDB 1.1 in MySQL 5.5 and higher, and the InnoDB Plugin for MySQL 5.1. (Bug #58912, Bug #11765900)
Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug #54568, CVE-2010-3836)
Incompatible Change: When auto_increment_increment is greater than one, values generated by a bulk insert that reaches the maximum column value could wrap around rather producing an overflow error.
As a consequence of the fix, it is no longer possible for an auto-generated value to be equal to the maximum BIGINT UNSIGNED value. It is still possible to store that value manually, if the column can accept it. (Bug #39828, Bug #11749800)
Important Change: Partitioning: Date and time functions used as partitioning functions now have the types of their operands checked; use of a value of the wrong type is now disallowed in such cases. In addition, EXTRACT(WEEK FROM col_name), where col_name is a DATE or DATETIME column, is now disallowed altogether because its return value depends on the value of the default_week_format system variable. (Bug #54483, Bug #11761948)
See also Bug #57071, Bug #11764255.
Important Change: Replication: The CHANGE MASTER TO statement required the value for RELAY_LOG_FILE to be an absolute path, whereas the MASTER_LOG_FILE path could be relative.
The inconsistent behavior is resolved by permitting relative paths for RELAY_LOG_FILE, and by using the same basename for RELAY_LOG_FILE as for MASTER_LOG_FILE. For more information, see Section 12.5.2.1, “CHANGE MASTER TO Syntax”. (Bug #12190, Bug #11745232)
Partitioning: InnoDB Storage Engine: The partitioning handler did not pass locking information to a table's storage engine handler. This caused high contention and thus slower performance when working with partitioned InnoDB tables. (Bug #59013)
InnoDB Storage Engine: This fix introduces a new configuration option, innodb_change_buffer_max_size, which defines the size of the change buffer as a percentage of the size of the buffer pool. Because the change buffer shares memory space with the buffer pool, a workload with a high rate of DML operations could cause pages accessed by queries to age out of the buffer pool sooner than desirable. This fix also devotes more I/O capacity to flushing entries from the change buffer when it exceeds 1/2 of its maximum size. (Bug #11766168, Bug #59214)
InnoDB Storage Engine: The presence of a double quotation mark inside the COMMENT field for a column could prevent a foreign key constraint from being created properly. (Bug #59197, Bug #11766154)
InnoDB Storage Engine: It was not possible to query the information_schema.innodb_trx table while other connections were running queries involving BLOB types. (Bug #55397, Bug #11762763)
InnoDB Storage Engine: InnoDB returned values for “rows examined” in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger “false positives” in combination with the max_join_size setting, because the queries did not really examine as many rows as reported.
A new configuration option innodb_stats_method lets you specify how NULL values are treated when calculating index statistics. Allowed values are nulls_equal (the default), nulls_unequal and null_ignored. The meanings of these values are similar to those of the myisam_stats_method option. (Bug #30423)
Partitioning: Failed ALTER TABLE ... PARTITION statements could cause memory leaks. (Bug #56380, Bug #11763641)
See also Bug #46949, Bug #11755209, Bug #56996, Bug #11764187.
Two unused test files in storage/ndb/test/sql contained incorrect versions of the GNU Lesser General Public License. The files and the directory containing them have been removed. (Bug #11810224)
See also Bug #11810156.
Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338, Bug #11766266)
Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in which case—if the transaction could not be rolled back safely—the SQL thread could hang.
Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546, Bug #11765563)
Replication: mysqlbinlog printed USE statements to its output only when the default database changed between events. To illustrate how this could cause problems, suppose that a user issued the following sequence of statements:
```
CREATE DATABASE mydb;
USE mydb;
CREATE TABLE mytable (column_definitions);
DROP DATABASE mydb;
CREATE DATABASE mydb;
USE mydb;
CREATE TABLE mytable (column_definitions);
```
When played back using mysqlbinlog, the second CREATE TABLE statement failed with Error: No Database Selected because the second USE statement was not played back, due to the fact that a database other than mydb was never selected.
This fix insures that mysqlbinlog outputs a USE statement whenever it reads one from the binary log. (Bug #50914, Bug #11758677)
Replication: The --help text for mysqlbinlog now indicates that the --verbose (-v) option outputs pseudo-SQL that is not necessarily valid SQL and cannot be guaranteed to work verbatim in MySQL clients. (Bug #47557, Bug #11755743)
An assertion was raised if an XA COMMIT was issued when an XA transaction had already encountered an error (such as a deadlock) that required the transaction to be rolled back. (Bug #59986, Bug #11766788)
On some systems, debug builds of comp_err.c could fail due to an uninitialized variable. (Bug #59906, Bug #11766729)
Setting the optimizer_switch system value to an invalid value caused a server crash. (Bug #59894, Bug #11766719)
Attempting to create a spatial index on a CHAR column longer than 31 bytes led to an assertion failure if the server was compiled with safemutex support. (Bug #59888, Bug #11766714)
Aggregation followed by a subquery could produce an incorrect result. (Bug #59839, Bug #11766675)
The Performance Schema did not update status handler status variables, so SHOW STATUS LIKE '%handler%' produced undercounted values. (Bug #59799, Bug #11766645)
Internally, XOR items partially behaved like functions and partially as conditions. This resulted in inconsistent handling and crashes. The issue is fixed by consistently treating XOR items as functions. (Bug #59793, Bug #11766642)
An incorrect character set pointer passed to my_strtoll10_mb2() caused an assertion to be raised. (Bug #59648, Bug #11766519)
DES_DECRYPT() could crash if the argument was not produced by DES_ENCRYPT(). (Bug #59632, Bug #11766505)
The server and client did not always properly negotiate authentication plugin names. (Bug #59453, Bug #11766356)
--autocommit=ON did not work (it set the global autocommit value to 0, not 1). (Bug #59432, Bug #11766339)
FIND_IN_SET() could work differently in MySQL 5.5 than in 5.1. (Bug #59405, Bug #11766317)
mysqldump did not quote database names in ALTER DATABASE statements in its output, which could cause an error at reload time for database names containing a dash. (Bug #59398, Bug #11766310)
If filesort fell back to an ordinary sort/merge, it could fail to handle memory correctly. (Bug #59331, Bug #11766260)
Comparisons of aggregate values with TIMESTAMP values were incorrect. (Bug #59330, Bug #11766259)
The “greedy” query plan optimizer failed to consider the size of intermediate query results when calculating the cost of a query. This could result in slowly executing queries when there are much faster execution plans available. (Bug #59326, Bug #11766256)
A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values:
```
SELECT DISTINCT col_name ... ORDER BY col_name DESC;
```
(Bug #59308, Bug #11766241)
The MYSQL_HOME environment variable was being ignored. (Bug #59280, Bug #11766219)
SHOW PRIVILEGES did not display a row for the PROXY privilege. (Bug #59275, Bug #11766216)
SHOW PROFILE could truncate source file names or fail to show function names. (Bug #59273, Bug #11766214)
For DIV expressions, assignment of the result to multiple variables could cause a server crash. (Bug #59241, Bug #11766191)
See also Bug #8457.
MIN(year_col) could return an incorrect result in some cases. (Bug #59211, Bug #11766165)
With index condition pushdown enabled, a join could produce an extra row due to parts of the select condition for the second table in the join not being evaluated. (Bug #59186, Bug #11766144)
DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173)
The ESCAPE clause for the LIKE operator permits only expressions that evaluate to a constant at execution time, but aggregate functions were not being rejected. (Bug #59149, Bug #11766110)
Valgrind warnings about uninitialized variables were corrected. (Bug #59145, Bug #11766106)
Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075)
mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109, Bug #11766074)
There was an erroneous restriction on file attributes for LOAD DATA INFILE. (Bug #59085, Bug #11766052)
SHOW CREATE TRIGGER failed if there was a temporary table with the same name as the trigger subject table. (Bug #58996, Bug #11765972)
The DEFAULT_CHARSET and DEFAULT_COLLATION CMake options did not work. (Bug #58991, Bug #11765967)
In a subquery, a UNION with no referenced tables (or only a reference to the virtual table dual) did not permit an ORDER BY clause. (Bug #58970, Bug #11765950)
OPTIMIZE TABLE for an InnoDB table could raise an assertion if the operation failed because it had been killed. (Bug #58933, Bug #11765920)
If max_allowed_packet was set larger than 16MB, the server failed to reject too-large packets with “Packet too large” errors. (Bug #58887, Bug #11765878)
With index condition pushdown enabled, incorrect results were returned for queries on MyISAM tables involving HAVING and LIMIT, when the column in the WHERE condition contained NULL. (Bug #58838, Bug #11765835)
An uninitialized variable for the index condition pushdown access method could result in a server crash or Valgrind warnings. (Bug #58837, Bug #11765834)
A NOT IN predicate with a subquery containing a HAVING clause could retrieve too many rows, when the subquery itself returned NULL. (Bug #58818, Bug #11765815)
Running a query against an InnoDB table twice, first with index condition pushdown enabled and then with it disabled, could produce different results. (Bug #58816, Bug #11765813)
An assertion was raised if a stored routine had a DELETE IGNORE statement that failed but due to the IGNORE had not reported any error. (Bug #58709, Bug #11765717)
WHERE conditions of the following forms were evaluated incorrectly and could return incorrect results:
```
WHERE null-valued-const-expression NOT IN (subquery)
WHERE null-valued-const-expression IN (subquery) IS UNKNOWN
```
(Bug #58628, Bug #11765642)
Issuing EXPLAIN EXTENDED for a query that would use condition pushdown could cause mysqld to crash. (Bug #58553, Bug #11765570)
An OUTER JOIN query using WHERE col_name IS NULL could return an incorrect result. (Bug #58490, Bug #11765513)
Starting the server with the --defaults-file=file_name option, where the file name had no extension, caused a server crash. (Bug #58455, Bug #11765482)
Outer joins with an empty table could produce incorrect results. (Bug #58422, Bug #11765451)
In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371, Bug #11765406)
When mysqladmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221, Bug #11765270)
Some string-manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong data type. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225)
Condition pushdown optimization could push down conditions with incorrect column references. (Bug #58134, Bug #11765196)
injector::transaction did not have support for rollback. (Bug #58082, Bug #11765150)
Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099)
The fix for Bug #25192 caused load_defaults() to add an argument separator to distinguish options loaded from option files from those provided on the command line, whether or not the application needed it. (Bug #57953, Bug #11765041)
See also Bug #11746296.
The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450, Bug #11764598)
If a multiple-table update updated a row through two aliases and the first update physically moved the row, the second update failed to locate the row. This resulted in different errors depending on the storage engine, although these errors did not accurately describe the problem:
- MyISAM: Got error 134 from storage engine
- InnoDB: Can't find record in 'tbl'
For MyISAM, which is nontransactional, the update executed first was performed but the second was not. In addition, for two equal multiple-table update statements, one could succeed and the other fail depending on whether the record actually moved, which is inconsistent.
Now such an update returns an error if it will update a table through multiple aliases, and perform an update that may physically move the row in at least one of these aliases. (Bug #57373, Bug #11764529, Bug #55385, Bug #11762751)
SHOW WARNINGS output following EXPLAIN EXTENDED could include unprintable characters. (Bug #57341, Bug #11764503)
Outer joins on a unique key could return incorrect results. (Bug #57034, Bug #11764219)
For a query that used a subquery that included GROUP BY inside a < ANY() construct, no rows were returned when there should have been. (Bug #56690, Bug #11763918)
Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817)
On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089)
On Windows, an object in thread local storage could be used before the object was created. (Bug #55730, Bug #11763065)
If one connection locked the mysql.func table using either FLUSH TABLES WITH READ LOCK or LOCK TABLE mysql.func WRITE and a second connection tried to either create or drop a UDF function, a deadlock occurred when the first connection tried to use a UDF function. (Bug #53322, Bug #11760878)
DISTINCT aggregates on DECIMAL UNSIGNED fields could trigger an assertion. (Bug #52171, Bug #11759827)
On FreeBSD, if mysqld was killed with a SIGHUP signal, it could corrupt InnoDB .ibd files. (Bug #51023, Bug #11758773)
An assertion could be raised if –1 was inserted into an AUTO_INCREMENT column by a statement writing more than one row. (Bug #50619, Bug #11758417)
A query that contained an aggregate function but no GROUP BY clause was implicitly grouped. But implicitly grouped queries return zero or one row, so ordering does not make sense. (Bug #47853)
The parser failed to initialize some internal objects properly, which could cause a server crash in the cleanup phase after statement execution. (Bug #47511, Bug #11755703)
When CASE ... WHEN arguments had different character sets, 8-bit values could be referenced as utf16 or utf32 values, raising an assertion. (Bug #44793, Bug #11753363)
When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332, Bug #11752979)
Bitmap functions used in one thread could change bitmaps used by other threads, raising an assertion. (Bug #43152, Bug #11752069)
DATE_ADD() and DATE_SUB() return a string if the first argument is a string, but incorrectly returned a binary string. Now they return a character string with a collation of connection_collation. (Bug #31384, Bug #11747221)

D.1.3. Changes in MySQL 5.6.1 (Not released Milestone 5)

Performance Schema Notes

The Performance Schema has these additions:
- The setup_consumers table contents have changed. Previously, the table used a “flat” structure with a one-to-one correspondence between consumer name and destination table. This has been replaced with a hierarchy of consumer settings that enable progressively finer control of which destinations receive events. The previous xxx_summary_xxx consumers no longer exist. Instead, the Performance Schema maintains appropriate summaries automatically for the levels for which settings in the consumer hierarchy are enabled. For example, if only the top-level (global) consumer is enabled, only global summaries are maintained. Others, such as thread-level summaries, are not. See Section 19.2.3.2.1.4, “Pre-Filtering by Consumer”. In addition, optimizations have been added to reduce Performance Schema overhead.
- It is now possible to filter events by object using the new setup_objects table. Currently, this table can be used to selectively instrument tables, based on schema names and/or table names. See Section 19.2.3.2.1.2, “Pre-Filtering by Object”. A new table, objects_summary_global_by_type, summarizes events for objects.
- It is now possible to filter events by thread, and the Performance Schema collects more information for each thread. A new table, setup_actors, can be used to selectively instrument user connections, based on the user name and/or host name of each connecting session. The threads table, which contains a row for each active server thread, was extended with several new columns. With these additions, the information available in threads is like that available from the INFORMATION_SCHEMA.PROCESSLIST table or the output from SHOW PROCESSLIST. Thus, all three serve to provide information for thread-monitoring purposes. Use of threads differs from use of the other two thread information sources in these ways:
  - Access to threads does not require a mutex and has minimal impact on server performance. INFORMATION_SCHEMA.PROCESSLIST and SHOW PROCESSLIST have negative performance consequences because they require a mutex.
  - threads provides additional information for each thread, such as whether it is a foreground or background thread, and the location within the server associated with the thread.
  - threads provides information about background threads. This means that threads can be used to monitor activity the other thread information sources cannot.
  - You can control which threads are monitored by setting the INSTRUMENTED column or by using the setup_actors table.
  For these reasons, DBAs who perform server monitoring using INFORMATION_SCHEMA.PROCESSLIST or SHOW PROCESSLIST may wish to monitor using threads instead.
If you upgrade to this release of MySQL from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate these changes into the performance_schema database.
For more information, see Chapter 19, MySQL Performance Schema.

Functionality Added or Changed

Incompatible Change: The following obsolete constructs have been removed. Where alternatives are shown, applications should be updated to use them.
- The --log server option and the log system variable. Instead, use the --general_log option to enable the general query log and the --general_log_file=file_name option to set the general query log file name.
- The --log-slow-queries server option and the log_slow_queries system variable. Instead, use the --slow_query_log option to enable the slow query log and the --slow_query_log_file=file_name option to set the slow query log file name.
- The --one-thread server option. Use --thread_handling=no-threads instead.
- The --skip-thread-priority server option.
- The engine_condition_pushdown system variable. Use the engine_condition_pushdown flag of the optimizer_switch variable instead.
- The have_csv, have_innodb, have_ndbcluster, and have_partitioning system variables. Use SHOW ENGINES instead.
- The sql_big_tables system variable. Use big_tables instead.
- The sql_low_priority_updates system variable. Use low_priority_updates instead.
- The sql_max_join_size system variable. Use max_join_size instead.
- The SLAVE START and SLAVE STOP statements. Use the START SLAVE and STOP SLAVE statements instead.
- The ONE_SHOT modifier for the SET statement.
Important Change: Replication: Replication filtering options such as --replicate-do-db, --replicate-rewrite-db, and --replicate-do-table were not consistent with one another in regard to case sensitivity. Now all --replicate-* options follow the same rules for case sensitivity applying to names of databases and tables elsewhere in the MySQL server, including the effects of the lower_case_table_names system variable. (Bug #51639, Bug #11759334)
Important Change: Replication: Added the MASTER_RETRY_COUNT option to the CHANGE MASTER TO statement, and a corresponding Master_Retry_Count column to the output of SHOW SLAVE STATUS. The option sets the value shown in this column. MASTER_RETRY_COUNT is intended eventually to replace the older (and now deprecated) --master-retry-count server option, and is now the preferred method for setting the maximum number of times that the slave may attempt to reconnect after losing its connection to the master. (Bug #44209, Bug #11752887, Bug #44486, Bug #11753110)
Replication: SHOW SLAVE STATUS now displays the actual number of retries for each connection attempt made by the I/O thread. (Bug #56416, Bug #11763675)
Replication: Added the Slave_last_heartbeat status variable, which shows when a replication slave last received a heartbeat signal. The value is displayed using TIMESTAMP format. (Bug #45441)
Replication: Timestamps have been added to the output of SHOW SLAVE STATUS to show when the most recent I/O and SQL thread errors occurred. The Last_IO_Error column is now prefixed with the timestamp for the most recent I/O error, and Last_SQL_Error shows the timestamp for the most recent SQL thread error. The timestamp values use the format YYMMDD HH:MM:SS in both of these columns. For more information, see Section 12.4.5.35, “SHOW SLAVE STATUS Syntax”. (Bug #43535, Bug #11752361)
There is now a bind_address system variable containing the value of the --bind-address option. This enables the address to be accessed at runtime. (Bug #44355, Bug #11752999)
“Unknown table” error messages that included only the table name now include the database name as well. (Bug #34750, Bug #11747993)
Previously, EXPLAIN output for a large union truncated the UNION RESULT row at the end of the list as follows if the string became too large:
```
<union1,2,3,4,...>
```
To make it easier to understand the union boundaries, truncation now occurs in the middle of the string:
```
<union1,2,3,...,9>
```
(Bug #30597, Bug #11747073)
The OpenGIS specification defines functions that test the relationship between two geometry values. MySQL originally implemented these functions such that they used object bounding rectangles and returned the same result as the corresponding MBR-based functions. Corresponding versions are now available that use precise object shapes. These versions are named with an ST_ prefix. For example, Contains() uses object bounding rectangles, whereas ST_Contains() uses object shapes. For more information, see Section 11.17.5.4.2, “Functions That Test Spatial Relationships Between Geometries”.
There are also now ST_ aliases for existing spatial functions that were already exact. For example, ST_IsEmpty() is an alias for IsEmpty() (Bug #4249, Bug #11744883)
The following items are deprecated and will be removed in a future MySQL release. Where alternatives are shown, applications should be updated to use them.
- The thread_concurrency system variable.
- The --language server option. Use the --lc-messages-dir and --lc-messages options instead.
- The --master-retry-count server option. Use the MASTER_RETRY_COUNT option the CHANGE MASTER TO statement instead.
Support for adding Unicode collations that are based on the Unicode Collation Algorithm (UCA) has been improved:
- MySQL now recognizes a larger subset of the LDML syntax that is used to write collation descriptions. In many cases, it is possible to download a collation definition from the Unicode Common Locale Data Repository and paste the relevant part (that is, the part between the <rules> and </rules> tags) into the MySQL Index.xml file.
- Character representation in LDML rules is more flexible. Any character can be written literally, not just basic Latin letters. For collations based on UCA 5.2.0, hexadecimal notation can be used for any character, not just BMP characters.
- When problems are found while parsing Index.xml, better diagnostics are produced.
- For collations that require tailoring rules, there is no longer a fixed size limit on the tailoring information.
For more information, see Section 9.4.4.2, “LDML Syntax Supported in MySQL”, and Section 9.4.4.3, “Diagnostics During Index.xml Parsing”.
TO_BASE64() and FROM_BASE64() functions are now available to perform encoding to and from base-64 strings.
The Unicode implementation has been extended to include a utf16le character set, which corresponds to the UTF-16LE encoding of the Unicode character set. This is similar to utf16 (UTF-16) but is little-endian rather than big-endian.
Two utf16le collations are available:
- utf16le_general_ci: The default collation, case sensitive (similar to utf16_general_ci).
- utf16le_bin: Case sensitive, with by-codepoint comparison that provides the same order as utf16_bin.
There are some limitations on the use of utf16le. With the exception of the item regarding user-defined collations, these are the same as the limitations on ucs2, utf16, and utf32.
- utf16le cannot be used as a client character set, which means that it also does not work for SET NAMES or SET CHARACTER SET.
- It is not possible to use LOAD DATA INFILE to load data files that use utf16le.
- FULLTEXT indexes cannot be created on a column that uses utf16le. However, you can perform IN BOOLEAN MODE searches on the column without an index.
- The use of ENCRYPT() with utf16le is not recommended because the underlying system call expects a string terminated by a zero byte.
- It is not possible to create user-defined UCA collations for utf16le because there is no utf16le_unicode_ci collation, which would serve as the basis for such collations.
Changes to replication in MySQL 5.6 make mysqlbinlog output generated by the --base64-output=ALWAYS option unusable. ALWAYS is now an invalid value for this option. If the option is given without a value, the effect is now the same as --base64-output=AUTO rather than --base64-output=ALWAYS.
See also Bug #28760.
Croatian collations were added for Unicode character sets: utf8_croatian_ci, ucs2_croatian_ci, utf8mb4_croatian_ci, utf16_croatian_ci, and utf32_croatian_ci. Thee collations have tailoring for Croatian letters: Č, Ć, Dž, Đ, Lj, Nj, Š, Ž. They are based on Unicode 4.0.
Several changes were made to optimizer-related system variables:
- The optimizer_switch system variable has new engine_condition_pushdown and index_condition_pushdown flags to control whether storage engine condition pushdown and index condition pushdown optimizations are used. The engine_condition_pushdown system variable now is deprecated. For information about condition pushdown, see Section 7.13.3, “Engine Condition Pushdown Optimization”, and Section 7.13.4, “Index Condition Pushdown Optimization”.
- The optimizer_switch system variable has new mrr and mrr_cost_based flags to control use of the Multi-Range Read optimization. The optimizer_use_mrr system variable has been removed. For information about Multi-Range Read, see Section 7.13.10, “Multi-Range Read Optimization”.
- The join_cache_level system variable has been renamed to optimizer_join_cache_level. This enables a single SHOW VARIABLES LIKE 'optimizer%' statement to show more optimizer-related settings.
The Block Nested-Loop (BNL) Join algorithm previously used only for inner joins has been extended and can be employed for outer join operations, including nested outer joins. For more information, see Section 7.13.11, “Block Nested-Loop Joins”.
In conjunction with this work, a new system variable, optimizer_join_cache_level, controls how join buffering is done.
A --bind-address option has been added to a number of MySQL client programs: mysql, mysqldump, mysqladmin, mysqlbinlog, mysqlcheck, mysqlimport, and mysqlshow. This is for use on a computer having multiple network interfaces, and enables you to choose which interface is used to connect to the MySQL server.
A corresponding change was made to the mysql_options() C API function, which now has a MYSQL_OPT_BIND option for specifying the interface. The argument is a host name or IP address (specified as a string).

Bugs Fixed

Incompatible Change: Replication: The behavior of INSERT DELAYED statements when using statement-based replication has changed as follows:
Previously, when using binlog_format=STATEMENT, a warning was issued in the client when executing INSERT DELAYED; now, no warning is issued in such cases.
Previously, when using binlog_format=STATEMENT, INSERT DELAYED was logged as INSERT DELAYED; now, it is logged as an INSERT, without the DELAYED option.
However, when binlog_format=STATEMENT, INSERT DELAYED continues to be executed as INSERT (without the DELAYED option). The behavior of INSERT DELAYED remains unchanged when using binlog_format=ROW: INSERT DELAYED generates no warnings, is executed as INSERT DELAYED, and is logged using the row-based format.
This change also affects binlog_format=MIXED, because INSERT DELAYED is no longer considered unsafe. Now, when the logging format is MIXED, no switch to row-based logging occurs. This means that the statement is logged as a simple INSERT (that is, without the DELAYED option), using the statement-based logging format. (Bug #54579, Bug #11762035)
See also Bug #56678, Bug #11763907, Bug #57666.
This regression was introduced by Bug #39934, Bug #11749859.
Incompatible Change: Replication: When determining whether to replicate a CREATE DATABASE, DROP DATABASE, or ALTER DATABASE statement, database-level options now take precedence over any --replicate-wild-do-table options. In other words, when trying to replicate one of these statements, --replicate-wild-do-table options are now checked if and only if there are no database-level options that apply to the statement. (Bug #46110, Bug #11754498)
Incompatible Change: Starvation of FLUSH TABLES WITH READ LOCK statements occurred when there was a constant load of concurrent DML statements in two or more connections. Deadlock occurred when a connection that had some table open through a HANDLER statement tried to update data through a DML statement while another connection tried to execute FLUSH TABLES WITH READ LOCK concurrently.
These problems resulted from the global read lock implementation, which was reimplemented with the following consequences:
- To solve deadlock in event-handling code that was exposed by this patch, the LOCK_event_metadata mutex was replaced with metadata locks on events. As a result, DDL operations on events are now prohibited under LOCK TABLES. This is an incompatible change.
- The global read lock (FLUSH TABLES WITH READ LOCK) no longer blocks DML and DDL on temporary tables. Before this patch, server behavior was not consistent in this respect: In some cases, DML/DDL statements on temporary tables were blocked; in others, they were not. Since the main use cases for FLUSH TABLES WITH READ LOCK are various forms of backups and temporary tables are not preserved during backups, the server now consistently permits DML/DDL on temporary tables under the global read lock.
- The set of thread states has changed:
  - Waiting for global metadata lock is replaced by Waiting for global read lock.
  - Previously, Waiting for release of readlock was used to indicate that DML/DDL statements were waiting for release of a read lock and Waiting to get readlock was used to indicate that FLUSH TABLES WITH READ LOCK was waiting to acquire a global read lock. Now Waiting for global read lock is used for both cases.
  - Previously, Waiting for release of readlock was used for all statements that caused an explicit or implicit commit to indicate that they were waiting for release of a read lock and Waiting for all running commits to finish was used by FLUSH TABLES WITH READ LOCK. Now Waiting for commit lock is used for both cases.
  - There are two other new states, Waiting for trigger metadata lock and Waiting for event metadata lock.
(Bug #57006, Bug #11764195, Bug #54673, Bug #11762116)
Incompatible Change: CREATE TABLE statements (including CREATE TABLE ... LIKE) are now prohibited whenever a LOCK TABLES statement is in effect.
One consequence of this change is that CREATE TABLE ... LIKE makes the same checks as CREATE TABLE and does not just copy the .frm file. This means that if the current SQL mode is different from the mode in effect when the original table was created, the table definition might be considered invalid for the new mode and the statement will fail. (Bug #42546, Bug #11751609)
InnoDB Storage Engine: Replication: If the master had innodb_file_per_table=OFF, innodb_file_format=Antelope (and innodb_strict_mode=OFF), or both, certain CREATE TABLE options, such as KEY_BLOCK_SIZE, were ignored. This could permit the master to avoid raising ER_TOO_BIG_ROWSIZE errors.
However, the ignored CREATE TABLE options were still written into the binary log, so that, if the slave had innodb_file_per_table=ON and innodb_file_format=Barracuda, it could encounter an ER_TOO_BIG_ROWSIZE error while executing the record from the log, causing the slave SQL thread to abort and replication to fail.
In the case where the master was running MySQL 5.1 and the slave was MySQL 5.5 (or later), the failure occurred when both master and slave were running with default values for innodb_file_per_table and innodb_file_format. This could cause problems during upgrades.
To address this issue, the default values for innodb_file_per_table and innodb_file_format are reverted to the MySQL 5.1 default values—that is, OFF and Antelope, respectively. (Bug #56318, Bug #11763590)
InnoDB Storage Engine: With binary logging enabled, InnoDB could halt during crash recovery with a message referring to a transaction ID of 0. (Bug #54901, Bug #11762323)
Replication: Due to changes made in MySQL 5.5.3, settings made in the binlog_cache_size and max_binlog_cache_size server system variables affected both the binary log statement cache (also introduced in that version) and the binary log transactional cache (formerly known simply as the binary log cache). This meant that the resources used as a result of setting either or both of these variables were double the amount expected. To rectify this problem, these variables now affect only the transactional cache. The fix for this issue also introduces two new system variables binlog_stmt_cache_size and max_binlog_stmt_cache_size, which affect only the binary log statement cache.
In addition, the Binlog_cache_use status variable was incremented whenever either cache was used, and Binlog_cache_disk_use was incremented whenever the disk space from either cache was used, which caused problems with performance tuning of the statement and transactional caches, because it was not possible to determine which of these was being exceeded when attempting to troubleshoot excessive disk seeks and related problems. This issue is solved by changing the behavior of these two status variables such that they are incremented only in response to usage of the binary log transactional cache, as well as by introducing two new status variables Binlog_stmt_cache_use and Binlog_stmt_cache_disk_use, which are incremented only by usage of the binary log statement cache.
The behavior of the max_binlog_cache_size system variable with regard to active sessions has also been changed to match that of the binlog_cache_size system variable: Previously, a change in max_binlog_cache_size took effect in existing sessions; now, as with a change in binlog_cache_size, a change in max_binlog_cache_size takes effect only in sessions begun after the value was changed.
For more information, see System variables used with the binary log, and Section 5.1.5, “Server Status Variables”. (Bug #57275, Bug #11764443)
Replication: The Binlog_cache_use and Binlog_cache_disk_use status variables were incremented twice by a change to a table using a transactional storage engine. (Bug #56343, Bug #11763611)
Replication: When STOP SLAVE is issued, the slave SQL thread rolls back the current transaction and stops immediately if the transaction updates only tables which use transactional storage engines. Previously, this occurred even when the transaction contained CREATE TEMPORARY TABLE statements, DROP TEMPORARY TABLE statements, or both, although these statements cannot be rolled back. Because temporary tables persist for the lifetime of a user session (in the case, the replication user), they remain until the slave is stopped or reset. When the transaction is restarted following a subsequent START SLAVE statement, the SQL thread aborts with an error that a temporary table to be created (or dropped) already exists (or does not exist, in the latter case).
Following this fix, if an ongoing transaction contains CREATE TEMPORARY TABLE statements, DROP TEMPORARY TABLE statements, or both, the SQL thread now waits until the transaction ends, then stops. (Bug #56118, Bug #11763416)
Replication: When an error occurred in the generation of the name for a new binary log file, the error was logged but not shown to the user. (Bug #46166)
See also Bug #37148, Bug #11748696, Bug #40611, Bug #11750196, Bug #43929, Bug #51019.
Replication: When lower_case_table_names was set to 1 on the slave, but not on the master, names of databases in replicated statements were not converted, causing replication to fail on slaves using case-sensitive file systems. This occurred for both statement-based and row-based replication.
In addition, when using row-based replication with lower_case_table_names set to 1 on the slave only, names of tables were also not converted, also causing replication failure on slaves using case-sensitive file systems. (Bug #37656)
A Valgrind failure occurred in fn_format when called from archive_discover. (Bug #58205, Bug #11765259)
Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion. (Bug #57279, Bug #11764447)
In bootstrap mode, the server could not execute statements longer than 10,000 characters. (Bug #55817, Bug #11763139)
NULL values were not grouped properly for some joins containing GROUP BY. (Bug #45267, Bug #11753766)
A HAVING clause could be lost if an index for ORDER BY was available, incorrectly permitting additional rows to be returned. (Bug #45227, Bug #11753730)
The optimizer could underestimate the memory required for column descriptors during join processing and cause memory corruption or a server crash. (Bug #42744, Bug #11751763)
The server returned incorrect results for WHERE ... OR ... GROUP BY queries against InnoDB tables. (Bug #37977, Bug #11749031)
An incorrectly checked XOR subquery optimization resulted in an assertion failure. (Bug #37899, Bug #11748998)
A query that could use one index to produce the desired ordering and another index for range access with index condition pushdown could cause a server crash. (Bug #37851, Bug #11748981)
With index condition pushdown enabled, InnoDB could crash due to a mismatch between what pushdown code expected to be in a record versus what was actually there. (Bug #36981, Bug #11748647)
The range optimizer ignored conditions on inner tables in semi-join IN subqueries, causing the optimizer to miss good query execution plans. (Bug #35674, Bug #11748263)
A server crash or memory overrun could occur with a dependent subquery and joins. (Bug #34799, Bug #11748009)
Selecting from a view that referenced the same table in the FROM clause and an IN clause caused a server crash. (Bug #33245)
Deeply nested subqueries could cause stack overflow or a server crash. (Bug #32680, Bug #11747503)
The server crashed on optimization of queries that compared an indexed DECIMAL column with a string value. (Bug #32262, Bug #11747426)
The server crashed on optimizations that used the range checked for each record access method. (Bug #32229, Bug #11747417)
If the optimizer used a Multi-Range Read access method for index lookups, incorrect results could occur for rows that contained any BLOB or TEXT data types. (Bug #30622, Bug #11747076)
Compared to MySQL 5.1, the optimizer failed to use join buffering for certain queries, resulting in slower performance for those queries. (Bug #30363, Bug #11747028)
For Multi-Range Read scans used to resolve LIMIT queries, failure to close the scan caused file descriptor leaks for MyISAM tables. (Bug #30221, Bug #11746994)
SHOW CREATE DATABASE did not account for the value of the lower_case_table_names system variable. (Bug #21317, Bug #11745926)

D.1.4. Changes in MySQL 5.6.0 (Not released Milestone 4)

Globally Unique Server IDs

Replication: Globally unique IDs for MySQL servers were implemented. A UUID is now obtained automatically when the MySQL server starts. The server first checks for a UUID written in the auto.cnf file (in the server's data directory), and uses this UUID if found. Otherwise, the server generates a new UUID and saves it to this file (and creates the file if it does not already exist). This UUID is available as the server_uuid system variable.
MySQL replication masters and slaves know each other's UUIDs. The value of a slave's UUID can be read on the master as the system variable slave_uuid, as well as in the output of SHOW SLAVE HOSTS. After a slave is started (with START SLAVE), the value of the master's UUID is available on the slave as the master_uuid system variable, as well as in the output of SHOW SLAVE STATUS.
For more information, see Section 15.1.3, “Replication and Binary Logging Options and Variables”. (Bug #33815, Bug #11747723)
See also Bug #16927, Bug #11745543.

Performance Schema Notes

The Performance Schema now includes instrumentation for table input and output. Instrumented operations include row-level accesses to persistent base tables or temporary tables. Operations that affect rows are fetch, insert, update, and delete. For a view, waits are associated with base tables referenced by the view.

Functionality Added or Changed

Partitioning: It is now possible to exchange a partition of a partitioned table or a subpartition of a subpartitioned table with a nonpartitioned table that otherwise has the same structure using the ALTER TABLE ... EXCHANGE PARTITION statement. This can be used, for example, for importing and exporting partitions.
For more information and examples, see Section 16.3.3, “Exchanging Partitions and Subpartitions with Tables”.
Replication: The unused and deprecated server options --init-rpl-role and --rpl-recovery-rank, as well as the unused and deprecated status variable Rpl_status, have been removed. (Bug #54649, Bug #11762095)
See also Bug #34437, Bug #11747900, Bug #34635, Bug #11747961.
Replication: The SHOW SLAVE STATUS statement now has a Master_Info_File field indicating the location of the master.info file. (Bug #50316, Bug #11758151)
Replication: MySQL now supports delayed replication such that a slave server deliberately lags behind the master by at least a specified amount of time. The default delay is 0 seconds. Use the new MASTER_DELAY option for CHANGE MASTER TO to set the delay to N seconds:
```
CHANGE MASTER TO MASTER_DELAY = N;
```
An event received from the master is not executed until at least N seconds later than its execution on the master.
START SLAVE and STOP SLAVE take effect immediately and ignore any delay. RESET SLAVE resets the delay to 0.
SHOW SLAVE STATUS has three new fields that provide information about the delay:
- SQL_Delay: The number of seconds that the slave must lag the master.
- SQL_Remaining_Delay: When Slave_SQL_Running_State is Waiting until MASTER_DELAY seconds after master executed event, this field contains the number of seconds left of the delay. At other times, this field is NULL.
- Slave_SQL_Running_State: The state of the SQL thread (analogous to Slave_IO_State). The value is identical to the State value of the SQL thread as displayed by SHOW PROCESSLIST.
When the slave SQL thread is waiting for the delay to elapse before executing an event, SHOW PROCESSLIST displays its State value as Waiting until MASTER_DELAY seconds after master executed event.
The relay-log.info file now contains the delay value, so the file format has changed. See Section 15.2.2.2, “Slave Status Logs”. In particular, the first line of the file now indicates how many lines are in the file. If you downgrade a slave server to a version older than MySQL 5.6, the older server will not read the file correctly. To address this, modify the file in a text editor to delete the initial line containing the number of lines.
The introduction of delayed replication entails these restrictions:
- Previously the BINLOG statement could execute all types of events. Now it can execute only format description events and row events.
- The output from mysqlbinlog --base64-output=ALWAYS cannot be parsed. ALWAYS becomes an invalid value for this option in 5.6.1.
For additional information, see Section 15.3.9, “Delayed Replication”. (Bug #28760, Bug #11746794)
The Romansh locale 'rm_CH' is now a permissible value for the lc_time_names system variable. (Bug #50915, Bug #11758678)
mysqlbinlog now has a --binlog-row-event-max-size option to enable large row events to be read from binary log files. (Bug #49932)
mysqldump now has an --add-drop-trigger option which adds a DROP TRIGGER IF EXISTS statement before each dumped trigger definition. (Bug #34325, Bug #11747863)
Vietnamese collations were added for the Unicode character sets. Those based on Unicode Collation Algorithm 5.2.0 have names of the form xxx_vietnamese_520_ci (for example, utf8_vietnamese_520_ci). Those based on Unicode Collation Algorithm 4.0.0 have names of the form xxx_vietnamese_ci (for example, utf8_vietnamese_ci). These collations are the same as the corresponding xxx_unicode_520_ci and xxx_unicode_ci collations except for precomposed characters which are accented versions of “A”, “D”, “E”, “O”, and “U”. There is no change to ideographic characters derived from Chinese. There are no digraphs.
Unicode collation names now may include a version number to indicate the Unicode Collation Algorithm (UCA) version on which the collation is based. Initial collations thus created use version UCA 5.2.0. For example, utf8_unicode_520_ci is based on UCA 5.2.0. UCA-based Unicode collation names that do not include a version number are based on version 4.0.0.
LOWER() and UPPER() perform case folding according to the collation of their argument. A character that has uppercase and lowercase versions only in a Unicode version more recent than 4.0.0 will be converted by these functions only if the argument has a collation that uses a recent enough UCA version.
The LDML rules for creating user-defined collations are extended to permit an optional version attribute in <collation> tags to indicate the UCA version on which the collation is based. If the version attribute is omitted, its default value is 4.0.0. See Section 9.4.4, “Adding a UCA Collation to a Unicode Character Set”.
In MySQL 5.5, setting optimizer_search_depth to the deprecated value of 63 switched to the algorithm used in MySQL 5.0.0 (and previous versions) for performing searches. The value of 63 is now treated as invalid.
The Unicode character sets now have a xxx_german2_ci collation that provides DIN-2 (phone book) ordering (for example, utf8_german2_ci). See Section 9.1.14.1, “Unicode Character Sets”.
mysqlbinlog now has the capability to back up a binary log in its original binary format. When invoked with the --read-from-remote-server and --raw options, mysqlbinlog connects to a server, requests the log files, and writes output files in the same format as the originals. See Section 4.6.7.3, “Using mysqlbinlog to Back Up Binary Log Files”.
A new SQL function, WEIGHT_STRING(), returns the weight string for an input string. The weight string represents the sorting and comparison value of the input string. See Section 11.5, “String Functions”.

Bugs Fixed

Security Fix: Bug #49124 was fixed.
Security Fix: Bug #49124 and Bug #11757121 were fixed.
InnoDB Storage Engine: The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug #55581, Bug #11762927)
Replication: The internal flag indicating whether a user value was signed or unsigned (unsigned_flag) could sometimes change between the time that the user value was recorded for logging purposes and the time that the value was actually written to the binary log, which could lead to inconsistency. Now unsigned_flag is copied when the user variable value is copied, and the copy of unsigned_flag is then used for logging. (Bug #51426, Bug #11759138)
See also Bug #49562, Bug #11757508.
The embedded server could crash when determining which directories to search for option files. (Bug #55062, Bug #11762465)
Performance Schema code was subject to a buffer overflow. (Bug #53363)
On Windows, an IPv6 connection to the server could not be made using an IPv4 address or host name. (Bug #52381, Bug #11760016)
Subquery execution for EXPLAIN could be done incorrectly and raise an assertion. (Bug #52317, Bug #11759957)
There was a mixup between GROUP BY and ORDER BY concerning which indexes should be considered or permitted during query optimization. (Bug #52081, Bug #11759746)
On Windows, the my_rename() function failed to check whether the source file existed. (Bug #51861, Bug #11759540)
The ref column of EXPLAIN output for subquery lines could be missing information. (Bug #50257, Bug #11758106)
Passwords for CREATE USER statements were written to the binary log in plaintext rather than in ciphertext. (Bug #50172)
The BLACKHOLE storage engine failed to load on Solaris and OpenSolaris if DTrace probes had been enabled. (Bug #47748, Bug #11755909)
Some error messages included a literal mysql database name rather than a parameter for the database name. (Bug #46792, Bug #11755079)
In the ER_TABLEACCESS_DENIED_ERROR error message, the command name parameter could be truncated. (Bug #45355, Bug #11753840)
On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181)
To forestall the occurrence of possible relocation errors in the future, libmysys, libmystrings, and libdbug have been changed from normal libraries to “noinst” libtool helper libraries, and are no longer installed as separate libraries. (Bug #29791, Bug #11746931)
A suboptimal query execution plan could be chosen when there were several possible range and ref accesses. Now preference is given to the keys that match the most parts and choosing the best one among them. (Bug #26106, Bug #11746406)
Searches for data on a partial index for a column using the utf8 character set would fail. (Bug #24858)
For queries with GROUP BY, FORCE INDEX was not ignored as it should have been when it would result in a more expensive query execution plan. (Bug #18144, Bug #11745649)

D.2. MySQL Connector/ODBC (MyODBC) Change History

D.2.1. Changes in MySQL Connector/ODBC Version 5.1.x
D.2.2. Changes in MySQL Connector/ODBC Version 5.0.x
D.2.3. Changes in MySQL Connector/ODBC Version 3.51.x

D.2.1. Changes in MySQL Connector/ODBC Version 5.1.x

D.2.1.1. Changes in MySQL Connector/ODBC 5.1.9 (Not released yet)
D.2.1.2. Changes in MySQL Connector/ODBC 5.1.8 (07 November 2010)
D.2.1.3. Changes in MySQL Connector/ODBC 5.1.7 (24 August 2010)
D.2.1.4. Changes in MySQL Connector/ODBC 5.1.6 (09 November 2009)
D.2.1.5. Changes in MySQL Connector/ODBC 5.1.5 (18 August 2008)
D.2.1.6. Changes in MySQL Connector/ODBC 5.1.4 (15 April 2008)
D.2.1.7. Changes in MySQL Connector/ODBC 5.1.3 (26 March 2008)
D.2.1.8. Changes in MySQL Connector/ODBC 5.1.2 (13 February 2008)
D.2.1.9. Changes in MySQL Connector/ODBC 5.1.1 (13 December 2007)
D.2.1.10. Changes in MySQL Connector/ODBC 5.1.0 (10 September 2007)

D.2.1.1. Changes in MySQL Connector/ODBC 5.1.9 (Not released yet)

Bugs Fixed

When executing the SQLProcedureColumns() ODBC function, the driver reported the following error:
```
MySQL server does not provide the requested information
```
(Bug #50400)
When using MySQL Connector/ODBC to fetch data, if a net_write_timeout condition occurred, the operation returned the standard "end of data" status, rather than an error. (Bug #39878)

D.2.1.2. Changes in MySQL Connector/ODBC 5.1.8 (07 November 2010)

Functionality Added or Changed

Documentation in .CHM and .HLP format has been removed from the distribution. (Bug #56232)

Bugs Fixed

For some procedure and parameter combinations SQLProcedureColumns() did not work correctly. For example, it could not return records for an existing procedure with correct parameters supplied.
Further, it returned incorrect data for column 7, TYPE_NAME. For example, it returned VARCHAR(20) instead of VARCHAR. (Bug #57182)
The MySQL Connector/ODBC MSI installer did not set the InstallLocation value in the Microsoft Windows registry. (Bug #56978)
In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the uploaded data contained errors, such as primary key duplication, and foreign key violation. (Bug #56804)
SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if the query was parameterized and not all parameters were bound.
Note, MSDN states that “For performance reasons, an application should not call SQLColAttribute/SQLDescribeCol before executing a statement.” However, it should still be possible to do so if performance reasons are not paramount. (Bug #56717)
When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the driver ran SET @@sql_select_limit=1, which limited the resultset to just one row. (Bug #56677)
After installing MySQL Connector/ODBC, the system DSN created could not be configured or deleted. An error dialog was displayed, showing the error message “Invalid attribute string”.
In this case the problem was due to the fact that the driver could not parse the NULL-separated connection string. (Bug #56233)
When used after a call to SQLTables(), SQLRowCount() did not return the correct value. (Bug #55870)
When attempting to install the latest Connector/ODBC 5.1.6 on Windows using the MSI, with an existing 5.1.x version already installed, the following error was generated:
```
Another version of this product is already installed.  Installation of this version
cannot continue.  To configure or remove the existing version of this product, use
Add/Remove Programs on the Control Panel.
```
Also, the version number displayed in the ODBC Data Source Administrator/Drivers tab did not get updated when removing or installing a new version of 5.1.x. (Bug #54314)

D.2.1.3. Changes in MySQL Connector/ODBC 5.1.7 (24 August 2010)

Functionality Added or Changed

MySQL Connector/ODBC has been changed to support the CLIENT_INTERACTIVE flag. (Bug #48603)

Bugs Fixed

SQLColAttribute(SQL_DESC_PRECISION...) function returned incorrect results for type identifiers that have a negative value:

#define SQL_LONGVARCHAR       (-1) returned 4294967295
#define SQL_BINARY            (-2) returned 4294967294
#define SQL_VARBINARY         (-3) returned 4294967293
#define SQL_LONGVARBINARY     (-4) returned 4294967292
#define SQL_BIGINT            (-5) returned 4294967291
#define SQL_TINYINT           (-6) returned 4294967290
#define SQL_BIT               (-7) returned 4294967289

They were returned as 32-bit unsigned integer values. This only happened on 64-bit Linux. (Bug #55024)

SQLColAttribute for SQL_DESC_OCTET_LENGTH returned length including terminating null byte. It should not have included the null byte. (Bug #54206)
The SQLColumns function returned the incorrect transfer octet length into the column BUFFER_LENGTH for DECIMAL type. (Bug #53235)
SQLForeignKeys() did not return the correct information. The list of foreign keys in other tables should not have included foreign keys that point to unique constraints in the specified table. (Bug #51422)

In contrast to all other ODBC catalog functions SQLTablePrivileges required the user to have SELECT privilege on MySQL schemata, otherwise the function returned with an error:

SQL Error. Native Code: 1142, SQLState: HY000, Return Code: -1
[MySQL][ODBC 5.1 Driver][mysqld-5.0.67-community-nt]SELECT command denied to user
'repadmin'@'localhost' for table 'tables_priv'
[Error][SQL Error]Error executing SQLTablePrivileges for object cat: myrep, object Name:
xxxxxxxxxx

(Bug #50195)

MySQL Connector/ODBC manually added a LIMIT clause to the end of certain SQL statements, causing errors for statements that contained code that should be positioned after the LIMIT clause. (Bug #49726)
If NO_BACKSLASH_ESCAPES mode was used on a server, escaping binary data led to server query parsing errors. (Bug #49029)
Bulk upload operations did not work for queries that used parameters. (Bug #48310)
Retrieval of the current catalog at the moment when a connection was not ready, such as when the connection had been broken or when not all pending results had been processed, resulted in the application crashing. (Bug #46910)
Describing a view or table caused SQLPrepare to prefetch table data. For large tables this created an intolerable performance hit. (Bug #46411)
If an application was invoked by the root user, SQLDriverConnect() was not able to use the username and password in the connection string to connect to the database. (Bug #45378)
Calling SQLColAttribute on a date column did not set SQL_DESC_DATETIME_INTERVAL_CODE. SQLColAttribute returned SQL_SUCCESS but the integer passed in was not set to SQL_CODE_DATE. (Bug #44576)
Conversions for many types were missing from the file driver/info.c. (Bug #43855)
The SQLTables() function required approximately two to four minutes to return the list of 400 tables in a database. The SHOW TABLE STATUS query used by SQLTables() was extremely slow for InnoDB tables with a large number of rows because the query was calculating the approximate number of rows in each table. Further, the results could not be cached due to non-deterministic nature of the result set (the row count was re-calculated every time), impacting performance further. (Bug #43664)
Executing SQLForeignKeys to get imported foreign keys for tables took an excessively long time. For example, getting imported foreign keys for 252 tables to determine parent/child dependencies took about 3 minutes and 14 seconds for the 5.1.5 driver, whereas it took 3 seconds for the 3.5x.x driver. (Bug #39562)
SQLDescribeCol returned incorrect column definitions for SQLTables result. (Bug #37621)
When opening ADO.Recordset from Microsoft Access 2003, a run-time error occurred:
```
ErrNo: -2147467259 ErrMessage: Data provider or other service returned an E_FAIL status.
```
(Bug #36996)
SQLPrimaryKeysW returned mangled strings for table name, column name and primary key name. (Bug #36441)
On Windows, the SOCKET parameter to the DSN was used as the named pipe name to connect to. This was not exposed in the Windows setup GUI. (Bug #34477)
MySQL Connector/ODBC returned a value of zero for a column with a non-zero value. This happened when the column had a data type of BIT, and any numeric type was used in SQLBindCol. (Bug #32821)
Option for handling bad dates was not available in the GUI. (Bug #30539)

D.2.1.4. Changes in MySQL Connector/ODBC 5.1.6 (09 November 2009)

Functionality Added or Changed

In the MySQL Data Source Configuration dialog, an excessive number of tabs were required to navigate to selection of a database. MySQL Connector/ODBC has been changed to make the tab order more practical, thereby enabling faster configuration of a Data Source. (Bug #42905)

Bugs Fixed

An error randomly occurred on Windows 2003 Servers (German language Version) serving classic ASP scripts on IIS6 MDAC version 2.8 SP2 on Windows 2003 SP2. The application connected to MySQL Server 5.0.44-log with a charset of UTF-8 Unicode (utf8). The MySQL server was running on Gentoo Linux.
The script error occurred sporadically on the following line of code:
```
SET my_conn = Server.CreateObject("ADODB.Connection")
my_conn.Open ConnString  <- ERROR
```
The connection was either a DSN or the explicit connection string:
```
Driver={MySQL ODBC 5.1 Driver};SERVER=abc.abc.abc.abc;DATABASE=dbname;UID=uidname;PWD=pwdname;PORT=3306;OPTION=67108864;
```
The error occurred on connections established using either a DNS or a connection string.
When IISState and Debug Diagnostic Tool 1.0.0.152 was used to analyse the code, the following crash analysis was generated:
```
MYODBC5!UTF16TOUTF32+6In 4640-1242788336.dmp the assembly instruction at
myodbc5!utf16toutf32+6 in C:\Programme\MySQL\Connector ODBC 5.1\myodbc5.dll from MySQL AB
has caused an access violation exception (0xC0000005) when trying to read from memory
location 0x194dd000 on thread 33
```
(Bug #44971)
MySQL Connector/ODBC overwrote the query log. MySQL Connector/ODBC was changed to append the log, rather than overwrite it. (Bug #44965)
MySQL Connector/ODBC failed to build with MySQL 5.1.30 due to incorrect use of the data type bool. (Bug #42120)
Inserting a new record using SQLSetPos did not correspond to the database name specified in the SELECT statement when querying tables from databases other than the current one.
SQLSetPos attempted to do the INSERT in the current database, but finished with a SQL_ERROR result and “Table does not exist” message from MySQL Server. (Bug #41946)
Calling SQLDescribeCol() with a NULL buffer and nonzero buffer length caused a crash. (Bug #41942)
MySQL Connector/ODBC updated some fields with random values, rather than with NULL. (Bug #41256)
When a column of type DECIMAL containing NULL was accessed, MySQL Connector/ODBC returned a 0 rather than a NULL. (Bug #41081)
In Access 97, when linking a table containing a LONGTEXT or TEXT field to a MySQL Connector/ODBC DSN, the fields were shown as TEXT(255) in the table structure. Data was therefore truncated to 255 characters. (Bug #40932)
Calling SQLDriverConnect() with a NULL pointer for the output buffer caused a crash if SQL_DRIVER_NOPROMPT was also specified:
```
SQLDriverConnect(dbc, NULL, "DSN=myodbc5", SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT)
```
(Bug #40316)
Setting the ADO Recordset decimal field value to 44.56 resulted in an incorrect value of 445600.0000 being stored when the record set was updated with the Update method. (Bug #39961)
The SQLTablesW API gave incorrect results. For example, table name and table type were returned as NULL rather than as the correct values. (Bug #39957)
MyODBC would crash when a character set was being used on the server that was not supported in the client, for example cp1251:
```
[MySQL][ODBC 5.1 Driver][mysqld-5.0.27-community-nt]Restricted data type attribute violation
```
The fix causes MyODBC to return an error message instead of crashing. (Bug #39831)
Binding SQL_C_BIT to an INTEGER column did not work.
The sql_get_data() function only worked correctly for BOOLEAN columns that corresponded to SQL_C_BIT buffers. (Bug #39644)
When the SQLTables method was called with NULL passed as the tablename parameter, only one row in the resultset, with table name of NULL was returned, instead of all tables for the given database. (Bug #39561)
The SQLGetInfo() function returned 0 for SQL_CATALOG_USAGE information. (Bug #39560)
MyODBC Driver 5.1.5 was not able to connect if the connection string parameters contained spaces or tab symbols. For example, if the SERVER parameter was specified as “SERVER= localhost” instead of “SERVER=localhost” the following error message will be displayed:
```
[MySQL][ODBC 5.1 Driver] Unknown MySQL server host ' localhost' (11001).
```
(Bug #39085)
The pointer passed to the SQLDriverConnect method to retrieve the output connection string length was one greater than it should have been due to the inclusion of the NULL terminator. (Bug #38949)
Data-at-execution parameters were not supported during positioned update. This meant updating a long text field with a cursor update would erroneously set the value to null. This would lead to the error Column 'column_name' cannot be null while updating the database, even when column_name had been assigned a valid nonnull string. (Bug #37649)
The SQLDriverConnect method truncated the OutputConnectionString parameter to 52 characters. (Bug #37278)
The connection string option Enable Auto-reconnect did not work. When the connection failed, it could not be restored, and the errors generated were the same as if the option had not been selected. (Bug #37179)
Insertion of data into a LONGTEXT table field did not work. If such an attempt was made the corresponding field would be found to be empty on examination, or contain random characters. (Bug #36071)
No result record was returned for SQLGetTypeInfo for the TIMESTAMP data type. An application would receive the result return code 100 (SQL_NO_DATA_FOUND). (Bug #30626)
It was not possible to use MySQL Connector/ODBC to connect to a server using SSL. The following error was generated:
```
Runtime error '-2147467259 (80004005)':

[MySQL][ODBC 3.51 Driver]SSL connection error.
```
(Bug #29955)
When the recordSet.Update function was called to update an adLongVarChar field, the field was updated but the recordset was immediately lost. This happened with driver cursors, whether the cursor was opened in optimistic or pessimistic mode.
When the next update was called the test code would exit with the following error:
```
-2147467259 : Query-based update failed because the row to update could not be found.
```
(Bug #26950)
Microsoft Access was not able to read BIGINT values properly from a table with just two columns of type BIGINT and VARCHAR. #DELETE appeared instead of the correct values. (Bug #17679)

D.2.1.5. Changes in MySQL Connector/ODBC 5.1.5 (18 August 2008)

Bugs Fixed

ODBC TIMESTAMP string format is not handled properly by the MyODBC driver. When passing a TIMESTAMP or DATE to MyODBC, in the ODBC format: {d <date>} or {ts <timestamp>}, the string that represents this is copied once into the SQL statement, and then added again, as an escaped string. (Bug #37342)
The connector failed to prompt for additional information required to create a DSN-less connection from an application such as Microsoft Excel. (Bug #37254)
SQLDriverConnect does not return SQL_NO_DATA on cancel. The ODBC documentation specifies that this method should return SQL_NO_DATA when the user cancels the dialog to connect. The connector, however, returns SQL_ERROR. (Bug #36293)
Assigning a string longer than 67 characters to the TableType parameter resulted in a buffer overrun when the SQLTables() function was called. (Bug #36275)
The ODBC connector randomly uses logon information stored in odbc-profile, or prompts the user for connection information and ignores any settings stored in odbc-profile. (Bug #36203)
After having successfully established a connection, a crash occurs when calling SQLProcedures() followed by SQLFreeStmt(), using the ODBC C API. (Bug #36069)

D.2.1.6. Changes in MySQL Connector/ODBC 5.1.4 (15 April 2008)

Bugs Fixed

Wrong result obtained when using sum() on a decimal(8,2) field type. (Bug #35920)
The driver installer could not create a new DSN if many other drivers were already installed. (Bug #35776)
The SQLColAttribute() function returned SQL_TRUE when querying the SQL_DESC_FIXED_PREC_SCALE (SQL_COLUMN_MONEY) attribute of a DECIMAL column. Previously, the correct value of SQL_FALSE was returned; this is now again the case. (Bug #35581)
On Linux, SQLGetDiagRec() returned SQL_SUCCESS in cases when it should have returned SQL_NO_DATA. (Bug #33910)
The driver crashes ODBC Administrator on attempting to add a new DSN. (Bug #32057)

D.2.1.7. Changes in MySQL Connector/ODBC 5.1.3 (26 March 2008)

Platform-Specific Notes

Important Change: You must uninstall previous 5.1.x editions of MySQL Connector/ODBC before installing the new version.
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.

Bugs Fixed

Important Change: In previous versions, the SSL certificate would automatically be verified when used as part of the MySQL Connector/ODBC connection. The default mode is now to ignore the verificate of certificates. To enforce verification of the SSL certificate during connection, use the SSLVERIFY DSN parameter, setting the value to 1. (Bug #29955, Bug #34648)
Inserting characters to a UTF8 table using surrogate pairs would fail and insert invalid data. (Bug #34672)
Installation of MySQL Connector/ODBC would fail because it was unable to uninstall a previous installed version. The file being requested would match an older release version than any installed version of the connector. (Bug #34522)
Using SqlGetData in combination with SQL_C_WCHAR would return overlapping data. (Bug #34429)
Descriptor records were not cleared correctly when calling SQLFreeStmt(SQL_UNBIND). (Bug #34271)
The dropdown selection for databases on a server when creating a DSN was too small. The list size now automatically adjusts up to a maximum size of 20 potential databases. (Bug #33918)
Microsoft Access would be unable to use DBEngine.RegisterDatabase to create a DSN using the MySQL Connector/ODBC driver. (Bug #33825)
MySQL Connector/ODBC erroneously reported that it supported the CAST() and CONVERT() ODBC functions for parsing values in SQL statements, which could lead to bad SQL generation during a query. (Bug #33808)
Using a linked table in Access 2003 where the table has a BIGINT column as the first column in the table, and is configured as the primary key, shows #DELETED for all rows of the table. (Bug #24535)
Updating a RecordSet when the query involves a BLOB field would fail. (Bug #19065)

D.2.1.8. Changes in MySQL Connector/ODBC 5.1.2 (13 February 2008)

MySQL Connector/ODBC 5.1.2-beta, a new version of the ODBC driver for the MySQL database management system, has been released. This release is the second 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.

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.
Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of MySQL Connector/ODBC 5.1.x before upgrading.
See also Bug #34571.

Functionality Added or Changed

Explicit descriptors are implemented. (Bug #32064)
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.
Changed SQL_ATTR_PARAMSET_SIZE to return an error until support for it is implemented.
Disabled MYSQL_OPT_SSL_VERIFY_SERVER_CERT when using an SSL connection.
SQLForeignKeys uses INFORMATION_SCHEMA when it is available on the server, which enables more complete information to be returned.

Bugs Fixed

The SSLCIPHER option would be incorrectly recorded within the SSL configuration on Windows. (Bug #33897)
Within the GUI interface, when connecting to a MySQL server on a nonstandard port, the connection test within the GUI would fail. The issue was related to incorrect parsing of numeric values within the DSN when the option was not configured as the last parameter within the DSN. (Bug #33822)
Specifying a nonexistent database name within the GUI dialog would result in an empty list, not an error. (Bug #33615)
When deleting rows from a static cursor, the cursor position would be incorrectly reported. (Bug #33388)
SQLGetInfo() reported characters for SQL_SPECIAL_CHARACTERS that were not encoded correctly. (Bug #33130)
Retrieving data from a BLOB column would fail within SQLGetDatawhen the target data type was SQL_C_WCHAR due to incorrect handling of the character buffer. (Bug #32684)
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)
When accessing column data, FLAG_COLUMN_SIZE_S32 did not limit the octet length or display size reported for fields, causing problems with Microsoft Visual FoxPro.
The list of ODBC functions that could have caused failures in Microsoft software when retrieving the length of LONGBLOB or LONGTEXT columns includes:
- SQLColumns
- SQLColAttribute
- SQLColAttributes
- SQLDescribeCol
- SQLSpecialColumns (theoretically can have the same problem)
(Bug #12805, Bug #30890)
Dynamic cursors on statements with parameters were not supported. (Bug #11846)
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)

D.2.1.9. 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.
Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of MySQL Connector/ODBC 5.1.x before upgrading.
See also Bug #34571.

Functionality Added or Changed

Incompatible Change: Replaced myodbc3i (now myodbc-installer) with MySQL Connector/ODBC 5.0 version.
Incompatible Change: Removed monitor (myodbc3m) and dsn-editor (myodbc3c).
Incompatible Change: Do not permit 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 nonthreadsafe 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 MySQL 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)
MySQL 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.

D.2.1.10. 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.
Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of MySQL Connector/ODBC 5.1.x before upgrading.
See also Bug #34571.

Functionality Added or Changed

Added support for Unicode functions (SQLConnectW, etc).
Added descriptor support (SQLGetDescField, SQLGetDescRec, etc).
Added support for SQL_C_WCHAR.

D.2.2. Changes in MySQL Connector/ODBC Version 5.0.x

D.2.2.1. Changes in MySQL Connector/ODBC 5.0.12 (Never released)
D.2.2.2. Changes in MySQL Connector/ODBC 5.0.11 (31 January 2007)
D.2.2.3. Changes in MySQL Connector/ODBC 5.0.10 (14 December 2006)
D.2.2.4. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)
D.2.2.5. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)
D.2.2.6. Changes in MySQL Connector/ODBC 5.0.7 (08 November 2006)
D.2.2.7. Changes in MySQL Connector/ODBC 5.0.6 (03 November 2006)
D.2.2.8. Changes in MySQL Connector/ODBC 5.0.5 (17 October 2006)
D.2.2.9. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)
D.2.2.10. Changes in Connector/ODBC 5.0.2 (Never released)
D.2.2.11. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)

D.2.2.1. 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.

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)

D.2.2.2. 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.

D.2.2.3. 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)

D.2.2.4. 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_NUMERIC_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 using SQLColAttribute/SQL_DESC_DISPLAY_SIZE.
Fixed buffer length return for SQLDriverConnect.
ODBC v2 behavior 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.

D.2.2.5. 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 handling 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.

D.2.2.6. 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.

D.2.2.7. 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

MySQL 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 MySQL Connector/ODBC 3.51 installed before installing this version.

Bugs Fixed

You no longer have to have MySQL Connector/ODBC 3.51 installed before installing this version.
MySQL Connector/ODBC supports both User and System DSNs.
Installation is provided in the form of a standard Microsoft System Installer (MSI).

D.2.2.8. 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 MySQL Connector/ODBC 3.51 installed before installing this version.

D.2.2.9. 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

D.2.2.10. Changes in Connector/ODBC 5.0.2 (Never released)

Connector/ODBC 5.0.2 was an internal implementation and testing release.

D.2.2.11. 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

D.2.3. Changes in MySQL Connector/ODBC Version 3.51.x

D.2.3.1. Changes in MySQL Connector/ODBC 3.51.28 (09 February 2011)
D.2.3.2. Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008)
D.2.3.3. Changes in MySQL Connector/ODBC 3.51.26 (07 July 2008)
D.2.3.4. Changes in MySQL Connector/ODBC 3.51.25 (11 April 2008)
D.2.3.5. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)
D.2.3.6. Changes in MySQL Connector/ODBC 3.51.23 (09 January 2008)
D.2.3.7. Changes in MySQL Connector/ODBC 3.51.22 (13 November 2007)
D.2.3.8. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)
D.2.3.9. Changes in MySQL Connector/ODBC 3.51.20 (10 September 2007)
D.2.3.10. Changes in MySQL Connector/ODBC 3.51.19 (10 August 2007)
D.2.3.11. Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)
D.2.3.12. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)
D.2.3.13. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)
D.2.3.14. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)
D.2.3.15. Changes in MySQL Connector/ODBC 3.51.14 (08 March 2007)
D.2.3.16. Changes in MySQL Connector/ODBC 3.51.13 (Never released)
D.2.3.17. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)
D.2.3.18. Changes in MySQL Connector/ODBC 3.51.11 (28 January 2005)

D.2.3.1. Changes in MySQL Connector/ODBC 3.51.28 (09 February 2011)

Bugs Fixed

SQLColAttribute(...SQL_DESC_CASE_SENSITIVE...) returned SQL_FALSE for binary types and SQL_TRUE for the rest. It should have returned SQL_TRUE for binary types, and SQL_FALSE for the rest. (Bug #54212)
SQLColAttribute for SQL_DESC_OCTET_LENGTH returned length including terminating null byte. It should not have included the null byte. (Bug #54206)
When executing the SQLProcedureColumns() ODBC function, the driver reported the following error:
```
MySQL server does not provide the requested information
```
(Bug #50400)
If NO_BACKSLASH_ESCAPES mode was used on a server, escaping binary data led to server query parsing errors. (Bug #49029)
Inserting a new record using SQLSetPos did not correspond to the database name specified in the SELECT statement when querying tables from databases other than the current one.
SQLSetPos attempted to do the INSERT in the current database, but finished with a SQL_ERROR result and “Table does not exist” message from MySQL Server. (Bug #41946)
When using MySQL Connector/ODBC to fetch data, if a net_write_timeout condition occurred, the operation returned the standard "end of data" status, rather than an error. (Bug #39878)
No result record was returned for SQLGetTypeInfo for the TIMESTAMP data type. An application would receive the result return code 100 (SQL_NO_DATA_FOUND). (Bug #30626)
Microsoft Access was not able to read BIGINT values properly from a table with just two columns of type BIGINT and VARCHAR. #DELETE appeared instead of the correct values. (Bug #17679)

D.2.3.2. Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008)

Bugs Fixed

The client program hung when the network connection to the server was interrupted. (Bug #40407)
The connection string option Enable Auto-reconnect did not work. When the connection failed, it could not be restored, and the errors generated were the same as if the option had not been selected. (Bug #37179)
It was not possible to use MySQL Connector/ODBC to connect to a server using SSL. The following error was generated:
```
Runtime error '-2147467259 (80004005)':

[MySQL][ODBC 3.51 Driver]SSL connection error.
```
(Bug #29955)

D.2.3.3. Changes in MySQL Connector/ODBC 3.51.26 (07 July 2008)

Functionality Added or Changed

There is a new connection option, FLAG_NO_BINARY_RESULT. When set this option disables charset 63 for columns with an empty org_table. (Bug #29402)

Bugs Fixed

When an ADOConnection is created and attempts to open a schema with ADOConnection.OpenSchema an access violation occurs in myodbc3.dll. (Bug #30770)
When SHOW CREATE TABLE was invoked and then the field values read, the result was truncated and unusable if the table had many rows and indexes. (Bug #24131)

D.2.3.4. Changes in MySQL Connector/ODBC 3.51.25 (11 April 2008)

Bugs Fixed

The SQLColAttribute() function returned SQL_TRUE when querying the SQL_DESC_FIXED_PREC_SCALE (SQL_COLUMN_MONEY) attribute of a DECIMAL column. Previously, the correct value of SQL_FALSE was returned; this is now again the case. (Bug #35581)
The driver crashes ODBC Administrator on attempting to add a new DSN. (Bug #32057)
When accessing column data, FLAG_COLUMN_SIZE_S32 did not limit the octet length or display size reported for fields, causing problems with Microsoft Visual FoxPro.
The list of ODBC functions that could have caused failures in Microsoft software when retrieving the length of LONGBLOB or LONGTEXT columns includes:
- SQLColumns
- SQLColAttribute
- SQLColAttributes
- SQLDescribeCol
- SQLSpecialColumns (theoretically can have the same problem)
(Bug #12805, Bug #30890)

D.2.3.5. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)

Bugs Fixed

Security Enhancement: Accessing a parameter with the type of SQL_C_CHAR, but with a numeric type and a length of zero, the parameter marker would get stripped from the query. In addition, an SQL injection was possible if the parameter value had a nonzero length and was not numeric, the text would be inserted verbatim. (Bug #34575)
Important Change: In previous versions, the SSL certificate would automatically be verified when used as part of the MySQL Connector/ODBC connection. The default mode is now to ignore the verificate of certificates. To enforce verification of the SSL certificate during connection, use the SSLVERIFY DSN parameter, setting the value to 1. (Bug #29955, Bug #34648)
When using ADO, the count of parameters in a query would always return zero. (Bug #33298)
Using tables with a single quote or other nonstandard characters in the table or column names through ODBC would fail. (Bug #32989)
When using Crystal Reports, table and column names would be truncated to 21 characters, and truncated columns in tables where the truncated name was the duplicated would lead to only a single column being displayed. (Bug #32864)
SQLExtendedFetch() and SQLFetchScroll() ignored the rowset size if the Don't cache result DSN option was set. (Bug #32420)
When using the ODBC SQL_TXN_READ_COMMITTED option, 'dirty' records would be read from tables as if the option had not been applied. (Bug #31959)
When creating a System DSN using the ODBC Administrator on Mac OS X, a User DSN would be created instead. The root cause is a problem with the iODBC driver manager used on Mac OS X. The fix works around this issue.
Note
ODBC Administrator may still be unable to register a System DSN unless the /Library/ODBC/odbc.ini file has the correct permissions. You should ensure that the file is writable by the admin group.
(Bug #31495)
Calling SQLFetch or SQLFetchScroll would return negative data lengths when using SQL_C_WCHAR. (Bug #31220)
SQLSetParam() caused memory allocation errors due to driver manager's mapping of deprecated functions (buffer length -1). (Bug #29871)
Static cursor was unable to be used through ADO when dynamic cursors were enabled. (Bug #27351)
Using connection.Execute to create a record set based on a table without declaring the cmd option as adCmdTable will fail when communicating with versions of MySQL 5.0.37 and higher. The issue is related to the way that SQLSTATE is returned when ADO tries to confirm the existence of the target object. (Bug #27158)
Updating a RecordSet when the query involves a BLOB field would fail. (Bug #19065)
With some connections to MySQL databases using MySQL Connector/ODBC, the connection would mistakenly report 'user cancelled' for accesses to the database information. (Bug #16653)

D.2.3.6. Changes in MySQL Connector/ODBC 3.51.23 (09 January 2008)

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

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

D.2.3.7. 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)

D.2.3.8. 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 permitted NULL values. This was dur to an issue with NULLABLE and IS_NULLABLE return values from the call to SQLColumns(). (Bug #26108)
MySQL 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. MySQL Connector/ODBC now correctly returns an SQLSTATE of 08S01. (Bug #3456)

D.2.3.9. 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 user name 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 check box 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.

D.2.3.10. 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 D.2.3.11, “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.

D.2.3.11. 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

Incompatible Change: The FLAG_DEBUG option was removed.
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 MySQL 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)
MySQL Connector/ODBC now supports batched statements. 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 #30081)
See also Bug #9927.
Fixed an issue where the myodbc3i would update the user ODBC configuration file (~/Library/ODBC/odbcinst.ini) instead of the system /Library/ODBC/odbcinst.ini. This was caused because myodbc3i was not honoring 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.

D.2.3.12. 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 enable 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)
MySQL 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, MySQL 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 permitted 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, MySQL 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 nonalphanumeric 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.

D.2.3.13. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)

Functionality Added or Changed

MySQL 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 cursors 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)
Return values from SQLTables() may be truncated. (Bug #22797)
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)

D.2.3.14. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)

Bugs Fixed

MySQL 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)
MySQL Connector/ODBC would return too many foreign key results when accessing tables with similar names. (Bug #4518)

D.2.3.15. 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 MySQL Connector/ODBC option parameters. (Bug #10910)
Added auto-reconnect option to MySQL 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)
MySQL Connector/ODBC may insert the wrong parameter values when using prepared statements under 64-bit Linux. (Bug #22446)
Using MySQL 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, MySQL 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, MySQL Connector/ODBC and the embedded MySQL server. (Bug #16535)
The SQLDriverConnect() ODBC method did not work with recent MySQL Connector/ODBC releases. (Bug #12393)

D.2.3.16. Changes in MySQL Connector/ODBC 3.51.13 (Never released)

Connector/ODBC 3.51.13 was an internal implementation and testing release.

This section has no changelog entries.

D.2.3.17. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)

Functionality Added or Changed

Bugs Fixed

Using stored procedures with ADO, where the CommandType 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)

D.2.3.18. 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)

D.3. MySQL Connector/Net Change History

D.3.1. Changes in MySQL Connector/Net Version 6.4.x
D.3.2. Changes in MySQL Connector/Net Version 6.3.x
D.3.3. Changes in MySQL Connector/Net Version 6.2.x
D.3.4. Changes in MySQL Connector/Net Version 6.1.x
D.3.5. Changes in MySQL Connector/Net Version 6.0.x
D.3.6. Changes in MySQL Connector/Net Version 5.3.x
D.3.7. Changes in MySQL Connector/Net Version 5.2.x
D.3.8. Changes in MySQL Connector/Net Version 5.1.x
D.3.9. Changes in MySQL Connector/Net Version 5.0.x
D.3.10. Changes in MySQL Connector/Net Version 1.0.x
D.3.11. Changes in MySQL Connector/Net Version 0.9.0 (30 August 2004)
D.3.12. Changes in MySQL Connector/Net Version 0.76
D.3.13. Changes in MySQL Connector/Net Version 0.75
D.3.14. Changes in MySQL Connector/Net Version 0.74
D.3.15. Changes in MySQL Connector/Net Version 0.71
D.3.16. Changes in MySQL Connector/Net Version 0.70
D.3.17. Changes in MySQL Connector/Net Version 0.68
D.3.18. Changes in MySQL Connector/Net Version 0.65
D.3.19. Changes in MySQL Connector/Net Version 0.60
D.3.20. Changes in MySQL Connector/Net Version 0.50

D.3.1. Changes in MySQL Connector/Net Version 6.4.x

D.3.1.1. Changes in MySQL Connector/Net 6.4.4 (Not yet released)
D.3.1.2. Changes in MySQL Connector/Net 6.4.3 (05 July 2011)
D.3.1.3. Changes in MySQL Connector/Net 6.4.2 (29 June 2011)
D.3.1.4. Changes in MySQL Connector/Net 6.4.1 (06 June 2011 Alpha)

D.3.1.1. Changes in MySQL Connector/Net 6.4.4 (Not yet released)

This release fixes bugs since 6.4.3.

Bugs Fixed

MySqlDataReader.Close was modified to use Default behavior when clearing remaining result sets. (Bug #61690, Bug #12723423)
MySqlScript was modified to enable correct processing of the DELIMITER command when not followed by a new line. (Bug #61680, Bug #12732279)
The ASP.NET membership provider was modified to create and query all related tables using lowercase names. (Bug #61108, Bug #12702009)
On Model First changed column types generated in SQL scripts to produce more suitable MySql types. (Bug #59244, Bug #12707104)

D.3.1.2. Changes in MySQL Connector/Net 6.4.3 (05 July 2011)

This release fixes bugs since 6.4.2.

Bugs Fixed

SchemaDefinition-5.5.ssdl was modified to treat CHAR(36) columns as a GUID. (Bug #61657, Bug #12708208)
SqlFragment.QuoteIdentifier was modified to add MySQL quotes around identifiers. (Bug #61635, Bug #12707285)

D.3.1.3. Changes in MySQL Connector/Net 6.4.2 (29 June 2011)

This release fixes bugs since 6.4.1.

Bugs Fixed

Modified MySqlConnection.BeginTransaction to throw a NotSupportedException for Snapshot isolation level. (Bug #61589, Bug #12698020)
Modified ProviderManifest.xml to map TIMESTAMP database columns to the DateTime .NET type. (Bug #55351, Bug #12652602)
Fixed Entity Framework provider GROUP BY clause generation by adding all group-by keys to the SELECT statement. (Bug #46742, Bug #12622129)

D.3.1.4. Changes in MySQL Connector/Net 6.4.1 (06 June 2011 Alpha)

First alpha release.

Functionality Added or Changed

Calling a stored procedure with output parameters caused a marked performance decrease. (Bug #60366, Bug #12425959)
Changed how the procedure schema collection is retrieved. If the connection string contains “use procedure bodies=true” then a SELECT is performed on the mysql.proc table directly, as this is up to 50 times faster than the current Information Schema implementation. If the connection string contains “use procedure bodies=false”, then the Information Schema collection is queried. (Bug #36694)

D.3.2. Changes in MySQL Connector/Net Version 6.3.x

D.3.2.1. Changes in MySQL Connector/Net 6.3.9 (Not yet released)
D.3.2.2. Changes in MySQL Connector/Net 6.3.8 (Not yet released)
D.3.2.3. Changes in MySQL Connector/Net 6.3.7 (22 June 2011)
D.3.2.4. Changes in MySQL Connector/Net 6.3.6 (03 January 2011)
D.3.2.5. Changes in MySQL Connector/Net 6.3.5 (12 October 2010)
D.3.2.6. Changes in MySQL Connector/Net 6.3.4 (01 September 2010 GA)
D.3.2.7. Changes in MySQL Connector/Net 6.3.3 (27 July 2010)
D.3.2.8. Changes in MySQL Connector/Net 6.3.2 (24 May 2010 beta)
D.3.2.9. Changes in MySQL Connector/Net 6.3.1 (02 March 2010)
D.3.2.10. Changes in MySQL Connector/Net 6.3.0 (16 February 2010 alpha)

D.3.2.1. Changes in MySQL Connector/Net 6.3.9 (Not yet released)

This release fixes bugs since 6.3.8.

Bugs Fixed

On Model First changed column types generated in SQL scripts to produce more suitable MySql types. (Bug #59244, Bug #12707104)

D.3.2.2. Changes in MySQL Connector/Net 6.3.8 (Not yet released)

This release fixes bugs since 6.3.7.

Bugs Fixed

MySqlDataReader.Close was modified to use Default behavior when clearing remaining result sets. (Bug #61690, Bug #12723423)
MySqlScript was modified to enable correct processing of the DELIMITER command when not followed by a new line. (Bug #61680, Bug #12732279)
SchemaDefinition-5.5.ssdl was modified to treat CHAR(36) columns as a GUID. (Bug #61657, Bug #12708208)
SqlFragment.QuoteIdentifier was modified to add MySQL quotes around identifiers. (Bug #61635, Bug #12707285)
Modified MySqlConnection.BeginTransaction to throw a NotSupportedException for Snapshot isolation level. (Bug #61589, Bug #12698020)
The ASP.NET membership provider was modified to create and query all related tables using lowercase names. (Bug #61108, Bug #12702009)
Modified ProviderManifest.xml to map TIMESTAMP database columns to the DateTime .NET type. (Bug #55351, Bug #12652602)

D.3.2.3. Changes in MySQL Connector/Net 6.3.7 (22 June 2011)

This release fixes bugs since 6.3.6.

Functionality Added or Changed

Calling a stored procedure with output parameters caused a marked performance decrease. (Bug #60366, Bug #12425959)

Bugs Fixed

MySQL Connector/Net 6.3.6 did not work with Visual Studio 2010. (Bug #60723, Bug #12394470)
MysqlDataReader.GetSchemaTable returned incorrect values and types. (Bug #59989, Bug #11776346)
All queries other than INSERT were executed individually instead of as a batch even though batching was enabled for the connection. (Bug #59616, Bug #11850286)

MySQL Connector/Net generated an exception when executing a query consisting of ';', for example:

mycmd(";",mycon)
mycmd.executenonquery()

The exception generated was:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MySql.Data.MySqlClient.MySqlCommand.TrimSemicolons(String sql)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #59537, Bug #11766433)

Setting Membership.ApplicationName had no effect. (Bug #59438, Bug #11770465)
A NullReferenceException was thrown on disposal of a TransactionScope object. (Bug #59346, Bug #11766272)
The setup wizard failed with the error “Setup Wizard ended prematurely because of an error”. This was because it assumed .NET Framework version 4.0 was located on the C: drive, when it was actually located on the E: drive. (Bug #59301)
Fixed Entity Framework provider GROUP BY clause generation by adding all group-by keys to the SELECT statement. (Bug #46742, Bug #12622129)

D.3.2.4. Changes in MySQL Connector/Net 6.3.6 (03 January 2011)

This release fixes bugs since 6.3.5.

Functionality Added or Changed

Changed how the procedure schema collection is retrieved. If the connection string contains “use procedure bodies=true” then a SELECT is performed on the mysql.proc table directly, as this is up to 50 times faster than the current Information Schema implementation. If the connection string contains “use procedure bodies=false”, then the Information Schema collection is queried. (Bug #36694)

Bugs Fixed

MembershipProvider did not generate hashes correctly if the algorithm was keyed. The Key of the algorithm should have been set if the HashAlgorithm was KeyedHashAlgorithm. (Bug #58906)
Code introduced to fix bug #54863 proved problematic on .NET version 3.5 and above. (Bug #58853)
The MySqlTokenizer contained unnecessary Substring and Trim calls:
```
string token = sql.Substring(startIndex, stopIndex - startIndex).Trim();
```
The variable token was not used anywhere in the code. (Bug #58757)
MySqlCommand.ExecuteReader(CommandBehavior) threw a NullReferenceException when being called with CommandBehavior.CloseConnection, if the SQL statement contained a syntax error, or contained invalid data such as an invalid column name. (Bug #58652)
ReadFieldLength() returned incorrect value for BIGINT autoincrement columns. (Bug #58373)
When attempting to create an ADO.NET Entity Data Model, MySQL connections were not available. (Bug #58278)
MySQL Connector/Net did not support the utf8mb4 character set. When attempting to connect to utf8mb4 tables or columns, an exception KeyNotFoundException was generated. (Bug #58244)

Installation of MySQL Connector/Net 6.3.5 failed. The error reported was:

MySQL Connector Net 6.3.5 Setup Wizard ended 
prematurely because of an error. Your system has not been modified.

(Bug #57654)

When the tracing driver was used and an SQL statement was longer than 300 characters, an ArgumentOutOfRangeExcpetion occurred if the statement also contained a quoted character, and the 300th character was in the middle of a quoted token. (Bug #57641)

Calling the Read() method on a DataReader obtained from MySqlHelper.ExecuteReader generated the following exception:

Unhandled Exception: MySql.Data.MySqlClient.MySqlException: Invalid attempt to R
ead when reader is closed.
   at MySql.Data.MySqlClient.MySqlDataReader.Read()
   at MySqlTest.MainClass.Main(String[] args)

(Bug #57501)

Default values returned for text columns were not quoted. This meant that the COLUMN_DEFAULT field of the GetSchema columns collection did not return a valid SQL expression. (Bug #56509)

When using MySQL Connector/Net on Mono 2.8 using .NET 4.0, attempting to connect to a MySQL database generated the following exception:

Unhandled Exception: System.MissingMethodException: Method not found:
 'System.Data.Common.DbConnection.EnlistTransaction'.
  at (wrapper remoting-invoke-with-check)
 MySql.Data.MySqlClient.MySqlConnection:Open ()

(Bug #56509)

MySQL Connector/Net for .NET/Mono attempted to dynamically load the assembly Mono.Posix.dll when a Unix socket was used to connect to the server. This failed and the connector was not able to use a Unix socket unless the Mono.Posix.dll assembly was previously loaded by the program. (Bug #56410)
The ADO.NET Entity Data Model could not add stored procedures from MySQL Server 5.0.45 but worked fine using MySQL Server 5.1. (Bug #55349)
In the ADO.NET Entity Data Model Wizard, the time to update a model scaled abnormally as the number of entities increased. (Bug #48791, Bug #12596237)

D.3.2.5. Changes in MySQL Connector/Net 6.3.5 (12 October 2010)

This release fixes bugs since 6.3.4.

Bugs Fixed

A typed dataset did not get the table name. (Bug #57894, Bug #11764989)
Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug #57265)
When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug #57092)
MySQL Connector/Net experienced two problems as follows:
1. A call to System.Data.Objects.ObjectContext.DatabaseExists() returned false, even if the database existed.
2. A call to System.Data.Objects.ObjectContext.CreateDatabase() created a database but with a name other than the one specified in the connection string. It then failed to use it when EDM objects were processed.
(Bug #56859)
Setting the Default Command Timeout connection string option had no effect. (Bug #56806)
When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug #56756)
MySqlHelper.ExecuteReader did not include an overload accepting MySqlParameter objects when using a MySqlConnection. However, MySqlHelper did include an overload for MySqlParameter objects when using a string object containing the connection string to the database. (Bug #56755)

MySQL Connector/Net 6.1.3 (GA) would not install on a Windows Server 2008 (Web Edition) clean installation. There were two problems:

If .NET framework version 4.0 was not installed, installation failed because c:\windows\microsoft.net\v4.0.* did not exist.

If .NET 4.0 was subsequently installed, then the following error was generated:

InstallFiles: File: MySql.Data.Entity.dll,  Directory: ,  Size: 229888
MSI (s) (E0:AC) [15:20:26:196]: Assembly Error:The assembly is built by a runtime newer
than the currently loaded runtime, and cannot be loaded.
MSI (s) (E0:AC) [15:20:26:196]: Note: 1: 1935 2:  3: 0x8013101B 4: IStream 5: Commit 6: 
MSI (s) (E0:A0) [15:20:26:196]: Note: 1: 1304 2: MySql.Data.Entity.dll 
Error 1304. Error writing to file: MySql.Data.Entity.dll. Verify that you have access to
that directory.

(Bug #56580)

D.3.2.6. Changes in MySQL Connector/Net 6.3.4 (01 September 2010 GA)

First GA release. This release fixes bugs since 6.3.3.

Bugs Fixed

The calculation of lockAge in the Session Provider sometimes generated a System.Data.SqlTypes.SqlNullValueException. (Bug #55701)

Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

System.OverflowException : Value was either too large or too small for a Double.

--OverflowException
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
numfmt)
at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
packet, Int64 length, Boolean nullVal)
at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
IMySqlValue valObject)
at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
at MySql.Data.MySqlClient.MySqlDataReader.Read()

(Bug #55644)

Calling MySqlDataAdapter.Update(DataTable) resulted in an unacceptable performance hit when updating large amounts of data. (Bug #55609)
If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:
```
Unable to load object with error: Object reference not
set to an instance of an object
```
(Bug #55170)
EventLog was not disposed in the SessionState provider. (Bug #52550)
When attempting to carry out an operation such as:
```
from p in db.Products where p.PostedDate>=DateTime.Now select p;
```
Where p.PostedDate is a DateTimeOffset, and the underlying column type is a TIMESTAMP, the following exception was generated:
```
MySqlException occurred
Unable to serialize date/time value
```
MySQL Connector/Net has now been changed so that all TIMESTAMP columns will be surfaced as DateTime. (Bug #52550)
Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug #50671)
The INSERT command was significantly slower with MySQL Connector/Net 6.x compared to 5.x, when compression was enabled. (Bug #48243)
Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug #44715)

D.3.2.7. Changes in MySQL Connector/Net 6.3.3 (27 July 2010)

This release fixes bugs since 6.3.2.

Bugs Fixed

MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug #54895)
Several calls to DataAdapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug #54863)
MySQL Connector/Net generated a null reference exception when TransactionScope was used by multiple threads. (Bug #54681)
The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug #54571)
The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug #54570)
If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adapter.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug #54386)
The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug #54152, Bug #53865)
MySQL Connector/Net did not process Thread.Abort() correctly, and failed to cancel queries currently running on the server. (Bug #54012)
MySQL Connector/Net 6.3.2 failed to install on Windows Vista. (Bug #53975)

Garbage Collector disposal of a MySqlConnection object caused the following exception:

System.IO.EndOfStreamException: Attempted to read past the end of the stream.
MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
Int32 count)
MySql.Data.MySqlClient.MySqlStream.LoadPacket()
Outer Exception Reading from the stream has failed.
...

(Bug #53457)

MySQL Connector/Net did not throw an EndOfStreamException exception when net_write_timeout was exceeded. (Bug #53439)

After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

[MySqlException (0x80004005): There is already an open DataReader associated with this
Connection which must be closed first.]
   MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
   Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
   Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
in ...:13
   Forecast.Page_Load(Object sender, EventArgs e) in ...:70
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) +627

(Bug #53357)

Membership schema creation failed if the default schema collation was not Latin1. (Bug #53174)
The MySQL Connector/Net installation failed due to machine.config files not being present in configuration folders.
MySQL Connector/Net has been changed to skip over configuration folders that do not contain a machine.config file. (Bug #52352)
CHAR(36) columns were not recognized as GUIDs when used in views with entity models. (Bug #52085)
When an application was subjected to increased concurrent load, MySQL Connector/Net generated the following error when calling stored procedures:
```
A DataTable named \'Procedure Parameters\'
already belongs to this DataSet.
      
```
(Bug #49118)
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)
When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.
MySQL Connector/Net has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug #38411)
Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug #33870)

D.3.2.8. Changes in MySQL Connector/Net 6.3.2 (24 May 2010 beta)

First Beta release. This release fixes bugs since 6.3.1.

Functionality Added or Changed

Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.
MySQL Connector/Net has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug #52562)
MySQL Connector/Net has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug #47467)

Bugs Fixed

After an exception, the internal datareader, MySqlCommand.Connection.Reader, was not properly closed (it was not set to null). If another query was subsequently executed on that command object an exception was generated with the message “There is already an open DataReader associated with this Connection which must be closed first.” (Bug #55558)
MySQL Connector/Net generated an exception when used to read a TEXT column containing more than 32767 bytes. (Bug #54040)
In MySQL Connector/Net, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug #52769)
The procedure cache affected the MySQL Connector/Net performance, reducing it by around 65%. This was due to unnecessary calls of String.Format(), related to debug logging. Even though the logging was disabled the string was still being formatted, resulting in impaired performance. (Bug #52475)
If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug #52187)
In MySQL Connector/Net, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:
```
mapping.Add("latin1", new CharacterSet("latin1", 1));
```
This meant that, for example, the Euro sign was not handled correctly.
The correct mapping should have been:
```
mapping.Add("latin1", new CharacterSet("windows-1252", 1));
```
This is because MySQL's latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug #51927)
A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug #51788)
When calling ExecuteNonQuery on a command object, the following exception occurred:
```
Index and length must refer to a location within the string.
Parameter name: length
```
(Bug #51610)
MySQL Connector/Net 6.3.1 failed to install. (Bug #51407, Bug #51604)
When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug #49850)

D.3.2.9. Changes in MySQL Connector/Net 6.3.1 (02 March 2010)

This release fixes bugs since 6.3.0.

Functionality Added or Changed

Connector/Net was not compatible with Visual Studio wizards that used square brackets to delimit symbols.
Connector/Net has been changed to include a new connection string option Sql Server mode that supports use of square brackets to delimit symbols. (Bug #35852)

Bugs Fixed

Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:
```
server=localhost;user=root;compress=;database=test;port=3306;password=123456;
```
(Bug #51209)
The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug #51149)
MySqlCommand.Parameters.Clear() did not work. (Bug #50444)
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)
When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug #50123)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

        MySql.Data.MySqlClient.MySqlException was unhandled
        Message="You have an error in your SQL syntax; check the manual that corresponds to your
        MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
        Source="MySql.Data"
        ErrorCode=-2147467259
        Number=1064
        StackTrace:
        à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
        à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
        lastInsertId)
        à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
        à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
      à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug #41629)

D.3.2.10. Changes in MySQL Connector/Net 6.3.0 (16 February 2010 alpha)

First alpha release of 6.3.

Functionality Added or Changed

Nested transaction scopes were not supported. MySQL Connector/Net now implements nested transaction scopes. A per-thread stack of scopes is maintained, which is necessary to handle nested scopes with the RequiresNew or Suppress options. (Bug #45098)
Support for MySQL Server 4.1 has been removed from MySQL Connector/Net starting with version 6.3.0. The connector will now throw an exception if you try to connect to a server of version less than 5.0.

Bugs Fixed

When adding a data set in Visual Studio 2008, the following error was generated:
```
Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.
```
This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug #48974)
Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug #48944)
The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug #48171)

D.3.3. Changes in MySQL Connector/Net Version 6.2.x

D.3.3.1. Changes in MySQL Connector/Net 6.2.6 (Not yet released)
D.3.3.2. Changes in MySQL Connector/Net 6.2.5 (05 July 2011)
D.3.3.3. Changes in MySQL Connector/Net 6.2.4 (30 August 2010)
D.3.3.4. Changes in MySQL Connector/Net 6.2.3 (10 April 2010)
D.3.3.5. Changes in MySQL Connector/Net 6.2.2 (22 December 2009 GA)
D.3.3.6. Changes in MySQL Connector/Net 6.2.1 (16 November 2009 beta)
D.3.3.7. Changes in MySQL Connector/Net 6.2.0 (21 October 2009 alpha)

D.3.3.1. Changes in MySQL Connector/Net 6.2.6 (Not yet released)

This release fixes bugs since 6.2.5.

Bugs Fixed

MySqlScript was modified to enable correct processing of the DELIMITER command when not followed by a new line. (Bug #61680, Bug #12732279)
The ASP.NET membership provider was modified to create and query all related tables using lowercase names. (Bug #61108, Bug #12702009)
On Model First changed column types generated in SQL scripts to produce more suitable MySql types. (Bug #59244, Bug #12707104)

D.3.3.2. Changes in MySQL Connector/Net 6.2.5 (05 July 2011)

This release fixes bugs since 6.2.4.

Bugs Fixed

SchemaDefinition-5.5.ssdl was modified to treat CHAR(36) columns as a GUID. (Bug #61657, Bug #12708208)
SqlFragment.QuoteIdentifier was modified to add MySQL quotes around identifiers. (Bug #61635, Bug #12707285)
Modified MySqlConnection.BeginTransaction to throw a NotSupportedException for Snapshot isolation level. (Bug #61589, Bug #12698020)
MysqlDataReader.GetSchemaTable returned incorrect values and types. (Bug #59989, Bug #11776346)
All queries other than INSERT were executed individually instead of as a batch even though batching was enabled for the connection. (Bug #59616, Bug #11850286)

MySQL Connector/Net generated an exception when executing a query consisting of ';', for example:

mycmd(";",mycon)
mycmd.executenonquery()

The exception generated was:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MySql.Data.MySqlClient.MySqlCommand.TrimSemicolons(String sql)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #59537, Bug #11766433)

Setting Membership.ApplicationName had no effect. (Bug #59438, Bug #11770465)
A NullReferenceException was thrown on disposal of a TransactionScope object. (Bug #59346, Bug #11766272)
MembershipProvider did not generate hashes correctly if the algorithm was keyed. The Key of the algorithm should have been set if the HashAlgorithm was KeyedHashAlgorithm. (Bug #58906)
Code introduced to fix bug #54863 proved problematic on .NET version 3.5 and above. (Bug #58853)
The MySqlTokenizer contained unnecessary Substring and Trim calls:
```
string token = sql.Substring(startIndex, stopIndex - startIndex).Trim();
```
The variable token was not used anywhere in the code. (Bug #58757)
MySqlCommand.ExecuteReader(CommandBehavior) threw a NullReferenceException when being called with CommandBehavior.CloseConnection, if the SQL statement contained a syntax error, or contained invalid data such as an invalid column name. (Bug #58652)
ReadFieldLength() returned incorrect value for BIGINT autoincrement columns. (Bug #58373)
MySQL Connector/Net did not support the utf8mb4 character set. When attempting to connect to utf8mb4 tables or columns, an exception KeyNotFoundException was generated. (Bug #58244)
A typed dataset did not get the table name. (Bug #57894, Bug #11764989)
Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug #57265)
When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug #57092)
Setting the Default Command Timeout connection string option had no effect. (Bug #56806)
When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug #56756)
MySqlHelper.ExecuteReader did not include an overload accepting MySqlParameter objects when using a MySqlConnection. However, MySqlHelper did include an overload for MySqlParameter objects when using a string object containing the connection string to the database. (Bug #56755)
Default values returned for text columns were not quoted. This meant that the COLUMN_DEFAULT field of the GetSchema columns collection did not return a valid SQL expression. (Bug #56509)
MySQL Connector/Net for .NET/Mono attempted to dynamically load the assembly Mono.Posix.dll when a Unix socket was used to connect to the server. This failed and the connector was not able to use a Unix socket unless the Mono.Posix.dll assembly was previously loaded by the program. (Bug #56410)
Modified ProviderManifest.xml to map TIMESTAMP database columns to the DateTime .NET type. (Bug #55351, Bug #12652602)
The ADO.NET Entity Data Model could not add stored procedures from MySQL Server 5.0.45 but worked fine using MySQL Server 5.1. (Bug #55349)
Fixed Entity Framework provider GROUP BY clause generation by adding all group-by keys to the SELECT statement. (Bug #46742, Bug #12622129)

D.3.3.3. Changes in MySQL Connector/Net 6.2.4 (30 August 2010)

This release fixes bugs since 6.2.3.

Functionality Added or Changed

Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.
MySQL Connector/Net has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug #52562)

Bugs Fixed

The calculation of lockAge in the Session Provider sometimes generated a System.Data.SqlTypes.SqlNullValueException. (Bug #55701)

Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

System.OverflowException : Value was either too large or too small for a Double.

--OverflowException
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
numfmt)
at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
packet, Int64 length, Boolean nullVal)
at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
IMySqlValue valObject)
at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
at MySql.Data.MySqlClient.MySqlDataReader.Read()

(Bug #55644)

After an exception, the internal datareader, MySqlCommand.Connection.Reader, was not properly closed (it was not set to null). If another query was subsequently executed on that command object an exception was generated with the message “There is already an open DataReader associated with this Connection which must be closed first.” (Bug #55558)
If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:
```
Unable to load object with error: Object reference not
set to an instance of an object
```
(Bug #55170)
MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug #54895)
Several calls to DataAdapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug #54863)
The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug #54571)
The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug #54570)
If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adapter.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug #54386)
The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug #54152, Bug #53865)
MySQL Connector/Net did not process Thread.Abort() correctly, and failed to cancel queries currently running on the server. (Bug #54012)

Garbage Collector disposal of a MySqlConnection object caused the following exception:

System.IO.EndOfStreamException: Attempted to read past the end of the stream.
MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
Int32 count)
MySql.Data.MySqlClient.MySqlStream.LoadPacket()
Outer Exception Reading from the stream has failed.
...

(Bug #53457)

MySQL Connector/Net did not throw an EndOfStreamException exception when net_write_timeout was exceeded. (Bug #53439)

After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

[MySqlException (0x80004005): There is already an open DataReader associated with this
Connection which must be closed first.]
   MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
   Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
   Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
in ...:13
   Forecast.Page_Load(Object sender, EventArgs e) in ...:70
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) +627

(Bug #53357)

Membership schema creation failed if the default schema collation was not Latin1. (Bug #53174)
In MySQL Connector/Net, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug #52769)
EventLog was not disposed in the SessionState provider. (Bug #52550)
The procedure cache affected the MySQL Connector/Net performance, reducing it by around 65%. This was due to unnecessary calls of String.Format(), related to debug logging. Even though the logging was disabled the string was still being formatted, resulting in impaired performance. (Bug #52475)
If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug #52187)
Periodically the session provider threw an SqlNullValueException exception. When this happened, the row within the my_aspnet_Sessions table had locked always set to '1'. The locked status never changed back to '0' and the user experienced the exception on every page, until their browser was closed and reopened (recreating a new sessionID), or the locked value was manually changed to '0'. (Bug #52175)
CHAR(36) columns were not recognized as GUIDs when used in views with entity models. (Bug #52085)
In MySQL Connector/Net, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:
```
mapping.Add("latin1", new CharacterSet("latin1", 1));
```
This meant that, for example, the Euro sign was not handled correctly.
The correct mapping should have been:
```
mapping.Add("latin1", new CharacterSet("windows-1252", 1));
```
This is because MySQL's latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug #51927)
Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug #50671)
When an application was subjected to increased concurrent load, MySQL Connector/Net generated the following error when calling stored procedures:
```
A DataTable named \'Procedure Parameters\'
already belongs to this DataSet.
      
```
(Bug #49118)
In the ADO.NET Entity Data Model Wizard, the time to update a model scaled abnormally as the number of entities increased. (Bug #48791, Bug #12596237)
The INSERT command was significantly slower with MySQL Connector/Net 6.x compared to 5.x, when compression was enabled. (Bug #48243)
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)
Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug #44715)
When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.
MySQL Connector/Net has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug #38411)
Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug #33870)

D.3.3.4. Changes in MySQL Connector/Net 6.2.3 (10 April 2010)

This release fixes bugs since 6.2.2.

Functionality Added or Changed

MySQL Connector/Net has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug #47467)

Bugs Fixed

A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug #51788)
When calling ExecuteNonQuery on a command object, the following exception occurred:
```
Index and length must refer to a location within the string.
Parameter name: length
```
(Bug #51610)
Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:
```
server=localhost;user=root;compress=;database=test;port=3306;password=123456;
```
(Bug #51209)
The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug #51149)
MySqlCommand.Parameters.Clear() did not work. (Bug #50444)
When the MySqlScript.execute() method was called, the following exception was generated:
```
InvalidOperationException : The CommandText property has not been properly initialized.
```
(Bug #50344)
When using the Compact Framework the following exception occurred when attempting to connect to a MySQL Server:
```
System.InvalidOperationException was unhandled
  Message="Timeouts are not supported on this stream."
```
(Bug #50321)
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)
When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug #50123)
When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug #49850)
MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug #49794)
A FormatException was generated when an empty string was returned from a stored function. (Bug #49642)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

        MySql.Data.MySqlClient.MySqlException was unhandled
        Message="You have an error in your SQL syntax; check the manual that corresponds to your
        MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
        Source="MySql.Data"
        ErrorCode=-2147467259
        Number=1064
        StackTrace:
        à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
        à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
        lastInsertId)
        à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
        à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
      à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug #45277)
A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug #41629)

D.3.3.5. Changes in MySQL Connector/Net 6.2.2 (22 December 2009 GA)

First GA release of 6.2. This release fixes bugs since 6.2.1.

Bugs Fixed

When adding a data set in Visual Studio 2008, the following error was generated:
```
Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.
```
This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug #48974)
Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug #48944)
The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug #48171)

MySQL Connector/Net generated an invalid operation exception during a transaction rollback:

System.InvalidOperationException: Connection must be valid and open to rollback
transaction
   at MySql.Data.MySqlClient.MySqlTransaction.Rollback()
   at MySql.Data.MySqlClient.MySqlConnection.CloseFully()
   at
MySql.Data.MySqlClient.MySqlPromotableTransaction.System.Transactions.IPromotableSinglePhaseNotification.Rollback(SinglePhaseEnlistment
singlePhaseEnlistment)
...

(Bug #35330)

Connection objects were not garbage collected when not in use. (Bug #31996)

D.3.3.6. Changes in MySQL Connector/Net 6.2.1 (16 November 2009 beta)

This release fixes bugs since 6.2.0.

Functionality Added or Changed

The MySqlParameter class now has a property named PossibleValues. This property is NULL unless the parameter is created by MySqlCommandBuilder.DeriveParameters. Further, it will be NULL unless the parameter is of type enum or set - in this case it will be a list of strings that are the possible values for the column. This feature is designed as an aid to the developer. (Bug #48586)
Prior to MySQL Connector/Net 6.2, MySqlCommand.CommandTimeout included user processing time, that is processing time not related to direct use of the connector. Timeout was implemented through a .NET Timer, that triggered after CommandTimeout seconds.
MySQL Connector/Net 6.2 introduced timeouts that are aligned with how Microsoft handles SqlCommand.CommandTimeout. This property is the cumulative timeout for all network reads and writes during command execution or processing of the results. A timeout can still occur in the MySqlReader.Read method after the first row is returned, and does not include user processing time, only IO operations.
Further details on this can be found in the relevant Microsoft documentation.
Starting with MySQL Connector/Net 6.2, there is a background job that runs every three minutes and removes connections from pool that have been idle (unused) for more than three minutes. The pool cleanup frees resources on both client and server side. This is because on the client side every connection uses a socket, and on the server side every connection uses a socket and a thread.
Prior to this change, connections were never removed from the pool, and the pool always contained the peak number of open connections. For example, a web application that peaked at 1000 concurrent database connections would consume 1000 threads and 1000 open sockets at the server, without ever freeing up those resources from the connection pool.
MySQL Connector/Net now supports the processing of certificates when connecting to an SSL-enabled MySQL Server. For further information see the connection string option SSL Mode in the section Section 20.2.6, “Connector/Net Connection String Options Reference” and the tutorial Section 20.2.4.7, “Tutorial: Using SSL with MySQL Connector/Net”.

Bugs Fixed

Cloning of MySqlCommand was not typesafe. To clone a MySqlCommand it was necessary to do:
```
        MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
      
```
MySQL Connector/Net was changed so that it was possible to do:
```
        MySqlCommand clone = comm.Clone();
      
```
(Bug #48460)
When used, the Encrypt connection string option caused a “Keyword not supported” exception to be generated.
This option is in fact obsolete, and the option SSL Mode should be used instead. Although the Encrypt option has been fixed so that it does not generate an exception, it will be removed completely in version 6.4. (Bug #48290)
When building the MySql.Data project with .NET Framework 3.5 installed, the following build output was displayed:
```
Project file contains ToolsVersion="4.0", which is not supported by this version of
MSBuild. Treating the project as if it had ToolsVersion="3.5".
```
The project had been created using the .NET Framework 4.0, which was beta, instead of using the 3.5 framework. (Bug #48271)
It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.
MySQL Connector/Net was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug #48100)
An entity model created from a schema containing a table with a column of type UNSIGNED BIGINT and a view of the table did not behave correctly. When an entity was created and mapped to the view, the column that was of type UNSIGNED BIGINT was displayed as BIGINT. (Bug #47872)
MySQL Connector/Net session support did not work with MySQL Server versions prior to 5.0, as the Session Provider used a call to TIMESTAMPDIFF, which was not available on servers prior to 5.0. (Bug #47219)

D.3.3.7. Changes in MySQL Connector/Net 6.2.0 (21 October 2009 alpha)

The first alpha release of 6.2.

Bugs Fixed

When using a BINARY(16) column to represent a GUID and having specified “old guids = true” in the connection string, the values were returned correctly until a null value was encountered in that field. After the null value was encountered a format exception was thrown with the following message:
```
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
```
(Bug #47928)
The Session Provider created invalid “session expires” on a random basis.
This was due to the fact that the Session Provider was incorrectly reading from the root web.config, rather than from the application specific web.config. (Bug #47815)

When loading the MySQLClient-mono.sln file included with the Connector/Net source into Mono Develop, the following error occurred:

/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
Unsupported or unrecognized project:
'/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'

If the file was modified to remove this problem, then attempting to build the solution generated the following error:

/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
override but no suitable property found to override

(Bug #47048)

D.3.4. Changes in MySQL Connector/Net Version 6.1.x

D.3.4.1. Changes in MySQL Connector/Net 6.1.7 (Not released GA)
D.3.4.2. Changes in MySQL Connector/Net 6.1.6 (Not released GA)
D.3.4.3. Changes in MySQL Connector/Net 6.1.5 (30 August 2010 GA)
D.3.4.4. Changes in MySQL Connector/Net 6.1.4 (28 April 2010 GA)
D.3.4.5. Changes in MySQL Connector/Net 6.1.3 (16 November 2009 GA)
D.3.4.6. Changes in MySQL Connector/Net 6.1.2 (08 September 2009 GA)
D.3.4.7. Changes in MySQL Connector/Net 6.1.1 (20 August 2009 beta)
D.3.4.8. Changes in MySQL Connector/Net 6.1.0 (15 July 2009 alpha)

D.3.4.1. Changes in MySQL Connector/Net 6.1.7 (Not released GA)

This release fixes bugs since 6.1.6.

Bugs Fixed

MySqlScript was modified to enable correct processing of the DELIMITER command when not followed by a new line. (Bug #61680, Bug #12732279)
SchemaDefinition-5.5.ssdl was modified to treat CHAR(36) columns as a GUID. (Bug #61657, Bug #12708208)
SqlFragment.QuoteIdentifier was modified to add MySQL quotes around identifiers. (Bug #61635, Bug #12707285)
The ASP.NET membership provider was modified to create and query all related tables using lowercase names. (Bug #61108, Bug #12702009)

D.3.4.2. Changes in MySQL Connector/Net 6.1.6 (Not released GA)

This release fixes bugs since 6.1.5.

Bugs Fixed

Modified MySqlConnection.BeginTransaction to throw a NotSupportedException for Snapshot isolation level. (Bug #61589, Bug #12698020)
MysqlDataReader.GetSchemaTable returned incorrect values and types. (Bug #59989, Bug #11776346)
All queries other than INSERT were executed individually instead of as a batch even though batching was enabled for the connection. (Bug #59616, Bug #11850286)

MySQL Connector/Net generated an exception when executing a query consisting of ';', for example:

mycmd(";",mycon)
mycmd.executenonquery()

The exception generated was:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MySql.Data.MySqlClient.MySqlCommand.TrimSemicolons(String sql)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #59537, Bug #11766433)

Setting Membership.ApplicationName had no effect. (Bug #59438, Bug #11770465)
MembershipProvider did not generate hashes correctly if the algorithm was keyed. The Key of the algorithm should have been set if the HashAlgorithm was KeyedHashAlgorithm. (Bug #58906)
Code introduced to fix bug #54863 proved problematic on .NET version 3.5 and above. (Bug #58853)
The MySqlTokenizer contained unnecessary Substring and Trim calls:
```
string token = sql.Substring(startIndex, stopIndex - startIndex).Trim();
```
The variable token was not used anywhere in the code. (Bug #58757)
MySqlCommand.ExecuteReader(CommandBehavior) threw a NullReferenceException when being called with CommandBehavior.CloseConnection, if the SQL statement contained a syntax error, or contained invalid data such as an invalid column name. (Bug #58652)
ReadFieldLength() returned incorrect value for BIGINT autoincrement columns. (Bug #58373)
MySQL Connector/Net did not support the utf8mb4 character set. When attempting to connect to utf8mb4 tables or columns, an exception KeyNotFoundException was generated. (Bug #58244)
A typed dataset did not get the table name. (Bug #57894, Bug #11764989)
Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug #57265)
When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug #57092)
Setting the Default Command Timeout connection string option had no effect. (Bug #56806)
When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug #56756)
MySqlHelper.ExecuteReader did not include an overload accepting MySqlParameter objects when using a MySqlConnection. However, MySqlHelper did include an overload for MySqlParameter objects when using a string object containing the connection string to the database. (Bug #56755)
Default values returned for text columns were not quoted. This meant that the COLUMN_DEFAULT field of the GetSchema columns collection did not return a valid SQL expression. (Bug #56509)
MySQL Connector/Net for .NET/Mono attempted to dynamically load the assembly Mono.Posix.dll when a Unix socket was used to connect to the server. This failed and the connector was not able to use a Unix socket unless the Mono.Posix.dll assembly was previously loaded by the program. (Bug #56410)
Modified ProviderManifest.xml to map TIMESTAMP database columns to the DateTime .NET type. (Bug #55351, Bug #12652602)
The ADO.NET Entity Data Model could not add stored procedures from MySQL Server 5.0.45 but worked fine using MySQL Server 5.1. (Bug #55349)
Fixed Entity Framework provider GROUP BY clause generation by adding all group-by keys to the SELECT statement. (Bug #46742, Bug #12622129)

D.3.4.3. Changes in MySQL Connector/Net 6.1.5 (30 August 2010 GA)

This release fixes bugs since 6.1.4.

Bugs Fixed

The calculation of lockAge in the Session Provider sometimes generated a System.Data.SqlTypes.SqlNullValueException. (Bug #55701)

Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

System.OverflowException : Value was either too large or too small for a Double.

--OverflowException
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
numfmt)
at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
packet, Int64 length, Boolean nullVal)
at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
IMySqlValue valObject)
at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
at MySql.Data.MySqlClient.MySqlDataReader.Read()

(Bug #55644)

If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:
```
Unable to load object with error: Object reference not
set to an instance of an object
```
(Bug #55170)
MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug #54895)
Several calls to DataAdapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug #54863)
The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug #54571)
The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug #54570)
If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adapter.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug #54386)
The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug #54152, Bug #53865)

Garbage Collector disposal of a MySqlConnection object caused the following exception:

System.IO.EndOfStreamException: Attempted to read past the end of the stream.
MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
Int32 count)
MySql.Data.MySqlClient.MySqlStream.LoadPacket()
Outer Exception Reading from the stream has failed.
...

(Bug #53457)

MySQL Connector/Net did not throw an EndOfStreamException exception when net_write_timeout was exceeded. (Bug #53439)

After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

[MySqlException (0x80004005): There is already an open DataReader associated with this
Connection which must be closed first.]
   MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
   Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
   Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
in ...:13
   Forecast.Page_Load(Object sender, EventArgs e) in ...:70
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) +627

(Bug #53357)

Membership schema creation failed if the default schema collation was not Latin1. (Bug #53174)
EventLog was not disposed in the SessionState provider. (Bug #52550)
CHAR(36) columns were not recognized as GUIDs when used in views with entity models. (Bug #52085)
Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug #50671)
When an application was subjected to increased concurrent load, MySQL Connector/Net generated the following error when calling stored procedures:
```
A DataTable named \'Procedure Parameters\'
already belongs to this DataSet.
      
```
(Bug #49118)
In the ADO.NET Entity Data Model Wizard, the time to update a model scaled abnormally as the number of entities increased. (Bug #48791, Bug #12596237)
The INSERT command was significantly slower with MySQL Connector/Net 6.x compared to 5.x, when compression was enabled. (Bug #48243)
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)
Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug #44715)
When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.
MySQL Connector/Net has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug #38411)
Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug #33870)

D.3.4.4. Changes in MySQL Connector/Net 6.1.4 (28 April 2010 GA)

This release fixes bugs since 6.1.3.

Functionality Added or Changed

Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.
MySQL Connector/Net has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug #52562)
MySQL Connector/Net has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug #47467)

Bugs Fixed

In MySQL Connector/Net, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug #52769)
If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug #52187)
In MySQL Connector/Net, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:
```
mapping.Add("latin1", new CharacterSet("latin1", 1));
```
This meant that, for example, the Euro sign was not handled correctly.
The correct mapping should have been:
```
mapping.Add("latin1", new CharacterSet("windows-1252", 1));
```
This is because MySQL's latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug #51927)
A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug #51788)
When calling ExecuteNonQuery on a command object, the following exception occurred:
```
Index and length must refer to a location within the string.
Parameter name: length
```
(Bug #51610)
The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug #51149)
MySqlCommand.Parameters.Clear() did not work. (Bug #50444)
When the MySqlScript.execute() method was called, the following exception was generated:
```
InvalidOperationException : The CommandText property has not been properly initialized.
```
(Bug #50344)
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)
When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug #50123)
When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug #49850)
MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug #49794)
A FormatException was generated when an empty string was returned from a stored function. (Bug #49642)
When adding a data set in Visual Studio 2008, the following error was generated:
```
Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.
```
This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug #48974)
Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug #48944)
The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug #48171)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

        MySql.Data.MySqlClient.MySqlException was unhandled
        Message="You have an error in your SQL syntax; check the manual that corresponds to your
        MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
        Source="MySql.Data"
        ErrorCode=-2147467259
        Number=1064
        StackTrace:
        à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
        à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
        lastInsertId)
        à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
        à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
      à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug #45277)
A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug #41629)

D.3.4.5. Changes in MySQL Connector/Net 6.1.3 (16 November 2009 GA)

This release fixes bugs since 6.1.2.

Bugs Fixed

Cloning of MySqlCommand was not typesafe. To clone a MySqlCommand it was necessary to do:
```
        MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
      
```
MySQL Connector/Net was changed so that it was possible to do:
```
        MySqlCommand clone = comm.Clone();
      
```
(Bug #48460)
When building the MySql.Data project with .NET Framework 3.5 installed, the following build output was displayed:
```
Project file contains ToolsVersion="4.0", which is not supported by this version of
MSBuild. Treating the project as if it had ToolsVersion="3.5".
```
The project had been created using the .NET Framework 4.0, which was beta, instead of using the 3.5 framework. (Bug #48271)

If MySqlConnection.GetSchema was called for "Indexes" on a table named “b`a`d” as follows:

DataTable schemaPrimaryKeys = connection.GetSchema(
  "Indexes",
  new string[] { null, schemaName, "b`a`d"});

Then the following exception was generated:

You have an error in your SQL syntax; check the manual that corresponds to
your MySQL server version for the right syntax to use near 'a`d`' at line 1

(Bug #48101)

It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.
MySQL Connector/Net was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug #48100)
For some character sets such as UTF-8, a CHAR column would sometimes be incorrectly interpreted as a GUID by MySQL Connector/Net.
MySQL Connector/Net was changed so that a column would only be interpreted as a GUID if it had a character length of 36, as opposed to a byte length of 36. (Bug #47985)
When using a BINARY(16) column to represent a GUID and having specified “old guids = true” in the connection string, the values were returned correctly until a null value was encountered in that field. After the null value was encountered a format exception was thrown with the following message:
```
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
```
(Bug #47928)
An entity model created from a schema containing a table with a column of type UNSIGNED BIGINT and a view of the table did not behave correctly. When an entity was created and mapped to the view, the column that was of type UNSIGNED BIGINT was displayed as BIGINT. (Bug #47872)
The Session Provider created invalid “session expires” on a random basis.
This was due to the fact that the Session Provider was incorrectly reading from the root web.config, rather than from the application specific web.config. (Bug #47815)

Attempting to build MySQL Connector/Net 6.1 MySQL.Data from source code on Windows failed with the following error:

...\clones\6.1\MySql.Data\Provider\Source\NativeDriver.cs(519,29): error CS0122:
'MySql.Data.MySqlClient.MySqlPacket.MySqlPacket()' is inaccessible due to its protection level

(Bug #47354)

When tables were auto created for the Session State Provider they were set to use the MySQL Server's default collation, rather than the default collation set for the containing database. (Bug #47332)

When loading the MySQLClient-mono.sln file included with the Connector/Net source into Mono Develop, the following error occurred:

/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
Unsupported or unrecognized project:
'/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'

If the file was modified to remove this problem, then attempting to build the solution generated the following error:

/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
override but no suitable property found to override

(Bug #47048)

D.3.4.6. Changes in MySQL Connector/Net 6.1.2 (08 September 2009 GA)

This is the first GA release of 6.1. This release fixes bugs since 6.1.1.

Bugs Fixed

The MySQL Connector/Net Session State Provider truncated session data to 64KB, due to its column types being set to BLOB. (Bug #47339)

MySQL Connector/Net generated the following exception when using the Session State provider:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'MINUTEWHERE SessionId =
'dtmgga55x35oi255nrfrxe45' AND ApplicationId = 1 AND Loc' at line 1 
Description: An unhandled exception occurred during the execution of the current web
request. Please review the stack trace for more information about the error and where it
originated in the code. 

Exception Details: MySql.Data.MySqlClient.MySqlException: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL server version for the right
syntax to use near 'MINUTEWHERE SessionId = 'dtmgga55x35oi255nrfrxe45' AND ApplicationId =
1 AND Loc' at line 1

(Bug #46939)

If an error occurred during connection to a MySQL Server, deserializing the error message from the packet buffer caused a NullReferenceException to be thrown. When the method MySqlPacket::ReadString() attempted to retrieve the error message, the following line of code threw the exception:
```
        string s = encoding.GetString(bits, (int)buffer.Position, end - (int)buffer.Position);
      
```
This was due to the fact that the encoding field had not been initialized correctly. (Bug #46844)
Input parameters were missing from Stored Procedures when using them with ADO.NET Data Entities. (Bug #44985)
MySQL Connector/Net did not time out correctly. The command timeout was set to 30 secs, but MySQL Connector/Net hung for several hours. (Bug #43761)

D.3.4.7. Changes in MySQL Connector/Net 6.1.1 (20 August 2009 beta)

This is the first Beta release of 6.1.

Bugs Fixed

In the MySqlDataReader class the GetSByte function returned a byte value instead of an sbyte value. (Bug #46620)

The MySQL Connector/Net Profile Provider, MySql.Web.Profile.MySQLProfileProvider, generated an error when running on Mono. When an attempt was made to save a string in Profile.Name the string was not saved to the my_aspnet_Profiles table. If an attempt was made to force the save with Profile.Save() the following error was generated:

        Server Error in '/mono' Application

        --------------------------------------------------------------------------------

        The requested feature is not implemented.
        Description: HTTP 500. Error processing request.

        Stack Trace: 

        System.NotImplementedException: The requested feature is not implemented.
        at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction
        (System.Transactions.Transaction transaction) [0x00000] 
        at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000] 
        at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues
        (System.Configuration.SettingsContext context,
        System.Configuration.SettingsPropertyValueCollection collection) [0x00000] 
        

        --------------------------------------------------------------------------------
        Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433

(Bug #46375)

An exception was generated when using TIMESTAMP columns with the Entity Framework. (Bug #46311)
MySQL Connector/Net sometimes hung, without generating an exception. This happened if a read from a stream failed returning a 0, causing the code in LoadPacket() to enter an infinite loop. (Bug #46308)

When using MySQL Connector/Net 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:

        connection.GetSchema("Columns", ...);

The exception generated was:

        'connection.GetSchema("Columns")' threw an exception of type
        'System.ArgumentException'System.Data.DataTable {System.ArgumentException}
        base{"Input string was not in a correct format.Couldn't store <'Select'> in
        NUMERIC_PRECISION Column.  Expected type is UInt64."}System.Exception
        {System.ArgumentException}

(Bug #46270)

The MySQL Connector/Net method StoredProcedure.GetParameters(string) ignored the programmer's setting of the UseProcedureBodies option. This broke any application for which the application's parameter names did not match the parameter names in the Stored Procedure, resulting in an ArgumentException with the message “Parameter 'foo' not found in the collection.” and the following stack trace:

        MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri
        ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C#
        MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25
        bytesC#
        MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha
        vior behavior = SequentialAccess) Line 405 + 0xb bytesC#
        MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma
        ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC#
        System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System
        .Data.CommandBehavior behavior) + 0xb bytes
        System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet
        dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int
        startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand
        command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) +
        0x83 bytes
        System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int
        startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command,
        System.Data.CommandBehavior behavior) + 0x120 bytes
        System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) +
        0x5f bytes

(Bug #46213)

Conversion of MySQL TINYINT(1) to boolean failed. (Bug #46205, Bug #46359, Bug #41953)
When populating a MySQL database table in Visual Studio using the Table Editor, if a VARCHAR(10) column was changed to a VARCHAR(20) column an exception was generated:
```
        SystemArgumentException: DataGridViewComboBoxCell value is not valid.
      To replace this default dialog please handle the DataError Event.
```
(Bug #46100)
The Entity Framework provider was not calling DBSortExpression correctly when the Skip and Take methods were used, such as in the following statement:
```
        TestModel.tblquarantine.OrderByDescending(q => q.MsgDate).Skip(100).Take(100).ToList();
      
```
This resulted in the data being unsorted. (Bug #45723)

The MySQL Connector/Net 6.0.4 installer failed with an error. The error message generated was:

        There is a problem with this Windows Installer package. A DLL required for this
        install to complete could not be run. Contact your support personnel or package vendor.

When OK was clicked to acknowledge the error the installer exited. (Bug #45474)

Calling the Entity Framework SaveChanges() method of any MySQL ORM Entity with a column type TIME, generated an error message:
```
Unknown PrimitiveKind Time
```
(Bug #45457)
Insert into two tables failed when using the Entity Framework. The exception generated was:
```
        The value given is not an instance of type 'Edm.Int32'
      
```
(Bug #45077)
Errors occurred when using the Entity Framework with cultures that used a comma as the decimal separator. This was because the formatting for SINGLE, DOUBLE and DECIMAL values was not handled correctly. (Bug #44455)
When attempting to connect to MySQL using the Compact Framework version of MySQL Connector/Net, an IndexOutOfRangeException exception was generated on trying to open the connection. (Bug #43736)
When reading data, such as with a MySqlDataAdapter on a MySqlConnection, MySQL Connector/Net could potentially enter an infinite loop in CompressedStream.ReadNextpacket() if compression was enabled. (Bug #43678)
An error occurred when building MySQL Connector/Net from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.
When an attempt was made to build (for example) the MySQL Connector/Net 5.2 branch using the command:
```
        $ nant -buildfile:Client.build
      
```
The following error occurred:
```
        BUILD FAILED

        Error loading buildfile.
        Encoding name 'Windows-1252' not supported.
        Parameter name: name
      
```
(Bug #42411)
MySQL Connector/Net CHM documentation stated that MySQL Server 3.23 was supported. (Bug #42110)
In the case of long network inactivity, especially when connection pooling was used, connections were sometimes dropped, for example, by firewalls.
Note: The bugfix introduced a new keepalive parameter, which prevents disconnects by sending an empty TCP packet after a specified timeout. (Bug #40684)
Calling a Stored Procedure with an output parameter through MySQL Connector/Net resulted in a memory leak. Calling the same Stored Procedure without an output parameter did not result in a memory leak. (Bug #36027)

D.3.4.8. Changes in MySQL Connector/Net 6.1.0 (15 July 2009 alpha)

This is the first Alpha release of 6.1.

Functionality Added or Changed

Changed GUID type - The backend representation of a guid type has been changed to be CHAR(36). This is so you can use the server UUID() function to populate a GUID table. UUID generates a 36 character string. Developers of older applications can add old guids=true to the connection string and the old BINARY(16) type will be used instead.
Support for native output parameters - This is supported when connected to a server that supports native output parameters. This includes servers as of 5.5.3 and 6.0.8.
Session State Provider - This enables you to store the state of your website in a MySQL server.
Website Configuration Dialog - This is a new wizard that is activated by clicking a button on the toolbar at the top of the Visual Studio Solution Explorer. It works in conjunction with the ASP.Net administration pages, making it easier to activate and set advanced options for the different MySQL web providers included.

D.3.5. Changes in MySQL Connector/Net Version 6.0.x

D.3.5.1. Changes in MySQL Connector/Net 6.0.8 (Not released)
D.3.5.2. Changes in MySQL Connector/Net 6.0.7 (30 August 2010)
D.3.5.3. Changes in MySQL Connector/Net 6.0.6 (28 April 2010)
D.3.5.4. Changes in MySQL Connector/Net 6.0.5 (12 November 2009)
D.3.5.5. Changes in MySQL Connector/Net 6.0.4 (16 June 2009)
D.3.5.6. Changes in MySQL Connector/Net 6.0.3 (28 April 2009)
D.3.5.7. Changes in MySQL Connector/Net 6.0.2 (07 April 2009 beta)
D.3.5.8. Changes in MySQL Connector/Net 6.0.1 (02 April 2009 beta)
D.3.5.9. Changes in MySQL Connector/Net 6.0.0 (02 March 2009 alpha)

D.3.5.1. Changes in MySQL Connector/Net 6.0.8 (Not released)

Fixes bugs since 6.0.7.

Bugs Fixed

MysqlDataReader.GetSchemaTable returned incorrect values and types. (Bug #59989, Bug #11776346)
All queries other than INSERT were executed individually instead of as a batch even though batching was enabled for the connection. (Bug #59616, Bug #11850286)

MySQL Connector/Net generated an exception when executing a query consisting of ';', for example:

mycmd(";",mycon)
mycmd.executenonquery()

The exception generated was:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MySql.Data.MySqlClient.MySqlCommand.TrimSemicolons(String sql)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #59537, Bug #11766433)

Setting Membership.ApplicationName had no effect. (Bug #59438, Bug #11770465)
MembershipProvider did not generate hashes correctly if the algorithm was keyed. The Key of the algorithm should have been set if the HashAlgorithm was KeyedHashAlgorithm. (Bug #58906)
Code introduced to fix bug #54863 proved problematic on .NET version 3.5 and above. (Bug #58853)
The MySqlTokenizer contained unnecessary Substring and Trim calls:
```
string token = sql.Substring(startIndex, stopIndex - startIndex).Trim();
```
The variable token was not used anywhere in the code. (Bug #58757)
MySqlCommand.ExecuteReader(CommandBehavior) threw a NullReferenceException when being called with CommandBehavior.CloseConnection, if the SQL statement contained a syntax error, or contained invalid data such as an invalid column name. (Bug #58652)
ReadFieldLength() returned incorrect value for BIGINT autoincrement columns. (Bug #58373)
MySQL Connector/Net did not support the utf8mb4 character set. When attempting to connect to utf8mb4 tables or columns, an exception KeyNotFoundException was generated. (Bug #58244)
A typed dataset did not get the table name. (Bug #57894, Bug #11764989)
Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug #57265)
When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug #57092)
Setting the Default Command Timeout connection string option had no effect. (Bug #56806)
When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug #56756)
Default values returned for text columns were not quoted. This meant that the COLUMN_DEFAULT field of the GetSchema columns collection did not return a valid SQL expression. (Bug #56509)
MySQL Connector/Net for .NET/Mono attempted to dynamically load the assembly Mono.Posix.dll when a Unix socket was used to connect to the server. This failed and the connector was not able to use a Unix socket unless the Mono.Posix.dll assembly was previously loaded by the program. (Bug #56410)
The ADO.NET Entity Data Model could not add stored procedures from MySQL Server 5.0.45 but worked fine using MySQL Server 5.1. (Bug #55349)

D.3.5.2. Changes in MySQL Connector/Net 6.0.7 (30 August 2010)

Fixes bugs since 6.0.6.

Bugs Fixed

Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

System.OverflowException : Value was either too large or too small for a Double.

--OverflowException
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
numfmt)
at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
packet, Int64 length, Boolean nullVal)
at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
IMySqlValue valObject)
at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
at MySql.Data.MySqlClient.MySqlDataReader.Read()

(Bug #55644)

MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug #54895)
Several calls to DataAdapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug #54863)
The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug #54570)
If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adapter.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug #54386)
The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug #54152, Bug #53865)

Garbage Collector disposal of a MySqlConnection object caused the following exception:

System.IO.EndOfStreamException: Attempted to read past the end of the stream.
MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
Int32 count)
MySql.Data.MySqlClient.MySqlStream.LoadPacket()
Outer Exception Reading from the stream has failed.
...

(Bug #53457)

After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

[MySqlException (0x80004005): There is already an open DataReader associated with this
Connection which must be closed first.]
   MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
   MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
   Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
   Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
in ...:13
   Forecast.Page_Load(Object sender, EventArgs e) in ...:70
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) +627

(Bug #53357)

Membership schema creation failed if the default schema collation was not Latin1. (Bug #53174)
EventLog was not disposed in the SessionState provider. (Bug #52550)
Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug #50671)
When an application was subjected to increased concurrent load, MySQL Connector/Net generated the following error when calling stored procedures:
```
A DataTable named \'Procedure Parameters\'
already belongs to this DataSet.
      
```
(Bug #49118)
In the ADO.NET Entity Data Model Wizard, the time to update a model scaled abnormally as the number of entities increased. (Bug #48791, Bug #12596237)
The INSERT command was significantly slower with MySQL Connector/Net 6.x compared to 5.x, when compression was enabled. (Bug #48243)
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)
Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug #44715)
When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.
MySQL Connector/Net has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug #38411)
Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug #33870)

D.3.5.3. Changes in MySQL Connector/Net 6.0.6 (28 April 2010)

Fixes bugs since 6.0.5.

Functionality Added or Changed

Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.
MySQL Connector/Net has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug #52562)
MySQL Connector/Net has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug #47467)

Bugs Fixed

If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:
```
Unable to load object with error: Object reference not
set to an instance of an object
```
(Bug #55170)
In MySQL Connector/Net, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug #52769)
If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug #52187)
In MySQL Connector/Net, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:
```
mapping.Add("latin1", new CharacterSet("latin1", 1));
```
This meant that, for example, the Euro sign was not handled correctly.
The correct mapping should have been:
```
mapping.Add("latin1", new CharacterSet("windows-1252", 1));
```
This is because MySQL's latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug #51927)
A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug #51788)
When calling ExecuteNonQuery on a command object, the following exception occurred:
```
Index and length must refer to a location within the string.
Parameter name: length
```
(Bug #51610)
The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug #51149)
MySqlCommand.Parameters.Clear() did not work. (Bug #50444)
When the MySqlScript.execute() method was called, the following exception was generated:
```
InvalidOperationException : The CommandText property has not been properly initialized.
```
(Bug #50344)
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug #50171)
When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug #50123)
When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug #49850)
MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug #49794)
A FormatException was generated when an empty string was returned from a stored function. (Bug #49642)
When adding a data set in Visual Studio 2008, the following error was generated:
```
Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.
```
This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug #48974)
Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug #48944)
The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug #48171)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

        MySql.Data.MySqlClient.MySqlException was unhandled
        Message="You have an error in your SQL syntax; check the manual that corresponds to your
        MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
        Source="MySql.Data"
        ErrorCode=-2147467259
        Number=1064
        StackTrace:
        à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
        à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
        lastInsertId)
        à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
        à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
      à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug #45277)
A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug #41629)

D.3.5.4. Changes in MySQL Connector/Net 6.0.5 (12 November 2009)

This is a new release, fixing recently discovered bugs.

Bugs Fixed

Cloning of MySqlCommand was not typesafe. To clone a MySqlCommand it was necessary to do:
```
        MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
      
```
MySQL Connector/Net was changed so that it was possible to do:
```
        MySqlCommand clone = comm.Clone();
      
```
(Bug #48460)

If MySqlConnection.GetSchema was called for "Indexes" on a table named “b`a`d” as follows:

DataTable schemaPrimaryKeys = connection.GetSchema(
  "Indexes",
  new string[] { null, schemaName, "b`a`d"});

Then the following exception was generated:

You have an error in your SQL syntax; check the manual that corresponds to
your MySQL server version for the right syntax to use near 'a`d`' at line 1

(Bug #48101)

It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.
MySQL Connector/Net was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug #48100)
An entity model created from a schema containing a table with a column of type UNSIGNED BIGINT and a view of the table did not behave correctly. When an entity was created and mapped to the view, the column that was of type UNSIGNED BIGINT was displayed as BIGINT. (Bug #47872)

When loading the MySQLClient-mono.sln file included with the Connector/Net source into Mono Develop, the following error occurred:

/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
Unsupported or unrecognized project:
'/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'

If the file was modified to remove this problem, then attempting to build the solution generated the following error:

/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
override but no suitable property found to override

(Bug #47048)

If an error occurred during connection to a MySQL Server, deserializing the error message from the packet buffer caused a NullReferenceException to be thrown. When the method MySqlPacket::ReadString() attempted to retrieve the error message, the following line of code threw the exception:
```
        string s = encoding.GetString(bits, (int)buffer.Position, end - (int)buffer.Position);
      
```
This was due to the fact that the encoding field had not been initialized correctly. (Bug #46844)
In the MySqlDataReader class the GetSByte function returned a byte value instead of an sbyte value. (Bug #46620)

        Server Error in '/mono' Application

        --------------------------------------------------------------------------------

        The requested feature is not implemented.
        Description: HTTP 500. Error processing request.

        Stack Trace: 

        System.NotImplementedException: The requested feature is not implemented.
        at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction
        (System.Transactions.Transaction transaction) [0x00000] 
        at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000] 
        at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues
        (System.Configuration.SettingsContext context,
        System.Configuration.SettingsPropertyValueCollection collection) [0x00000] 
        

        --------------------------------------------------------------------------------
        Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433

(Bug #46375)

An exception was generated when using TIMESTAMP columns with the Entity Framework. (Bug #46311)
MySQL Connector/Net sometimes hung, without generating an exception. This happened if a read from a stream failed returning a 0, causing the code in LoadPacket() to enter an infinite loop. (Bug #46308)

When using MySQL Connector/Net 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:

        connection.GetSchema("Columns", ...);

The exception generated was:

        'connection.GetSchema("Columns")' threw an exception of type
        'System.ArgumentException'System.Data.DataTable {System.ArgumentException}
        base{"Input string was not in a correct format.Couldn't store <'Select'> in
        NUMERIC_PRECISION Column.  Expected type is UInt64."}System.Exception
        {System.ArgumentException}

(Bug #46270)

        MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri
        ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C#
        MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25
        bytesC#
        MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha
        vior behavior = SequentialAccess) Line 405 + 0xb bytesC#
        MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma
        ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC#
        System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System
        .Data.CommandBehavior behavior) + 0xb bytes
        System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet
        dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int
        startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand
        command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) +
        0x83 bytes
        System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int
        startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command,
        System.Data.CommandBehavior behavior) + 0x120 bytes
        System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) +
        0x5f bytes

(Bug #46213)

Conversion of MySQL TINYINT(1) to boolean failed. (Bug #46205, Bug #46359, Bug #41953)
When populating a MySQL database table in Visual Studio using the Table Editor, if a VARCHAR(10) column was changed to a VARCHAR(20) column an exception was generated:
```
        SystemArgumentException: DataGridViewComboBoxCell value is not valid.
      To replace this default dialog please handle the DataError Event.
```
(Bug #46100)
In MySQL Connector/Net 6.0.4 using GetProcData generated an error because the parameters data table was only created if MySQL Server was at least version 6.0.6, or if the UseProcedureBodies connection string option was set to true.
Also the DeriveParameters command generated a null reference exception. This was because the parameters data table, which was null, was used in a for each loop. (Bug #45952)
The Entity Framework provider was not calling DBSortExpression correctly when the Skip and Take methods were used, such as in the following statement:
```
        TestModel.tblquarantine.OrderByDescending(q => q.MsgDate).Skip(100).Take(100).ToList();
      
```
This resulted in the data being unsorted. (Bug #45723)
The EscapeString code carried out escaping by calling string.Replace multiple times. This resulted in a performance bottleneck, as for every line a new string was allocated and another was disposed of by the garbage collector. (Bug #45699)

Adding the Allow Batch=False option to the connection string caused MySQL Connector/Net to generate the error:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL
      server version for the right syntax to use near 'SET character_set_results=NULL' at line 1

(Bug #45502)

The MySQL Connector/Net 6.0.4 installer failed with an error. The error message generated was:

        There is a problem with this Windows Installer package. A DLL required for this
        install to complete could not be run. Contact your support personnel or package vendor.

When OK was clicked to acknowledge the error the installer exited. (Bug #45474)

A MySQL Connector/Net test program that connected to MySQL Server using the connection string option compress=true crashed, but only when running on Mono. The program worked as expected when running on Microsoft Windows.
This was due to a bug in Mono. MySQL Connector/Net was modified to avoid using WeakReferences in the Compressed stream class, which was causing the crash. (Bug #45463)
Calling the Entity Framework SaveChanges() method of any MySQL ORM Entity with a column type TIME, generated an error message:
```
Unknown PrimitiveKind Time
```
(Bug #45457)
Insert into two tables failed when using the Entity Framework. The exception generated was:
```
        The value given is not an instance of type 'Edm.Int32'
      
```
(Bug #45077)
Input parameters were missing from Stored Procedures when using them with ADO.NET Data Entities. (Bug #44985)
Errors occurred when using the Entity Framework with cultures that used a comma as the decimal separator. This was because the formatting for SINGLE, DOUBLE and DECIMAL values was not handled correctly. (Bug #44455)
When attempting to connect to MySQL using the Compact Framework version of MySQL Connector/Net, an IndexOutOfRangeException exception was generated on trying to open the connection. (Bug #43736)
When reading data, such as with a MySqlDataAdapter on a MySqlConnection, MySQL Connector/Net could potentially enter an infinite loop in CompressedStream.ReadNextpacket() if compression was enabled. (Bug #43678)
An error occurred when building MySQL Connector/Net from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.
When an attempt was made to build (for example) the MySQL Connector/Net 5.2 branch using the command:
```
        $ nant -buildfile:Client.build
      
```
The following error occurred:
```
        BUILD FAILED

        Error loading buildfile.
        Encoding name 'Windows-1252' not supported.
        Parameter name: name
      
```
(Bug #42411)
After a Reference to "C:\Program Files\MySQL\MySQL Connector Net 5.2.4\Compact Framework\MySql.Data.CF.dll" was added to a Windows Mobile 5.0 project, the project then failed to build, generating a Microsoft Visual C# compiler error.
The error generated was:
```
Error 2 The type 'System.Runtime.CompilerServices.CompilerGeneratedAttribute' 
      has no constructors defined MysqlTest
      Error 3 Internal Compiler Error (0xc0000005 at address 5A7E3714): 
      likely culprit is 'COMPILE'.
```
(Bug #42261)
MySQL Connector/Net CHM documentation stated that MySQL Server 3.23 was supported. (Bug #42110)
In the case of long network inactivity, especially when connection pooling was used, connections were sometimes dropped, for example, by firewalls.
Note: The bugfix introduced a new keepalive parameter, which prevents disconnects by sending an empty TCP packet after a specified timeout. (Bug #40684)

MySQL Connector/Net generated the following exception:

System.NullReferenceException: Object reference not set to an instance of an object.
      bei MySql.Data.MySqlClient.MySqlCommand.TimeoutExpired(Object commandObject)
      bei System.Threading._TimerCallback.TimerCallback_Context(Object state)
      bei System.Threading.ExecutionContext.runTryCode(Object userData)
      bei
      System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode
      code, CleanupCode backoutCode, Object userData)
      bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading._TimerCallback.PerformTimerCallback(Object state)

(Bug #40005)

Calling a Stored Procedure with an output parameter through MySQL Connector/Net resulted in a memory leak. Calling the same Stored Procedure without an output parameter did not result in a memory leak. (Bug #36027)
Using a DataAdapter with a linked MySqlCommandBuilder the following exception was thrown when trying to call da.Update(DataRow[] rows):
```
Connection must be valid and open
```
(Bug #34657)

D.3.5.5. Changes in MySQL Connector/Net 6.0.4 (16 June 2009)

This is the first post-GA release, fixing recently discovered bugs.

Bugs Fixed

If a certain socket exception occurred when trying to establish a MySQL database connection, MySQL Connector/Net displayed an exception message that appeared to be unrelated to the underlying problem. This masked the problem and made diagnosing problems more difficult.
For example, if, when establishing a database connection using TCP/IP, Windows on the local machine allocated an ephemeral port that conflicted with a socket address still in use, then Windows/.NET would throw a socket exception with the following error text:
```
Only one usage of each socket address (protocol/network address/port) is normally
      permitted IP ADDRESS/PORT.
```
However, MySQL Connector/Net masked this socket exception and displayed an exception with the following text:
```
Unable to connect to any of the specified MySQL hosts.
```
(Bug #45021)

A SQL query string containing an escaped backslash caused an exception to be generated:

Index and length must refer to a location within the string.
      Parameter name: length
      at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean
      fAlwaysCopy)
      at MySql.Data.MySqlClient.MySqlTokenizer.NextParameter()
      at MySql.Data.MySqlClient.Statement.InternalBindParameters(String sql,
      MySqlParameterCollection parameters, MySqlPacket packet)
      at MySql.Data.MySqlClient.Statement.BindParameters()
      at MySql.Data.MySqlClient.PreparableStatement.Execute()
      at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior be‎havior)
      at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()

(Bug #44960)

The Microsoft Visual Studio solution file MySQL-VS2005.sln was invalid. Several projects could not be loaded and thus it was not possible to build MySQL Connector/Net from source. (Bug #44822)
The Data Set editor generated an error when attempts were made to modify insert, update or delete commands:
```
Error in WHERE clause near '@'.
      Unable to parse query text.
```
(Bug #44512)
The DataReader in MySQL Connector/Net 6.0.3 considered a BINARY(16) field as a GUID with a length of 16. (Bug #44507)

When creating a new DataSet the following error was generated:

Failed to open a connection to database.
      Cannot load type with name 'MySQL.Data.VisualStudio.StoredProcedureColumnEnumerator'

(Bug #44460)

The MySQL Connector/Net MySQLRoleProvider reported that there were no roles, even when roles existed. (Bug #44414)
MySQL Connector/Net was missing the capability to validate the server's certificate when using encryption. This made it possible to conduct a man-in-the-middle attack against the connection, which defeated the security provided by SSL. (Bug #38700)

D.3.5.6. Changes in MySQL Connector/Net 6.0.3 (28 April 2009)

First GA release.

Functionality Added or Changed

The MySqlTokenizer failed to split fieldnames from values if they were not separated by a space. This also happened if the string contained certain characters. As a result MySqlCommand.ExecuteNonQuery raised an index out of range exception.
The resulting errors are illustrated by the following examples. Note, the example statements do not have delimiting spaces around the = operator.
```
INSERT INTO anytable SET Text='test--test';
```
The tokenizer incorrectly interpreted the value as containing a comment.
```
UPDATE anytable SET Project='123-456',Text='Can you explain this ?',Duration=15 WHERE
      ID=4711;'
```
A MySqlException was generated, as the ? in the value was interpreted by the tokenizer as a parameter sign. The error message generated was:
```
Fatal error encountered during command execution.
      EXCEPTION: MySqlException - Parameter '?'' must be defined.
```
(Bug #44318)

Bugs Fixed

MySQL.Data was not displayed as a Reference inside Microsoft Visual Studio 2008 Professional.
When a new C# project was created in Microsoft Visual Studio 2008 Professional, MySQL.Data was not displayed when References, Add Reference was selected. (Bug #44141)
Column types for SchemaProvider and ISSchemaProvider did not match.
When the source code in SchemaProvider.cs and ISSchemaProvider.cs were compared it was apparent that they were not using the same column types. The base provider used SQL such as SHOW CREATE TABLE, while ISSchemaProvider used the schema information tables. Column types used by the base class were INT64 and the column types used by ISSchemaProvider were UNSIGNED. (Bug #44123)

D.3.5.7. Changes in MySQL Connector/Net 6.0.2 (07 April 2009 beta)

This is a new development release, fixing recently discovered bugs.

Bugs Fixed

MySQL Connector/Net 6.0.1 did not load in Microsoft Visual Studio 2008 and Visual Studio 2005 Pro.
The following error message was generated:
```
.NET Framework Data Provider for MySQL: The data provider object factory service was not
      found.
```
(Bug #44064)

D.3.5.8. Changes in MySQL Connector/Net 6.0.1 (02 April 2009 beta)

This is a new Beta development release, fixing recently discovered bugs.

Bugs Fixed

An insert and update error was generated by the decimal data type in the Entity Framework, when a German collation was used. (Bug #43574)
Generating an Entity Data Model (EDM) schema with a table containing columns with data types MEDIUMTEXT and LONGTEXT generated a runtime error message “Max value too long or too short for Int32”. (Bug #43480)

D.3.5.9. Changes in MySQL Connector/Net 6.0.0 (02 March 2009 alpha)

This is a new Alpha development release.

Bugs Fixed

A null reference exception was generated when MySqlConnection.ClearPool(connection) was called. (Bug #42801)

D.3.6. Changes in MySQL Connector/Net Version 5.3.x

D.3.6.1. Changes in MySQL Connector/Net 5.3.0 (Not released)

D.3.6.1. Changes in MySQL Connector/Net 5.3.0 (Not released)

Bugs Fixed

The Web Provider did not work at all on a remote host, and did not create a database when using autogenerateschema="true". (Bug #39072)
The MySQL Connector/Net installer program ended prematurely without reporting the specific error. (Bug #39019)
When called with an incorrect password the MembershipProvider.GetPassword() method threw a MySQLException instead of a MembershipPasswordException . (Bug #38939)
Possible overflow in MySqlPacket.ReadLong(). (Bug #36997)
The TokenizeSql method was adding query overhead and causing high CPU utilization for larger queries. (Bug #36836)

D.3.7. Changes in MySQL Connector/Net Version 5.2.x

D.3.7.1. Changes in MySQL Connector/Net 5.2.8 (Not released)
D.3.7.2. Changes in MySQL Connector/Net 5.2.7 (15 July 2009)
D.3.7.3. Changes in MySQL Connector/Net 5.2.6 (28 April 2009)
D.3.7.4. Changes in MySQL Connector/Net 5.2.5 (19 November 2008)
D.3.7.5. Changes in MySQL Connector/Net 5.2.4 (13 November 2008)
D.3.7.6. Changes in MySQL Connector/Net 5.2.3 (19 August 2008)
D.3.7.7. Changes in MySQL Connector/Net 5.2.2 (12 May 2008)
D.3.7.8. Changes in MySQL Connector/Net 5.2.1 (27 February 2008)
D.3.7.9. Changes in MySQL Connector/Net 5.2.0 (11 February 2008)

D.3.7.1. Changes in MySQL Connector/Net 5.2.8 (Not released)

Bugs Fixed

If MySqlConnection.GetSchema was called for "Indexes" on a table named “b`a`d” as follows:

DataTable schemaPrimaryKeys = connection.GetSchema(
  "Indexes",
  new string[] { null, schemaName, "b`a`d"});

Then the following exception was generated:

You have an error in your SQL syntax; check the manual that corresponds to
your MySQL server version for the right syntax to use near 'a`d`' at line 1

(Bug #48101)

When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug #47153)
In the MySqlDataReader class the GetSByte function returned a byte value instead of an sbyte value. (Bug #46620)

When trying to create stored procedures from an SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

        MySql.Data.MySqlClient.MySqlException was unhandled
        Message="You have an error in your SQL syntax; check the manual that corresponds to your
        MySQL server version for the right syntax to use near 'DELIMITER' at line 1"
        Source="MySql.Data"
        ErrorCode=-2147467259
        Number=1064
        StackTrace:
        à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
        à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
        lastInsertId)
        à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
        à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
        à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
      à MySql.Data.MySqlClient.MySqlScript.Execute()

Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug #46429)

        Server Error in '/mono' Application

        --------------------------------------------------------------------------------

        The requested feature is not implemented.
        Description: HTTP 500. Error processing request.

        Stack Trace: 

        System.NotImplementedException: The requested feature is not implemented.
        at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction
        (System.Transactions.Transaction transaction) [0x00000] 
        at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000] 
        at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues
        (System.Configuration.SettingsContext context,
        System.Configuration.SettingsPropertyValueCollection collection) [0x00000] 
        

        --------------------------------------------------------------------------------
        Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433

(Bug #46375)

When using MySQL Connector/Net 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:

        connection.GetSchema("Columns", ...);

The exception generated was:

        'connection.GetSchema("Columns")' threw an exception of type
        'System.ArgumentException'System.Data.DataTable {System.ArgumentException}
        base{"Input string was not in a correct format.Couldn't store <'Select'> in
        NUMERIC_PRECISION Column.  Expected type is UInt64."}System.Exception
        {System.ArgumentException}

(Bug #46270)

        MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri
        ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C#
        MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25
        bytesC#
        MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha
        vior behavior = SequentialAccess) Line 405 + 0xb bytesC#
        MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma
        ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC#
        System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System
        .Data.CommandBehavior behavior) + 0xb bytes
        System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet
        dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int
        startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand
        command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) +
        0x83 bytes
        System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int
        startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command,
        System.Data.CommandBehavior behavior) + 0x120 bytes
        System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) +
        0x5f bytes

(Bug #46213)

Conversion of MySQL TINYINT(1) to boolean failed. (Bug #46205, Bug #46359, Bug #41953)
If the application slept for longer than the specified net_write_timeout, and then resumed Read operations on a connection, then the application failed silently. (Bug #45978)
When reading data, such as with a MySqlDataAdapter on a MySqlConnection, MySQL Connector/Net could potentially enter an infinite loop in CompressedStream.ReadNextpacket() if compression was enabled. (Bug #43678)
An error occurred when building MySQL Connector/Net from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.
When an attempt was made to build (for example) the MySQL Connector/Net 5.2 branch using the command:
```
        $ nant -buildfile:Client.build
      
```
The following error occurred:
```
        BUILD FAILED

        Error loading buildfile.
        Encoding name 'Windows-1252' not supported.
        Parameter name: name
      
```
(Bug #42411)
MySQL Connector/Net CHM documentation stated that MySQL Server 3.23 was supported. (Bug #42110)
Using a DataAdapter with a linked MySqlCommandBuilder the following exception was thrown when trying to call da.Update(DataRow[] rows):
```
Connection must be valid and open
```
(Bug #34657)

D.3.7.2. Changes in MySQL Connector/Net 5.2.7 (15 July 2009)

Bugs Fixed

The EscapeString code carried out escaping by calling string.Replace multiple times. This resulted in a performance bottleneck, as for every line a new string was allocated and another was disposed of by the garbage collector. (Bug #45699)
A MySQL Connector/Net test program that connected to MySQL Server using the connection string option compress=true crashed, but only when running on Mono. The program worked as expected when running on Microsoft Windows.
This was due to a bug in Mono. MySQL Connector/Net was modified to avoid using WeakReferences in the Compressed stream class, which was causing the crash. (Bug #45463)
If a certain socket exception occurred when trying to establish a MySQL database connection, MySQL Connector/Net displayed an exception message that appeared to be unrelated to the underlying problem. This masked the problem and made diagnosing problems more difficult.
For example, if, when establishing a database connection using TCP/IP, Windows on the local machine allocated an ephemeral port that conflicted with a socket address still in use, then Windows/.NET would throw a socket exception with the following error text:
```
Only one usage of each socket address (protocol/network address/port) is normally
      permitted IP ADDRESS/PORT.
```
However, MySQL Connector/Net masked this socket exception and displayed an exception with the following text:
```
Unable to connect to any of the specified MySQL hosts.
```
(Bug #45021)
The Microsoft Visual Studio solution file MySQL-VS2005.sln was invalid. Several projects could not be loaded and thus it was not possible to build MySQL Connector/Net from source. (Bug #44822)
The MySQL Connector/Net MySQLRoleProvider reported that there were no roles, even when roles existed. (Bug #44414)
After a Reference to "C:\Program Files\MySQL\MySQL Connector Net 5.2.4\Compact Framework\MySql.Data.CF.dll" was added to a Windows Mobile 5.0 project, the project then failed to build, generating a Microsoft Visual C# compiler error.
The error generated was:
```
Error 2 The type 'System.Runtime.CompilerServices.CompilerGeneratedAttribute' 
      has no constructors defined MysqlTest
      Error 3 Internal Compiler Error (0xc0000005 at address 5A7E3714): 
      likely culprit is 'COMPILE'.
```
(Bug #42261)

MySQL Connector/Net generated the following exception:

System.NullReferenceException: Object reference not set to an instance of an object.
      bei MySql.Data.MySqlClient.MySqlCommand.TimeoutExpired(Object commandObject)
      bei System.Threading._TimerCallback.TimerCallback_Context(Object state)
      bei System.Threading.ExecutionContext.runTryCode(Object userData)
      bei
      System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode
      code, CleanupCode backoutCode, Object userData)
      bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading._TimerCallback.PerformTimerCallback(Object state)

(Bug #40005)

When a TableAdapter was created on a DataSet, it was not possible to use a stored procedure with variables. The following error was generated:
```
The method or operation is not implemented
```
(Bug #39409)

D.3.7.3. Changes in MySQL Connector/Net 5.2.6 (28 April 2009)

Functionality Added or Changed

A new connection string option has been added: use affected rows. When true the connection will report changed rows instead of found rows. (Bug #44194)

Bugs Fixed

Calling GetSchema() on Indexes or IndexColumns failed where index or column names were restricted.
In SchemaProvider.cs, methods GetIndexes() and GetIndexColumns() passed their restrictions directly to GetTables(). This only worked if the restrictions were no more specific than schemaName and tableName. If IndexName was given, this was passed to GetTables() where it was treated as TableType. As a result no tables were returned, unless the index name happened to be BASE TABLE or VIEW. This meant that both methods failed to return any rows. (Bug #43991)
GetSchema("MetaDataCollections") should have returned a table with a column named “NumberOfRestrictions” not “NumberOfRestriction”.
This can be confirmed by referencing the Microsoft Documentation. (Bug #43990)
Requests sent to the MySQL Connector/Net role provider to remove a user from a role failed. The query log showed the query was correctly executed within a transaction which was immediately rolled back. The rollback was caused by a missing call to the Complete method of the transaction. (Bug #43553)
When using MySqlBulkLoader.Load(), the text file is opened by NativeDriver.SendFileToServer. If it encountered a problem opening the file as a stream, an exception was generated and caught. An attempt to clean up resources was then made in the finally{} clause by calling fs.Close(), but since the stream was never successfully opened, this was an attempt to execute a method of a null reference. (Bug #43332)
A null reference exception was generated when MySqlConnection.ClearPool(connection) was called. (Bug #42801)
MySQLMembershipProvider.ValidateUser only used the userId to validate. However, it should also use the applicationId to perform the validation correctly.
The generated query was, for example:
```
SELECT Password, PasswordKey, PasswordFormat, IsApproved, Islockedout
      FROM my_aspnet_Membership WHERE userId=13
```
Note that applicationId is not used. (Bug #42574)
There was an error in the ProfileProvider class in the private ProfileInfoCollection GetProfiles() function. The column of the final table was named “lastUpdatdDate” ('e' is missing) instead of the correct “lastUpdatedDate”. (Bug #41654)
The GetGuid() method of MySqlDataReader did not treat BINARY(16) column data as a GUID. When operating on such a column a FormatException exception was generated. (Bug #41452)
When ASP.NET membership was configured to not require password question and answer using requiresQuestionAndAnswer="false", a SqlNullValueException was generated when using MembershipUser.ResetPassword() to reset the user password. (Bug #41408)
If a Stored Procedure contained spaces in its parameter list, and was then called from MySQL Connector/Net, an exception was generated. However, the same Stored Procedure called from the MySQL Query Analyzer or the MySQL Client worked correctly.
The exception generated was:
```
        Parameter '0' not found in the collection.
      
```
(Bug #41034)
The DATETIME format contained an erroneous space. (Bug #41021)
When MySql.Web.Profile.MySQLProfileProvider was configured, it was not possible to assign a name other than the default name MySQLProfileProvider.
If the name SCC_MySQLProfileProvider was assigned, an exception was generated when attempting to use Page.Context.Profile['custom prop'].
The exception generated was:
```
The profile default provider was not found.
```
Note that the exception stated: 'the profile default provider...', even though a different name was explicitly requested. (Bug #40871)
When ExecuteNonQuery was called with a command type of Stored Procedure it worked for one user but resulted in a hang for another user with the same database permissions.
However, if CALL was used in the command text and ExecuteNonQuery was used with a command type of Text, the call worked for both users. (Bug #40139)

D.3.7.4. Changes in MySQL Connector/Net 5.2.5 (19 November 2008)

Bugs Fixed

Visual Studio 2008 displayed the following error three times on start-up:

        "Package Load Failure

        Package 'MySql.Data.VisualStudio.MySqlDataProviderPackage, MySql.VisualStudio,
        Version=5.2.4, Culture=neutral, PublicKeyToken=null' has failed to load properly (GUID =
        {79A115C9-B133-4891-9E7B-242509DAD272}).  Please contact the package vendor for
        assistance.  Application restart is recommended, due to possible environment corruption.
        Would you like to disable loading the package in the future?  You may use
        'devenve/resetskippkgs' to re-enable package loading."

(Bug #40726)

D.3.7.5. Changes in MySQL Connector/Net 5.2.4 (13 November 2008)

Bugs Fixed

MySqlDataReader did not feature a GetSByte method. (Bug #40571)
When working with stored procedures MySQL Connector/Net generated an exception Unknown "table parameters" in information_schema. (Bug #40382)
GetDefaultCollation and GetMaxLength were not thread safe. These functions called the database to get a set of parameters and cached them in two static dictionaries in the function InitCollections. However, if many threads called them they would try to insert the same keys in the collections resulting in duplicate key exceptions. (Bug #40231)
If connection pooling was not set explicitly in the connection string, MySQL Connector/Net added “;Pooling=False” to the end of the connection string when MySqlCommand.ExecuteReader() was called.
If connection pooling was explicitly set in the connection string, when MySqlConnection.Open() was called it converted “Pooling=True” to “pooling=True”.
If MySqlCommand.ExecuteReader() was subsequently called, it concatenated “;Pooling=False” to the end of the connection string. The resulting connection string was thus terminated with “pooling=True;Pooling=False”. This disabled connection pooling completely. (Bug #40091)
The connection string option Functions Return String did not set the correct encoding for the result string. Even though the connection string option Functions Return String=true; is set, the result of SELECT DES_DECRYPT() contained “??” instead of the correct national character symbols. (Bug #40076)
If, when using the MySqlTransaction transaction object, an exception was thrown, the transaction object was not disposed of and the transaction was not rolled back. (Bug #39817)
After the ConnectionString property was initialized using the public setter of DbConnectionStringBuilder, the GetConnectionString method of MySqlConnectionStringBuilder incorrectly returned null when true was assigned to the includePass parameter. (Bug #39728)
When using ProfileProvider, attempting to update a previously saved property failed. (Bug #39330)
Reading a negative time value greater than -01:00:00 returned the absolute value of the original time value. (Bug #39294)
Inserting a negative time value (negative TimeSpan) into a Time column through the use of MySqlParameter caused MySqlException to be thrown. (Bug #39275)
When a data connection was created in the server explorer of Visual Studio 2008 Team, an error was generated when trying to expand stored procedures that had parameters.
Also, if TableAdapter was right-clicked and then Add, Query, Use Existing Stored Procedures selected, if you then attempted to select a stored procedure, the window would close and no error message would be displayed. (Bug #39252)
The Web Provider did not work at all on a remote host, and did not create a database when using autogenerateschema="true". (Bug #39072)
MySQL Connector/Net called hashed password methods not supported in Mono 2.0 Preview 2. (Bug #38895)

D.3.7.6. Changes in MySQL Connector/Net 5.2.3 (19 August 2008)

Functionality Added or Changed

Error string was returned after a 28000 second wait_timeout. This has been changed to generate a ConnectionState.Closed event. (Bug #38119)
Changed how the procedure schema collection is retrieved. If use procedure bodies=true then the mysql.proc table is selected directly as this is up to 50 times faster than the current information_schema implementation. If use procedure bodies=false, then the information_schema collection is queried. (Bug #36694)
String escaping functionality has been moved from the MySqlString class to the MySqlHelper class, where it can be accessed by the EscapeString method. (Bug #36205)

Bugs Fixed

The GetOrdinal() method failed to return the ordinal if the column name string contained an accent. (Bug #38721)
MySQL Connector/Net uninstaller did not clean up all installed files. (Bug #38534)
There was a short circuit evaluation error in the MySqlCommand.CheckState() method. When the statement connection == null was true a NullReferenceException was thrown and not the expected InvalidOperationException. (Bug #38276)
The provider did not silently create the user if the user did not exist. (Bug #38243)
Executing a command that resulted in a fatal exception did not close the connection. (Bug #37991)
When a prepared insert query is run that contains an UNSIGNED TINYINT in the parameter list, the complete query and data that should be inserted is corrupted and no error is thrown. (Bug #37968)

In a .NET application MySQL Connector/Net modifies the connection string so that it contains several occurrences of the same option with different values. This is illustrated by the example that follows.

The original connection string:

        host=localhost;database=test;uid=*****;pwd=*****;
      connect timeout=25; auto enlist=false;pooling=false;

The connection string after closing MySqlDataReader:

        host=localhost;database=test;uid=*****;pwd=*****;
        connect timeout=25;auto enlist=false;pooling=false;
        Allow User Variables=True;Allow User Variables=False;
      Allow User Variables=True;Allow User Variables=False;

(Bug #37955)

Unnecessary network traffic was generated for the normal case where the web provider schema was up to date. (Bug #37469)
MySqlReader.GetOrdinal() performance enhancements break existing functionality. (Bug #37239)
The autogenerateschema option produced tables with incorrect collations. (Bug #36444)
GetSchema did not work correctly when querying for a collection, if using a non-English locale. (Bug #35459)
When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug #33322)
Using the MySQL Visual Studio plugin and a MySQL 4.1 server, certain field types (ENUM) would not be identified correctly. Also, when looking for tables, the plugin would list all tables matching a wildcard pattern of the database name supplied in the connection string, instead of only tables within the specified database. (Bug #30603)

D.3.7.7. Changes in MySQL Connector/Net 5.2.2 (12 May 2008)

Bugs Fixed

Product documentation incorrectly stated '?' is the preferred parameter marker. (Bug #37349)
An incorrect value for a bit field would returned in a multi-row query if a preceding value for the field returned NULL. (Bug #36313)
Tables with GEOMETRY field types would return an unknown data type exception. (Bug #36081)
When using the MySQLProfileProvider, setting profile details and then reading back saved data would result in the default values being returned instead of the updated values. (Bug #36000)
When creating a connection, setting the ConnectionString property of MySqlConnection to NULL would throw an exception. (Bug #35619)
The DbCommandBuilder.QuoteIdentifer method was not implemented. (Bug #35492)
When using encrypted passwords, the GetPassword() function would return the wrong string. (Bug #35336)
An error would be raised when calling GetPassword() with a NULL value. (Bug #35332)
When retrieving data where a field has been identified as containing a GUID value, the incorrect value would be returned when a previous row contained a NULL value for that field. (Bug #35041)
Using the TableAdapter Wizard would fail when generating commands that used stored procedures due to the change in supported parameter characters. (Bug #34941)
When creating a new stored procedures, the new parameter code which permits the use of the @ symbol would interfere with the specification of a DEFINER. (Bug #34940)
When using SqlDataSource to open a connection, the connection would not automatically be closed when access had completed. (Bug #34460)
There was a high level of contention in the connection pooling code that could lead to delays when opening connections and submitting queries. The connection pooling code has been modified to try and limit the effects of the contention issue. (Bug #34001)
Using the TableAdaptor wizard in combination with a suitable SELECT statement, only the associated INSERT statement would also be created, rather than the required DELETE and UPDATE statements. (Bug #31338)
Fixed problem in datagrid code related to creating a new table. This problem may have been introduced with .NET 2.0 SP1.
Fixed profile provider that would throw an exception if you were updating a profile that already existed.

D.3.7.8. Changes in MySQL Connector/Net 5.2.1 (27 February 2008)

Bugs Fixed

When using the provider to generate or update users and passwords, the password checking algorithm would not validate the password strength or requirements correctly. (Bug #34792)
When executing statements that used stored procedures and functions, the new parameter code could fail to identify the correct parameter format. (Bug #34699)
The installer would fail to the DDEX provider binary if the Visual Studio 2005 component was not selected. The result would lead to MySQL Connector/Net not loading properly when using the interface to a MySQL server within Visual Studio. (Bug #34674)
A number of issues were identified in the case, connection and schema areas of the code for MembershipProvider, RoleProvider, ProfileProvider. (Bug #34495)
When using web providers, the MySQL Connector/Net would check the schema and cache the application id, even when the connection string had been set. The effect would be to break the membership provider list. (Bug #34451)
Attempting to use an isolation level other than the default with a transaction scope would use the default isolation level. (Bug #34448)
When altering a stored procedure within Visual Studio, the parameters to the procedure could be lost. (Bug #34359)
A race condition could occur within the procedure cache resulting the cache contents overflowing beyond the configured cache size. (Bug #34338)
Fixed problem with Visual Studio 2008 integration that caused pop-up menus on server explorer nodes to not function
The provider code has been updated to fix a number of outstanding issues.

D.3.7.9. Changes in MySQL Connector/Net 5.2.0 (11 February 2008)

Functionality Added or Changed

Performing GetValue() on a field TINYINT(1) returned a BOOLEAN. While not a bug, this caused problems in software that expected an INT to be returned. A new connection string option Treat Tiny As Boolean has been added with a default value of true. If set to false the provider will treat TINYINT(1) as INT. (Bug #34052)
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

Some speed improvements have been implemented in the TokenizeSql process used to identify elements of SQL statements. (Bug #34220)
When accessing tables from different databases within the same TransactionScope, the same user/password combination would be used for each database connection. MySQL Connector/Net does not handle multiple connections within the same transaction scope. An error is now returned if you attempt this process, instead of using the incorrect authorization information. (Bug #34204)
The status of connections reported through the state change handler was not being updated correctly. (Bug #34082)
Incorporated some connection string cache optimizations sent to us by Maxim Mass. (Bug #34000)
In an open connection where the server had disconnected unexpectedly, the status information of the connection would not be updated properly. (Bug #33909)
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 defined 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 MySQL 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)

D.3.8. Changes in MySQL Connector/Net Version 5.1.x

D.3.8.1. Changes in MySQL Connector/Net 5.1.8 (Not released)
D.3.8.2. Changes in MySQL Connector/Net 5.1.7 (21 August 2008)
D.3.8.3. Changes in MySQL Connector/Net 5.1.6 (12 May 2008)
D.3.8.4. Changes in MySQL Connector/Net 5.1.5 (Not released)
D.3.8.5. Changes in MySQL Connector/Net 5.1.4 (20 November 2007)
D.3.8.6. Changes in MySQL Connector/Net 5.1.3 (21 September 2007 beta)
D.3.8.7. Changes in MySQL Connector/Net 5.1.2 (18 June 2007)
D.3.8.8. Changes in MySQL Connector/Net 5.1.1 (23 May 2007)
D.3.8.9. Changes in MySQL Connector/Net 5.1.0 (01 May 2007)

D.3.8.1. Changes in MySQL Connector/Net 5.1.8 (Not released)

Bugs Fixed

Calling GetSchema() on Indexes or IndexColumns failed where index or column names were restricted.
In SchemaProvider.cs, methods GetIndexes() and GetIndexColumns() passed their restrictions directly to GetTables(). This only worked if the restrictions were no more specific than schemaName and tableName. If IndexName was given, this was passed to GetTables() where it was treated as TableType. As a result no tables were returned, unless the index name happened to be BASE TABLE or VIEW. This meant that both methods failed to return any rows. (Bug #43991)
The DATETIME format contained an erroneous space. (Bug #41021)
If connection pooling was not set explicitly in the connection string, MySQL Connector/Net added “;Pooling=False” to the end of the connection string when MySqlCommand.ExecuteReader() was called.
If connection pooling was explicitly set in the connection string, when MySqlConnection.Open() was called it converted “Pooling=True” to “pooling=True”.
If MySqlCommand.ExecuteReader() was subsequently called, it concatenated “;Pooling=False” to the end of the connection string. The resulting connection string was thus terminated with “pooling=True;Pooling=False”. This disabled connection pooling completely. (Bug #40091)

MySQL Connector/Net generated the following exception:

System.NullReferenceException: Object reference not set to an instance of an object.
      bei MySql.Data.MySqlClient.MySqlCommand.TimeoutExpired(Object commandObject)
      bei System.Threading._TimerCallback.TimerCallback_Context(Object state)
      bei System.Threading.ExecutionContext.runTryCode(Object userData)
      bei
      System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode
      code, CleanupCode backoutCode, Object userData)
      bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
      ContextCallback callback, Object state)
      bei System.Threading._TimerCallback.PerformTimerCallback(Object state)

(Bug #40005)

If, when using the MySqlTransaction transaction object, an exception was thrown, the transaction object was not disposed of and the transaction was not rolled back. (Bug #39817)
When a prepared insert query is run that contains an UNSIGNED TINYINT in the parameter list, the complete query and data that should be inserted is corrupted and no error is thrown. (Bug #37968)
Calling MySqlDataAdapter.FillSchema on a SELECT statement that referred to a table that did not exist left the connection in a bad state. After this call, all SELECT statements returned an empty result set. If the SELECT statement referred to a table that did exist then everything worked as expected. (Bug #30518)

D.3.8.2. Changes in MySQL Connector/Net 5.1.7 (21 August 2008)

Bugs Fixed

There was a short circuit evaluation error in the MySqlCommand.CheckState() method. When the statement connection == null was true a NullReferenceException was thrown and not the expected InvalidOperationException. (Bug #38276)
Executing a command that resulted in a fatal exception did not close the connection. (Bug #37991)

The original connection string:

        host=localhost;database=test;uid=*****;pwd=*****;
      connect timeout=25; auto enlist=false;pooling=false;

The connection string after closing MySqlDataReader:

        host=localhost;database=test;uid=*****;pwd=*****;
        connect timeout=25;auto enlist=false;pooling=false;
        Allow User Variables=True;Allow User Variables=False;
      Allow User Variables=True;Allow User Variables=False;

(Bug #37955)

As MySqlDbType.DateTime is not available in VB.Net the warning The datetime enum value is obsolete was always shown during compilation. (Bug #37406)
An unknown MySqlErrorCode was encountered when opening a connection with an incorrect password. (Bug #37398)
Documentation incorrectly stated that “the DataColumn class in .NET 1.0 and 1.1 does not permit columns with type of UInt16, UInt32, or UInt64 to be autoincrement columns”. (Bug #37350)
SemaphoreFullException is generated when application is closed. (Bug #36688)
GetSchema did not work correctly when querying for a collection, if using a non-English locale. (Bug #35459)
When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug #33322)
Using the MySQL Visual Studio plugin and a MySQL 4.1 server, certain field types (ENUM) would not be identified correctly. Also, when looking for tables, the plugin would list all tables matching a wildcard pattern of the database name supplied in the connection string, instead of only tables within the specified database. (Bug #30603)

D.3.8.3. Changes in MySQL Connector/Net 5.1.6 (12 May 2008)

Bugs Fixed

When creating a connection pool, specifying an invalid IP address will cause the entire application to crash, instead of providing an exception. (Bug #36432)
An incorrect value for a bit field would returned in a multi-row query if a preceding value for the field returned NULL. (Bug #36313)
The MembershipProvider will raise an exception when the connection string is configured with enablePasswordRetrival = true and RequireQuestionAndAnswer = false. (Bug #36159)
When calling GetNumberOfUsersOnline an exception is raised on the submitted query due to a missing parameter. (Bug #36157)
Tables with GEOMETRY field types would return an unknown data type exception. (Bug #36081)
When creating a connection, setting the ConnectionString property of MySqlConnection to NULL would throw an exception. (Bug #35619)
The DbCommandBuilder.QuoteIdentifer method was not implemented. (Bug #35492)
When using SqlDataSource to open a connection, the connection would not automatically be closed when access had completed. (Bug #34460)
Attempting to use an isolation level other than the default with a transaction scope would use the default isolation level. (Bug #34448)
When altering a stored procedure within Visual Studio, the parameters to the procedure could be lost. (Bug #34359)
A race condition could occur within the procedure cache resulting the cache contents overflowing beyond the configured cache size. (Bug #34338)
Using the TableAdaptor wizard in combination with a suitable SELECT statement, only the associated INSERT statement would also be created, rather than the required DELETE and UPDATE statements. (Bug #31338)

D.3.8.4. Changes in MySQL Connector/Net 5.1.5 (Not released)

Functionality Added or Changed

Performing GetValue() on a field TINYINT(1) returned a BOOLEAN. While not a bug, this caused problems in software that expected an INT to be returned. A new connection string option Treat Tiny As Boolean has been added with a default value of true. If set to false the provider will treat TINYINT(1) as INT. (Bug #34052)

Bugs Fixed

Some speed improvements have been implemented in the TokenizeSql process used to identify elements of SQL statements. (Bug #34220)
When accessing tables from different databases within the same TransactionScope, the same user/password combination would be used for each database connection. MySQL Connector/Net does not handle multiple connections within the same transaction scope. An error is now returned if you attempt this process, instead of using the incorrect authorization information. (Bug #34204)
The status of connections reported through the state change handler was not being updated correctly. (Bug #34082)
Incorporated some connection string cache optimizations sent to us by Maxim Mass. (Bug #34000)
In an open connection where the server had disconnected unexpectedly, the status information of the connection would not be updated properly. (Bug #33909)
MySQL Connector/Net would fail to compile properly with nant. (Bug #33508)
Problem with membership provider would mean that FindUserByEmail would fail with a MySqlException because it was trying to add a second parameter with the same name as the first. (Bug #33347)
Using compression in the MySQL connection with MySQL Connector/Net would be slower than using native (uncompressed) communication. (Bug #27865)

D.3.8.5. 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 noninput 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 MySqlDateTime.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)
MySQL 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 defined 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 MySQL 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)

D.3.8.6. Changes in MySQL Connector/Net 5.1.3 (21 September 2007 beta)

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)

D.3.8.7. 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)

D.3.8.8. 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 MySQL Connector/Net on Windows would fail if VisualStudio had not already been installed. (Bug #28260)
MySQL 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 performance. (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.

D.3.8.9. 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!).

D.3.9. Changes in MySQL Connector/Net Version 5.0.x

D.3.9.1. Changes in MySQL Connector/Net 5.0.10 (Not released)
D.3.9.2. Changes in MySQL Connector/Net 5.0.9 (Not released)
D.3.9.3. Changes in MySQL Connector/Net 5.0.8 (21 August 2007)
D.3.9.4. Changes in MySQL Connector/Net 5.0.7 (18 May 2007)
D.3.9.5. Changes in MySQL Connector/Net 5.0.6 (22 March 2007)
D.3.9.6. Changes in MySQL Connector/Net 5.0.5 (07 March 2007)
D.3.9.7. Changes in MySQL Connector/Net 5.0.4 (Not released)
D.3.9.8. Changes in MySQL Connector/Net 5.0.3 (05 January 2007)
D.3.9.9. Changes in MySQL Connector/Net 5.0.2 (06 November 2006)
D.3.9.10. Changes in MySQL Connector/Net 5.0.1 (01 October 2006)
D.3.9.11. Changes in MySQL Connector/Net 5.0.0 (08 August 2006)

D.3.9.1. Changes in MySQL Connector/Net 5.0.10 (Not released)

Bugs Fixed

If, when using the MySqlTransaction transaction object, an exception was thrown, the transaction object was not disposed of and the transaction was not rolled back. (Bug #39817)
Executing a command that resulted in a fatal exception did not close the connection. (Bug #37991)
When a prepared insert query is run that contains an UNSIGNED TINYINT in the parameter list, the complete query and data that should be inserted is corrupted and no error is thrown. (Bug #37968)

The original connection string:

        host=localhost;database=test;uid=*****;pwd=*****;
      connect timeout=25; auto enlist=false;pooling=false;

The connection string after closing MySqlDataReader:

        host=localhost;database=test;uid=*****;pwd=*****;
        connect timeout=25;auto enlist=false;pooling=false;
        Allow User Variables=True;Allow User Variables=False;
      Allow User Variables=True;Allow User Variables=False;

(Bug #37955)

When creating a connection pool, specifying an invalid IP address will cause the entire application to crash, instead of providing an exception. (Bug #36432)
GetSchema did not work correctly when querying for a collection, if using a non-English locale. (Bug #35459)
When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug #33322)

D.3.9.2. Changes in MySQL Connector/Net 5.0.9 (Not released)

Bugs Fixed

The DbCommandBuilder.QuoteIdentifer method was not implemented. (Bug #35492)
Setting the size of a string parameter after the value could cause an exception. (Bug #32094)
Creation of parameter objects with noninput 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 MySqlDateTime.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 defined 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)

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

D.3.9.4. 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 performance. (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 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)

D.3.9.5. 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 MySQL Connector/Net 5.0.5. (Bug #26960)

D.3.9.6. 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 enable calling procedures without using procedure metadata.

Bugs Fixed

MySqlConnection.GetSchema fails with NullReferenceException for Foreign Keys. (Bug #26660)
MySQL Connector/Net would fail to install under Windows Vista. (Bug #26430)
Opening a connection would be slow due to host name 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 correct CLR data type. (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, data type. (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 host name 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)
MySQL Connector/Net would not compile properly when used with Mono 1.2. (Bug #24263)
Applications would crash when calling with CommandType set to StoredProcedure.

D.3.9.7. Changes in MySQL Connector/Net 5.0.4 (Not released)

This is a new Beta development release, fixing recently discovered bugs.

This section has no changelog entries.

D.3.9.8. 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)

D.3.9.9. 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, MySQL 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, MySQL Connector/Net would incorrectly resolve host names. (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 MySQL Connector/Net 5.0.2 must be installed. (Bug #23071)
Using Windows Vista (RC2) as a nonprivileged 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)
MySQL Connector/Net did not work as a data source for the SqlDataSource object used by ASP.NET 2.0. (Bug #16126)

D.3.9.10. Changes in MySQL Connector/Net 5.0.1 (01 October 2006)

Bugs Fixed

MySQL Connector/Net on a Turkish 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 MySQL 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 MySQL Connector/Net exception. (Bug #18391)
Incorrect field/data lengths could be returned for VARCHAR UTF8 columns. (Bug #14592)
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)

D.3.9.11. 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)

D.3.10. Changes in MySQL Connector/Net Version 1.0.x

D.3.10.1. Changes in MySQL Connector/Net 1.0.11 (Not released)
D.3.10.2. Changes in MySQL Connector/Net 1.0.10 (24 August 2007)
D.3.10.3. Changes in MySQL Connector/Net 1.0.9 (02 February 2007)
D.3.10.4. Changes in MySQL Connector/Net 1.0.8 (20 October 2006)
D.3.10.5. Changes in MySQL Connector/Net 1.0.7 (21 November 2005)
D.3.10.6. Changes in MySQL Connector/Net 1.0.6 (03 October 2005)
D.3.10.7. Changes in MySQL Connector/Net 1.0.5 (29 August 2005)
D.3.10.8. Changes in MySQL Connector/Net 1.0.4 (20 January 2005)
D.3.10.9. Changes in MySQL Connector/Net 1.0.3 (12 October 2004 gamma)
D.3.10.10. Changes in MySQL Connector/Net 1.0.2 (15 November 2004 gamma)
D.3.10.11. Changes in MySQL Connector/Net 1.0.1 (27 October 2004 beta)
D.3.10.12. Changes in MySQL Connector/Net 1.0.0 (01 September 2004)

D.3.10.1. Changes in MySQL Connector/Net 1.0.11 (Not released)

Bugs Fixed

Attempting to utilize MySQL Connector .Net version 1.0.10 throws a fatal exception under Mono when pooling is enabled. (Bug #33682)
Setting the size of a string parameter after the value could cause an exception. (Bug #32094)
Creation of parameter objects with noninput 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 MySQL Connector/Net incorrectly identifying BLOB fields as binary, rather than text. (Bug #30233)
Using compression in the MySQL connection with MySQL 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)

D.3.10.2. 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, data type. (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)

D.3.10.3. 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, MySQL 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 host name 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, MySQL Connector/Net would incorrectly resolve host names. (Bug #23758)
An System.OverflowException would be raised when accessing a varchar field over 255 bytes. (Bug #23749)
Nested transactions do not raise an error or warning. (Bug #22400)
Within Mono, using the PreparedStatement interface could result in an error due to a BitArray copying error. (Bug #18186)

D.3.10.4. 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 procedure metadata has been changed so that users without SELECT privileges on the mysql.proc table can use a stored procedure.

Bugs Fixed

MySQL Connector/Net on a Turkish 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 MySQL 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 MySQL 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 nonnull 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 permit single or double quotation marks 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)
Incorrect field/data lengths could be returned for VARCHAR UTF8 columns. (Bug #14592)
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)

D.3.10.5. 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)

D.3.10.6. Changes in MySQL Connector/Net 1.0.6 (03 October 2005)

Bugs Fixed

MySQL 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 MySQL Connector/Net 1.0.5 installer would not install alongside MySQL Connector/Net 1.0.4. (Bug #12835)

D.3.10.7. Changes in MySQL Connector/Net 1.0.5 (29 August 2005)

Bugs Fixed

MySQL Connector/Net could not connect to MySQL 4.1.14. (Bug #12771)
With multiple hosts in the connection string, MySQL 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)
MySQL Connector/Net interpreted the new decimal data type as a byte array. (Bug #11294)
Added support to call a stored function from MySQL 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)
MySQL Connector/Net could not work properly with certain regional settings. (WL#8228)

D.3.10.8. 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.

D.3.10.9. Changes in MySQL Connector/Net 1.0.3 (12 October 2004 gamma)

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.

D.3.10.10. Changes in MySQL Connector/Net 1.0.2 (15 November 2004 gamma)

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.

D.3.10.11. Changes in MySQL Connector/Net 1.0.1 (27 October 2004 beta)

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 data type. (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 constructor initialize problems in MySqlCommand() (Bug #5613)
Possible bug in MySqlParameter(string, object) constructor (Bug #5602)
Fixed Yet Another "object reference not set to an instance of an object" (Bug #5496)
Cannot run a stored procedure populating mysqlcommand.parameters (Bug #5474)
Setting DbType threw a NullReferenceException. (Bug #5469)
Calling GetChars on a LONGTEXT column threw an exception. (Bug #5458)
MySqlCommand saw instances of "?" as parameters in string literals. (Bug #5392)
DataReader reported all rows as NULL if one row was NULL. (Bug #5388)
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
Added test case for resetting the command text on a prepared command
Fixed problem where connection lifetime on the connect string was not being respected
Field buffers being reused to decrease memory allocations and increase speed
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 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
Virtualized driver subsystem so future releases could easily support client or embedded server support

D.3.10.12. 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.

D.3.11. 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 do not 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 enable 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 do not work 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".
Enable 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 DataAdapter updates from working right (thanks Michael King).
Fixed a misspelling in MySqlHelper.cs (thanks Patrick Kristiansen).

D.3.12. 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 permit 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 available.
Moved toolbox bitmaps into resource folder.
Changed field.cs to permit 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 infinitely (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).

D.3.13. Changes in MySQL Connector/Net Version 0.75

Enum values now supported as parameter values (thanks Philipp Sumi).
Year data type 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 user name 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).

D.3.14. 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 permit 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!).

D.3.15. 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).

D.3.16. 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 data type 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 quotation marks 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 permits 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.

D.3.17. 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 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).

D.3.18. 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.

D.3.19. 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.

D.3.20. 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.

D.4. MySQL Visual Studio Plugin Change History

D.4.1. Changes in MySQL Visual Studio Plugin 1.0.3 (Not yet released)
D.4.2. Changes in MySQL Visual Studio Plugin 1.0.2 (Not yet released)
D.4.3. Changes in MySQL Visual Studio Plugin 1.0.1 (04 October 2006)
D.4.4. Changes in MySQL Visual Studio Plugin 1.0.0 (04 October 2006)

Note

As of Connector/Net 5.1.2 (14 June 2007), the Visual Studion Plugin is part of the main Connector/Net package. For the change history for the Visual Studio Plugin, see Section D.3, “MySQL Connector/Net Change History”.

D.4.1. Changes in MySQL Visual Studio Plugin 1.0.3 (Not yet released)

Bugs Fixed

Running queries based on a stored procedure would cause the data set designer to terminate. (Bugs #26364)
DataSet wizard would show all tables instead of only the tables available within the selected database. (Bugs #26348)

D.4.2. Changes in MySQL Visual Studio Plugin 1.0.2 (Not yet released)

Bugs Fixed

The Add Connection dialog of the Server Explorer would freeze when accessing databases with capitalized characters in their name. (Bug #24875)
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)

D.4.3. Changes in MySQL Visual Studio Plugin 1.0.1 (04 October 2006)

This is a bug fix release to resolve an incompatibility issue with Connector/Net 5.0.1.

It is critical that this release only be used with Connector/Net 5.0.1. After installing Connector/Net 5.0.1, you will need to make a small change in your machine.config file. This file should be located at %win%\Microsoft.Net\Framework\v2.0.50727\CONFIG\machine.config (%win% should be the location of your Windows folder). Near the bottom of the file you will see a line like this:

<add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient"
description=".Net Framework Data Provider for MySQL"
type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data"/>

It needs to be changed to be like this:

<add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient"
description=".Net Framework Data Provider for MySQL"
type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data,
Version=5.0.1.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d"/>

This section has no changelog entries.

D.4.4. Changes in MySQL Visual Studio Plugin 1.0.0 (04 October 2006)

Bugs Fixed

Ability to work with MySQL objects (tables, views, stored procedures, etc) from within Server Explorer.
DDEX (Data Designer Extensibility) compatibility.

D.5. MySQL Connector/J Change History

D.5.1. Changes in MySQL Connector/J 5.1.x
D.5.2. Changes in MySQL Connector/J 5.0.x
D.5.3. Changes in MySQL Connector/J 3.1.x
D.5.4. Changes in MySQL Connector/J 3.0.x
D.5.5. Changes in MySQL Connector/J 2.0.x
D.5.6. Changes in MySQL Connector/J 1.2.x and lower

D.5.1. Changes in MySQL Connector/J 5.1.x

D.5.1.1. Changes in MySQL Connector/J 5.1.17 (07 July 2011)
D.5.1.2. Changes in MySQL Connector/J 5.1.16 (Not released)
D.5.1.3. Changes in MySQL Connector/J 5.1.15 (09 February 2011)
D.5.1.4. Changes in MySQL Connector/J 5.1.14 (6th December 2010)
D.5.1.5. Changes in MySQL Connector/J 5.1.13 (24 June 2010)
D.5.1.6. Changes in MySQL Connector/J 5.1.12 (18 February 2010)
D.5.1.7. Changes in MySQL Connector/J 5.1.11 (21 January 2010)
D.5.1.8. Changes in MySQL Connector/J 5.1.10 (23 September 2009)
D.5.1.9. Changes in MySQL Connector/J 5.1.9 (21 September 2009)
D.5.1.10. Changes in MySQL Connector/J 5.1.8 (16 July 2009)
D.5.1.11. Changes in MySQL Connector/J 5.1.7 (21 October 2008)
D.5.1.12. Changes in MySQL Connector/J 5.1.6 (07 March 2008)
D.5.1.13. Changes in MySQL Connector/J 5.1.5 (09 October 2007)
D.5.1.14. Changes in MySQL Connector/J 5.1.4 (Not Released)
D.5.1.15. Changes in MySQL Connector/J 5.1.3 (10 September 2007)
D.5.1.16. Changes in MySQL Connector/J 5.1.2 (29 June 2007)
D.5.1.17. Changes in MySQL Connector/J 5.1.1 (22 June 2007)
D.5.1.18. Changes in MySQL Connector/J 5.1.0 (11 April 2007)

D.5.1.1. Changes in MySQL Connector/J 5.1.17 (07 July 2011)

Fixes bugs found since release 5.1.16.

Bugs Fixed

LIKE was not optimized in then server when run against INFORMATION_SCHEMA tables and no wildcards were used. Databases/tables with '_' or '%' in their names (escaped or not) are handled by this code path, although slower, since it is rare to find these characters in table names in SQL. If there is a '_' or '%' in the string, LIKE takes care of that; otherwise, '=' is now used instead. The only exception is the information_schema database, which is handled separately. The patch covers both getTables() and getColumns(). (Bug #61332)
The first call to a stored procedure failed with “No Database Selected”. The workaround introduced in DatabaseMetaData.getCallStmtParameterTypes to fix the server bug where SHOW CREATE PROCEDURE was not respecting lowercase table names was misbehaving when the connection was not attached to a database and on case-insensitive operating systems. (Bug #61150)
There was a concurrency bottleneck in Java's character set encoding/decoding when converting bytes to/from String values.
Important
No longer use String.getBytes(...), or new String(byte[]...). Use the StringUtils method instead.
(Bug #61105)

D.5.1.2. Changes in MySQL Connector/J 5.1.16 (Not released)

Fixes bugs found since release 5.1.15.

Bugs Fixed

When auto-reconnect was used with cacheServerConfiguration, errors could occur when the host changed (in an HA setup, for example). (Bug #12325877)

D.5.1.3. Changes in MySQL Connector/J 5.1.15 (09 February 2011)

Fixes bugs found since release 5.1.14.

Bugs Fixed

Optional logging class com.mysql.jdbc.log.Log4JLogger was not included in the source/binary package for 5.1.14.
5.1.15 will ship with an SLF4J logger (which can then be plugged into Log4J). Unfortunately, it is not possible to ship a direct Log4J integration because the GPL is not compatible with Log4J's license. (Bug #59511, Bug #11766408)
The hard-coded list of reserved words in Connector/J was not updated to reflect the list of reserved words in MySQL Server 5.5. (Bug #59224)
MySqlProcedure accepted null arguments as parameters, however the JDBC meta data did not indicate that. (Bug #38367, Bug #11749186)
Using Connector/J to connect from a z/OS machine to a MySQL Server failed when the database name to connect to was included in the connection URL. This was because the name was sent in z/OS default platform encoding, but the MySQL Server expected Latin1.
It should be noted that when connecting from systems that do not use Latin1 as the default platform encoding, the following connection string options can be useful: passwordCharacterEncoding=ASCII and characterEncoding=ASCII. (Bug #18086, Bug #11745647)

D.5.1.4. Changes in MySQL Connector/J 5.1.14 (6th December 2010)

Fixes bugs found since release 5.1.13.

Functionality Added or Changed

Connector/J's load-balancing functionality only allowed the following events to trigger failover:
- Transaction commit/rollback
- CommunicationExceptions
- Matches to user-defined Exceptions using the loadBalanceSQLStateFailover, loadBalanceSQLExceptionSubclassFailover or loadBalanceExceptionChecker property.
This meant that connections where auto-commit was enabled were not balanced, except for Exceptions, and this was problematic in the case of distribution of read-only work across slaves in a replication deployment.
The ability to load-balance while auto-commit is enabled has now been added to Connector/J. This introduces two new properties:
1. loadBalanceAutoCommitStatementThreshold - defines the number of matching statements which will trigger the driver to (potentially) swap physical server connections. The default value (0) retains the previously-established behavior that connections with auto-commit enabled are never balanced.
2. loadBalanceAutoCommitStatementRegex - the regular expression against which statements must match. The default value (blank) matches all statements.
Load-balancing will be done after the statement is executed, before control is returned to the application. If rebalancing fails, the driver will silently swallow the resulting Exception (as the statement itself completed successfully). (Bug #55723)

Bugs Fixed

Connection failover left slave/secondary in read-only mode. Failover attempts between two read-write masters did not properly set this.currentConn.setReadOnly(false). (Bug #58706)
Connector/J mapped both 3-byte and 4-byte UTF8 encodings to the same Java UTF8 encoding.
To use 3-byte UTF8 with Connector/J set characterEncoding=utf8 and set useUnicode=true in the connection string.
To use 4-byte UTF8 with Connector/J configure the MySQL server with character_set_server=utf8mb4. Connector/J will then use that setting as long as characterEncoding has not been set in the connection string. This is equivalent to autodetection of the character set. (Bug #58232)
The CallableStatementRegression test suite failed with a Null Pointer Exception because the OUT parameter in the I__S.PARAMETERS table had no name, that is COLUMN_NAME had the value NULL. (Bug #58232)
DatabaseMetaData.supportsMultipleResultSets() was hard-coded to return false, even though Connector/J supports multiple result sets. (Bug #57380)
Using the useOldUTF8Behavior parameter failed to set the connection character set to latin1 as required.
In versions prior to 5.1.3, the handshake was done using latin1, and while there was logic in place to explicitly set the character set after the handshake was complete, this was bypassed when useOldUTF8Behavior was true. This was not a problem until 5.1.3, when the handshake was modified to use utf8, but the logic continued to allow the character set configured during that handshake process to be retained for later use. As a result, useOldUTF8Behavior effectively failed. (Bug #57262)
Invoking a stored procedure containing output parameters by its full name, where the procedure was located in another database, generated the following exception:
```
Parameter index of 1 is out of range (1, 0)
```
(Bug #57022)
When a JDBC client disconnected from a remote server using Connection.close(), the TCP connection remained in the TIME_WAIT state on the server side, rather than on the client side. (Bug #56979)
Leaving Trust/ClientCertStoreType properties unset caused an exception to be thrown when connecting with useSSL=true, as no default was used. (Bug #56955)
When load-balanced connections swap servers, certain session state was copied from the previously active connection to the newly-selected connection. State synchronized included:
- Auto-commit state
- Transaction isolation state
- Current schema/catalog
However, the read-only state was not synchronized, which caused problems if a write was attempted on a read-only connection. (Bug #56706)
When using Connector/J configured for failover (jdbc:mysql://host1,host2,... URLs), the non-primary servers re-balanced when the transactions on the master were committed or rolled-back. (Bug #56429)
An unhandled Null Pointer Exception (NPE) was generated in DatabaseMetaData.java when calling an incorrectly cased function name where no permission to access mysql.proc was available.
In addition to catching potential NPEs, a guard against calling JDBC functions with db_name.proc_name notation was also added. (Bug #56305)

Attempting to use JDBC4 functions on Connection objects resulted in errors being generated:

Exception in thread "main" java.lang.AbstractMethodError:
com.mysql.jdbc.LoadBalancedMySQLConnection.createBlob()Ljava/sql/Blob;
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at
com.mysql.jdbc.LoadBalancingConnectionProxy.invoke(LoadBalancingConnectionProxy.java:476)
   at $Proxy0.createBlob(Unknown Source)

(Bug #56099)

D.5.1.5. Changes in MySQL Connector/J 5.1.13 (24 June 2010)

Fixes bugs found since release 5.1.12.

Functionality Added or Changed

Connector/J did not support utf8mb4 for servers 5.5.2 and newer.
Connector/J now auto-detects servers configured with character_set_server=utf8mb4 or treats the Java encoding utf-8 passed using characterEncoding=... as utf8mb4 in the SET NAMES= calls it makes when establishing the connection. (Bug #54175)

Bugs Fixed

The method unSafeStatementInterceptors() contained an erroneous line of code, which resulted in the interceptor being called, but the result being thrown away. (Bug #53041)
There was a performance regression of roughly 25% between r906 and r907, which appeared to be caused by pushing the Proxy down to the I/O layer. (Bug #52534)
Logic in implementations of LoadBalancingConnectionProxy and LoadBalanceStrategy behaved differently as to which SQLExceptions trigger failover to a new host. The former looked at the first two characters of the SQLState:
```
if (sqlState.startsWith("08"))
...
```
The latter used a different test:
```
if (sqlEx instanceof CommunicationsException
  || "08S01".equals(sqlEx.getSQLState())) {
...
```
This meant it was possible for a new Connection object to throw an Exception when the first selected host was unavailable. This happened because MySqlIO.createNewIO() could throw an SQLException with a SQLState of “08001”, which did not trigger the “try another host” logic in the LoadBalanceStrategy implementations, so an Exception was thrown after having only attempted connecting to a single host. (Bug #52231)
In the file DatabaseMetadata.java, the function private void getCallStmtParameterTypes failed if the parameter was defined over more than one line by using the '\n' character. (Bug #52167)
The catalog parameter, PARAM_CAT, was not correctly processed when calling for metadata with getMetaData() on stored procedures. This was because PARAM_CAT was hardcoded in the code to NULL. In the case where nullcatalogmeanscurrent was true, which is its default value, a crash did not occur, but the metadata returned was for the stored procedures from the catalog currently attached to. If, however, nullcatalogmeanscurrent was set to false then a crash resulted.
Connector/J has been changed so that when NULL is passed as PARAM_CAT it will not crash when nullcatalogmeanscurrent is false, but rather iterate all catalogs in search of stored procedures. This means that PARAM_CAT is no longer hardcoded to NULL (see Bug #51904). (Bug #51912)
A load balanced Connection object with multiple open underlying physical connections rebalanced on commit(), rollback(), or on a communication exception, without validating the existing connection. This caused a problem when there was no pinging of the physical connections, using queries starting with “/* ping */”, to ensure they remained active. This meant that calls to Connection.commit() could throw a SQLException. This did not occur when the transaction was actually committed; it occurred when the new connection was chosen and the driver attempted to set the auto-commit or transaction isolation state on the newly chosen physical connection. (Bug #51783)
The rollback() method could fail to rethrow a SQLException if the server became unavailable during a rollback. The errant code only rethrew when ignoreNonTxTables was true and the exception did not have the error code 1196, SQLError.ER_WARNING_NOT_COMPLETE_ROLLBACK. (Bug #51776)
When the allowMultiQueries connection string option was set to true, a call to Statement.executeBatch() scanned the query for escape codes, even though setEscapeProcessing(false) had been called previously. (Bug #51704)
When a StatementInterceptor was used and an alternate ResultSet was returned from preProcess(), the original statement was still executed. (Bug #51666)
Objects created by ConnectionImpl, such as prepared statements, hold a reference to the ConnectionImpl that created them. However, when the load balancer picked a new connection, it did not update the reference contained in, for example, the PreparedStatement. This resulted in inserts and updates being directed to invalid connections, while commits were directed to the new connection. This resulted in silent data loss. (Bug #51643)
jdbc:mysql:loadbalance:// would connect to the same host, even though loadBalanceStrategy was set to a value of random, and multiple hosts were specified. (Bug #51266)
An unexpected exception when trying to register OUT parameters in CallableStatement.
Sometimes Connector/J was not able to register OUT parameters for CallableStatements. (Bug #43576)

D.5.1.6. Changes in MySQL Connector/J 5.1.12 (18 February 2010)

Fixes bugs found since release 5.1.11.

Bugs Fixed

The catalog parameter was ignored in the DatabaseMetaData.getProcedure() method. It returned all procedures in all databases. (Bug #51022)
A call to DatabaseMetaData.getDriverVersion() returned the revision as mysql-connector-java-5.1.11 ( Revision: ${svn.Revision} ). The variable ${svn.Revision} was not replaced by the SVN revision number. (Bug #50288)

D.5.1.7. Changes in MySQL Connector/J 5.1.11 (21 January 2010)

Fixes bugs found since release 5.1.10.

Functionality Added or Changed

Replication connections, those with URLs that start with jdbc:mysql:replication, now use a jdbc:mysql:loadbalance connection for the slave pool. This means that it is possible to set load balancing properties such as loadBalanceBlacklistTimeout and loadBalanceStrategy to choose a mechanism for balancing the load, and failover or fault tolerance strategy for the slave pool. (Bug #49537)

Bugs Fixed

NullPointerException sometimes occurred in invalidateCurrentConnection() for load-balanced connections. (Bug #50288)
The deleteRow method caused a full table scan, when using an updatable cursor and a multibyte character set. (Bug #49745)
For pooled connections, Connector/J did not process the session variable time_zone when set using the URL, resulting in incorrect timestamp values being stored. (Bug #49700)
The ExceptionInterceptor class did not provide a Connection context. (Bug #49607)
Ping left closed connections in the liveConnections map, causing subsequent Exceptions when that connection was used. (Bug #48605)

Using MysqlConnectionPoolDataSource with a load-balanced URL generated exceptions of type ClassCastException:

ClassCastException in MysqlConnectionPoolDataSource
Caused by: java.lang.ClassCastException: $Proxy0
   at
com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource.getPooledConnection(MysqlConne
ctionPoolDataSource.java:80)

java.lang.ClassCastException: $Proxy2
 at com.mysql.jdbc.jdbc2.optional.StatementWrapper.executeQuery(StatementWrapper.java:744)

(Bug #48486)

The implementation for load-balanced Connection used a proxy, which delegated method calls, including equals() and hashCode(), to underlying Connection objects. This meant that successive calls to hashCode() on the same object potentially returned different values, if the proxy state had changed such that it was utilizing a different underlying connection. (Bug #48442)
The batch rewrite functionality attempted to identify the start of the VALUES list by looking for “VALUES ” (with trailing space). However, valid MySQL syntax permits VALUES to be followed by whitespace or an opening parenthesis:
```
INSERT INTO tbl VALUES
(1);

INSERT INTO tbl VALUES(1);
```
Queries written with the above formats did not therefore gain the performance benefits of the batch rewrite. (Bug #48172)
A PermGen memory leaked was caused by the Connector/J statement cancellation timer (java.util.Timer). When the application was unloaded the cancellation timer did not terminate, preventing the ClassLoader from being garbage collected. (Bug #36565)
With the connection string option noDatetimeStringSync set to true, and server-side prepared statements enabled, the following exception was generated if an attempt was made to obtain, using ResultSet.getString(), a datetime value containing all zero components:
```
java.sql.SQLException: Value '0000-00-00' can not be represented as java.sql.Date
```
(Bug #32525)

D.5.1.8. Changes in MySQL Connector/J 5.1.10 (23 September 2009)

Fixes bugs found since release 5.1.9.

Bugs Fixed

The DriverManager.getConnection() method ignored a non-standard port if it was specified in the JDBC connection string. Connector/J always used the standard port 3306 for connection creation. For example, if the string was jdbc:mysql://localhost:6777, Connector/J would attempt to connect to port 3306, rather than 6777. (Bug #47494)

D.5.1.9. Changes in MySQL Connector/J 5.1.9 (21 September 2009)

Bugs Fixed

In the class com.mysql.jdbc.jdbc2.optional.SuspendableXAConnection, which is used when pinGlobalTxToPhysicalConnection=true, there is a static map (XIDS_TO_PHYSICAL_CONNECTIONS) that tracks the Xid with the XAConnection, however this map was not populated. The effect was that the SuspendableXAConnection was never pinned to the real XA connection. Instead it created new connections on calls to start, end, resume, and prepare. (Bug #46925)

When using the ON DUPLICATE KEY UPDATE functionality together with the rewriteBatchedStatements option set to true, an exception was generated when trying to execute the prepared statement:

INSERT INTO config_table (modified,id_) VALUES (?,?) ON DUPLICATE KEY UPDATE modified=?

The exception generated was:

java.sql.SQLException: Parameter index out of range (3 > number of parameters, which is
2).
	at com.sag.etl.job.processors.JdbcInsertProcessor.flush(JdbcInsertProcessor.java:135)
......
Caused by: java.sql.SQLException: Parameter index out of range (3 > number of parameters,
which is 2).
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055)
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926)
	at com.mysql.jdbc.PreparedStatement.checkBounds(PreparedStatement.java:3657)
	at com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:3641)
	at
com.mysql.jdbc.PreparedStatement.setBytesNoEscapeNoQuotes(PreparedStatement.java:3391)
	at
com.mysql.jdbc.PreparedStatement.setOneBatchedParameterSet(PreparedStatement.java:4203)
	at com.mysql.jdbc.PreparedStatement.executeBatchedInserts(PreparedStatement.java:1759)
	at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1441)
	at com.sag.etl.job.processors.JdbcInsertProcessor.flush(JdbcInsertProcessor.java:131)
	... 16 more

(Bug #46788)

When Connector/J encountered an error condition that caused it to create a CommunicationsException, it tried to build a friendly error message that helped diagnose what was wrong. However, if there had been no network packets received from the server, the error message contained the following incorrect text:
```
The last packet successfully received from the server was 1,249,932,468,916 milliseconds
ago.  The last packet sent successfully to the server was 0 milliseconds ago.
```
(Bug #46637)
The getSuperTypes method returned a result set with incorrect names for the first two columns. The name of the first column in the result set was expected to be TYPE_CAT and that of the second column TYPE_SCHEM. The method however returned the names as TABLE_CAT and TABLE_SCHEM for first and second column respectively. (Bug #44508)
SQLException for data truncation error gave the error code as 0 instead of 1265. (Bug #44324)
Calling ResultSet.deleteRow() on a table with a primary key of type BINARY(8) silently failed to delete the row, but only in some repeatable cases. The generated DELETE statement generated corrupted part of the primary key data. Specifically, one of the bytes was changed from 0x90 to 0x9D, although the corruption appeared to be different depending on whether the application was run on Windows or Linux. (Bug #43759)
Accessing result set columns by name after the result set had been closed resulted in a NullPointerException instead of a SQLException. (Bug #41484)
QueryTimeout did not work for batch statements waiting on a locked table.
When a batch statement was issued to the server and was forced to wait because of a locked table, Connector/J only terminated the first statement in the batch when the timeout was exceeded, leaving the rest hanging. (Bug #34555)
The parseURL method in class com.mysql.jdbc.Driver did not work as expected. When given a URL such as “jdbc:mysql://www.mysql.com:12345/my_database” to parse, the property PORT_PROPERTY_KEY was found to be null and the HOST_PROPERTY_KEY property was found to be “www.mysql.com:12345”.
Note
Connector/J has been fixed so that it will now always fill in the PORT property (using 3306 if not specified), and the HOST property (using localhost if not specified) when parseURL() is called. The driver also parses a list of hosts into HOST.n and PORT.n properties as well as adding a property NUM_HOSTS for the number of hosts it has found. If a list of hosts is passed to the driver, HOST and PORT will be set to the values given by HOST.1 and PORT.1 respectively. This change has centralized and cleaned up a large section of code used to generate lists of hosts, both for load-balanced and fault tolerant connections and their tests.
(Bug #32216)
Attempting to delete rows using ResultSet.deleteRow() did not delete rows correctly. (Bug #27431)
The setDate method silently ignored the Calendar parameter. The code was implemented as follows:
```
public void setDate(int parameterIndex, java.sql.Date x, Calendar cal) throws SQLException {
   setDate(parameterIndex, x);
}        
      
```
From reviewing the code it was apparent that the Calendar parameter cal was ignored. (Bug #23584)

D.5.1.10. Changes in MySQL Connector/J 5.1.8 (16 July 2009)

Bugs Fixed

The reported milliseconds since the last server packets were received/sent was incorrect by a factor of 1000. For example, the following method call:

SQLError.createLinkFailureMessageBasedOnHeuristics(
(ConnectionImpl) this.conn, 
System.currentTimeMillis() - 1000,
System.currentTimeMillis() - 2000,
e, 
false);

returned the following string:

The last packet successfully received from the server 
was 2 milliseconds ago. The last packet sent successfully to the 
server was 1 milliseconds ago.

(Bug #45419)

Calling Connection.serverPrepareStatement() variants that do not take result set type or concurrency arguments returned statements that produced result sets with incorrect defaults, namely TYPE_SCROLL_SENSITIVE. (Bug #45171)
The result set returned by getIndexInfo() did not have the format defined in the JDBC API specifications. The fourth column, DATA_TYPE, of the result set should be of type BOOLEAN. Connector/J however returns CHAR. (Bug #44869)
The result set returned by getTypeInfo() did not have the format defined in the JDBC API specifications. The second column, DATA_TYPE, of the result set should be of type INTEGER. Connector/J however returns SMALLINT. (Bug #44868)
The DEFERRABILITY column in database metadata result sets was expected to be of type SHORT. However, Connector/J returned it as INTEGER.
This affected the following methods: getImportedKeys(), getExportedKeys(), getCrossReference(). (Bug #44867)
The result set returned by getColumns() did not have the format defined in the JDBC API specifications. The fifth column, DATA_TYPE, of the result set should be of type INTEGER. Connector/J however returns SMALLINT. (Bug #44865)
The result set returned by getVersionColumns() did not have the format defined in the JDBC API specifications. The third column, DATA_TYPE, of the result set should be of type INTEGER. Connector/J however returns SMALLINT. (Bug #44863)
The result set returned by getBestRowIdentifier() did not have the format defined in the JDBC API specifications. The third column, DATA_TYPE, of the result set should be of type INTEGER. Connector/J however returns SMALLINT. (Bug #44862)

Connector/J contains logic to generate a message text specifically for streaming result sets when there are CommunicationsException exceptions generated. However, this code was never reached.

In the CommunicationsException code:

private boolean streamingResultSetInPlay = false;

public CommunicationsException(ConnectionImpl conn, long lastPacketSentTimeMs,
long lastPacketReceivedTimeMs, Exception underlyingException) {

this.exceptionMessage = SQLError.createLinkFailureMessageBasedOnHeuristics(conn,
      lastPacketSentTimeMs, lastPacketReceivedTimeMs, underlyingException,
      this.streamingResultSetInPlay);

streamingResultSetInPlay was always false, which in the following code in SQLError.createLinkFailureMessageBasedOnHeuristics() never being executed:

if (streamingResultSetInPlay) {
    exceptionMessageBuf.append(
    Messages.getString("CommunicationsException.ClientWasStreaming")); //$NON-NLS-1$
} else {
...

(Bug #44588)

The SQLError.createLinkFailureMessageBasedOnHeuristics() method created a message text for communication link failures. When certain conditions were met, this message included both “last packet sent” and “last packet received” information, but when those conditions were not met, only “last packet sent” information was provided.
Information about when the last packet was successfully received should be provided in all cases. (Bug #44587)
Statement.getGeneratedKeys() retained result set instances until the statement was closed. This caused memory leaks for long-lived statements, or statements used in tight loops. (Bug #44056)

Using useInformationSchema with DatabaseMetaData.getExportedKeys() generated the following exception:

com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException: Column
'REFERENCED_TABLE_NAME' in where clause is ambiguous
...
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1772)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1923)
at
com.mysql.jdbc.DatabaseMetaDataUsingInfoSchema.executeMetadataQuery(
DatabaseMetaDataUsingInfoSchema.java:50)
at
com.mysql.jdbc.DatabaseMetaDataUsingInfoSchema.getExportedKeys(
DatabaseMetaDataUsingInfoSchema.java:603)

(Bug #43714)

LoadBalancingConnectionProxy.doPing() did not have blacklist awareness.
LoadBalancingConnectionProxy implemented doPing() to ping all underlying connections, but it threw any exceptions it encountered during this process.
With the global blacklist enabled, it catches these exceptions, adds the host to the global blacklist, and only throws an exception if all hosts are down. (Bug #43421)
The method Statement.getGeneratedKeys() did not return values for UNSIGNED BIGINTS with values greater than Long.MAX_VALUE.
Unfortunately, because the server does not tell clients what TYPE the auto increment value is, the driver cannot consistently return BigIntegers for the result set returned from getGeneratedKeys(), it will only return them if the value is greater than Long.MAX_VALUE. If your application needs this consistency, it will need to check the class of the return value from .getObject() on the ResultSet returned by Statement.getGeneratedKeys() and if it is not a BigInteger, create one based on the java.lang.Long that is returned. (Bug #43196)
When the MySQL Server was upgraded from 4.0 to 5.0, the Connector/J application then failed to connect to the server. This was because authentication failed when the application ran from EBCDIC platforms such as z/OS. (Bug #43071)
When connecting with traceProtocol=true, no trace data was generated for the server greeting or login request. (Bug #43070)

Connector/J generated an unhandled StringIndexOutOfBoundsException:

java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1938)
at com.mysql.jdbc.EscapeProcessor.processTimeToken(EscapeProcessor.java:353)
at com.mysql.jdbc.EscapeProcessor.escapeSQL(EscapeProcessor.java:257)
at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1546)
at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1524)

(Bug #42253)

A ConcurrentModificationException was generated in LoadBalancingConnectionProxy:

java.util.ConcurrentModificationException
 at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
 at java.util.HashMap$KeyIterator.next(Unknown Source)
 at
com.mysql.jdbc.LoadBalancingConnectionProxy.getGlobalBlacklist(LoadBalancingConnectionProxy.java:520)
 at com.mysql.jdbc.RandomBalanceStrategy.pickConnection(RandomBalanceStrategy.java:55)
 at
com.mysql.jdbc.LoadBalancingConnectionProxy.pickNewConnection(LoadBalancingConnectionProxy.java:414)
 at
com.mysql.jdbc.LoadBalancingConnectionProxy.invoke(LoadBalancingConnectionProxy.java:390)

(Bug #42055)

SQL injection was possible when using a string containing U+00A5 in a client-side prepared statement, and the character set being used was SJIS/Windows-31J. (Bug #41730)
If there was an apostrophe in a comment in a statement that was being sent through Connector/J, the apostrophe was still recognized as a quote and put the state machine in EscapeTokenizer into the inQuotes state. This led to further parse errors.
For example, consider the following statement:
```
String sql = "-- Customer's zip code will be fixed\n" +
  "update address set zip_code = 99999\n" +
  "where not regexp '^[0-9]{5}([[.-.]])?([0-9]{4})?$'";
```
When passed through Connector/J, the EscapeTokenizer did not recognize that the first apostrophe was in a comment and thus set inQuotes to true. When that happened, the quote count was incorrect and thus the regular expression did not appear to be in quotation marks. With the parser not detecting that the regular expression was in quotation marks, the curly braces were recognized as escape sequences and were removed from the regular expression, breaking it. The server thus received SQL such as:
```
-- Customer's zip code will be fixed
update address set zip_code = '99999'
where not regexp '^[0-9]([[.-.]])?([0-9])?$'
```
(Bug #41566)
MySQL Connector/J 5.1.7 was slower than previous versions when the rewriteBatchedStatements option was set to true.
Note
The performance regression in indexOfIgnoreCaseRespectMarker()has been fixed. It has also been made possible for the driver to rewrite INSERT statements with ON DUPLICATE KEY UPDATE clauses in them, as long as the UPDATE clause contains no reference to LAST_INSERT_ID(), as that would cause the driver to return bogus values for getGeneratedKeys() invocations. This has resulted in improved performance over version 5.1.7.
(Bug #41532)

When accessing a result set column by name using ResultSetImpl.findColumn() an exception was generated:

java.lang.NullPointerException
at com.mysql.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1103)
at com.mysql.jdbc.ResultSetImpl.getShort(ResultSetImpl.java:5415)
at org.apache.commons.dbcp.DelegatingResultSet.getShort(DelegatingResultSet.java:219)
at com.zimbra.cs.db.DbVolume.constructVolume(DbVolume.java:297)
at com.zimbra.cs.db.DbVolume.get(DbVolume.java:197)
at com.zimbra.cs.db.DbVolume.create(DbVolume.java:95)
at com.zimbra.cs.store.Volume.create(Volume.java:227)
at com.zimbra.cs.store.Volume.create(Volume.java:189)
at com.zimbra.cs.service.admin.CreateVolume.handle(CreateVolume.java:48)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:428)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:285)

(Bug #41484)

The RETURN_GENERATED_KEYS flag was being ignored. For example, in the following code the RETURN_GENERATED_KEYS flag was ignored:
```
PreparedStatement ps = connection.prepareStatement("INSERT INTO table
  values(?,?)",PreparedStatement.RETURN_GENERATED_KEYS);
```
(Bug #41448)
When using Connector/J 5.1.7 to connect to MySQL Server 4.1.18 the following error message was generated:
```
Thu Dec 11 17:38:21 PST 2008 WARN: Invalid value {1} for server variable named {0},
falling back to sane default of {2}
```
This occurred with MySQL Server version that did not support auto_increment_increment. The error message should not have been generated. (Bug #41416)
When DatabaseMetaData.getProcedureColumns() was called, the value for LENGTH was always returned as 65535, regardless of the column type (fixed or variable) or the actual length of the column.
However, if you obtained the PRECISION value, this was correct for both fixed and variable length columns. (Bug #41269)
PreparedStatement.addBatch() did not check for all parameters being set, which led to inconsistent behavior in executeBatch(), especially when rewriting batched statements into multi-value INSERTs. (Bug #41161)

Error message strings contained variable values that were not expanded. For example:

Mon Nov 17 11:43:18 JST 2008 WARN: Invalid value {1} for server variable named {0},
falling back to sane default of {2}

(Bug #40772)

When using rewriteBatchedStatements=true with:

INSERT INTO table_name_values (...) VALUES (...)

Query rewriting failed because “values” at the end of the table name was mistaken for the reserved keyword. The error generated was as follows:

testBug40439(testsuite.simple.TestBug40439)java.sql.BatchUpdateException: You have an
error in your SQL syntax; check the manual that corresponds to your MySQL server version
for the right syntax to use near 'values (2,'toto',2),(id,data, ordr) values
(3,'toto',3),(id,data, ordr) values (' at line 1
at com.mysql.jdbc.PreparedStatement.executeBatchedInserts(PreparedStatement.java:1495)
at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1097)
at testsuite.simple.TestBug40439.testBug40439(TestBug40439.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at testsuite.simple.TestBug40439.main(TestBug40439.java:57)

(Bug #40439)

A statement interceptor received the incorrect parameters when used with a batched statement. (Bug #39426)
Using Connector/J 5.1.6 the method ResultSet.getObject returned a BYTE[] for following:
```
SELECT TRIM(rowid) FROM tbl
```
Where rowid had a type of INT(11) PRIMARY KEY AUTO_INCREMENT.
The expected return type was one of CHAR, VARCHAR, CLOB, however, a BYTE[] was returned.
Further, adding functionsNeverReturnBlobs=true to the connection string did not have any effect on the return type. (Bug #38387)

D.5.1.11. Changes in MySQL Connector/J 5.1.7 (21 October 2008)

Functionality Added or Changed

When statements include ON DUPLICATE UPDATE, and rewriteBatchedStatements is set to true, batched statements are not rewritten into the form INSERT INTO table VALUES (), (), (), instead the statements are executed sequentially.

Bugs Fixed

Statement.getGeneratedKeys() returned two keys when using ON DUPLICATE KEY UPDATE and the row was updated, not inserted. (Bug #42309)
When using the replication driver with autoReconnect=true, Connector/J checks in PreparedStatement.execute (also called by CallableStatement.execute) to determine if the first character of the statement is an “S”, in an attempt to block all statements that are not read-only-safe, for example non-SELECT statements. However, this also blocked CALLs to stored procedures, even if the stored procedures were defined as SQL READ DATA or NO SQL. (Bug #40031)
With large result sets ResultSet.findColumn became a performance bottleneck. (Bug #39962)
Connector/J ignored the value of the MySQL Server variable auto_increment_increment. (Bug #39956)
Connector/J failed to parse TIMESTAMP strings for nanos correctly. (Bug #39911)
When the LoadBalancingConnectionProxy handles a SQLException with SQL state starting with “08”, it calls invalidateCurrentConnection, which in turn removes that Connection from liveConnections and the connectionsToHostsMap, but it did not add the host to the new global blacklist, if the global blacklist was enabled.
There was also the possibility of a NullPointerException when trying to update stats, where connectionsToHostsMap.get(this.currentConn) was called:
```
int hostIndex = ((Integer) this.hostsToListIndexMap.get(this.connectionsToHostsMap.get(this.currentConn))).intValue();
```
This could happen if a client tried to issue a rollback after catching a SQLException caused by a connection failure. (Bug #39784)
When configuring the Java Replication Driver the last slave specified was never used. (Bug #39611)
When an INSERT ON DUPLICATE KEY UPDATE was performed, and the key already existed, the affected-rows value was returned as 1 instead of 0. (Bug #39352)
When using the random load balancing strategy and starting with two servers that were both unavailable, an IndexOutOfBoundsException was generated when removing a server from the whiteList. (Bug #38782)

Connector/J threw the following exception when using a read-only connection:

java.sql.SQLException: Connection is read-only. Queries leading to data
modification are not allowed.

(Bug #38747)

Connector/J was unable to connect when using a non-latin1 password. (Bug #37570)
The useOldAliasMetadataBehavior connection property was ignored. (Bug #35753)
Incorrect result is returned from isAfterLast() in streaming ResultSet when using setFetchSize(Integer.MIN_VALUE). (Bug #35170)
When getGeneratedKeys() was called on a statement that had not been created with RETURN_GENERATED_KEYS, no exception was thrown, and batched executions then returned erroneous values. (Bug #34185)
The loadBalance bestResponseTime blacklists did not have a global state. (Bug #33861)

D.5.1.12. Changes in MySQL Connector/J 5.1.6 (07 March 2008)

Functionality Added or Changed

Multiple result sets were not supported when using streaming mode to return data. Both normal statements and the resul sets from stored procedures now return multiple results sets, with the exception of result sets using registered OUTPUT parameters. (Bug #33678)
XAConnections and datasources have been updated to the JDBC-4.0 standard.
The profiler event handling has been made extensible using the profilerEventHandler connection property.
Add the verifyServerCertificate property. 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 nonverifying trust store and the "default" key store.

Bugs Fixed

DatabaseMetaData.getColumns() returns incorrect COLUMN_SIZE value for SET column. (Bug #36830)
When trying to read Time values like “00:00:00” with ResultSet.getTime(int) an exception is thrown. (Bug #36051)
JDBC connection URL parameters is ignored when using MysqlConnectionPoolDataSource. (Bug #35810)
When useServerPrepStmts=true and slow query logging is enabled, the connector throws a NullPointerException when it encounters a slow query. (Bug #35666)
When using the keyword “loadbalance” in the connection string and trying to perform load balancing between two databases, the driver appears to hang. (Bug #35660)
JDBC data type getter method was changed to accept only column name, whereas previously it accepted column label. (Bug #35610)
Prepared statements from pooled connections caused a NullPointerException when closed() under JDBC-4.0. (Bug #35489)
In calling a stored function returning a bigint, an exception is encountered beginning:
```
java.sql.SQLException: java.lang.NumberFormatException: For input string:
```
followed by the text of the stored function starting after the argument list. (Bug #35199)
The JDBC driver uses a different method for evaluating column names in resultsetmetadata.getColumnName() and when looking for a column in resultset.getObject(columnName). This causes Hibernate to fail in queries where the two methods yield different results, for example in queries that use alias names:
```
SELECT column AS aliasName from table
```
(Bug #35150)
MysqlConnectionPoolDataSource does not support ReplicationConnection. Notice that we implemented com.mysql.jdbc.Connection for ReplicationConnection, however, only accessors from ConnectionProperties are implemented (not the mutators), and they return values from the currently active connection. All other methods from com.mysql.jdbc.Connection are implemented, and operate on the currently active connection, with the exception of resetServerState() and changeUser(). (Bug #34937)
ResultSet.getTimestamp() returns incorrect values for month/day of TIMESTAMPs when using server-side prepared statements (not enabled by default). (Bug #34913)
RowDataStatic doesn't always set the metadata in ResultSetRow, which can lead to failures when unpacking DATE, TIME, DATETIME and TIMESTAMP types when using absolute, relative, and previous result set navigation methods. (Bug #34762)
When calling isValid() on an active connection, if the timeout is nonzero then the Connection is invalidated even if the Connection is valid. (Bug #34703)
It was not possible to truncate a BLOB using Blog.truncate() when using 0 as an argument. (Bug #34677)
When using a cursor fetch for a statement, the internal prepared statement could cause a memory leak until the connection was closed. The internal prepared statement is now deleted when the corresponding result set is closed. (Bug #34518)
When retrieving the column type name of a geometry field, the driver would return UNKNOWN instead of GEOMETRY. (Bug #34194)
Statements with batched values do not return correct values for getGeneratedKeys() when rewriteBatchedStatements is set to true, and the statement has an ON DUPLICATE KEY UPDATE clause. (Bug #34093)
The internal class ResultSetInternalMethods referenced the nonpublic class com.mysql.jdbc.CachedResultSetMetaData. (Bug #33823)
A NullPointerException could be raised when using client-side prepared statements and enabled the prepared statement cache using the cachePrepStmts. (Bug #33734)
Using server side cursors and cursor fetch, the table metadata information would return the data type name instead of the column name. (Bug #33594)
ResultSet.getTimestamp() would throw a NullPointerException instead of a SQLException when called on an empty ResultSet. (Bug #33162)
Load balancing connection using best response time would incorrectly "stick" to hosts that were down when the connection was first created.
We solve this problem with a black list that is used during the picking of new hosts. If the black list ends up including all configured hosts, the driver will retry for a configurable number of times (the retriesAllDown configuration property, with a default of 120 times), sleeping 250ms between attempts to pick a new connection.
We've also went ahead and made the balancing strategy extensible. To create a new strategy, implement the interface com.mysql.jdbc.BalanceStrategy (which also includes our standard "extension" interface), and tell the driver to use it by passing in the class name using the loadBalanceStrategy configuration property. (Bug #32877)
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" (that is, 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)
Retrieving the server version information for an active connection could return invalid information if the default character encoding on the host was not ASCII compatible. (Bug #31192)
Further fixes have been made to this bug in the event that a node is nonresponsive. Connector/J will now try a different random node instead of waiting for the node to recover before continuing. (Bug #31053)
ResultSet returned by Statement.getGeneratedKeys() is not closed automatically when statement that created it is closed. (Bug #30508)
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.

D.5.1.13. Changes in MySQL Connector/J 5.1.5 (09 October 2007)

New Features, 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 using SHOW PROCESSLIST on a MySQL server, or can be extended to support custom persistence of the information using a public interface).
Support for JDBC-4.0 XML processing using 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)
When calling setTimestamp on a prepared statement, the timezone information stored in the calendar object was ignored. This resulted in the incorrect DATETIME information being stored. The following example illustrates this:
```
Timestamp t = new Timestamp( cal.getTimeInMillis() );
ps.setTimestamp( N, t, cal );
```
(Bug #15604)

D.5.1.14. Changes in MySQL Connector/J 5.1.4 (Not Released)

Only released internally.

This section has no changelog entries.

D.5.1.15. Changes in MySQL Connector/J 5.1.3 (10 September 2007)

New Features, 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 using SHOW PROCESSLIST on a MySQL server, or can be extended to support custom persistence of the information using a public interface).
Support for JDBC-4.0 XML processing using 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 permit 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 is stored) for ResultSet rows are now behind an interface which enables 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" through 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 through 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 using 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.regexpackage. 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 PreparedStatementWrapper 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 using 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 to 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 permit 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.

D.5.1.16. 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 (that is, without SELECT or ON DUPLICATE KEY UPDATE clauses) INSERT or REPLACE statements.

D.5.1.17. 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 pluggability 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 is stored) for ResultSet rows are now behind an interface which enables 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" through 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.

D.5.1.18. 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 using 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.

D.5.2. Changes in MySQL Connector/J 5.0.x

D.5.2.1. Changes in MySQL Connector/J 5.0.8 (09 October 2007)
D.5.2.2. Changes in MySQL Connector/J 5.0.7 (20 July 2007)
D.5.2.3. Changes in MySQL Connector/J 5.0.6 (15 May 2007)
D.5.2.4. Changes in MySQL Connector/J 5.0.5 (02 March 2007)
D.5.2.5. Changes in MySQL Connector/J 5.0.4 (20 October 2006)
D.5.2.6. Changes in MySQL Connector/J 5.0.3 (26 July 2006 beta)
D.5.2.7. Changes in MySQL Connector/J 5.0.2 (11 July 2006)
D.5.2.8. Changes in MySQL Connector/J 5.0.1 (Not Released)
D.5.2.9. Changes in MySQL Connector/J 5.0.0 (22 December 2005)

D.5.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 is 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 PreparedStatementWrapper 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 using 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 to 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 permit 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 using 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 using 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.

D.5.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 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 nonzero 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 enable 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 enable 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 is 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 SELECTs for executeUpdate() in plain and prepared statements to be aware of the same types of comments. (Bug #28469)

D.5.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 with 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)

D.5.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 nonserver-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 is now configurable using logXaCommands property (defaults to false).
Added configuration property localSocketAddress, which is the host name 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 is 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 using 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 using 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. This occurred 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 underlying 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 enables 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.

D.5.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 using 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-to-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).

D.5.2.6. Changes in MySQL Connector/J 5.0.3 (26 July 2006 beta)

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

D.5.2.7. Changes in MySQL Connector/J 5.0.2 (11 July 2006)

Bugs Fixed

MysqlXaConnection.recover(int flags) now permits 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 enables 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 system 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)

D.5.2.8. Changes in MySQL Connector/J 5.0.1 (Not Released)

Not released due to a packaging error

This section has no changelog entries.

D.5.2.9. Changes in MySQL Connector/J 5.0.0 (22 December 2005)

Bugs Fixed

Added support for Connector/MXJ integration using 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 permits 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 using 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 is 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 ...}").
Do not permit .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 is 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).

D.5.3. Changes in MySQL Connector/J 3.1.x

D.5.3.1. Changes in MySQL Connector/J 3.1.15 (Not yet released)
D.5.3.2. Changes in MySQL Connector/J 3.1.14 (19 October 2006)
D.5.3.3. Changes in MySQL Connector/J 3.1.13 (26 May 2006)
D.5.3.4. Changes in MySQL Connector/J 3.1.12 (30 November 2005)
D.5.3.5. Changes in MySQL Connector/J 3.1.11 (07 October 2005)
D.5.3.6. Changes in MySQL Connector/J 3.1.10 (23 June 2005)
D.5.3.7. Changes in MySQL Connector/J 3.1.9 (22 June 2005)
D.5.3.8. Changes in MySQL Connector/J 3.1.8 (14 April 2005)
D.5.3.9. Changes in MySQL Connector/J 3.1.7 (18 February 2005)
D.5.3.10. Changes in MySQL Connector/J 3.1.6 (23 December 2004)
D.5.3.11. Changes in MySQL Connector/J 3.1.5 (02 December 2004)
D.5.3.12. Changes in MySQL Connector/J 3.1.4 (04 September 2004)
D.5.3.13. Changes in MySQL Connector/J 3.1.3 (07 July 2004)
D.5.3.14. Changes in MySQL Connector/J 3.1.2 (09 June 2004)
D.5.3.15. Changes in MySQL Connector/J 3.1.1 (14 February 2004 alpha)
D.5.3.16. Changes in MySQL Connector/J 3.1.0 (18 February 2003 alpha)

D.5.3.1. Changes in MySQL Connector/J 3.1.15 (Not yet released)

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)

D.5.3.2. Changes in MySQL Connector/J 3.1.14 (19 October 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 is required to check this property. (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 quotation marks 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)
DatabaseMetaData.getTables() or getColumns() with a bad catalog parameter threw an exception rather than return an empty result set (as required by the specification). (Bug #18258)
Fixed memory leak with profileSQL=true. (Bug #16987)
Fixed NullPointerException in MysqlDataSourceFactory due to Reference containing RefAddrs with null content. (Bug #16791)

D.5.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 using 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 the log class name if it cannot be found as specified. This enables 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)

D.5.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).
Do not permit 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.

D.5.3.5. Changes in MySQL Connector/J 3.1.11 (07 October 2005)

Bugs Fixed

The configuration property sessionVariables now permits you to specify variables that start with the “@” sign. (Bug #13453)
URL configuration parameters do not permit “&” 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 using .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 is not technically permitted by the JDBC specification, but we have historically permitted 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 is 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 is 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 is 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 quotation marks 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 quotation marks. (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)

D.5.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().

D.5.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 using 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 data type 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 SHORTs. (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 quotation marks not recognized when parsing client-side prepared statements. (Bug #10155)
Made JDBC2-compliant wrappers public to enable 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.

D.5.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 is 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)
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, using 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 is available,
2. Then JDK1.4 logging,
3. Then fallback to our STDERR logging.
(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 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 nonstring 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 BLOBs 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 file systems. (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.

D.5.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 nonrounding 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 using 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 nonwell-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)

D.5.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.

D.5.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 using 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 nonnumeric 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.

D.5.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 is 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 retrieving 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 primitives if a previous null was returned. (Bug #4689)
Optimized integer number parsing, enable “old” slower integer parsing using JDK classes using 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)

D.5.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 debugging 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.

D.5.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 using 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.

D.5.3.15. Changes in MySQL Connector/J 3.1.1 (14 February 2004 alpha)

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 through 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 data type 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 discrepencies 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 data type 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.

D.5.3.16. Changes in MySQL Connector/J 3.1.0 (18 February 2003 alpha)

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

D.5.4. Changes in MySQL Connector/J 3.0.x

D.5.4.1. Changes in MySQL Connector/J 3.0.17 (23 June 2005)
D.5.4.2. Changes in MySQL Connector/J 3.0.16 (15 November 2004)
D.5.4.3. Changes in MySQL Connector/J 3.0.15 (04 September 2004)
D.5.4.4. Changes in MySQL Connector/J 3.0.14 (28 May 2004)
D.5.4.5. Changes in MySQL Connector/J 3.0.13 (27 May 2004)
D.5.4.6. Changes in MySQL Connector/J 3.0.12 (18 May 2004)
D.5.4.7. Changes in MySQL Connector/J 3.0.11 (19 February 2004)
D.5.4.8. Changes in MySQL Connector/J 3.0.10 (13 January 2004)
D.5.4.9. Changes in MySQL Connector/J 3.0.9 (07 October 2003)
D.5.4.10. Changes in MySQL Connector/J 3.0.8 (23 May 2003)
D.5.4.11. Changes in MySQL Connector/J 3.0.7 (08 April 2003)
D.5.4.12. Changes in MySQL Connector/J 3.0.6 (18 February 2003)
D.5.4.13. Changes in MySQL Connector/J 3.0.5 (22 January 2003)
D.5.4.14. Changes in MySQL Connector/J 3.0.4 (06 January 2003)
D.5.4.15. Changes in MySQL Connector/J 3.0.3 (17 December 2002)
D.5.4.16. Changes in MySQL Connector/J 3.0.2 (08 November 2002)
D.5.4.17. Changes in MySQL Connector/J 3.0.1 (21 September 2002)
D.5.4.18. Changes in MySQL Connector/J 3.0.0 (31 July 2002)

D.5.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)

D.5.4.2. Changes in MySQL Connector/J 3.0.16 (15 November 2004)

Bugs Fixed

Made TINYINT(1) -> BIT/Boolean conversion configurable using 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, nonnegative) 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 nonwritable 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 or Connection.changeUser() when connected to MySQL-4.1 or newer.

D.5.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 nonnumeric types (should return max length in chars for nonbinary 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)

D.5.4.4. Changes in MySQL Connector/J 3.0.14 (28 May 2004)

Bugs Fixed

Fixed URL parsing error.

D.5.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)

D.5.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 enable 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 enable any charset to be returned to the driver for result sets. (Bug #2670)
Don't truncate BLOB or CLOB values when using setBytes() and 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 permit 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 enable the user to configure the state of the 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 enable clients of MysqlConnectionPoolDataSource to reset server state on getConnection() on a pooled connection.

D.5.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 using the characterEncoding property. Previously, only the Java-style encoding name of utf-8 would trigger this.

D.5.4.8. Changes in MySQL Connector/J 3.0.10 (13 January 2004)

Bugs Fixed

Enable caching of the parsing stage of prepared statements using 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)

D.5.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 outstanding 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 nonescaped input. (Bug #879)
When emptying input stream of unused rows for “streaming” result sets, have the current thread yield() every 100 rows to not monopolize CPU time. (Bug #879)
Issue exception on ResultSet.getXXX() 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 getXXX() when on insert row. (Bug #675)
Support InnoDB constraint 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().

D.5.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 file names 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().

D.5.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).

D.5.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 permitted 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).

D.5.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.

D.5.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 enable 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.

D.5.4.15. Changes in MySQL Connector/J 3.0.3 (17 December 2002)

Bugs Fixed

Allow user to alter behavior of Statement/ PreparedStatement.executeBatch() using continueBatchOnError property (defaults to true).
More robust escape tokenizer: Recognize -- comments, and permit 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 nonstatic.
Use nonaliased 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 permit 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.

D.5.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 enables 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 enables 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, 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 using 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 enables 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().

D.5.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(), PreparedStatement.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 host names, ports, or user names), as well as clearing “sensitive” data structures when possible.

D.5.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 using 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 enhancements: Driver is now 50–100% faster in most situations, and creates fewer temporary objects.

D.5.5. Changes in MySQL Connector/J 2.0.x

D.5.5.1. Changes in MySQL Connector/J 2.0.14 (16 May 2002)
D.5.5.2. Changes in MySQL Connector/J 2.0.13 (24 April 2002)
D.5.5.3. Changes in MySQL Connector/J 2.0.12 (07 April 2002)
D.5.5.4. Changes in MySQL Connector/J 2.0.11 (27 January 2002)
D.5.5.5. Changes in MySQL Connector/J 2.0.10 (24 January 2002)
D.5.5.6. Changes in MySQL Connector/J 2.0.9 (13 January 2002)
D.5.5.7. Changes in MySQL Connector/J 2.0.8 (25 November 2001)
D.5.5.8. Changes in MySQL Connector/J 2.0.7 (24 October 2001)
D.5.5.9. Changes in MySQL Connector/J 2.0.6 (16 June 2001)
D.5.5.10. Changes in MySQL Connector/J 2.0.5 (13 June 2001)
D.5.5.11. Changes in MySQL Connector/J 2.0.3 (03 December 2000)
D.5.5.12. Changes in MySQL Connector/J 2.0.1 (06 April 2000)
D.5.5.13. Changes in MySQL Connector/J 2.0.0pre5 (21 February 2000)
D.5.5.14. Changes in MySQL Connector/J 2.0.0pre4 (10 January 2000)
D.5.5.15. Changes in MySQL Connector/J 2.0.0pre (17 August 1999)

D.5.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.

D.5.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.

D.5.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.

D.5.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.

D.5.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).

D.5.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).

D.5.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).

D.5.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 available). (thanks to Dmitry Vereshchagin)
Fixed PreparedStatement generating SQL that would end up with syntax errors for some queries.
PreparedStatement.setCharacterStream() now implemented
Capitalize type names when capitalizeTypeNames=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.

D.5.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.

D.5.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.

D.5.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 enable (broken) Macromedia UltraDev to use the driver.
Implemented getBigDecimal() without scale component for JDBC2.

D.5.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.

D.5.5.13. Changes in MySQL Connector/J 2.0.0pre5 (21 February 2000)

Fixed Bad Handshake problem.

D.5.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.

D.5.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)

D.5.6. Changes in MySQL Connector/J 1.2.x and lower

D.5.6.1. Changes in MySQL Connector/J 1.2b (04 July 1999)
D.5.6.2. Changes in MySQL Connector/J 1.2a (14 April 1999)
D.5.6.3. Changes in MySQL Connector/J 1.1i (24 March 1999)
D.5.6.4. Changes in MySQL Connector/J 1.1h (08 March 1999)
D.5.6.5. Changes in MySQL Connector/J 1.1g (19 February 1999)
D.5.6.6. Changes in MySQL Connector/J 1.1f (31 December 1998)
D.5.6.7. Changes in MySQL Connector/J 1.1b (03 November 1998)
D.5.6.8. Changes in MySQL Connector/J 1.1 (02 September 1998)
D.5.6.9. Changes in MySQL Connector/J 1.0 (24 August 1998)
D.5.6.10. Changes in MySQL Connector/J 0.9d (04 August 1998)
D.5.6.11. Changes in MySQL Connector/J 0.9 (28 July 1998)
D.5.6.12. Changes in MySQL Connector/J 0.8 (06 July 1998)
D.5.6.13. Changes in MySQL Connector/J 0.7 (01 July 1998)
D.5.6.14. Changes in MySQL Connector/J 0.6 (21 May 1998)

D.5.6.1. Changes in MySQL Connector/J 1.2b (04 July 1999)

Better Documentation (in progress), in doc/mm.doc/book1.html
DBMD now permits 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 quotation marks 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 do not.
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 quotation marks.

D.5.6.2. 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)

D.5.6.3. 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!)

D.5.6.4. 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)

D.5.6.5. Changes in MySQL Connector/J 1.1g (19 February 1999)

Result set rows are now byte arrays. Blobs and Unicode work bidirectonally 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().

D.5.6.6. 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 using 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)

D.5.6.7. 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.

D.5.6.8. 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 using 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 using "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.

D.5.6.9. 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 LGPL

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

D.5.6.10. 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.

D.5.6.11. 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 enables 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.

D.5.6.12. 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.

D.5.6.13. 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.

D.5.6.14. 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()

D.6. MySQL Connector/MXJ Change History

D.6.1. Changes in MySQL Connector/MXJ 5.0.12 (07 July 2011)
D.6.2. Changes in MySQL Connector/MXJ 5.0.11 (24 November 2009)
D.6.3. Changes in MySQL Connector/MXJ 5.0.10 (Not released)
D.6.4. Changes in MySQL Connector/MXJ 5.0.9 (19 August 2008)
D.6.5. Changes in MySQL Connector/MXJ 5.0.8 (06 August 2007)
D.6.6. Changes in MySQL Connector/MXJ 5.0.7 (27 May 2007)
D.6.7. Changes in MySQL Connector/MXJ 5.0.6 (04 May 2007)
D.6.8. Changes in MySQL Connector/MXJ 5.0.5 (14 March 2007)
D.6.9. Changes in MySQL Connector/MXJ 5.0.4 (28 January 2007)
D.6.10. Changes in MySQL Connector/MXJ 5.0.3 (24 June 2006)
D.6.11. Changes in MySQL Connector/MXJ 5.0.2 (15 June 2006)
D.6.12. Changes in MySQL Connector/MXJ 5.0.1 (Not released)
D.6.13. Changes in MySQL Connector/MXJ 5.0.0 (09 December 2005)

D.6.1. Changes in MySQL Connector/MXJ 5.0.12 (07 July 2011)

Functionality Added or Changed

Incompatible Change: Connector/MXJ now contains MySQL 5.5.9, not MySQL 5.1.
These platform mappings were added:
- Windows_Vista-amd64=Win-x86
- Windows_2003-amd64=Win-x86
- Windows_2000-amd64=Win-x86
- FreeBSD-i386=FreeBSD-x86

D.6.2. Changes in MySQL Connector/MXJ 5.0.11 (24 November 2009)

Functionality Added or Changed

The embedded MySQL binaries have been updated to MySQL 5.1.40 for GPL releases and MySQL 5.1.40 for Commercial releases.
The contents of the directory used for bootstrapping the MySQL databases is now configurable by using the windows-share-dir-jar property. You should supply the name of a jar containing the files you want to use.
The embedded Aspect/J class has been removed.
The default timeout for the kill delay within the embedded test suite has been increased from 10 to 30 seconds.

Bugs Fixed

On startup Connector/MXJ generated an exception on Windows 7:

Exception in thread “Thread-3” java.util.MissingResourceException?: Resource
‘5-0-51a/Windows_7-x86/mysqld-nt.exe’ not found
at com.mysql.management.util.Streams.getResourceAsStream(Streams.java:133)
at com.mysql.management.util.Streams.getResourceAsStream(Streams.java:107)
at com.mysql.management.util.Streams$1.inner(Streams.java:149) at
com.mysql.management.util.Exceptions$VoidBlock?.exec(Exceptions.java:128)
at com.mysql.management.util.Streams.createFileFromResource(Streams.java:162)
at com.mysql.management.MysqldResource?.makeMysqld(MysqldResource?.java:533)
at com.mysql.management.MysqldResource?.deployFiles(MysqldResource?.java:518)
at com.mysql.management.MysqldResource?.exec(MysqldResource?.java:495)
at com.mysql.management.MysqldResource?.start(MysqldResource?.java:216)
at com.mysql.management.MysqldResource?.start(MysqldResource?.java:166)

The default platform-map.properties file, which maps platforms to the supplied binary bundles, has been updated with additional platforms, including Windows 7, Windows Server 2008, amd64 and sparcv9 for Solaris, and Mac OS X 64-bit. (Bug #48298)

D.6.3. Changes in MySQL Connector/MXJ 5.0.10 (Not released)

This was an internal only release.

Functionality Added or Changed

The embedded MySQL has been updated to the MySQL 5.1 series. The embedded MySQL binaries have been updated to MySQL 5.1.33 for GPL releases and MySQL 5.1.34 for Commercial releases.
The MySQL binary for Windows targets has been updated to be configurable through the windows-mysqld-command property. This is to handle the move in MySQL 5.1.33 from mysqld-nt.exe to mysqld.exe. The default value is mysqld.exe.

D.6.4. Changes in MySQL Connector/MXJ 5.0.9 (19 August 2008)

Functionality Added or Changed

The port used in the ConnectorMXJUrlTestExample and ConnectorMXJObjectTestExample port is no longer hard coded. Instead, the code uses the x-mxj_test_port property a default value of 3336
The utility used to kill MySQL on Windows (kill.exe) has been configured to be loaded from the kill.exe property, instead of being hard-coded. The corresponding timeout, KILL_DELAY has also been moved to the properties file and defaults to 5 minutes.
The embedded MySQL binaries have been updated to MySQL 5.0.51a for GPL releases and MySQL 5.0.54 for Commercial releases.
The timeout for kill operations in the embedded test suite has been set to a default of 10 seconds.

D.6.5. Changes in MySQL Connector/MXJ 5.0.8 (06 August 2007)

Functionality Added or Changed

The embedded documentation has been updated so that it now points to the main MySQL documentation pages in the MySQL reference manual.
The embedded MySQL binaries have been updated to MySQL 5.0.45 for GPL releases and MySQL 5.0.46 for Commercial releases.

D.6.6. Changes in MySQL Connector/MXJ 5.0.7 (27 May 2007)

Functionality Added or Changed

Updated the jar file name to be consistent with the Connector/J jar file name. Files are now formatted as mysql-connector-mxj-mxj-version.
The ConnectorMXJUrlTestExample and ConnectorMXJObjectTestExammple have been updated to include an example of initializing the user/password and creating an initial database. The InitializePasswordExample example class has now been removed.
The PatchedStandardSocketFactory class has been removed, because it fixed an issue in Connector/J that was corrected in Connector/J 5.0.6.
The embedded MySQL binaries have been updated to MySQL 5.0.41 for GPL releases and MySQL 5.0.42 for Commercial releases.

Bugs Fixed

Added a null-check to deal with class loaders where getClassLoader() returns null.

D.6.7. Changes in MySQL Connector/MXJ 5.0.6 (04 May 2007)

Functionality Added or Changed

Updated internal jar file names to include version information and be more consistent with Connector/J jar naming. For example, connector-mxj.jar is now mysql-connector-mxj-${mxj-version}.jar.
Updated commercial license files.
Added copyright notices to some classes which were missing them.
Added InitializeUser and QueryUtil classes to support new feature.
Added new tests for initial-user & expanded some existing tests.
ConnectorMXJUrlTestExample and ConnectorMXJObjectTestExample now demonstrate the initialization of user/password and creating the initial database (rather than using "test").
Added new connection property initialize-user which, if set to true will remove the default, un-passworded anonymous and root users, and create the user/password from the connection url.
Removed obsolete field SimpleMysqldDynamicMBean.lastInvocation.
Clarified code in DefaultsMap.entrySet().
Removed obsolete PatchedStandardSocketFactory java file.
Added main(String[]) to com/mysql/management/AllTestsSuite.java.
Errors reading portFile are now reported using stacktrace(err), previously System.err was used.
portFile now contains a new-line to be consistent with pidFile.
Fixed where versionString.trim() was ignored.
Removed references to File.deleteOnExit, a warning is printed instead.

Bugs Fixed

Changed tests to shutdown mysqld prior to deleting files.
Fixed port file to always be written 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.
Added null-check to deal with C/MXJ being loaded by the bootstrap classloaders with JVMs for which getClassLoader() returns null.
Added robustness around reading portfile.
Removed PatchedStandardSocketFactory (fixed in Connector/J 5.0.6).
Refactored duplication from tests and examples to QueryUtil.
Removed obsolete InitializePasswordExample

D.6.8. 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, 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 incorporates Reggie Bernett's SafeTerminateProcess and only calls the unsafe TerminateProcess as a final last resort.
New windows kill.exe fixes a 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 demonstrates that dataDir is a mutable MBean property.
Updated build.xml in prep for next release.
Changed SimpleMysqldDynamicMBean to create MysqldResource on demand to enable 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.

D.6.9. 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 mysqld 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 tolerant of /tmp being a symlink to /foo/tmp.

D.6.10. 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.

D.6.11. 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)

D.6.12. Changes in MySQL Connector/MXJ 5.0.1 (Not released)

This was an internal only release.

This section has no changelog entries.

D.6.13. 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 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.

D.7. MySQL Connector/C++ Change History

D.7.1. Changes in MySQL Connector/C++ 1.1.x
D.7.2. Changes in MySQL Connector/C++ 1.0.x

D.7.1. Changes in MySQL Connector/C++ 1.1.x

D.7.1.1. Changes in MySQL Connector/CPP 1.1.0 (13th September 2010 GA)

D.7.1.1. Changes in MySQL Connector/CPP 1.1.0 (13th September 2010 GA)

This fixes bugs since the first GA release 1.0.5 and introduces new features.

Functionality Added or Changed

Incompatible Change: API incompatible change: ConnectPropertyVal is no longer a struct by a typedef that uses boost::variant. Code such as:

sql::ConnectPropertyVal tmp;
tmp.str.val=passwd.c_str();
tmp.str.len=passwd.length();
connection_properties["password"] = tmp;

Should be changed to:

connection_properties["password"] = sql::ConnectPropertyVal(passwd);

Instances of std::auto_ptr have been changed to boost::scoped_ptr. Scoped array instances now use boost::scoped_array. Further, boost::shared_ptr and boost::weak_ptr are now used for guarding access around result sets.
LDFLAGS, CXXFLAGS and CPPFLAGS are now checked from the environment for every binary generated.
Connection map property OPT_RECONNECT was changed to be of type boolean from long long.
get_driver_instance() is now only available in dynamic library builds - static builds do not have this symbol. This was done to accommodate loading the DLL with LoadLibrary or dlopen. If you do not use CMake for building the source code you will need to define mysqlcppconn_EXPORTS if you are loading dynamically and want to use the get_driver_instance() entry point.
Connection::getClientOption(const sql::SQLString & optionName, void * optionValue) now accepts the optionName values metadataUseInfoSchema, defaultStatementResultType, defaultPreparedStatementResultType, and characterSetResults. In the previous version only metadataUseInfoSchema was permitted. The same options are available for Connection::setClientOption().

Bugs Fixed

Certain header files were incorrectly present in the source distribution. The fix excludes dynamically generated and platform specific header files from source packages generated using CPack. (Bug #45846)
CMake generated an error if configuring an out of source build, that is, when CMake was not called from the source root directory. (Bug #45843)
Using Prepared Statements caused corruption of the heap. (Bug #45048)
Missing includes when using GCC 4.4. Note that GCC 4.4 is not yet in use for any official MySQL Connector/C++ builds. (Bug #44931)
A bug was fixed in Prepared Statements. The bug occurred when a stored procedure was prepared without any parameters. This led to an exception. (Bug #44931)
Fixed a Prepared Statements performance issue. Reading large result sets was slow.
Fixed bug in ResultSetMetaData for statements and prepared statements, getScale and getPrecision returned incorrect results.

D.7.2. Changes in MySQL Connector/C++ 1.0.x

D.7.2.1. Changes in MySQL Connector/CPP 1.0.5 (21 April 2009)
D.7.2.2. Changes in MySQL Connector/CPP 1.0.4 (31 March 2009 beta)
D.7.2.3. Changes in MySQL Connector/CPP 1.0.3 (02 March 2009 alpha)
D.7.2.4. Changes in MySQL Connector/CPP 1.0.2 (19 December 2008 alpha)
D.7.2.5. Changes in MySQL Connector/CPP 1.0.1 (01 December 2008 alpha)

D.7.2.1. Changes in MySQL Connector/CPP 1.0.5 (21 April 2009)

This is the first Generally Available (GA) release.

Functionality Added or Changed

The interface of sql::ConnectionMetaData, sql::ResultSetMetaData and sql::ParameterMetaData was modified to have a protected destructor. As a result the client code has no need to destruct the metadata objects returned by the connector. MySQL Connector/C++ handles the required destruction. This enables statements such as:
```
connection->getMetaData->getSchema();
```
This avoids potential memory leaks that could occur as a result of losing the pointer returned by getMetaData().
Improved memory management. Potential memory leak situations are handled more robustly.
Changed the interface of sql::Driver and sql::Connection so they accept the options map by alias instead of by value.
Changed the return type of sql::SQLException::getSQLState() from std::string to const char * to be consistent with std::exception::what().
Implemented getResultSetType() and setResultSetType() for Statement. Uses TYPE_FORWARD_ONLY, which means unbuffered result set and TYPE_SCROLL_INSENSITIVE, which means buffered result set.
Implemented getResultSetType() for PreparedStatement. The setter is not implemented because currently PreparedStatement cannot do refetching. Storing the result means the bind buffers will be correct.
Added the option defaultStatementResultType to MySQL_Connection::setClientOption(). Also, the method now returns sql::Connection *.
Added Result::getType(). Implemented for the three result set classes.
Enabled tracing functionality when building with Microsoft Visual C++ 8 and later, which corresponds to Microsoft Visual Studio 2005 and later.
Added better support for named pipes, on Windows. Use pipe:// and add the path to the pipe. Shared memory connections are currently not supported.

Bugs Fixed

A bug was fixed in MySQL_Connection::setSessionVariable(), which had been causing exceptions to be thrown.

D.7.2.2. Changes in MySQL Connector/CPP 1.0.4 (31 March 2009 beta)

Functionality Added or Changed

An installer was added for the Windows operating system.
Minimum CMake version required was changed from 2.4.2 to 2.6.2. The latest version is required for building on Windows.
metadataUseInfoSchema was added to the connection property map, which enables control of the INFORMATION_SCHEMA for metadata.
Implemented MySQL_ConnectionMetaData::supportsConvert(from, to).
Added support for MySQL Connector/C.
Introduced ResultSetMetaData::isZerofill(), which is not in the JDBC specification.

Bugs Fixed

A bug was fixed in all implementations of ResultSet::relative() which was giving a wrong return value although positioning was working correctly.
A leak was fixed in MySQL_PreparedResultSet, which occurred when the result contained a BLOB column.

D.7.2.3. Changes in MySQL Connector/CPP 1.0.3 (02 March 2009 alpha)

Functionality Added or Changed

Added new tests in test/unit/classes. Those tests are mostly about code coverage. Most of the actual functionality of the driver is tested by the tests found in test/CJUnitPort.
New data types added to the list returned by DatabaseMetaData::getTypeInfo() are FLOAT UNSIGNED, DECIMAL UNSIGNED, DOUBLE UNSIGNED. Those tests may not be in the JDBC specification. However, due to the change you should be able to look up every type and type name returned by, for example, ResultSetMetaData::getColumnTypeName().
MySQL_Driver::getPatchVersion introduced.
Major performance improvements due to new buffered ResultSet implementation.
Addition of test/unit/README with instructions for writing bug and regression tests.
Experimental support for STLPort. This feature may be removed again at any time later without prior warning! Type cmake -L for configuration instructions.
Added properties enabled methods for connecting, which add many connect options. This uses a dictionary (map) of key value pairs. Methods added are Driver::connect(map), and Connection::Connection(map).
New BLOB implementation. sql::Blob was removed in favor of std::istream. C++'s IOStream library is very powerful, similar to PHP's streams. It makes no sense to reinvent the wheel. For example, you can pass a std::istringstream object to setBlob() if the data is in memory, or just open a file std::fstream and let it stream to the DB, or write its own stream. This is also true for getBlob() where you can just copy data (if a buffered result set), or stream data (if implemented).
Implemented ResultSet::getBlob() which returns std::stream.
Fixed MySQL_DatabaseMetaData::getTablePrivileges(). Test cases were added in the first unit testing framework.
Implemented MySQL_Connection::setSessionVariable() for setting variables like sql_mode.
Implemented MySQL_DatabaseMetaData::getColumnPrivileges().
cppconn/datatype.h has changed and is now used again. Reimplemented the type subsystem to be more usable - more types for binary and nonbinary strings.
Implementation for MySQL_DatabaseMetaData::getImportedKeys() for MySQL versions before 5.1.16 using SHOW, and above using INFORMATION_SCHEMA.
Implemented MySQL_ConnectionMetaData::getProcedureColumns().
make package_source now packs with bzip2.
Re-added getTypeInfo() with information about all types supported by MySQL and the sql::DataType.
Changed the implementation of MySQL_ConstructedResultSet to use the more efficient O(1) access method. This should improve the speed with which the metadata result sets are used. Also, there is less copying during the construction of the result set, which means that all result sets returned from the metadata functions will be faster.
Introduced, internally, sql::mysql::MyVal which has implicit constructors. Used in mysql_metadata.cpp to create result sets with native data instead of always string (varchar).
Renamed ResultSet::getLong() to ResultSet::getInt64(). resultset.h includes typdefs for Windows to be able to use int64_t.
Introduced ResultSet::getUInt() and ResultSet::getUInt64().
Improved the implementation for ResultSetMetaData::isReadOnly(). Values generated from views are read only. These generated values don't have db in MYSQL_FIELD set, while all normal columns do have.
Implemented MySQL_DatabaseMetaData::getExportedKeys().
Implemented MySQL_DatabaseMetaData::getCrossReference().

Bugs Fixed

Bug fixed in MySQL_PreparedResultSet::getString(). Returned string that had real data but the length was random. Now, the string is initialized with the correct length and thus is binary safe.
Corrected handling of unsigned server types. Now returning correct values.
Fixed handling of numeric columns in ResultSetMetaData::isCaseSensitive to return false.

D.7.2.4. Changes in MySQL Connector/CPP 1.0.2 (19 December 2008 alpha)

Functionality Added or Changed

Implemented getScale(), getPrecision() and getColumnDisplaySize() for MySQL_ResultSetMetaData and MySQL_Prepared_ResultSetMetaData.
Changed ResultSetMetaData methods getColumnDisplaySize(), getPrecision(), getScale() to return unsigned int instead of signed int.
DATE, DATETIME and TIME are now being handled when calling the MySQL_PreparedResultSet methods getString(), getDouble(), getInt(), getLong(), getBoolean().
Reverted implementation of MySQL_DatabaseMetaData::getTypeInfo(). Now unimplemented. In addition, removed cppconn/datatype.h for now, until a more robust implementation of the types can be developed.
Implemented MySQL_PreparedStatement::setNull().
Implemented MySQL_PreparedStatement::clearParameters().
Added PHP script examples/cpp_trace_analyzer.php to filter the output of the debug trace. Please see the inline comments for documentation. This script is unsupported.
Implemented MySQL_ResultSetMetaData::getPrecision() and MySQL_Prepared_ResultSetMetaData::getPrecision(), updating example.
Added new unit test framework for JDBC compliance and regression testing.
Added test/unit as a basis for general unit tests using the new test framework, see test/unit/example for basic usage examples.

Bugs Fixed

Fixed MySQL_PreparedStatementResultSet::getDouble() to return the correct value when the underlying type is MYSQL_TYPE_FLOAT.
Fixed bug in MySQL_ConnectionMetaData::getIndexInfo(). The method did not work because the schema name wasn't included in the query sent to the server.
Fixed a bug in MySQL_ConnectionMetaData::getColumns() which was performing a cartesian product of the columns in the table times the columns matching columnNamePattern. The example example/connection_meta_schemaobj.cpp was extended to cover the function.
Fixed bugs in MySQL_DatabaseMetaData. All supportsCatalogXXXXX methods were incorrectly returning true and all supportsSchemaXXXX methods were incorrectly returning false. Now supportsCatalogXXXXX returns false and supportsSchemaXXXXX returns true.
Fixed bugs in the MySQL_PreparedStatements methods setBigInt() and setDatetime(). They decremented the internal column index before forwarding the request. This resulted in a double-decrement and therefore the wrong internal column index. The error message generated was:
```
setString() ... invalid "parameterIndex"
```
Fixed a bug in getString(). getString() is now binary safe. A new example was also added.
Fixed bug in FLOAT handling.
Fixed MySQL_PreparedStatement::setBlob(). In the tests there is a simple example of a class implementing sql::Blob.

D.7.2.5. Changes in MySQL Connector/CPP 1.0.1 (01 December 2008 alpha)

Functionality Added or Changed

sql::mysql::MySQL_SQLException was removed. The distinction between server and client (connector) errors, based on the type of the exception, has been removed. However, the error code can still be checked to evaluate the error type.
Support for (n)make install was added. You can change the default installation path. Carefully read the messages displayed after executing cmake. The following are installed:
- Static and the dynamic version of the library, libmysqlcppconn.
- Generic interface, cppconn.
- Two MySQL specific headers:
  mysql_driver.h, use this if you want to get your connections from the driver instead of instantiating a MySQL_Connection object. This makes your code portable when using the common interface.
  mysql_connection.h, use this if you intend to link directly to the MySQL_Connection class and use its specifics not found in sql::Connection.
  However, you can make your application fully abstract by using the generic interface rather than these two headers.
Driver Manager was removed.
Added ConnectionMetaData::getSchemas() and Connection::setSchema().
ConnectionMetaData::getCatalogTerm() returns not applicable, there is no counterpart to catalog in MySQL Connector/C++.
Added experimental GCov support, cmake -DMYSQLCPPCONN_GCOV_ENABLE:BOOL=1

All examples can be given optional connection parameters on the command line, for example:

examples/connect tcp://host:port user pass database

examples/connect unix:///path/to/mysql.sock user pass database

Renamed ConnectionMetaData::getTables: TABLE_COMMENT to REMARKS.
Renamed ConnectionMetaData::getProcedures: PROCEDURE_SCHEMA to PROCEDURE_SCHEM.
Renamed ConnectionMetaData::getPrimaryKeys(): COLUMN to COLUMN_NAME, SEQUENCE to KEY_SEQ, and INDEX_NAME to PK_NAME.
Renamed ConnectionMetaData::getImportedKeys(): PKTABLE_CATALOG to PKTABLE_CAT, PKTABLE_SCHEMA to PKTABLE_SCHEM, FKTABLE_CATALOG to FKTABLE_CAT, FKTABLE_SCHEMA to FKTABLE_SCHEM.
Changed metadata column name TABLE_CATALOG to TABLE_CAT and TABLE_SCHEMA to TABLE_SCHEM to ensure JDBC compliance.
Introduced experimental CPack support, see make help.
All tests changed to create TAP compliant output.
Renamed sql::DbcMethodNotImplemented to sql::MethodNotImplementedException
Renamed sql::DbcInvalidArgument to sql::InvalidArgumentException
Changed sql::DbcException to implement the interface of JDBC's SQLException. Renamed to sql::SQLException.
Converted Connector/J tests added.
MySQL Workbench 5.1 changed to use MySQL Connector/C++ for its database connectivity.
New directory layout.

D.8. MySQL Proxy Change History

D.8.1. Changes in MySQL Proxy 0.8.2 (18 August 2011)
D.8.2. Changes in MySQL Proxy 0.8.1 (13 September 2010)
D.8.3. Changes in MySQL Proxy 0.8.0 (21 January 2010)
D.8.4. Changes in MySQL Proxy 0.7.2 (30 June 2009)
D.8.5. Changes in MySQL Proxy 0.7.1 (15 May 2009)
D.8.6. Changes in MySQL Proxy 0.7.0 (Not Released)
D.8.7. Changes in MySQL Proxy 0.6.1 (06 February 2008)
D.8.8. Changes in MySQL Proxy 0.6.0 (11 September 2007)
D.8.9. Changes in MySQL Proxy 0.5.1 (30 June 2007)
D.8.10. Changes in MySQL Proxy 0.5.0 (19 June 2007)

D.8.1. Changes in MySQL Proxy 0.8.2 (18 August 2011)

MySQL Proxy 0.8.2 is a maintenance release and focuses on these areas:

Adding the protocol changes of MySQL 5.5 and later
Removing the “admin” plugin from the list of default plugins, as it requires configuration since 0.8.1

Note to Windows Users

The Microsoft Visual C++ runtime libraries are now a requirement for running MySQL Proxy. Users that do not have these libraries must download and install the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update. For the current Proxy version, use the following link to obtain the package:
```
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26368
```
(Bug #12836100)

Functionality Added or Changed

Removed the “admin” plugin from the list of default plugins, as it requires configuration since 0.8.1.
Added support for OUT parameters in prepared statements in stored procedures with MySQL 5.5.
Added support for decoding all data types of the row-based replication protocol.
Added support for binary log checksums.

Bugs Fixed

Fixed handling of stored procedures with cursors with MySQL 5.5. (Bug #61998)
A crash occurred if the file named with the --defaults-file option did not exist. (Bug #59790)
The first characters of log messages were stripped. (Bug #59790)
A memory leak occurred if connection pooling was used. (Bug #56620)
A bogus timestamp log was produced if state tracking was not compiled in.
A crash could occur if run under Valgrind.
Fixed handling of “used columns” with row-based replication.

D.8.2. Changes in MySQL Proxy 0.8.1 (13 September 2010)

Functionality Added or Changed

Allow interception of LOAD DATA INFILE and SHOW ERRORS statements.
The unused network_mysqld_com_query_result_track_state() function has been deprecated.
chassis_set_fdlimit() has been deprecated in favor of chassis_fdlimit_set().
Shutdown hooks were added to free the global memory of third-party libraries such as openssl.
con->in_load_data_local has been removed.

Bugs Fixed

The admin plugin had an undocumented default value for --admin-password. (Bug #53429)
Use of LOAD DATA LOCAL INFILE caused the connection between the client and MySQL Proxy to abort. (Bug #51864)
If the backend MySQL server went down, and then the clock on the MySQL Proxy host went backward (for example, during daylight saving time adjustments), Proxy stopped forwarding queries to the backend. (Bug #50806)
network_address_set_address()->network_address_set_address_ip() called gethostbyname() which was not reentrant. This meant that a MySQL Proxy plugin needed to guard all calls to network_address_set_address() with a mutex. network_address_set_address() has been modified to be thread safe. (Bug #49099)
The hard limit was fixed for the case where the fdlimit was set. (Bug #48120)
MySQL Proxy returned an error message with a nonstandard SQL State when all backends were down:
```
"#07000(proxy) all backends are down"
```
This caused issues for clients with “retry” logic, as they could not handle these “custom” SQL States. (Bug #45417)
If MySQL Proxy used a UNIX socket, it did not remove the socket file at termination time. (Bug #38415)
The --proxy-read-only-backend-addresses option did not work. (Bug #38341, Bug #11749171)
When running configure to build, the error message relating to the lua libraries could be misleading. The wording and build advice have been updated.

D.8.3. Changes in MySQL Proxy 0.8.0 (21 January 2010)

Functionality Added or Changed

The --no-daemon has been renamed to The --daemon. By default, MySQL Proxy now starts in foreground mode. Use the --daemon option to override this and start in daemon mode.

Bugs Fixed

A memory leak occurred in MySQL Proxy if clients older than MySQL 4.1 connected to it. (Bug #50993)
A segmentation fault occurred in MySQL Proxy if clients older than MySQL 4.1 connected to it. (Bug #48641)
MySQL Proxy would load a configuration file with unsafe permissions, which could permit password information to be exposed through the file. MySQL Proxy now refuses to load a configuration file with unsafe permissions. (Bug #47589)
Several supplied scripts were updated to account for flag and structure changes:
- active-transactions.lua was updated to use the resultset_is_needed flag.
- ro-balance.lua was updated to use the resultset_is_needed flag and updated proxy.connection.dst.name structure.
- rw-splitting.lua was updated to use the resultset_is_needed flag and updated proxy.connections structure.
(Bug #47349, Bug #45408, Bug #47345, Bug #43424, Bug #42841, Bug #46141)
The line numbers provided in stack traces were off by one. (Bug #47348)
MySQL Proxy accepted more than one address in the value of the --proxy-backend-addresses option. You should specify one --proxy-backend-addresses option for each backend address. (Bug #47273)
MySQL Proxy returned the wrong version string internally from the proxy.PROXY_VERSION constant. (Bug #45996)
MySQL Proxy could stop accepting network packets if it received a large number of packets. The listen queue has been extended to permit a larger backlog. (Bug #45878, Bug #43278)
Due to a memory leak, memory usage for each new connection to the proxy increased, leading to very high consumption. (Bug #45272)
MySQL Proxy failed to work with certain versions of MySQL, including MySQL 5.1.15, where a change in the MySQL protocol existed. Now Proxy denies COM_CHANGE_USER commands when it is connected to MySQL 5.1.14 to 5.1.17 servers by sending back an error: COM_CHANGE_USER is broken on 5.1.14-.17, please upgrade the MySQL Server. (Bug #45167)
See also Bug #25371.
Logging to syslog with the --log-use-syslog option did not work. (Bug #36431)
MySQL Proxy could incorrectly insert NULL values into the returned result set, even though non-NULL values were returned in the original query. (Bug #35729)
MySQL Proxy raised an error when processing query packets larger than 16MB. (Bug #35202)

D.8.4. Changes in MySQL Proxy 0.7.2 (30 June 2009)

Bugs Fixed

On Windows, MySQL Proxy might not find the required modules during initialization. The core code has been updated to find the components correctly, and the Lua-based C modules are prefixed with lua- and Lua plugins with plugin-. (Bug #45833)

D.8.5. Changes in MySQL Proxy 0.7.1 (15 May 2009)

Bugs Fixed

Due to a memory leak, memory usage for each new connection to the proxy increased, leading to very high consumption. (Bug #45272)
The port number was reported incorrectly in proxy.connection.client.address. (Bug #43313)
Result sets with more than 250 fields could cause MySQL Proxy to crash. (Bug #43078)
MySQL Proxy was unable to increase its own maximum number of open files according to the limit specified by the --max-open-files option, if the limit was less than 8192. When set to debug level, Proxy now reports the open files limit and when the limit has been updated. (Bug #42783)
MySQL Proxy crashed when connecting to a MySQL 4.0 server. Now it generates an error message instead. (Bug #38601)
When using the rw-splitting.lua script, you could get an error when talking to the backend server:
```
2008-07-28 18:00:30: (critical) (read_query) [string
"/usr/local/share/mysql-proxy/rw-splitting.l..."]:218: bad argument #1 to 'ipairs' (table
expected, got userdata)
```
This led to Proxy closing the connection to the configured MySQL backend. (Bug #38419)
When using MySQL Proxy with multiple backends, failure of one backend caused Proxy to disconnect all backends and stop routing requests. (Bug #34793)

D.8.6. Changes in MySQL Proxy 0.7.0 (Not Released)

Functionality Added or Changed

Support for using a configuration file, in addition to the command-line options, has been added. To specify such a file, use the --defaults-file=file_name command-line option. See Section 14.7.3, “MySQL Proxy Command Options”. (Bug #30206)

A number of the internal structures developed for use with Lua scripts that work with MySQL Proxy have been updated and harmonized to make their meaning and contents easier to use and consistent across multiple locations.

The address information has been updated. Instead of a combined ip:port structure that you had to parse to extract the individual information, you can now access that information directly. For example, instead of structures providing a single .address item, you now have these items: name (the combined ip:port), address (the IP address), and port (port number). In addition, all addresses now supply both the src (source) and dst (destination) socket information for both ends of connections.
Some familiar structures have been updated to accommodate this information:
- proxy.connection.client.address is proxy.connection.client.src.name
- proxy.connection.server.address is proxy.connection.server.dst.name
proxy.backends is now in proxy.global.backends The .address field of each backend is an address-object as described earlier. For example, proxy.backends[1].address is proxy.global.backends[1].dst.name.

The read_auth() and read_handshake() functions no longer receive an auth parameter. Instead, all the data is available in the connection tables.

In read_handshake(), you access the information through the global proxy.connection table:

0.6	0.7
`auth.thread_id`	`proxy.connection.server.thread_id`
`auth.mysqld_version`	`proxy.connection.server.mysqld_version`
`auth.server_addr`	`proxy.connection.server.dst.name`
`auth.client_addr`	`proxy.connection.client.src.name`
`auth.scramble`	`proxy.connection.server.scramble_buffer`

In read_auth(), you can use the following:

0.6	0.7
`auth.username`	`proxy.connection.client.username`
`auth.password`	`proxy.connection.client.scrambled_password`
`auth.default_db`	`proxy.connection.client.default_db`
`auth.server_addr`	`proxy.connection.server.dst.name`
`auth.client_addr`	`proxy.connection.client.src.name`

In the proxy.queries:append() function, a third parameter is an (optional) table with options specific to the this packet. Specifically, if you want to have access to the result set in the read_query_result() hook, you must set the resultset_is_needed flag:
```
proxy.queries:append( 1, ..., { resultset_is_needed = true } )
```
For more information, see proxy.queries.
proxy.backends is now in proxy.global.backends.

Bugs Fixed

Security Enhancement: Accessing MySQL Proxy using a client or backend from earlier than MySQL 4.1 resulted in Proxy aborting with an assertion. This is because Proxy supports only MySQL 4.1 or higher. Proxy now reports a fault. (Bug #31419)
MySQL Proxy was configured with the LUA_PATH and LUA_CPATH directory locations according to the build host rather than the execution host. In addition, during installation, certain Lua source files could be installed into the incorrect locations. (Bug #44877, Bug #44497)
Using MySQL Proxy with very large return data sets from queries could cause a crash, with or without manipulation of the data set within the Lua engine. (Bug #39332)
MySQL Proxy terminated if a submitted packet was smaller than expected by the protocol. (Bug #36743)
When using MySQL Proxy in a master-master replication scenario, Proxy failed to identify failure in one of the replication masters and did not redirect connections to the other master. (Bug #35295)

D.8.7. Changes in MySQL Proxy 0.6.1 (06 February 2008)

Functionality Added or Changed

Fixed assertions on write errors.
Fixed sending fake server-greetings in connect_server().
Fixed error handling for socket functions on Windows.
Added new features to run-tests.lua.

D.8.8. Changes in MySQL Proxy 0.6.0 (11 September 2007)

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.
By default, MySQL Proxy now starts in daemon mode. Use the new --no-daemon option to override this. Added the --pid-file option for writing the process ID to a file after becoming a daemon.
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 test cases.
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 an assertion on COM_BINLOG_DUMP. (Bug #29764)
Fixed an assertion on result-packets like [field-len | fields | EOF | ERR]. (Bug #29732)
Fixed an assertion that MySQL Proxy raised at login time if a client specified no password and no default database. (Bug #29719)
Fixed an assertion at COM_SHUTDOWN. (Bug #29719)
Fixed a crash if proxy.connection is used in connect_server().
Fixed the glib2 check to require at least glib2 2.6.0.
Fixed an assertion at connect time when all backends are down.
Fixed connection stalling if read_query_result() raised an assertion.
Fixed length encoding on proxy.resultsets.
Fixed compilation on win32.
Fixed an assertion when connecting to MySQL 6.0.1.
Fixed decoding of length-encoded ints for 3-byte notation.
Fixed inj.resultset.affected_rows on SELECT queries.
Fixed handling of (SQL) NULL in result sets.
Fixed a memory leak when proxy.response.* is used.

D.8.9. 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 result sets 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 a compile error with MySQL 4.1.x on missing COM_STMT_*.
Fixed a crash on fields longer than 250 bytes when the result set is inspected.
Fixed a warning if connect_server() is not provided.
Fixed an assertion when an error occurs at initial script exec time.
Fixed an assertion when read_query_result() is not provided when PROXY_SEND_QUERY is used.

D.8.10. 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 C. Errors, Error Codes, and Common Problems	Home	Appendix E. Restrictions and Limits