Appendix C. MySQL Change History

Table of Contents

C.1. Changes in Release 5.5.x (Development)
C.1.1. Changes in MySQL 5.5.3 (Not yet released)
C.1.2. Changes in MySQL 5.5.2 (12 February 2010)
C.1.3. Changes in MySQL 5.5.1 (04 January 2010)
C.1.4. Changes in MySQL 5.5.0 (07 December 2009 Milestone 2)
C.2. MySQL Enterprise Monitor Change History
C.2.1. Changes in MySQL Enterprise Monitor 2.0.7 (Not yet released)
C.2.2. Changes in MySQL Enterprise Monitor 2.0.6 (27th August 2009)
C.2.3. Changes in MySQL Enterprise Monitor 2.0.5 (18th March 2009)
C.2.4. Changes in MySQL Enterprise Monitor 2.0.4 (5th February 2009)
C.2.5. Changes in MySQL Enterprise Monitor 2.0.3 (23rd January 2009)
C.2.6. Changes in MySQL Enterprise Monitor 2.0.2 (14th January 2009)
C.2.7. Changes in MySQL Enterprise Monitor 2.0.1 (15th December 2008)
C.2.8. Changes in MySQL Enterprise Monitor 2.0.0 (11th December 2008)
C.3. MySQL Connector/ODBC (MyODBC) Change History
C.3.1. Changes in MySQL Connector/ODBC 5.1.7 (Not yet released)
C.3.2. Changes in MySQL Connector/ODBC 5.1.6 (09 November 2009)
C.3.3. Changes in MySQL Connector/ODBC 5.1.5 (18 August 2008)
C.3.4. Changes in MySQL Connector/ODBC 5.1.4 (15 April 2008)
C.3.5. Changes in MySQL Connector/ODBC 5.1.3 (26 March 2008)
C.3.6. Changes in MySQL Connector/ODBC 5.1.2 (13 February 2008)
C.3.7. Changes in MySQL Connector/ODBC 5.1.1 (13 December 2007)
C.3.8. Changes in MySQL Connector/ODBC 5.1.0 (10 September 2007)
C.3.9. Changes in MySQL Connector/ODBC 5.0.12 (Never released)
C.3.10. Changes in MySQL Connector/ODBC 5.0.11 (31 January 2007)
C.3.11. Changes in MySQL Connector/ODBC 5.0.10 (14 December 2006)
C.3.12. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)
C.3.13. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)
C.3.14. Changes in MySQL Connector/ODBC 5.0.7 (08 November 2006)
C.3.15. Changes in MySQL Connector/ODBC 5.0.6 (03 November 2006)
C.3.16. Changes in MySQL Connector/ODBC 5.0.5 (17 October 2006)
C.3.17. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)
C.3.18. Changes in Connector/ODBC 5.0.2 (Never released)
C.3.19. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)
C.3.20. Changes in MySQL Connector/ODBC 3.51.28 (Not yet released)
C.3.21. Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008)
C.3.22. Changes in MySQL Connector/ODBC 3.51.26 (07 July 2008)
C.3.23. Changes in MySQL Connector/ODBC 3.51.25 (11 April 2008)
C.3.24. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)
C.3.25. Changes in MySQL Connector/ODBC 3.51.23 (09 January 2008)
C.3.26. Changes in MySQL Connector/ODBC 3.51.22 (13 November 2007)
C.3.27. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)
C.3.28. Changes in MySQL Connector/ODBC 3.51.20 (10 September 2007)
C.3.29. Changes in MySQL Connector/ODBC 3.51.19 (10 August 2007)
C.3.30. Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)
C.3.31. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)
C.3.32. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)
C.3.33. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)
C.3.34. Changes in MySQL Connector/ODBC 3.51.14 (08 March 2007)
C.3.35. Changes in MySQL Connector/ODBC 3.51.13 (Never released)
C.3.36. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)
C.3.37. Changes in MySQL Connector/ODBC 3.51.11 (28 January 2005)
C.4. MySQL Connector/NET Change History
C.4.1. Changes in MySQL Connector/NET Version 6.3.x
C.4.2. Changes in MySQL Connector/NET Version 6.2.x
C.4.3. Changes in MySQL Connector/NET Version 6.1.x
C.4.4. Changes in MySQL Connector/NET Version 6.0.x
C.4.5. Changes in MySQL Connector/NET Version 5.3.x
C.4.6. Changes in MySQL Connector/NET Version 5.2.x
C.4.7. Changes in MySQL Connector/NET Version 5.1.x
C.4.8. Changes in MySQL Connector/NET Version 5.0.x
C.4.9. Changes in MySQL Connector/NET Version 1.0.x
C.4.10. Changes in MySQL Connector/NET Version 0.9.0 (30 August 2004)
C.4.11. Changes in MySQL Connector/NET Version 0.76
C.4.12. Changes in MySQL Connector/NET Version 0.75
C.4.13. Changes in MySQL Connector/NET Version 0.74
C.4.14. Changes in MySQL Connector/NET Version 0.71
C.4.15. Changes in MySQL Connector/NET Version 0.70
C.4.16. Changes in MySQL Connector/NET Version 0.68
C.4.17. Changes in MySQL Connector/NET Version 0.65
C.4.18. Changes in MySQL Connector/NET Version 0.60
C.4.19. Changes in MySQL Connector/NET Version 0.50
C.5. MySQL Visual Studio Plugin Change History
C.5.1. Changes in MySQL Visual Studio Plugin 1.0.3 (Not yet released)
C.5.2. Changes in MySQL Visual Studio Plugin 1.0.2 (Not yet released)
C.5.3. Changes in MySQL Visual Studio Plugin 1.0.1 (4 October 2006)
C.5.4. Changes in MySQL Visual Studio Plugin 1.0.0 (4 October 2006)
C.6. MySQL Connector/J Change History
C.6.1. Changes in MySQL Connector/J 5.1.x
C.6.2. Changes in MySQL Connector/J 5.0.x
C.6.3. Changes in MySQL Connector/J 3.1.x
C.6.4. Changes in MySQL Connector/J 3.0.x
C.6.5. Changes in MySQL Connector/J 2.0.x
C.6.6. Changes in MySQL Connector/J 1.2b (04 July 1999)
C.6.7. Changes in MySQL Connector/J 1.2.x and lower
C.7. MySQL Connector/MXJ Change History
C.7.1. Changes in MySQL Connector/MXJ 5.0.11 (24th November 2009)
C.7.2. Changes in MySQL Connector/MXJ 5.0.10 (Never released)
C.7.3. Changes in MySQL Connector/MXJ 5.0.9 (19 August 2008)
C.7.4. Changes in MySQL Connector/MXJ 5.0.8 (06 August 2007)
C.7.5. Changes in MySQL Connector/MXJ 5.0.7 (27 May 2007)
C.7.6. Changes in MySQL Connector/MXJ 5.0.6 (04 May 2007)
C.7.7. Changes in MySQL Connector/MXJ 5.0.5 (14 March 2007)
C.7.8. Changes in MySQL Connector/MXJ 5.0.4 (28 January 2007)
C.7.9. Changes in MySQL Connector/MXJ 5.0.3 (24 June 2006)
C.7.10. Changes in MySQL Connector/MXJ 5.0.2 (15 June 2006)
C.7.11. Changes in MySQL Connector/MXJ 5.0.1 (Never released)
C.7.12. Changes in MySQL Connector/MXJ 5.0.0 (09 December 2005)
C.8. MySQL Connector/C++ Change History
C.8.1. Changes in MySQL Connector/C++ 1.1.x
C.8.2. Changes in MySQL Connector/C++ 1.0.x
C.9. MySQL Proxy Change History
C.9.1. Changes in MySQL Proxy 0.8.0 (Not Yet Released)
C.9.2. Changes in MySQL Proxy 0.7.3 (Not Yet Released)
C.9.3. Changes in MySQL Proxy 0.7.2 (30 June 2009)
C.9.4. Changes in MySQL Proxy 0.7.1 (15 May 2009)
C.9.5. Changes in MySQL Proxy 0.7.0 (Never Released)
C.9.6. Changes in MySQL Proxy 0.6.1 (06 February 2008)
C.9.7. Changes in MySQL Proxy 0.6.0 (11 September 2007)
C.9.8. Changes in MySQL Proxy 0.5.1 (30 June 2007)
C.9.9. Changes in MySQL Proxy 0.5.0 (19 June 2007)

This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 5.5, which is currently MySQL 5.5.3. 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.5 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.

C.1. Changes in Release 5.5.x (Development)

An overview of which features were added in MySQL 5.5 can be found here: Section 1.5, “What Is New in MySQL 5.5”.

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

For discussion of upgrade issues that you many encounter for upgrades to MySQL 5.5 from MySQL 5.4, see Section 2.12.1.1, “Upgrading from MySQL 5.4 to 5.5”.

C.1.1. Changes in MySQL 5.5.3 (Not yet released)

Performance Schema Notes:

  • MySQL Server now includes Performance Schema, a feature for monitoring server execution at a low level. It is implemented via the PERFORMANCE_SCHEMA storage engine and the performance_schema database. Performance Schema focuses primarily on performance data. This differs from INFORMATION_SCHEMA, which serves for inspection of metadata. For more information, see Chapter 20, MySQL Performance Schema.

    To create the performance_schema database if you are upgrading from an earlier release, run mysql_upgrade and restart the server. See Section 4.4.7, “mysql_upgrade — Check Tables for MySQL Upgrade”.

InnoDB Plugin Notes:

  • This release includes InnoDB Plugin 1.0.6. This version is considered of Release Candidate (RC) quality.

Functionality added or changed:

  • Performance: The performance of internal functions that trim multiple spaces from strings when comparing them has been improved. (Bug#14637)

  • Incompatible Change: The following obsolete constructs have been removed. Where alternatives are shown, applications should be updated to use them.

    (Bug#48048)

    See also Bug#47974.

  • Incompatible Change: Aliases for wildcards (as in SELECT t.* AS 'alias' FROM t) are no longer accepted and result in an error. Previously, such aliases were ignored silently. (Bug#27249)

  • Incompatible Change: The server now includes dtoa, a library for conversion between strings and numbers by David M. Gay. In MySQL, this library provides the basis for improved conversion between string or DECIMAL values and approximate-value (FLOAT/DOUBLE) numbers:

    • Consistent conversion results across platforms, which eliminates, for example, Unix versus Windows conversion differences.

    • Accurate representation of values in cases where results previously did not provide sufficient precision, such as for values close to IEEE limits.

    • Conversion of numbers to string format with the best possible precision. The precision of dtoa is always the same or better than that of the standard C library functions.

    Because the conversions produced by this library differ in some cases from previous results, the potential exists for incompatibilities in applications that rely on previous results. For example, applications that depend on a specific exact result from previous conversions might need adjustment to accommodate additional precision.

    For additional information about the properties of dtoa conversions, see Section 11.2.2, “Type Conversion in Expression Evaluation”.

    See also Bug#12860, Bug#21497, Bug#26788, Bug#24541, Bug#34015.

  • Incompatible Change: Several columns were added to the INFORMATION_SCHEMA.ROUTINES table to provide information about the RETURNS clause data type for stored functions: DATA_TYPE, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH, NUMERIC_PRECISION, NUMERIC_SCALE, CHARACTER_SET_NAME, and COLLATION_NAME.

    This change produces an incompatibility for applications that depend on column order in the ROUTINES table because the new columns appear between the ROUTINE_TYPE and DTD_IDENTIFIER columns. Such applications may need to be adjusted to account for the new columns.

  • Important Change: Replication: RESET MASTER and RESET SLAVE now reset the values shown for Last_IO_Error, Last_IO_Errno, Last_SQL_Error, and Last_SQL_Errno in the output of SHOW SLAVE STATUS. (Bug#34654)

    See also Bug#44270.

  • Important Change: The --skip-thread-priority option is now deprecated such that the server won't change the thread priorities by default. Giving threads different priorities might yield marginal improvements in some platforms (where it actually works), but it might instead cause significant degradation depending on the thread count and number of processors. Meddling with the thread priorities is a not a safe bet as it is very dependent on the behavior of the CPU scheduler and system where MySQL is being run. (Bug#35164, Bug#37536)

  • mysqltest has a new --max-connections option to set a higher number of maximum allowed server connections than the default 128. This option can also be passed via mysql-test-run.pl. (Bug#51135)

  • mysql-test-run.pl has a new --portbase option and a corresponding MTR_PORT_BASE environment variable for setting the port range, as an alternative to the existing --build-thread option. (Bug#50182)

  • SHOW PROFILE CPU has been ported to Windows. Thanks to Alex Budovski for the patch. (Bug#50057)

  • mysql-test-run.pl has a new --gprof option that runs the server through the gprof profiler, much the same way the currently supported --gcov option runs it through gcov. (Bug#49345)

  • mysqltest has a new lowercase_result command that converts the output of the next statement to lowercase. This is useful for test cases where the lettercase may vary between platforms. (Bug#48863)

  • mysqltest has a new remove_files_wildcard command that removes files matching a pattern from a directory. (Bug#39774)

  • MySQL support for adding collations using LDML specifications did not support the <i> identity rule that indicates one character sorts identically to another. The <i> rule now is supported. (Bug#37129)

  • For boolean options, the option-processing library now prints additional information in the --help message: If the option is enabled by default, the message says so and indicates that the --skip form of the option disables the option. This affects all compiled MySQL programs that use the library. (Bug#35224)

  • The use of the SQL_CACHE and SQL_NO_CACHE options in SELECT statements now is checked more restrictively: 1) Previously, both options could be given in the same statement. This is no longer true; only one can be given. 2) Previously, these options could be given in SELECT statements that were not at the top-level. This is no longer true; the options are disallowed in subqueries (including subqueries in the FROM clause, and SELECT statements in unions other than the first SELECT. (Bug#35020)

  • Added the --auto-vertical-output option to mysql which causes result sets to be displayed vertically if they are too wide for the current window, and using normal tabular format otherwise. (This applies to statements terminated by ; or \G.) (Bug#26780)

  • TRUNCATE TABLE now is allowed for a table for which a WRITE lock has been acquired with LOCK TABLES. (Bug#20667)

    See also Bug#46452.

  • FLUSH LOGS now takes an optional log_type value so that FLUSH log_type LOGS can be used to flush only a specified log type. These log_type options are allowed:

    • BINARY closes and reopens the binary log files.

    • ENGINE closes and reopens any flushable logs for installed storage engines.

    • ERROR closes and reopens the error log file.

    • GENERAL closes and reopens the general query log file.

    • RELAY closes and reopens the relay log files.

    • SLOW closes and reopens the slow query log file.

    Thanks to Eric Bergen for the patch to implement this feature. (Bug#14104)

  • Previously, prepared CALL statements could be used via the C API only for stored procedures that produce at most one result set, and applications could not use placeholders for OUT or INOUT parameters. For prepared CALL statements used via PREPARE and EXECUTE, placeholders could not be used for OUT or INOUT parameters.

    For the C API, prepared CALL support now is expanded in the following ways:

    • A stored procedure can produce any number of result sets. The number of columns and the data types of the columns need not be the same for all result sets.

    • The final values of OUT and INOUT parameters are available to the calling application after the procedure returns. These parameters are returned as an extra single-row result set following any result sets produced by the procedure itself. The row contains the values of the OUT and INOUT parameters in the order in which they are declared in the procedure parameter list.

    • A new C API function, mysql_stmt_next_result(), is available for processing stored procedure results. See Section 21.9.15, “C API Support for Prepared CALL Statements”.

    • The CLIENT_MULTI_RESULTS flag now is enabled by default. It no longer needs to be enabled when you call mysql_real_connect(). (This flag is necessary for executing stored procedures because they can produce multiple result sets.)

    For PREPARE and EXECUTE, placeholder support for OUT and INOUT parameters is now available. See Section 12.2.1, “CALL Syntax”. (Bug#11638, Bug#17898)

  • Three options were added to mysqldump make it easier to generate a dump from a slave server:

    (Bug#8368)

  • mysqladmin now allows the password value to be omitted following the password command. In this case, mysqladmin prompts for the password value, which enables you to avoid specifying the password on the command line. Omitting the password value should be done only if password is the final command on the mysqladmin command line. Otherwise, the next argument is taken as the password. (Bug#5724)

  • Some conversions between Japanese character sets are more efficient.

  • When the server detects MyISAM table corruption, it now writes additional information to the error log, such as the name and line number of the source file, and the list of threads accessing the table. Example: Got an error from thread_id=1, mi_dynrec.c:368. This is useful information to include in bug reports.

  • The TABLESPACES table has been added to INFORMATION_SCHEMA for tracking tablespace details.

  • Added the PARAMETERS table to INFORMATION_SCHEMA. The PARAMETERS table provides information about stored function and procedure parameters, and about return values for stored functions.

  • The maximum length of table comments was extended from 60 to 2048 characters. The maximum length of column comments was extended from 255 to 1024 characters. Index definitions now can include a comment of up to 1024 characters.

Bugs fixed:

  • Performance: Replication: When writing events to the binary log, transactional events (that is, events that operate on transactional tables) are written to a thread-specific transaction cache, which is then written to the binary log on commit. In order to handle nontransactional events, there was a lock taken on the binary log (when entering the function MYSQL_BIN_LOG::write()), even when the event was written to the transaction cache instead of the binary log, causing a major bottleneck in replication performance. (Bug#42757)

  • Security Fix: The server crashed if an account with the CREATE ROUTINE privilege but not the EXECUTE privilege attempted to create a stored procedure. (Bug#44798)

  • Security Enhancement: When the DATA DIRECTORY or INDEX DIRECTORY clause of a CREATE TABLE statement referred to a subdirectory of the data directory via a symlinked component of the data directory path, it was accepted, when for security reasons it should be rejected. (Bug#39277)

  • Incompatible Change: Replication: The --binlog_format system variable can no longer be set inside a transaction. In other words, the binary logging format can no longer be changed while a transaction is in progress. (Bug#47863)

  • Incompatible Change: For debug builds, wttempts to execute RESET statements within a transaction that had acquired metadata locks led to an assertion failure.

    As a result of this bug fix, RESET statements now cause an implicit commit. (Bug#51336)

  • Incompatible Change: A deadlock occurred for this sequence of events: Session 1 locked a table using LOCK TABLES; Session 2 dropped the database containing the table; Session 1 created any database.

    A consequence of this bug fix is that CREATE DATABASE is disallowed within a session that has an active LOCK TABLES statement. (Bug#49988)

  • Incompatible Change: For application compatibility reasons, when sql_auto_is_null is 1, MySQL converts auto_inc_col IS NULL to auto_inc_col = LAST_INSERT_ID(). However, this was being done regardless of whether the predicate was alone or at the top level. Now it occurs only when it is a single top-level predicate.

    In conjunction with this bug fix, the default value of the sql_auto_is_null system variable has been changed from 1 to 0, which may cause incompatibilities with existing applications. (Bug#41371)

  • Incompatible Change: The parser accepted illegal syntax in a FOREIGN KEY clause:

    • Multiple MATCH clauses.

    • Multiple ON DELETE clauses.

    • Multiple ON UPDATE clauses.

    • MATCH clauses specified after ON UPDATE or ON DELETE. In case of multiple redundant clauses, this leads to confusion, and implementation-dependent results.

    These illegal syntaxes are now properly rejected. Existing applications that used them will require adjustment. (Bug#34455)

  • Incompatible Change: The Locked thread state was equivalent to the Table lock state and has been removed. It no longer appears in SHOW PROCESSLIST output. (Bug#28870)

  • Incompatible Change: Several changes were made to the processing of multiple-table DELETE statements:

    • Statements could not perform cross-database deletes unless the tables were referred to without using aliases. This limitation has been lifted and table aliases now are allowed.

    • Previously, alias declarations could be given for tables elsewhere than in the table_references part of the syntax. This could lead to ambiguous statements that have unexpected results such as deleting rows from the wrong table. Example:

      DELETE FROM t1 AS a2 USING t1 AS a1 INNER JOIN t2 AS a2;
      

      Now alias declarations can be declared only in the table_references part. Elsewhere in the statement, alias references are allowed but not alias declarations.

    • Alias resolution was improved so that it is no longer possible to have inconsistent or ambiguous aliases for tables.

    Statements containing alias constructs that are no longer allowed must be rewritten. (Bug#27525)

    See also Bug#30234.

  • Incompatible Change: DROP TABLE now is allowed only if you have acquired a WRITE lock with LOCK TABLES, or if you hold no locks, or if the table is a TEMPORARY table.

    Previously, if other tables were locked, you could drop a table with a read lock or no lock, which could lead to deadlocks between clients. The new stricter behavior means that some usage scenarios will fail when previously they did not. (Bug#25858)

  • Incompatible Change: If a data definition language (DDL) statement occurred for a table that was being used by another session in an active transaction, statements could be written to the binary log in the wrong order. For example, this could happen if DROP TABLE occurred for a table being used in a transaction. This is now prevented by deferring release of metadata locks on tables used within a transaction until the transaction ends.

    This bug fix results in some incompatibilities with previous versions:

    • A table that is being used by a transaction within one session cannot be used in DDL statements by other sessions until the transaction ends.

    • FLUSH TABLES WITH READ LOCK blocks for active transactions that hold metadata locks until those transactions end. The same is true for attempts to set the global value of the read_only system variable.

    (Bug#989, Bug#39675)

  • Important Change: Replication: For an engine that supported only row-based replication, replication stopped with an error when executing row events.

    As part of the fix for this issue, the EXAMPLE storage engine is now changed so that it supports statement-based logging only. Previously, it supported row-based logging only. (Bug#39934)

  • Partitioning: When using a debug build of MySQL, if a query against a partitioned table having an index on one or more DOUBLE columns used that index, the server failed with an assertion. (Bug#45816)

  • Partitioning: The first time that a query against the INFORMATION_SCHEMA.TABLES table for partitioned tables using the ARCHIVE engine was run, it returned invalid data. If the server had been restarted since such a table had been created, or if the table had never actually been opened, its DATA_LENGTH was reported as 0 bytes. (The second and subsequent attempts to issue the same query returned the expected result.) (Bug#44622)

  • Partitioning: ALTER TABLE on a partitioned table caused unnecessary deadlocks. (Bug#43867)

    See also Bug#46654.

  • Partitioning: Attempting to drop a partitioned table from one connection while waiting for the completion of an ALTER TABLE that had been issued from a different connection, and that changed the storage engine used by the table, could cause the server to crash. (Bug#42438)

  • Partitioning: After attempting to create a duplicate index on a partitioned table (and having the attempt fail as expected), a subsequent attempt to create a new index on the table caused the server to hang. (Bug#40181)

  • Partitioning: When used on a partitioned table, ALTER TABLE produced the wrong error message when the name of a nonexistent storage engine was used in the ENGINE clause. (Bug#35765)

  • Partitioning: When one user was in the midst of a transaction on a partitioned table, a second user performing an ALTER TABLE on this table caused the server to hang. (Bug#34604)

  • Partitioning: Portions of the partitioning code were refactored in response to potential regression issues uncovered while working on the fix for Bug#31210. (Bug#32115)

    See also Bug#40281.

  • Replication: When using the row-based or mixed replication format with a debug build of the MySQL server, inserts into columns using the UTF32 character set on the master caused the slave to crash. (Bug#51787)

    See also Bug#51716.

  • Replication: When using the row-based or mixed replication format, column values using the UTF16 character set on the master were padded incorrectly on the slave. (Bug#51716)

    See also Bug#51787.

  • Replication: An issue internal to the code, first seen in Bug#49132 but not completely resolved in the fix for that bug, was removed. This should prevent similar issues to those in the previous bug with binlog_format changes following DDL statements.

    For developers working with the MySQL Server code: the public class variable THD::current_stmt_binlog_row_based was supposed to have been removed as part of the fix for Bug#39934, but was still present in the code. If a developer later tried to use this variable, it could cause the previous issues to re-occur, and possibly new ones to arise. The variable has now been removed; the previously added class functions THD::is_current_stmt_binlog_format_row(), THD::set_current_stmt_binlog_format_row(), and THD::clear_current_stmt_binlog_format_row() should be used instead. (Bug#51021)

  • Replication: Adding an index to a table on the master caused the slave to stop logging slow queries to the slow query log. (Bug#50620)

  • Replication: On a replication slave, a race condition between the I/O thread and FLUSH LOGS could crash the server. (Bug#50364)

  • Replication: If a CHANGE MASTER TO statement set MASTER_HEARTBEAT_PERIOD to 30 or higher, Slave_received_heartbeats did not increase on the slave. This caused the slave to reconnect before the time indicated by slave_net_timeout had elapsed.

    This issue affected big-endian 64-bit platforms such as Solaris/SPARC. (Bug#50296)

  • Replication: The error message given when trying to replicate (using statement-based mode) insertions into an AUTO_INCREMENT column by a stored function or a trigger was improved. (Bug#50192)

  • Replication: The server could deadlock when FLUSH LOGS was executed concurrently with DML statements. To fix this problem, nontransactional changes are now always flushed before transactional changes. (Bug#50038)

  • Replication: Metadata for GEOMETRY fields was not properly stored by the slave in its definitions of tables. (Bug#49836)

    See also Bug#48776.

  • Replication: Column length information generated by InnoDB did not match that generated by MyISAM, which caused invalid metadata to be written to the binary log when trying to replicate BIT columns. (Bug#49618)

  • Replication: Statement-based replication of user variables having numeric data types did not always work correctly. (Bug#49562)

  • Replication: When using the semi-synchronous replication plugin on Windows, the wait time calculated when the master was waiting for reply from the slave was incorrect. In addition, when the wait time was less than the current time, the master did not wait for a reply at all.

    This issue was caused by the fact that a different internal function was used to get current time by the plugin on Windows as opposed to other platforms, and this function was not correctly implemented. Now the Windows version of the plugin uses the same function as other platforms for this purpose. (Bug#49557)

  • Replication: Due to a change in the format of the information used by the slave to connect to the master, which could cause to reject connection attempts to older masters by newer slaves. (Bug#49259)

    This regression was introduced by Bug#13963.

  • Replication: When using row-based logging, a failing INSERT...SELECT statement on a nontransactional table was not flagged correctly, such that, if a rollback was requested and no other nontransactional table had been updated, nothing was written to the binary log. (Bug#47175)

    See also Bug#40278.

  • Replication: When using row-based replication, the incomplete logging of a group of events involving both transaction and nontransactional tables could cause STOP SLAVE to hang. (Bug#45940)

    See also Bug#319, Bug#38205.

  • Replication: There were two related issues concerning handling of unsafe statements and setting of the binary logging format when there were open temporary tables on the master, and the existing replication format was row-based or mixed:

    1. When using binlog_format=ROW, and an unsafe statement was executed while there were open temporary tables on the master, the statement SET @@session.binlog_format = MIXED failed with the error Cannot switch out of the row-based binary log format when the session has open temporary tables.

    2. When using binlog_format=MIXED, and an unsafe statement was executed while there were open temporary tables on the master, the statement SET @@session.binlog_format = STATEMENT caused any subsequent DML statements to be written to the binary log using the row-based format instead of the statement-based format.

    (Bug#45855, Bug#45856)

  • Replication: Statements that updated AUTO_INCREMENT columns in multiple tables were logged using the row-based format when --binlog_format was set to MIXED, but did not cause an Unsafe statement warning to be generated when --binlog_format was set to STATEMENT. (Bug#45827)

    See also Bug#39934.

  • Replication: Even though INSERT DELAYED statements are unsafe for statement-based replication, they caused the statement only to be logged in row format when the binary logging format was MIXED, but did not cause a warning to be generated when the binary logging format was STATEMENT. (Bug#45825)

  • Replication: When using MIXED binary logging format, statements containing a LIMIT clause and occurring in stored routines were not written to the log as row events. (Bug#45785)

  • Replication: When using statement-based replication, database-level character sets were not always honored by the replication SQL thread. This could cause data inserted on the master using LOAD DATA to be replicated using the wrong character set.

    Note

    This was not an issue when using row-based replication.

    (Bug#45516)

  • Replication: STOP SLAVE did not flush the relay log or the master.info or relay-log.info files, which could lead to corruption if the server crashed. (Bug#44188)

  • Replication: Large transactions and statements could corrupt the binary log if the size of the cache (as set by max_binlog_cache_size) was not large enough to store the changes.

    Now, for transactions that do not fit into the cache, the statement is not logged, and the statement generates an error instead.

    For nontransactional changes that do not fit into the cache, the statement is also not logged — an incident event is logged after committing or rolling back any pending transaction, and the statement then raises an error.

    Note

    If a failure occurs before the incident event is written the binary log, the slave does not stop, and the master does not report any errors.

    (Bug#43929)

    See also Bug#37148.

  • Replication: On Windows, RESET MASTER failed in the event of a missing binlog file rather than issuing a warning and completing the rest of the statement. (Bug#42150, Bug#42218)

  • Replication: Executing the sequence of statements RESET SLAVE, RESET MASTER, and FLUSH LOGS, when binary log or relay log files listed in the index file could not be found, could cause the server to crash. This could happen, for example, when these files had been moved or deleted manually. (Bug#41902)

  • Replication: MySQL creates binary logs in a numbered sequence, with a maximum possible 4294967295 concurrent log files, 4294967295 being the maximum value for an unsigned long integer. However, binary log file extensions were turned into negative numbers once the variable used to hold the value reached the maximum value for a signed long integer (2147483647). Consequently, when the sequence value was incremented to the next (negative) number, this caused MySQL to try to create the file using a .000000 extension, causing the server to fail since this file already existed.

    Negative file extensions are now disallowed, and an error is returned when the limit is reached. In addition, FLUSH LOGS now also reports warnings to the user, if the extension number has reached the limit, and warnings are printed to the error log when the limit is approaching. (Bug#40611)

  • Replication: Issuing concurrent STOP SLAVE, START SLAVE, and RESET SLAVE statements using different connections caused the replication slave to crash. (Bug#38716)

    See also Bug#38715, Bug#44312.

  • Replication: A slave compiled using --with-libevent and run with --thread-handling=pool-of-threads could sometimes crash. (Bug#36929)

  • Replication: mysqlbinlog sometimes failed when trying to create temporary files; this was because it ignored the specified temp file directory and tried to use the system /tmp directory instead. (Bug#35546)

    See also Bug#35543.

  • Replication: A CHANGE MASTER TO statement with no MASTER_HEARTBEAT_PERIOD option failed to reset the heartbeat period to its default value. (Bug#34686)

  • Replication: Formerly, only slaves that had been started with the --report-hosts option were visible in the output of SHOW SLAVE HOSTS. Now, all slaves that are registered with the master appear in SHOW SLAVE HOSTS output. (Bug#13963)

    See also Bug#21132, Bug#21869.

  • mysqld_multi failed due to a syntax error in the script. (Bug#51468)

  • ALTER TABLE on a MERGE table that has been locked using LOCK TABLES ... WRITE incorrectly produced an ER_TABLE_NOT_LOCKED_FOR_WRITE error. (Bug#51240)

  • On some Unix/Linux platforms, an error during build from source could be produced, referring to a missing LT_INIT program. This is due to versions of libtool 2.1 and earlier. (Bug#51009)

  • Referring to a subquery result in a HAVING clause could produce incorrect results. (Bug#50995)

  • Use of filesort plus the join cache normally is preferred to a full index scan. But it was used even if the index is clustered, in which case, the clustered index scan can be faster. (Bug#50843)

  • For debug builds, SHOW BINARY LOGS caused an assertion to be raised if binary logging was not enabled. (Bug#50780)

  • Incorrect handling of BIT columns in temporary tables could lead to spurious duplicate-key errors. (Bug#50591)

  • An uninitialized hash table caused a crash when accessed. (Bug#50555)

  • The return value for calls to put information into the stored routine cache were not consistently checked, causing an assertion to be raised. (Bug#50412)

  • comp_err did not build on FreeBSD. (Bug#50362)

  • Full-text queries that used the truncation operator (*) could enter an infinite loop. (Bug#50351)

  • mysqld did not recognize most of the options given on the command line when it was compiled for 32-bit Solaris using the Sun Studio compiler. (Bug#50221)

  • mysql --show-warnings crashed if the server connection was lost. (Bug#49646)

  • For string-valued system variables containing multibyte characters, the byte length was used in contexts where the character length was more appropriate. (Bug#49645)

  • SHOW VARIABLES did not correctly display string-valued system variables that contained \0 characters. (Bug#49644)

  • MySQL program option-processing code incorrectly displayed some options when printing ambiguous-option errors. (Bug#49640)

  • Setting binlog_format to DEFAULT assigned a value different from the default. (Bug#49540)

  • mysqltest no longer lets you execute an SQL statement on a connection after doing a send command, unless you do a reap first. This was previously accepted but could produce unpredictable results. (Bug#49269)

  • Valgrind warnings for several logging messages were corrected. (Bug#49130)

  • For debug builds on Windows, warnings about incorrect use of debugging directives were written to the error log. The directives were rewritten to eliminate these messages. (Bug#49025)

  • On POSIX systems, calls to select() with a file descriptor set larger than FD_SETSIZE resulted in unpredictable I/O errors; for example, when a large number of tables required repair. (Bug#48929)

  • A dependent subquery containing COUNT(DISTINCT col_name)) could be evaluated incorrectly. (Bug#48920)

  • If IPv6 support in the operating system was turned off, mysqld crashed in network_init(). (Bug#48915)

  • Building MySQL on Fedora Core 12 64-bit failed, due to errors in comp_err. (Bug#48864)

  • If a stored function contained a RETURN statement with an ENUM value in the ucs2 character set, SHOW CREATE FUNCTION and SELECT DTD_IDENTIFIER FROM INFORMATION_SCHEMA.ROUTINES returned incorrect values. (Bug#48766)

  • An ARZ file missing from the database directory caused the server to crash. (Bug#48757)

  • If an INSERT DELAYED handler thread was killed by a connection, the error message was copied from the handler thread to the connection thread but not acted on, leading to an assert. (Bug#48725)

  • Concurrent execution of INSERT DELAYED and FLUSH TABLES could lead to deadlock. (Bug#48724)

  • If a prepared statement using a merged view referencing an INFORMATION_SCHEMA table was executed, no metadata lock of the view was taken. Consequently, it was possible for concurrent DDL statements on the view to execute and cause statements to be written in the wrong order to the binary log. (Bug#48315)

  • An aliasing violation in the C API could lead to a crash. (Bug#48284)

  • If REPAIR TABLE was used on a table already read-locked by LOCK TABLES, the repair mistakenly tried to upgrade the read lock to an exclusive lock, triggering an assertion. (Bug#48248)

  • FLUSH TABLES WITH READ LOCK could deadlock when executed against concurrent DDL statements for stored routines or account-management statements. (Bug#48210)

  • Slow CALL statements were not always logged to the slow query log because execution time for multiple-statement stored procedures was assessed incorrectly. (Bug#47905)

  • Failure to open a view with a nonexistent DEFINER was improperly handled and the server would crash later attempting to lock the view. (Bug#47734)

  • If a prepared statement used both a MERGE table and a stored function or trigger, execution sometimes failed with a No such table error. (Bug#47648)

  • CREATE VIEW raised an assertion if a temporary table existed with the same name as the view. (Bug#47635)

  • The assert could be raised if ALTER VIEW was used to alter a view (existing or nonexisting) and a temporary table with the same name already existed. (Bug#47335)

  • If a temporary table was created with the same name as a view referenced in a stored routine, routine execution could raise an assertion. (Bug#47313)

  • Selecting from the process list in the embedded server caused a crash. (Bug#47304)

    See also Bug#43733.

  • Programs did not exit if the option file specfied by --defaults-file was not found. (Bug#47216)

  • Attempts to print octal numbers with my_vsnprintf() could cause a crash. (Bug#47212)

  • Corrected a potential problem of unintended overwriting of files when the MY_DONT_OVERWRITE_FILE flag was used. (Bug#47126)

  • When HANDLER OPEN was attempted on a MERGE table, an error occurred because this is an unsupported operation, but locks could remain unreleased. (Bug#47098)

  • For debug builds, an assertion failure could result from concurrent execution of statements involving stored functions or triggers that were using several tables and DDL statements that affected those tables. (Bug#46748)

  • Deadlock occurred if one session was running a multiple-statement transaction that involved a single partitioned table and another session attempted to alter the table. (Bug#46654)

  • Selecting from a MERGE table with a corrupted child MyISAM table could cause a server crash when the server attempted to automatically repair the child table. (Bug#46610)

  • The server could crash attempting to flush privileges after receipt of a SIGHUP signal. (Bug#46495)

  • HANDLER OPEN followed by TRUNCATE TABLE could cause a server crash. (Bug#46452)

    See also Bug#20667.

  • If INSERT INTO tbl_name invoked a stored function that modified tbl_name, the server crashed. (Bug#46374)

  • HANDLER statements within a transaction that already holds metadata locks could lead to deadlocks. (Bug#46224)

  • Deadlock could occur for INFORMATION_SCHEMA queries when execution attempted to open a table or its .frm file. (Bug#46044)

  • For queries that used GROUP_CONCAT(DISTINCT ...), the value of max_heap_table_size was used for memory allocation, which could be excessive. Now the minimum of max_heap_table_size and tmp_table_size is used. (Bug#46018)

  • Improperly closing tables when INSERT DELAYED needed to reopen tables could cause an assertion failure. (Bug#45949)

    See also Bug#18484.

  • Grouping by a subquery in a query with a DISTINCT aggregate function led to incorrect and unordered grouping values. (Bug#45640)

  • For an IPv6-enabled MySQL server, privileges specified using standard IPv4 addresses for hosts were not matched (only IPv4-mapped addresses were handled correctly).

    As part of the fix for this bug, a new build option --disable-ipv6 has been introduced. Compiling MySQL with this option causes all IPv6-specific code in the server to be ignored.

    Important

    If the server has been compiled using --disable-ipv6, it is not able to resolve hostnames correctly when run in an IPv6 environment.

    (Bug#45606)

    See also Bug#38247, Bug#43006, Bug#45283, Bug#45584.

  • The hostname cache failed to work correctly. (Bug#45584)

    See also Bug#38247, Bug#43006, Bug#45283, Bug#45606.

  • A Windows Installation using the GUI installer would fail with:

    MySQL Server 5.1 Setup Wizard ended prematurely
    
    The wizard was interrupted before MySQL Server 5.1. could be completely installed.
    
    Your system has not been modified. To complete installation at another time, please run
    setup again.
    
    Click Finish to exit the wizard

    This was due to an step in the MSI installer that could fail to execute correctly on some environments. (Bug#45418)

  • Propagation of a large unsigned numeric constant in WHERE expressions could lead to incorrect results. This also affected EXPLAIN EXTENDED, which printed incorrect numeric constants in such transformed WHERE expressions. (Bug#45360)

  • There was no timeout for attempts to acquire metadata locks (for example, a DROP TABLE attempt for a table that was open in another transaction would not time out).

    To handle such situations, there is now a lock_wait_timeout system variable that specifies the timeout in seconds for attempts to acquire metadata locks. The allowed values range from 1 to 3153600 (1 year). The default is 3153600.

    This timeout applies to all statements that use metadata locks. These include DML and DDL operations on tables, views, stored procedures, and stored functions, as well as LOCK TABLES, FLUSH TABLES WITH READ LOCK, and HANDLER statements.

    The timeout value applies separately for each metadata lock attempt. A given statement can require more than one lock, so it is possible for the statement to block for longer than the lock_wait_timeout value before reporting a timeout error. When lock timeout occurs, ER_LOCK_WAIT_TIMEOUT is reported.

    lock_wait_timeout does not apply to delayed inserts, which always execute with a timeout of 1 year. This is done to avoid unnecessary timeouts because a session that issues a delayed insert receives no notification of delayed insert timeouts.

    In addition, the unused table_lock_wait_timeout system variable was removed. (Bug#45225)

  • Valgrind warnings about uninitialized variables in optimizer code were silenced. (Bug#45195)

  • Killing a delayed-insert thread could cause a server crash. (Bug#45067)

  • Execution of FLUSH TABLES or FLUSH TABLES WITH READ LOCK concurrently with LOCK TABLES resulted in deadlock. (Bug#45066)

  • The mysql_real_connect() C API function only attempted to connect to the first IP address returned for a hostname. This could be a problem if a hostname mapped to multiple IP address and the server was not bound to the first one returned. Now mysql_real_connect() attempts to connect to all IPv4 or IPv6 addresses that a domain name maps to. (Bug#45017)

    See also Bug#47757.

  • Some plugins configured as mandatory could be disabled at server startup. (Bug#44691)

  • InnoDB took a shared row lock when executing SELECT statements inside a stored function as a part of a transaction using REPEATABLE READ. This prevented other transactions from updating the row. (Bug#44613)

  • MySQL Server allowed the creation of a merge table based on views but crashed when attempts were made to read from that table. The following example demonstrates this:

    #Create a test table
    CREATE TABLE tmp (id int, c char(2));                                           
    
    #Create two VIEWs upon it
    CREATE VIEW v1 AS SELECT * FROM tmp;                                            
    CREATE VIEW v2 AS SELECT * FROM tmp;                                            
    
    #Finally create a MERGE table upon the VIEWs
    CREATE TABLE merge (id int, c char(2))
    ENGINE=MERGE UNION(v1, v2);
    
    #Reading from the merge table lead to a crash
    SELECT * FROM merge;

    The final line of the code generated the crash. (Bug#44040)

  • A natural join of INFORMATION_SCHEMA tables could cause an assertion failure. (Bug#43834)

  • When used in conjunction with LOCK TABLES, FLUSH TABLE tbl_list waited for all tables with old versions to clear from the table definition list, rather than only the named tables. (Bug#43685)

  • HANDLER statements are now disallowed if a table lock has been acquired with LOCK TABLES. (Bug#43272)

  • In the embedded server, stack overflow checks for recursive stored procedure calls did not work and stack overflow could occur. (Bug#43201)

  • The IPv6 loopback address ::1 was interpeted as a hostname rather than a numeric IP address.

    In addition, the IPv6-enabled server on Windows interpeted the hostname localhost as ::1 only, which failed to match the default root@127.0.0.1 entry in the mysql.user privilege table. (Bug#43006)

    See also Bug#38247, Bug#45283, Bug#45584, Bug#45606.

  • The server could crash if an attempt to open a MERGE table child MyISAM table failed. (Bug#42862)

  • Comparison of TIME values could lose the sign of operands. (Bug#42664)

  • MAKETIME() could lose the sign of negative arguments. (Bug#42662)

  • SEC_TO_TIME() could lose the sign of negative arguments. (Bug#42661)

  • Concurrent execution of a LOCK TABLES ... READ statement and DML statements affecting the same InnoDB table for debug builds of MySQL server might lead to Found lock of type 6 that is write and read locked warnings in the error log. (Bug#42147)

  • Setting key_buffer_size to a negative value could lead to very large allocations. Now an error occurs. (Bug#42103)

  • An assertion failure could occur if OPTIMIZE TABLE was started on an InnoDB table and the table was altered to a different storage engine during the optimization operation. (Bug#42074)

  • The state of a thread for the embedded server was always displayed as Writing to net, which is incorrect because there is no network connection for the embedded server. (Bug#41971)

  • The patch for Bug#10374 broke named-pipe and shared-memory connections on Windows. (Bug#41860)

  • Purging the stored routine cache could take a long time and render the server unresponsive. (Bug#41804)

  • The CSV engine did not parse '\X' characters when they occurred in unquoted fields. (Bug#40814)

  • When archive tables were joined on their primary keys, a query returned no result if the optimizer chose to use this index. (Bug#40677)

  • mysqld_safe did not treat dashes and underscores as equivalent in option names. Thanks to Erik Ljungstrom for the patch to fix this bug. (Bug#40368)

  • Threads were set to the Table lock state in such a way that use of this state by other threads to check for a lock wait was subject to a race condition. (Bug#39897)

  • Plugin shutdown could lead to an assertion failure caused by using an already destroyed mutex in the metadata locking subsystem. (Bug#39674)

  • Dropping a locked Maria table leads to an assertion failure. (Bug#39395)

  • Host name lookup failure could lead to a server crash. (Bug#39153)

  • flush_cache_records() did not correctly check for errors that should cause statement execution to stop, leading to a server crash. (Bug#39022)

  • Valgrind warnings that occurred for SHOW TABLE STATUS with InnoDB tables were silenced. (Bug#38479)

  • An IPv6-enabled MySQL server did not resolve the IP addresses of incoming connections correctly, with the result that a connection that attempted to match any privilege table entries using fully-qualified domain names for hostnames or hostnames using wildcards were dropped. (Bug#38247)

    See also Bug#43006, Bug#45283, Bug#45584, Bug#45606.

  • Concurrent execution of ALTER TABLE for InnoDB table and a transaction that tried to read and then update the table could result in a deadlock between table-level locks and InnoDB row locks, which was detected only after the innodb_lock_wait_timeout timeout occurred. (Bug#37346)

  • Previously, statements inside a stored program did not clear the warning list. For example, warnings or errors generated by statements within a trigger or stored function would be accumulated and added to the message list for the statement that activated the trigger or invoked the function, “polluting” the output of SHOW WARNINGS or SHOW ERRORS for the outer statement. Normally, messages for a statement that can generate messages replace messages from the previous such statement. The effect was that a statement could have a different effect on the message list depending on whether it executed inside or outside of a stored program.

    Now within a stored program, successive statements that can generate messages update the message list and replace messages from the previous such statement. Only messages from the last of these statements is copied to the message list for the outer statement. (Bug#36649)

  • myisampack --join did not create the destination table .frm file. (Bug#36573)

  • The parser incorrectly allowed MySQL error code 0 to be specified for a condition handler. (This is incorrect because the condition must be a failure condition and 0 indicates success.) (Bug#36510)

  • When parsing or formatting interval values of DAY_MICROSECOND type, fractional seconds were not handled correctly when more-significant fields were implied or omitted. (Bug#36466)

  • mysql_install_db failed if run as root and the root directory (/) was not writable. (Bug#36462)

  • mysql_stmt_prepare() did not reset the list of messages (those messages available via SHOW WARNINGS). (Bug#36004)

  • mysqlbinlog left temporary files on the disk after shutdown, leading to the pollution of the temporary directory, which eventually caused mysqlbinlog to fail. This caused problems in testing and other situations where mysqlbinlog might be invoked many times in a relatively short period of time. (Bug#35543)

  • When building MySQL when using a different target directory (for example using the VPATH environment variable), the build of the embedded readline component would fail. (Bug#35250)

  • String-valued system variables could be assigned literal values, but could not be assigned values using expressions. Now expressions are legal. (Bug#34883, Bug#46314)

  • The sql_mode system variable could be assigned the illegal value of '?'. (Bug#34834)

  • Some system variables could not be assigned the value DEFAULT to assign their default value. (Bug#34829, Bug#34878)

  • Compiling MySQL on FreeBSD would fail due to missing definitions for certain network constants. (Bug#34292)

  • Creation of a temporary BLOB or TEXT column could create a column with the wrong maximum length. (Bug#33969)

  • INSERT INTO ... VALUES(DEFAULT) failed to insert the correct value for ENUM columns. For MyISAM tables, an empty value was inserted. For CSV tables, the table became corrupt. (Bug#33717)

  • When read_only was enabled, the server incorrectly prevented data modifications to TEMPORARY tables belonging to transactional storage engines such as InnoDB. (Bug#33669)

  • Constant expressions in WHERE, HAVING, or ON clauses were not cached, but were evaluated for each row. This caused a slowdown of query execution, especially if constant user-defined functions or stored functions were used. (Bug#33546)

  • The parser accepted an INTO clause in nested SELECT statements, which is invalid because such statements must return their results to the outer context. (Bug#33204)

  • Killing a statement that invoked a stored function could return an incorrect error message indicating table corruption rather than that the statement had been interrupted. (Bug#32140)

  • Occurrence of an error within a stored routine did not always cause immediate statement termination. (Bug#31881)

  • For DROP FUNCTION db_name.func_name (that is, when the function name is qualified with the database name), the statement should apply only to a stored function named func_name in the given database. However, if a UDF with the same name existed, the statement dropped the UDF instead. (Bug#31767)

  • Concurrent statements using a stored function and DROP FUNCTION for that function could break statement-based replication. (Bug#30977)

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

    See also Bug#12860.

  • ALTER TABLE could not be used to add columns to a table if the table had an index on a utf8 column with a TEXT data type. (Bug#26180)

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

  • Some system variables displayed by SHOW VARIABLES could not be selected using SELECT @@{GLOBAL,SESSION}.var_name. (Bug#25430)

  • Statements to create, alter, or drop a view were not waiting for completion of statements that were using the view, which led to incorrect sequences of statements in the binary log when statement-based logging was enabled. (Bug#25144)

  • Previously, the server handled character data types for a stored routine parameter, local routine variable created with DECLARE, or stored function return value as follows: If the CHARACTER SET attribute was present, the COLLATE attribute was not supported, so the character set's default collation was used. (This includes use of BINARY, which in this context specifies the binary collation of the character set.) If there was no CHARACTER SET attribute, the database character set and its default collation were used.

    Now for character data types, if there is a CHARACTER SET attribute in the declaration, the specified character set and its default collation is used. If the COLLATE is also present, that collation is used rather than the default collation. If there is no CHARACTER SET attribute, the database character set and collation in effect at routine creation time are used. (The database character set and collation are given by the value of the character_set_database and collation_database system variables.) (Bug#24690)

  • Data truncated for column col_num at row row_num warnings were generated for some (constant) values that did not have too high precision. (Bug#24541)

  • A statement that caused a circular wait among statements did not return a deadlock error. Now the server detects deadlock and returns ER_LOCK_DEADLOCK. (Bug#22876)

  • Several data-modification statements were not being counted toward the MAX_UPDATES_PER_HOUR user resource limit. (Bug#21793)

  • When inserting an extraordinarly large value into a DOUBLE column, the value could be truncated in such a way that the new value cannot be reloaded manually or from the output of mysqldump. (Bug#21497)

  • The value of sql_slave_skip_counter was empty when displayed by SHOW VARIABLES or INFORMATION_SCHEMA.GLOBAL_VARIABLES. (Bug#20413, Bug#37187)

  • For INSERT DELAYED statements issued for a table while an ALTER TABLE operation on the table was in progress, the server could return a spurious Server shutdown in progress error. (Bug#18484)

    See also Bug#45949.

  • Delayed-insert threads were counted as connected but not as created, incorrectly leading to a Threads_connected value greater than the Threads_created value. (Bug#17954)

  • The character set was not being properly initialized for CAST() with a type such as CHAR(2) BINARY, which resulted in incorrect results or a server crash. (Bug#17903)

  • Stored procedure exception handlers were catching fatal errors (such as out of memory errors), which could cause execution not to stop to due a continue handler. Now fatal errors are not caught by exception handlers and a fatal error is returned to the client. (Bug#15192)

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

  • For CREATE TABLE, the parser did not enforce that parentheses were present in a CHECK (expr) clause; now it does. The parser did not enforce that CONSTRAINT [symbol] without a following CHECK clause was illegal; now it does. (Bug#11714, Bug#35578, Bug#38696)

  • If a connection was waiting for a GET_LOCK() lock or a SLEEP() call, and the connection aborted, the server did not detect this and thus did not close the connection. This caused a waste of system resources allocated to dead connections. Now the server checks such a connection every five seconds to see whether it has been aborted. If so, the connection is killed (and any lock request is aborted). (Bug#10374)

  • perror did not work for errors described in the sql/share/errmsg.txt file. (Bug#10143)

  • The grammar for GROUP BY, when used with WITH CUBE or WITH ROLLUP, caused a conflict with the grammar for view definitions that included WITH CHECK OPTION. (Bug#9801)

  • For the DIV operator, incorrect results could occur for noninteger operands that exceed BIGINT range. Now, if either operand has a noninteger type, the operands are converted to DECIMAL and divided using DECIMAL arithmetic before converting the result to BIGINT. If the result exceeds BIGINT range, an error occurs. (Bug#8457)

  • Labels in stored routines did not work if the character set was not latin1. (Bug#7088)

C.1.2. Changes in MySQL 5.5.2 (12 February 2010)

InnoDB Plugin Notes:

  • This release includes InnoDB Plugin 1.0.6. This version is considered of Release Candidate (RC) quality.

Functionality added or changed:

  • Replication: Introduced the --binlog-direct-non-transactional-updates server option. This option causes updates using the statement-based logging format to tables using nontransactional engines to be written directly to the binary log, rather than to the transaction cache.

    Before using this option, be certain that you have no dependencies between transactional and nontransactional tables. A statement that both selects from an InnoDB table and inserts into a MyISAM table is an example of such a dependency. For more information, see Section 16.1.3.4, “Binary Log Options and Variables”. (Bug#46364)

    See also Bug#28976, Bug#40116.

Bugs fixed:

  • Performance: The method for comparing INFORMATION_SCHEMA names and database names was nonoptimal and an improvement was made: When the database name length is already known, a length check is made first and content comparison skipped if the lengths are unequal. (Bug#49501)

  • Performance: The MD5() and SHA1() functions had excessive overhead for short strings. (Bug#49491)

  • Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us with a proof-of-concept script that allowed us to reproduce this bug. (Bug#50227, CVE-2009-4484)

  • Incompatible Change: In plugin.h, the MYSQL_REPLICATION_PLUGIN symbol was out of synchrony with its value in MySQL 6.0 because the lower-valued MYSQL_AUDIT_PLUGIN was not present. To correct this, MYSQL_AUDIT_PLUGIN has been added in MySQL 5.5, changing the value of MYSQL_REPLICATION_PLUGIN from 5 to 6. Attempts to load the audit plugin produce an error occurs because only the MYSQL_AUDIT_PLUGIN symbol was added, not the audit plugin itself. This error will go away when the audit plugin is added to MySQL 5.5. Replication plugins from earlier 5.5.x releases must be recompiled against the current release before they will work with the current release. (Bug#49894)

  • Important Change: Replication: The RAND() function is now marked as unsafe for statement-based replication. Using this function now generates a warning when binlog_format=STATEMENT and causes the the format to switch to row-based logging when binlog_format=MIXED.

    This change is being introduced because, when RAND() was logged in statement mode, the seed was also written to the binary log, so the replication slave generated the same sequence of random numbers as was generated on the master. While this could make replication work in some cases, the order of affected rows was still not guaranteed when this function was used in statements that could update multiple rows, such as UPDATE or INSERT ... SELECT; if the master and the slave retrieved rows in different order, they began to diverge. (Bug#49222)

  • Partitioning: When used on partitioned tables, the records_in_range handler call checked all partitions, rather than the unpruned partitions only. (Bug#48846)

    See also Bug#37252, Bug#47261.

  • Partitioning: When an ALTER TABLE ... REORGANIZE PARTITION statement on an InnoDB table failed due to innodb_lock_wait_timeout expiring while waiting for a lock, InnoDB did not clean up any temporary files or tables which it had created. Attempting to reissue the ALTER TABLE statement following the timeout could lead to storage engine errors, or possibly a crash of the server. (Bug#47343)

  • Replication: FLUSH LOGS could in some circumstances crash the server. This occurred because the I/O thread could concurrently access the relay log I/O cache while another thread was performing the FLUSH LOGS, which closes and reopens the relay log and, while doing so, initializes (or re-initializes) its I/O cache. This could cause problems if some other thread (in this case, the I/O thread) is accessing it at the same time.

    Now the thread performing the FLUSH LOGS takes a lock on the relay log before actually flushing it. (Bug#50364)

  • Replication: With semisynchronous replication, memory allocated for handling transactions could be freed while still in use, resulting in a server crash. (Bug#50157)

  • Replication: In some cases, inserting into a table with many columns could cause the binary log to become corrupted. (Bug#50018)

    See also Bug#42749.

  • Replication: When using row-based replication, setting a BIT or CHAR column of a MyISAM table to NULL, then trying to delete from the table, caused the slave to fail with the error Can't find record in table. (Bug#49481, Bug#49482)

  • Replication: A LOAD DATA INFILE statement that loaded data into a table having a column name that had to be escaped (such as `key` INT) caused replication to fail when logging in mixed or statement mode. In such cases, the master wrote the LOAD DATA event into the binary log without escaping the column names. (Bug#49479)

    See also Bug#47927.

  • Replication: When logging in row-based mode, DDL statements are actually logged as statements; however, statements that affected temporary tables and followed DDL statements failed to reset the binary log format to ROW, with the result that these statements were logged using the statement-based format. Now the state of binlog_format is restored after a DDL statement has been written to the binary log. (Bug#49132)

  • Replication: Spatial data types caused row-based replication to crash. (Bug#48776)

  • Replication: When using row-based logging, the statement CREATE TABLE t IF NOT EXIST ... SELECT was logged as CREATE TEMPORARY TABLE t IF NOT EXIST ... SELECT when t already existed as a temporary table. This was caused by the fact that the temporary table was opened and the results of the SELECT were inserted into it when a temporary table existed and had the same name.

    Now, when this statement is executed, t is created as a base table, the results of the SELECT are inserted into it — even if there already exists a temporary table having the same name — and the statement is logged correctly. (Bug#47418)

    See also Bug#47442.

  • Replication: Due to a change in the size of event representations in the binary log, when replicating from a MySQL 4.1 master to a slave running MySQL 5.0.60 or later, the START SLAVE UNTIL statement did not function correctly, stopping at the wrong position in the log. Now the slave detects that the master is using the older version of the binary log format, and corrects for the difference in event size, so that the slave stops in the correct position. (Bug#47142)

  • Replication: Manually removing entries from the binary log index file on a replication master could cause the server to repeatedly send the same binary log file to slaves. (Bug#28421)

  • The SSL certificates in the test suite were about to expire. They have been updated with expiration dates in the year 2015. (Bug#50642)

  • SPATIAL indexes were allowed on columns with non-spatial data types, resulting in a server crash for subsequent table inserts. (Bug#50574)

  • Index prefixes could be specified with a length greater than the associated column, resulting in a server crash for subsequent table inserts. (Bug#50542)

  • Use of loose index scan optimization for an aggregate function with DISTINCT (for example, COUNT(DISTINCT)) could produce incorrect results. (Bug#50539)

  • The printstack function does not exist on Solaris 8 or earlier, which would lead to a compilation failure. (Bug#50409)

  • A user could see tables in INFORMATION_SCHEMA.TABLES without appropriate privileges for them. (Bug#50276)

  • Debug output for join structures was garbled. (Bug#50271)

  • The server crashed when an InnoDB background thread attempted to write a message containing a partitioned table name to the error log. (Bug#50201)

  • Within a stored routine, selecting the result of CONCAT_WS() with a routine parameter argument into a user variable could return incorrect results. (Bug#50096)

  • The filesort sorting method applied to a CHAR(0) column could lead to a server crash. (Bug#49897)

  • EXPLAIN EXTENDED UNION ... ORDER BY caused a crash when the ORDER BY referred to a nonconstant or full-text function or a subquery. (Bug#49734)

  • Some prepared statements could raise an assertion when re-executed. (Bug#49570)

  • sql_buffer_result had an effect on non-SELECT statements, contrary to the documentation. (Bug#49552)

  • In some cases a subquery need not be evaluated because it returns only aggregate values that can be calculated from table metadata. This sometimes was not handled by the enclosing subquery, resulting in a server crash. (Bug#49512)

  • Mixing full-text searches and row expressions caused a crash. (Bug#49445)

  • Creating or dropping a table with 1023 transactions active caused an assertion failure. (Bug#49238)

  • mysql-test-run.pl now recognizes the MTR_TESTCASE_TIMEOUT, MTR_SUITE_TIMEOUT, MTR_SHUTDOWN_TIMEOUT, and MTR_START_TIMEOUT environment variables. If they are set, their values are used to set the --testcase-timeout, --suite-timeout, --shutdown-timeout, and --start-timeout options, respectively. (Bug#49210)

  • Several strmake() calls had an incorrect length argument (too large by one). (Bug#48983)

  • On Fedora 12, strmov() did not guarantee correct operation for overlapping source and destination buffer. Calls were fixed to use an overlap-safe version instead. (Bug#48866)

  • With one thread waiting for a lock on a table, if another thread dropped the table and created a new table with the same name and structure, the first thread would not notice that the table had been re-created and would try to used cached metadata that belonged to the old table but had been freed. (Bug#48157)

  • If an invocation of a stored procedure failed in the table-open stage, subsequent invocations that did not fail in that stage could cause a crash. (Bug#47649)

  • A crash occurred when a user variable that was assigned to a subquery result was used as a result field in a SELECT statement with aggregate functions. (Bug#47371)

  • When the mysql client was invoked with the --vertical option, it ignored the --skip-column-names option. (Bug#47147)

  • If innodb_force_recovery was set to 4 or higher, the server could crash when opening an InnoDB table containing an auto-increment column. MySQL versions 5.1.31 and later were affected. (Bug#46193)

  • The optimizer could continue to execute a query after a storage engine reported an error, leading to a server crash. (Bug#46175)

  • If EXPLAIN encountered an error in the query, a memory leak occurred. (Bug#45989)

  • A race condition on the privilege hash tables allowed one thread to try to delete elements that had already been deleted by another thread. A consequence was that SET PASSWORD or FLUSH PRIVILEGES could cause a crash. (Bug#35589, Bug#35591)

  • 1) In rare cases, if a thread was interrupted during a FLUSH PRIVILEGES operation, a debug assertion occurred later due to improper diagnostic area setup. 2) A KILL operation could cause a console error message referring to a diagnostic area state without first ensuring that the state existed. (Bug#33982)

  • ALTER TABLE with both DROP COLUMN and ADD COLUMN clauses could crash or lock up the server. (Bug#31145)

  • The Table_locks_waited waited variable was not incremented in the cases that a lock had to be waited for but the waiting thread was killed or the request was aborted. (Bug#30331)

C.1.3. Changes in MySQL 5.5.1 (04 January 2010)

When the publishing process for MySQL 5.5.1-m2 was already running, the MySQL team was informed about a security problem in the SSL connect area (a possibility to crash the server). The problem is caused by a buffer overflow in the yaSSL library. MySQL Servers using OpenSSL are not affected; it can only occur when SSL (using yaSSL) is enabled.

This problem is still under detailed investigation with the various versions, configurations, and platforms. When that has finished, the problem will be fixed as soon as possible, and new binaries for the affected versions will be released. However, building and testing these binaries in the various configurations on the various platforms will take some time.

The bug is tracked with a CVE ID already: CVE-2009-4484. The related bug report (Bug#50227) is currently marked private, it will be made public once the new binaries are out.

In the meantime, we repeat the general security hint: If it is not absolutely necessary that external machines can connect to your database instance, we recommend that the server's connection port be blocked by a firewall to prevent any such illegitimate accesses.

InnoDB Plugin Notes:

  • InnoDB Plugin has been upgraded to version 1.0.6. This version is considered of Release Candidate (RC) quality. The InnoDB Plugin Change History may contain information in addition to those changes reported here.

RPM Notes:

  • The version information in RPM package files has been changed:

    • The “level” field of a MySQL version number is now also included in the RPM version and in the package file name.

    • The RPM “release” value now starts to count from 1, not 0.

    For example, the generic x86 server RPM file of 5.5.1-m2 is named MySQL-server-5.5.1_m2-1.glibc23.i386.rpm. This improves consistency with other formats that also include the level (for this version: “m2”) in the file name. For example, the tar.gz filename is mysql-5.5.1-m2-linux-i686-glibc23.tar.gz. The different separator, underscore '_' for RPM, is required by the syntax of RPM.

Functionality added or changed:

  • Partitioning: The UNIX_TIMESTAMP() function is now supported in partitioning expressions using TIMESTAMP columns. For example, it now possible to create a partitioned table such as this one:

    CREATE TABLE t (c TIMESTAMP) 
    PARTITION BY RANGE ( UNIX_TIMESTAMP(c) ) (
        PARTITION p0 VALUES LESS THAN (631148400),
        PARTITION p1 VALUES LESS THAN (946681200),
        PARTITION p2 VALUES LESS THAN (MAXVALUE)
    );
    

    All other expressions involving TIMESTAMP values are now rejected with an error when attempting to create a new partitioned table or to alter an existing partitioned table.

    When accessing an existing partitioned table having a timezone-dependent partitioning function (where the table was using a previous version of MySQL), a warning rather than an error is issued. In such cases, you should fix the table. One way of doing this is to alter the table's partitioning expression so that it uses UNIX_TIMESTAMP(). (Bug#42849)

Bugs fixed:

  • Performance: When the query cache is fragmented, the size of the free block lists in the memory bins grows, which causes query cache invalidation to become slow. There is now a 50ms timeout for a SELECT statement waiting for the query cache lock. If the timeout expires, the statement executes without using the query cache. (Bug#39253)

    See also Bug#21074.

  • Incompatible Change: Replication: The file names for the semisynchronous plugins were prefixed with lib, unlike file names for other plugins. The file names no longer have a lib prefix.

    This change introduces an incompatibility if the plugins had been installed using the previous names. To handle this, uninstall the older version before installing the newer version. For example, use these statements for the master side plugins on Unix:

    mysql> UNINSTALL PLUGIN rpl_semi_sync_master;
    mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
    

    If you do not uninstall the older version first, attempting to install the newer version results in an error:

    mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
    ERROR 1125 (HY000): Function 'rpl_semi_sync_master' already exists
    

    For the slave side, similar statements apply:

    mysql> UNINSTALL PLUGIN rpl_semi_sync_slave;
    mysql> INSTALL PLUGIN rpl_semi_sync_slave SONAME 'semisync_slave.so';
    
  • Important Change: Replication: The following functions have been marked unsafe for statement-based replication:

    None of the functions just listed are guaranteed to replicate correctly when using the statement-based format, because they can produce different results on the master and the slave. The use of any of these functions while binlog_format is set to STATEMENT is logged with the warning, Statement is not safe to log in statement format. When binlog_format is set to MIXED, the binary logging format is automatically switched to the row-based format whenever one of these functions is used. (Bug#47995)

  • Partitioning: When SHOW CREATE TABLE was invoked for a table that had been created using the COLUMNS keyword or the TO_SECONDS() function, the output contained the wrong MySQL version number in the conditional comments. (Bug#49591)

  • Partitioning: A query that searched on a ucs2 column failed if the table was partitioned. (Bug#48737)

  • Partitioning: In some cases, it was not possible to add a new column to a table that had subpartitions. (Bug#48276)

  • Partitioning: SELECT COUNT(*) from a partitioned table failed when using the ONLY_FULL_GROUP_BY SQL mode. (Bug#46923)

    This regression was introduced by Bug#45807.

  • Partitioning: SUBPARTITION BY KEY failed with DEFAULT CHARSET=utf8. (Bug#45904)

  • Replication: When using row-based logging, TRUNCATE TABLE was written to the binary log even if the affected table was temporary, causing replication to fail. (Bug#48350)

  • Replication: A flaw in the implementation of the purging of binary logs could result in orphaned files being left behind in the following circumstances:

    • If the server failed or was killed while purging binary logs.

      If the server failed or was killed after creating of a new binary log when the new log file was opened for the first time.

    In addition, if the slave was not connected during the purge operation, it was possible for a log file that was in use to be removed; this could lead data loss and possible inconsistencies between the master and slave. (Bug#45292)

  • Replication: When using the STATEMENT or MIXED logging format, the statements LOAD DATA CONCURRENT LOCAL INFILE and LOAD DATA CONCURRENT INFILE were logged as LOAD DATA LOCAL INFILE and LOAD DATA LOCAL INFILE, respectively (in other words, the CONCURRENT keyword was omitted). As a result, when using replication with either of these logging modes, queries on the slaves were blocked by the replication SQL thread while trying to execute the affected statements. (Bug#34628)

  • Cluster Replication: When expire_logs_days was set, the thread performing the purge of the log files could deadlock, causing all binary log operations to stop. (Bug#49536)

  • For debug builds on Windows, SAFEMALLOC was defined inconsistently, leading to mismatches when using my_malloc() and my_free(). (Bug#49811)

  • The mysql.server script had incorrect shutdown logic. (Bug#49772)

  • The push_warning_printf() function was being called with an invalid error level MYSQL_ERROR::WARN_LEVEL_ERROR, causing an assertion failure. To fix the problem, MYSQL_ERROR::WARN_LEVEL_ERROR has been replaced by MYSQL_ERROR::WARN_LEVEL_WARN. (Bug#49638)

  • The result of comparison between nullable BIGINT and INT columns was inconsistent. (Bug#49517)

  • A Valgrind error in make_cond_for_table_from_pred() was corrected. Thanks to Sergey Petrunya for the patch to fix this bug. (Bug#49506)

  • When compiling on Windows, an error in the CMake definitions for InnoDB would cause the engine to be built incorrectly. (Bug#49502)

  • Incorrect cache initialization prevented storage of converted constant values and could produce incorrect comparison results. (Bug#49489)

  • Comparisons involving YEAR values could produce incorrect results. (Bug#49480)

    See also Bug#43668.

  • Valgrind warnings for CHECKSUM TABLE were corrected. (Bug#49465)

  • Specifying an index algorithm (such as BTREE) for SPATIAL or FULLTEXT indexes caused a server crash. These index types do not support algorithm specification, and it is now disallowed to do so. (Bug#49250)

  • The optimizer sometimes incorrectly handled conditions of the form WHERE col_name='const1' AND col_name='const2'. (Bug#49199)

  • Execution of DECODE() and ENCODE() could be inefficient because multiple executions within a single statement reinitialized the random generator multiple times even with constant parameters. (Bug#49141)

  • With binary logging enabled, REVOKE ... ON {PROCEDURE|FUNCTION} FROM ... could cause a crash. (Bug#49119)

  • The LIKE operator did not work correctly when using an index for a ucs2 column. (Bug#49028)

  • check_key_in_view() was missing a DBUG_RETURN in one code branch, causing a crash in debug builds. (Bug#48995)

  • If a query involving a table was terminated with KILL, a subsequent SHOW CREATE TABLE for that table caused a server crash. (Bug#48985)

  • Privileges for stored routines were ignored for mixed-case routine names. (Bug#48872)

    See also Bug#41049.

  • Building MySQL on Fedora Core 12 64-bit failed, due to errors in comp_err. (Bug#48864)

  • Concurrent ALTER TABLE operations on an InnoDB table could raise an assertion. (Bug#48782)

  • Incomplete reset of internal TABLE structures could cause a crash with eq_ref table access in subqueries. (Bug#48709)

  • During query execution, ranges could be merged incorrectly for OR operations and return an incorrect result. (Bug#48665)

  • The InnoDB Table Monitor reported the FLOAT and DOUBLE data types incorrectly. (Bug#48526)

  • Re-execution of a prepared statement could cause a server crash. (Bug#48508)

  • With row-based binary logging, the server crashed for statements of the form CREATE TABLE IF NOT EXISTS existing_view LIKE temporary_table. This occurred because the server handled the existing view as a table when logging the statement. (Bug#48506)

  • The error message for ER_UPDATE_INFO was subject to buffer overflow or truncation. (Bug#48500)

  • DISTINCT was ignored for queries with GROUP BY WITH ROLLUP and only const tables. (Bug#48475)

  • Loose index scan was inappropriately chosen for some WHERE conditions. (Bug#48472)

  • The server could crash and corrupt the tablespace if the InnoDB tablespace was configured with too small a value, or if many CREATE TEMPORARY TABLE statements were executed and the temporary file directory filled up with innodb_file_per_table enabled. (Bug#48469)

  • Parts of the range optimizer could be initialized incorrectly, resulting in Valgrind errors. (Bug#48459)

  • A bad typecast could cause query execution to allocate large amounts of memory. (Bug#48458)

  • SHOW BINLOG EVENTS could fail with a error: Wrong offset or I/O error. (Bug#48357)

  • Valgrind warnings related to binary logging of LOAD DATA INFILE statements were corrected. (Bug#48340)

  • On Windows, InnoDB could not be built as a statically linked library. (Bug#48317)

  • mysql_secure_installation did not work on Solaris. (Bug#48086)

  • When running mysql_secure_installation, the command would fail if the root password contained multiple spaces, \, # or quote characters. (Bug#48031)

  • MATCH IN BOOLEAN MODE searches could return too many results inside a subquery. (Bug#47930)

  • User-defined collations with an ID less then 256 were not initialized correctly when loaded and caused a server crash. (Bug#47756)

  • If a session held a global read lock acquired with FLUSH TABLES WITH READ LOCK, a lock for one table acquired with LOCK TABLES, and issued an INSERT DELAYED statement for another table, deadlock could occur. (Bug#47682)

  • The mysql client status command displayed an incorrect value for the server character set. (Bug#47671)

  • Connecting to a 4.1.x server from a 5.1.x or higher mysql client resulted in a memory-free error when disconnecting. (Bug#47655)

  • Queries containing GROUP BY ... WITH ROLLUP that did not use indexes could return incorrect results. (Bug#47650)

  • Assignment of a system variable sharing the same base name as a declared stored program variable in the same context could lead to a crash. (Bug#47627)

  • On Solaris, no stack trace was printed to the error log after a crash. (Bug#47391)

  • The first execution of STOP SLAVE UNTIL stopped too early. (Bug#47210)

  • The innodb_file_format_check system variable could not be set at runtime to DEFAULT or to the value of a user-defined variable. (Bug#47167)

  • After a binary upgrade to MySQL 5.1 from a MySQL 5.0 installation that contains ARCHIVE tables, accessing those tables caused the server to crash, even if you had run mysql_upgrade or CHECK TABLE ... FOR UPGRADE.

    To work around this problem, use mysqldump to dump all ARCHIVE tables before upgrading, and reload them into MySQL 5.1 after upgrading. The same problem occurs for binary downgrades from MySQL 5.1 to 5.0. (Bug#47012)

  • The IGNORE clause on a DELETE statement masked an SQL statement error that occurred during trigger processing. (Bug#46425)

  • Valgrind errors for InnoDB Plugin were corrected. (Bug#45992, Bug#46656)

  • The return value was not checked for some my_hash_insert() calls. (Bug#45613)

  • It was possible for init_available_charsets() not to initialize correctly. (Bug#45058)

  • GROUP BY on a constant (single-row) InnoDB table joined to other tables caused a server crash. (Bug#44886)

  • For a VARCHAR(N) column, ORDER BY BINARY(col_name) sorted using only the first N bytes of the column, even though column values could be longer than N bytes if they contained multibyte characters. (Bug#44131)

  • For YEAR(2) values, MIN(), MAX(), and comparisons could yield incorrect results. (Bug#43668)

  • Comparison with NULL values sometimes did not produce a correct result. (Bug#42760)

  • In debug builds, killing a LOAD XML INFILE statement raised an assertion.

    Implemented in the course of fixing this bug, mysqltest has a new send_eval command that combines the functionality of the existing send and eval commands. (Bug#42520)

  • The server could crash when attempting to access a non-conformant mysql.proc system table. For example, the server could crash when invoking stored procedure-related statements after an upgrade from MySQL 5.0 to 5.1 without running mysql_upgrade. (Bug#41726)

  • The mysql_upgrade command would create three additional fields to the mysql.proc table (character_set_client, collation_connection, and db_collation), but did not populate the fields with correct values. This would lead to error messages reported during stored procedure execution. (Bug#41569)

  • Use of InnoDB monitoring (SHOW ENGINE INNODB STATUS or one of the InnoDB Monitor tables) could cause a server crash due to invalid access to a shared variable in a concurrent environment. (Bug#38883)

  • When compressed MyISAM files were opened, they were always memory mapped, sometimes causing memory-swapping problems. To deal with this, a new system variable, myisam_mmap_size, was added to limit the amount of memory used for memory mapping of MyISAM files. (Bug#37408)

  • When running mysql_secure_installation on Windows, the command would fail to load a required module, Term::ReadKey, which was required for correct operation. (Bug#35106)

  • If the --log-bin server option was set to a directory name with a trailing component separator character, the basename of the binary log files was empty so that the created files were named .000001 and .index. The same thing occurred with the --log-bin-index, --relay-log, and --relay-log-index options. Now the server reports and error and exits. (Bug#34739)

  • If a comparison involved a constant value that required type conversion, the converted value might not be cached, resulting in repeated conversion and poorer performance. (Bug#34384)

  • Using the SHOW ENGINE INNODB STATUS statement when using partitions in InnoDB tables caused Invalid (old?) table or database name errors to be logged. (Bug#32430)

  • Output from mysql --html did not encode the <, >, or & characters. (Bug#27884)

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

    See also Bug#39253.

  • On some Windows systems, InnoDB could report Operating system error number 995 in a file operation due to transient driver or hardware problems. InnoDB now retries the operation and adds Retry attempt is made to the error message. (Bug#3139)

C.1.4. Changes in MySQL 5.5.0 (07 December 2009 Milestone 2)

Previously, MySQL development proceeded by including a large set of features and moving them over many versions within a release series through several stages of maturity (Alpha, Beta, and so forth). This development model had a disadvantage in that problems with only part of the code could hinder timely release of the whole. As you might have found when testing MySQL Server 6.0, alpha quality code could jeopardize the stability of the entire release. (One consequence of this was that MySQL Server 6.0 has been withdrawn for now.)

MySQL development now uses a milestone model. The move to this model provides for more frequent milestone releases, with each milestone proceeding through a small number of releases having a focus on a specific subset of thoroughly tested features. Following the releases for one milestone, development proceeds with the next milestone; that is, another small number of releases that focuses on the next small set of features, also thoroughly tested.

MySQL 5.5.0-m2 is the first release for Milestone 2. The new features of this milestone may be considered to be initially of beta quality. For subsequent Milestone 2 releases, we plan to use increasing version numbers (5.5.1 and higher) while continuing to employ the “-m2” suffix. For Milestone 3, we plan to change the suffix to “-m3”. Version designators with “-alpha” or “-beta” suffixes are no used.

You may notice that the MySQL 5.5.0 release is designated as Milestone 2 rather than Milestone 1. This is because MySQL 5.4 was actually designated as Milestone 1, although we had not yet begun referring to milestone numbers as part of version numbers at the time.

InnoDB Plugin Notes:

  • The InnoDB Plugin is included in MySQL 5.5 releases as the built-in version of InnoDB. The version of the InnoDB Plugin in this release is 1.0.5 and is considered of Release Candidate (RC) quality.

    The InnoDB Plugin offers new features, improved performance and scalability, enhanced reliability and new capabilities for flexibility and ease of use. Among the features of the InnoDB Plugin are “Fast index creation,” table and index compression, file format management, new INFORMATION_SCHEMA tables, capacity tuning, multiple background I/O threads, and group commit.

    For information about these features, see the InnoDB Plugin Manual at http://www.innodb.com/products/innodb_plugin/plugin-documentation. For general information about using InnoDB in MySQL, see Section 13.6, “The InnoDB Storage Engine”.

Functionality added or changed:

  • Incompatible Change: Dynamic plugins now must be linked against the libmysqlservices.a library (use -lmysqlservices). For an example showing what Makefile.am should look like, see Section 22.2.3.3, “Creating a Plugin Library”. (Bug#48461)

  • Incompatible Change: Several changes have been made regarding the language and character set of error messages:

    • The --language option for specifying the directory for the error message file is now deprecated. The new --lc-messages-dir and --lc-messages options should be used instead, and --language is handled as an alias for --lc-messages-dir.

    • The language system variable has been removed and replaced with the new lc_messages_dir and lc_messages system variables. lc_messages_dir has only a global value and is read only. lc_messages has global and session values and can be modified at runtime, so the error message language can be changed while the server is running, and individual clients each can have a different error message language by changing their session lc_messages value to a different locale name.

    • Error messages previously were constructed in a mix of character sets. This issue is resolved by constructing error messages internally within the server using UTF-8 and returning them to the client in the character set specified by the character_set_results system variable. The content of error messages therefore may in some cases differ from the messags returned previously.

    For more information, see Section 9.2, “Setting the Error Message Language”, and Section 9.1.6, “Character Set for Error Messages”.

    See also Bug#46218, Bug#46236.

  • Partitioning: New PARTITION BY RANGE COLUMNS(column_list) and PARTITION BY LIST COLUMNS(column_list) options are added for the CREATE TABLE and ALTER TABLE statements.

    A major benefit of RANGE COLUMNS and LIST COLUMNS partitioning is that they make it possible to define ranges or lists based on column values that use string, date, or datetime values.

    These new extensions also broaden the scope of partition pruning to provide better coverage for queries using comparisons on multiple columns in the WHERE clause, some examples being WHERE a = 1 AND b < 10 and WHERE a = 1 AND b = 10 AND c < 10.

    For more information, see Section 17.2.1, “RANGE Partitioning”, Section 17.2.2, “LIST Partitioning”, and Section 17.4, “Partition Pruning”.

  • Partitioning: A new ALTER TABLE option, TRUNCATE PARTITION, makes it possible to delete rows from one or more selected partitions only. Unlike the case with ALTER TABLE ... DROP PARTITION, ALTER TABLE ... TRUNCATE PARTITION merely deletes all rows from the specified partition or partitions, and does not change the definition of the table.

  • Partitioning: It is now possible to assign indexes on partitioned MyISAM tables to key caches using the CACHE INDEX and to preload such indexes into the cache using LOAD INDEX INTO CACHE statements. Cache assignment and preloading of indexes for such tables can be performed for one, several, or all partitions of the table.

    This functionality is supported for only those partitioned tables that employ the MyISAM storage engine.

  • Cluster Replication: Replication: A replication heartbeat mechanism has been added to facilitate monitoring. This provides an alternative to checking log files, making it possible to detect in real time when a slave has failed.

    Configuration of heartbeats is done via a new MASTER_HEARTBEAT_PERIOD = interval clause for the CHANGE MASTER TO statement (see Section 12.6.2.1, “CHANGE MASTER TO Syntax”); monitoring can be done by checking the values of the status variables Slave_heartbeat_period and Slave_received_heartbeats (see Section 5.1.7, “Server Status Variables”).

    The addition of replication heartbeats addresses a number of issues:

    (Bug#20435, Bug#29309, Bug#30932)

  • Replication: The global server variable sync_relay_log is introduced for use on replication slaves. Setting this variable to a nonzero integer value N causes the slave to synchronize the relay log to disk after every N events. Setting its value to 0 allows the operating system to handle synchronization of the file. The action of this variable, when enabled, is analogous to how the sync_binlog variable works with regard to binary logs on a replication master.

    The global server variables sync_master_info and sync_relay_log_info are introduced for use on replication slaves to control synchronization of, respectively, the master.info and relay.info files.

    In each case, setting the variable to a nonzero integer value N causes the slave to synchronize the corresponding file to disk after every N events. Setting its value to 0 allows the operating system to handle synchronization of the file instead.

    The actions of these variables, when enabled, are analogous to how the sync_binlog variable works with regard to binary logs on a replication master.

    An additional system variable relay_log_recovery is also now available. When enabled, this variable causes a replication slave to discard relay log files obtained from the replication master following a crash.

    These variables can also be set in my.cnf, or by using the --sync-relay-log, --sync-master-info, --sync-relay-log-info, and --relay-log-recovery server options.

    For more information, see Section 16.1.3.3, “Replication Slave Options and Variables”. (Bug#31665, Bug#35542, Bug#40337)

  • Replication: Because SHOW BINLOG EVENTS cannot be used to read events from relay log files, a new SHOW RELAYLOG EVENTS statement has been added for this purpose. (Bug#28777)

  • Replication: In circular replication, it was sometimes possible for an event to propagate such that it would be reapplied on all servers. This could occur when the originating server was removed from the replication circle and so could no longer act as the terminator of its own events, as normally happens in circular replication.

    In order to prevent this from occurring, a new IGNORE_SERVER_IDS option is introduced for the CHANGE MASTER TO statement. This option takes a list of replication server IDs; events having a server ID which appears in this list are ignored and not applied. For more information, see Section 12.6.2.1, “CHANGE MASTER TO Syntax”.

    In conjunction with the introduction of IGNORE_SERVER_IDS, SHOW SLAVE STATUS has a new field Replicate_Ignore_Server_Ids that displays information about ignored servers. (Bug#25998)

    See also Bug#27808.

  • Replication: MySQL now supports an interface for semisynchronous replication: A commit performed on the master side blocks before returning to the session that performed the transaction until at least one slave acknowledges that it has received and logged the events for the transaction. Semisynchronous replication is implemented through an optional plugin component. See Section 16.3.8, “Semisynchronous Replication”.

  • The InnoDB buffer pool is divided into two sublists: A new sublist containing blocks that are heavily used by queries, and an old sublist containing less-used blocks and from which candidates for eviction are taken. In the default operation of the buffer pool, a block when read in is loaded at the midpoint and then moved immediately to the head of the new sublist as soon as an access occurs. In the case of a table scan (such as performed for a mysqldump operation), each block read by the scan ends up moving to the head of the new sublist because multiple rows are accessed from each block. This occurs even for a one-time scan, where the blocks are not otherwise used by other queries. Blocks may also be loaded by the read-ahead background thread and then moved to the head of the new sublist by a single access. These effects can be disadvantageous because they push blocks that are in heavy use by other queries out of the new sublist to the old sublist where they become subject to eviction.

    InnoDB Plugin now provides two system variables that enable LRU algorithm tuning:

    • innodb_old_blocks_pct

      Specifies the approximate percentage of the buffer pool used for the old block sublist. The range of values is 5 to 95. The default value is 37 (that is, 3/8 of the pool).

    • innodb_old_blocks_time

      Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before it can be moved to the new sublist. The default value is 0: A block inserted into the old sublist moves immediately to the new sublist the first time it is accessed, no matter how soon after insertion the access occurs. If the value is greater than 0, blocks remain in the old sublist until an access occurs at least that many ms after the first access. For example, a value of 1000 causes blocks to stay in the old sublist for 1 second after the first access before they become eligible to move to the new sublist. See Section 7.4.6, “The InnoDB Buffer Pool”

    For additional information, see Section 7.4.6, “The InnoDB Buffer Pool”. (Bug#45015)

  • Two status variables have been added to SHOW STATUS output. Innodb_buffer_pool_read_ahead and Innodb_buffer_pool_read_ahead_evicted indicate the number of pages read in by the InnoDB read-ahead background thread, and the number of such pages evicted without ever being accessed, respectively. Also, the status variables Innodb_buffer_pool_read_ahead_rnd and Innodb_buffer_pool_read_ahead_seq status variables have been removed. (Bug#42885)

  • Columns that provide a catalog value in INFORMATION_SCHEMA tables (for example, TABLES.TABLE_CATALOG) now have a value of def rather than NULL. (Bug#35427)

  • The deprecated --default-table-type server option has been removed. (Bug#34818)

  • Previously, mysqldump would not dump the INFORMATION_SCHEMA database and ignored it if it was named on the command line. Now, mysqldump will dump INFORMATION_SCHEMA if it is named on the command line. Currently, this requires that the --skip-lock-tables (or --skip-opt) option be given. (Bug#33762)

  • Several undocumented C API functions were removed: mysql_manager_close(), mysql_manager_command(), mysql_manager_connect(), mysql_manager_fetch_line(), mysql_manager_init(), mysql_disable_reads_from_master(), mysql_disable_rpl_parse(), mysql_enable_reads_from_master(), mysql_enable_rpl_parse(), mysql_master_query(), mysql_master_send_query(), mysql_reads_from_master_enabled(), mysql_rpl_parse_enabled(), mysql_rpl_probe(), mysql_rpl_query_type(), mysql_set_master(), mysql_slave_query(), and mysql_slave_send_query(). (Bug#31952, Bug#31954)

  • Sinhala collations utf8_sinhala_ci and ucs2_sinhala_ci were added for the utf8 and ucs2 character sets. (Bug#26474)

  • If the value of the --log-warnings option is greater than 1, the server now writes access-denied errors for new connection attempts to the error log (for example, if a client user name or password is incorrect). (Bug#25822)

  • On WIndows, use of POSIX I/O interfaces in mysys was replaced with Win32 API calls (CreateFile(), WriteFile(), and so forth) and the default maximum number of open files has been increased to 16384. The maximum can be increased further by using the --open-files-limit=N option at server startup. (Bug#24509)

  • The TRADITIONAL SQL mode now includes NO_ENGINE_SUBSTITUTION. (Bug#21099)

  • MySQL now implements the SQL standard SIGNAL and RESIGNAL statements. See Section 12.8.8, “SIGNAL and RESIGNAL. (Bug#11661)

  • The undocumented, deprecated, and not useful SHOW COLUMN TYPES statement has been removed. (Bug#5299)

  • The FORMAT() function now supports an optional third parameter that enables a locale to be specified to be used for the result number's decimal point, thousands separator, and grouping between separators. Allowable locale values are the same as the legal values for the lc_time_names system variable (see Section 9.7, “MySQL Server Locale Support”). For example, the result from FORMAT(1234567.89,2,'de_DE') is 1.234.567,89. If no locale is specified, the default is 'en_US'.

  • The Greek locale 'el_GR' is now an allowable value for the lc_time_names system variable.

  • Previously, in the absence of other information, the MySQL client programs mysql, mysqladmin, mysqlcheck, mysqlimport, and mysqlshow used the compiled-in default character set, usually latin1.

    Now these clients can autodetect which character set to use based on the operating system setting, such as the value of the LANG or LC_ALL locale environment language on Unix system or the code page setting on Windows systems. For systems on which the locale is available from the OS, the client uses it to set the default character set rather than using the compiled-in default. Thus, users can configure the locale in their environment for use by MySQL clients. For example, setting LANG to ru_RU.KOI8-R causes the koi8r character set to be used. The OS character set is mapped to the closest MySQL character set if there is no exact match. If the client does not support the matching character set, it uses the compiled-in default. (For example, ucs2 is not supported as a connection character set.)

    Third-party applications that wish to use character set autodetection based on the OS setting can use the following mysql_options() call before connecting to the server:

    mysql_options(mysql,
                  MYSQL_SET_CHARSET_NAME,
                  MYSQL_AUTODETECT_CHARSET_NAME);
    

    See Section 9.1.4, “Connection Character Sets and Collations”.

  • mysql_upgrade now has an --upgrade-system-tables option that causes only the system tables to be upgraded. With this option, data upgrades are not performed.

  • The CREATE TABLESPACE privilege has been introduced. This privilege exists at the global (superuser) level and enables you to create, alter, and drop tablespaces and logfile groups.

  • The server now supports a Debug Sync facility for thread synchronization during testing and debugging. To compile in this facility, configure MySQL with the --enable-debug-sync option. The debug_sync system variable provides the user interface Debug Sync. mysqld and mysql-test-run.pl support a --debug-sync-timeout option to enable the facility and set the default synchronization point timeout.

  • Added the TO_SECONDS() function, which converts a date or datetime value to a number of seconds since the year 0.

  • Parser performance was improved for identifier scanning and conversion of ASCII string literals.

  • The LOAD XML INFILE statement was added. This statement makes it possible to read data directly from XML files into database tables. For more information, see Section 12.2.7, “LOAD XML Syntax”.

Bugs fixed:

  • Performance: The server unnecessarily acquired a query cache mutex even with the query cache disabled, resulting in a small performance decrement which could show up as threads often in state “invalidating query cache entries (table)”, particularly on a replication slave with row-based replication. Now if the server is started with query_cache_type set to 0, it does not acquire the query cache mutex. This has the implication that the query cache cannot be enabled at runtime. (Bug#38551)

  • Performance: The InnoDB adaptive hash latch is released (if held) for several potentially long-running operations. This improves throughput for other queries if the current query is removing a temporary table, changing a temporary table from memory to disk, using CREATE TABLE ... SELECT, or performing a MyISAM repair on a table used within a transaction. (Bug#32149)

  • Important Change: Security Fix: It was possible to circumvent privileges through the creation of MyISAM tables employing the DATA DIRECTORY and INDEX DIRECTORY options to overwrite existing table files in the MySQL data directory. Use of the MySQL data directory in DATA DIRECTORY and INDEX DIRECTORY is now disallowed. This is now also true of these options when used with partitioned tables and individual partitions of such tables. (Bug#32167, CVE-2008-2079)

    See also Bug#39277.

  • Security Fix: MySQL clients linked against OpenSSL can be tricked not to check server certificates. (Bug#47320, CVE-2009-4028)

  • Security Fix: The server crashed if an account without the proper privileges attempted to create a stored procedure. (Bug#44658)

  • Incompatible Change: For system variables that take values of ON or OFF, OF was accepted as a legal variable. Now system variables that take “enumeration” values must be assigned the full value. This affects some other variables that previously could be assigned using unambiguous prefixes of allowable values, such as tx_isolation. (Bug#34828)

  • Incompatible Change: In binary installations of MySQL, the supplied binary-configure script would start and configure MySQL, even when command help was requested with the --help command-line option. The --help, if provided, will no longer start and install the server. (Bug#30954)

  • Incompatible Change: Access privileges for several statements are more accurately checked:

    (Bug#27145)

  • Important Change: Replication: MyISAM transactions replicated to a transactional slave left the slave in an unstable condition. This was due to the fact that, when replicating from a nontransactional storage engine to a transactional engine with autocommit turned off, no BEGIN and COMMIT statements were written to the binary log; thus, on the slave, a never-ending transaction was started.

    The fix for this issue includes enforcing autocommit mode on the slave by replicating all autocommit=1 statements from the master. (Bug#29288)

  • Important Change: Replication: The CHANGE MASTER TO statement required the value for RELAY_LOG_FILE to be an absolute path, while the MASTER_LOG_FILE path could be relative.

    The inconsistent behavior is resolved by allowing 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.6.2.1, “CHANGE MASTER TO Syntax”. (Bug#12190)

  • Important Change: An option that requires a value, when specified in an option file without a value, was assigned the text of the next line in the file as the value. Now, if you fail to specify a required value in an option file, the server aborts with an error.

    This change does not effect how options are handled by the server when they are used on the command line. For example, starting the server using mysqld_safe --relay-log --relay-log-index & causes the server to create relay log files named --relay-log-index.000001, --relay-log-index.000002, and so on, because the --relay-log option expects an argument. (Bug#25192)

  • Partitioning: An ALTER TABLE ... ADD PARTITION statement that caused open_files_limit to be exceeded led to a crash of the MySQL server. (Bug#46922)

    See also Bug#47343.

  • Partitioning: When performing an INSERT ... SELECT into a partitioned table, read_buffer_size bytes of memory were allocated for every partition in the target table, resulting in consumption of large amounts of memory when the table had many partitions (more than 100).

    This fix changes the method used to estimate the buffer size required for each partition and limits the total buffer size to a maximum of approximately 10 times read_buffer_size. (Bug#45840)

  • Partitioning: The cardinality of indexes on partitioned tables was calculated using the first partition in the table, which could result in suboptimal query execution plans being chosen. Now the partition having the most records is used instead, which should result in better use of indexes and thus improved performance of queries against partitioned tables in many if not most cases. (Bug#44059)

  • Partitioning: Truncating a partitioned MyISAM table did not reset the AUTO_INCREMENT value. (Bug#35111)

  • Partitioning: For partitioned tables with more than ten partitions, a full table scan was used in some cases when only a subset of the partitions were needed. (Bug#33730)

  • Replication: When using statement-based or mixed-format replication, the database name was not written to the binary log when executing a LOAD DATA statement. This caused problems when the table being loaded belonged to a database other than the current database; data could be loaded into the wrong table (if a table having the same name existed in the current database) or replication could fail (if no table having that name existed in the current database). Now a table referenced in a LOAD DATA statement is always logged using its fully qualified name when the database to which it belongs is not the current database. (Bug#48297)

  • Replication: When a session was closed on the master, temporary tables belonging to that session were logged with the wrong database names when either of the following conditions was true:

    1. The length of the name of the database to which the temporary table belonged was greater than the length of the current database name.

    2. The current database was not set.

    (Bug#48216)

    See also Bug#46861, Bug#48297.

  • Replication: When using row-based replication, changes to nontransactional tables that occurred early in a transaction were not immediately flushed upon committing a statement. This behavior could break consistency since changes made to nontransactional tables become immediately visible to other connections. (Bug#47678)

    See also Bug#47287, Bug#46864, Bug#43929, Bug#46129.

  • Replication: When mysqlbinlog --verbose was used to read a binary log that had been recorded using the row-based format, the output for events that updated some but not all columns of tables was not correct. (Bug#47323)

  • Replication: Performing ALTER TABLE ... DISABLE KEYS on a slave table caused row-based replication to fail. (Bug#47312)

  • Replication: When using the row-based format to replicate a transaction involving both transactional and nontransactional engines, which contained a DML statement affecting multiple rows, the statement failed; if this transaction was followed by a COMMIT, the master and the slave could diverge, because the statement was correctly rolled back on the master, but was applied on the slave. (Bug#47287)

    See also Bug#46864.

  • Replication: BEGIN statements were not included in the output of mysqlbinlog. (Bug#46998)

  • Replication: A problem with the BINLOG statement in the output of mysqlbinlog could break replication; statements could be logged with the server ID stored within events by the BINLOG statement rather than the ID of the running server. With this fix, the server ID of the server executing the statements can no longer be overridden by the server ID stored in the binary log's format description statement. (Bug#46640)

    This regression was introduced by Bug#32407.

  • Replication: When using row-based replication, DROP TEMPORARY TABLE IF EXISTS was written to the binary log if the table named in the statement did not exist, even though a DROP TEMPORARY TABLE statement should never be logged in row-based logging mode, whether the table exists or not. (Bug#46572)

  • Replication: Concurrent transactions that inserted rows into a table with an AUTO_INCREMENT column could break statement-based or mixed-format replication error 1062 Duplicate entry '...' for key 'PRIMARY' on the slave. This was especially likely to happen when one of the transactions activated a trigger that inserted rows into the table with the AUTO_INCREMENT column, although other conditions could also cause the issue to manifest. (Bug#45677)

  • Replication: The internal function get_master_version_and_clock() (defined in sql/slave.cc) ignored errors and passed directly when queries failed, or when queries succeeded but the result retrieved was empty. Now this function tries to reconnect the master if a query fails due to transient network problems, and to fail otherwise. The I/O thread now prints a warning if the same system variables do not exist on master (in the event the master is a very old version of MySQL, compared to the slave.) (Bug#45214)

  • Replication: Replicating TEXT or VARCHAR columns declared as NULL on the master but NOT NULL on the slave caused the slave to crash. (Bug#43789)

    See also Bug#38850, Bug#43783, Bug#43785, Bug#47741, Bug#48091.

  • Replication: By default, all statements executed by the mysql_upgrade program on the master are written to the binary log, then replicated to the slave. In some cases, this can result in problems; for example, it attempted to alter log tables on replicated databases (this failed due to logging being enabled).

    As part of this fix, a mysql_upgrade option, --write-binlog, is added. Its inverse, --skip-write-binlog, can be used to disable binary logging while the upgrade is in progress. (Bug#43579)

  • Replication: This fix handles 2 issues encountered on replication slaves during startup:

    1. A failure while allocating the master info structure caused the slave to crash.

    2. A failure during recovery caused the relay log file not to be properly initialized which led to a crash on the slave.

    (Bug#43075)

  • Replication: When the logging format was set without binary logging being enabled, the server failed to start. Now in such cases, the server starts successfully, binlog_format is set, and a warning is logged instead of an error. (Bug#42928)

  • Replication: On the master, if a binary log event is larger than max_allowed_packet, the error message ER_MASTER_FATAL_ERROR_READING_BINLOG is sent to a slave when it requests a dump from the master, thus leading the I/O thread to stop. On a slave, the I/O thread stops when receiving a packet larger than max_allowed_packet.

    In both cases, however, there was no Last_IO_Error reported, which made it difficult to determine why the slave had stopped in such cases. Now, Last_IO_Error is reported when max_allowed_packet is exceeded, and provides the reason for which the slave I/O thread stopped. (Bug#42914)

    See also Bug#14068, Bug#47200, Bug#47303.

  • Replication: When using statement-based replication and the transaction isolation level was set to READ COMMITTED or a less strict level, InnoDB returned an error even if the statement in question was filtered out according to the --binlog-do-db or --binlog-ignore-db rules in effect at the time. (Bug#42829)

  • Replication: When using row-based format, replication failed with the error Could not execute Write_rows event on table ...; Field '...' doesn't have a default value when an INSERT was made on the master without specifying a value for a column having no default, even if strict server SQL mode was not in use and the statement would otherwise have succeeded on the master. Now the SQL mode is checked, and the statement is replicated unless strict mode is in effect. For more information, see Section 5.1.8, “Server SQL Modes”. (Bug#38173)

    See also Bug#38262, Bug#43992.

  • Replication: When autocommit was set equal to 1 after starting a transaction, the binary log did not commit the outstanding transaction. The reason this happened was that the binary log commit function saw only the values of the new settings, and decided that there was nothing to commit.

    This issue was first observed when using the Falcon storage engine, but it is possible that it affected other storage engines as well. (Bug#37221)

  • Replication: FLUSH LOGS did not actually close and reopen the binary log index file. (Bug#34582)

    See also Bug#5.0.90.

  • Replication: An error message relating to permissions required for SHOW SLAVE STATUS was confusing. (Bug#34227)

  • Replication: The --base64-output option for mysqlbinlog was not honored for all types of events. This interfered in some cases with performing point-in-time recovery. (Bug#32407)

    See also Bug#46640, Bug#34777.

  • Replication: The value of Slave_IO_running in the output of SHOW SLAVE STATUS did not distinguish between all 3 possible states of the slave I/O thread (not running; running but not connected; connected). Now the value Connecting (rather than No) is shown when the slave I/O thread is running but the slave is not connected to a replication master.

    The server system variable Slave_running also reflects this change, and is now consistent with what is shown for Slave_IO_running. (Bug#30703, Bug#41613)

  • Replication: Queries which were written to the slow query log on the master were not written to the slow query log on the slave. (Bug#23300)

    See also Bug#48632.

  • Replication: Valgrind revealed an issue with mysqld that as corrected: memory corruption in replication slaves when switching databases. (Bug#19022)

  • API: The fix for Bug#24507 could lead in some cases to client application failures due to a race condition. Now the server waits for the “dummy” thread to return before exiting, thus making sure that only one thread can initialize the POSIX threads library. (Bug#42850)

  • Certain INTERVAL expressions could cause a crash on 64-bit systems. (Bug#48739)

  • Following a literal, the COLLATE clause was mishandled such that different results can be produced depending whether an index is used. (Bug#48447)

  • SUM() artificially increased the precision of a DECIMAL argument, which was truncated when a temporary table was created to hold the results. (Bug#48370)

    See also Bug#45261.

  • If an outer query was invalid, a subquery might not even be set up. EXPLAIN EXTENDED did not expect this and caused a crash by trying to dereference improperly set up information. (Bug#48295)

  • A query containing a view using temporary tables and multiple tables in the FROM clause and PROCEDURE ANALYSE() caused a server crash.

    As a result of this bug fix, PROCEDURE ANALYSE() is legal only in a top-level SELECT. (Bug#48293)

    See also Bug#46184.

  • Error handling was missing for SELECT statements containing subqueries in the WHERE clause and that assigned a SELECT result to a user variable. The server could crash as a result. (Bug#48291)

  • An assertion could fail if the optimizer used a SPATIAL index. (Bug#48258, Bug#47019)

  • Memory-allocation failures were handled incorrectly in the InnoDB os_mem_alloc_large() function. (Bug#48237)

  • WHERE clauses with outer_value_list NOT IN subquery were handled incorrectly if the outer value list contained multiple items at least one of which could be NULL. (Bug#48177)

  • Searches using a non-default collation could return different results for a table when partitioning was and was not used. (Bug#48161)

  • A combination of GROUP BY WITH ROLLUP, DISTINCT and the const join type in a query caused a server crash when the optimizer chose to employ a temporary table to resolve DISTINCT. (Bug#48131)

  • The subquery optimizer had a memory leak. (Bug#48060)

  • Server shutdown failed on Windows. (Bug#48047)

  • In some cases, using a null microsecond part in a WHERE condition (for example, WHERE date_time_field <= 'YYYY-MM-DD HH:MM:SS.0000') could lead to incorrect results due to improper DATETIME comparison. (Bug#47963)

  • A build configured using the --without-server option did not compile the yaSSL code, so if --with-ssl was also used, the build failed. (Bug#47957)

  • When a query used a DATE or DATETIME value formatted using any separator characters other than hyphen ('-') and a >= condition matching only the greatest value in an indexed column, the result was empty if an index range scan was employed. (Bug#47925)

  • mysys/mf_keycache.c requires threading, but no test was made for thread support. (Bug#47923)

  • For debug builds, an assertion could fail during the next statement executed for a temporary table after a multiple-table UPDATE involving that table and modified an AUTO_INCREMENT column with a user-supplied value. (Bug#47919)

  • The mysys/mf_strip.c file, which defines the strip_sp() function, has been removed from the MySQL source. The function was no longer used within the main build, and the supplied function was causing symbol errors on Windows builds. (Bug#47857)

  • When building storage engines on Windows it was not possible to specify additional libraries within the CMake file required for the build. An ${engine}_LIBS macro has been added to the files to support these additional storage-engine specific libraries. (Bug#47797)

  • When building a pluggable storage engine on Windows, the engine name could be based on the directory name where the engine was located, rather than the configured storage engine name. (Bug#47795)

  • During cleanup of a stored procedure's internal structures, the flag to ignore the errors for INSERT IGNORE or UPDATE IGNORE was not cleaned up, which could result in a server crash. (Bug#47788)

  • If the first argument to GeomFromWKB() function was a geometry value, the function just returned its value. However, it failed to preserve the argument's null_value flag, which caused an unexpected NULL value to be returned to the caller, resulting in a server crash. (Bug#47780)

  • InnoDB could crash when updating spatial values. (Bug#47777)

  • The pthread_cond_wait() implementations for Windows could deadlock in some rare circumstances. (Bug#47768)

  • The encoding of values for SET system_variable = identifier statements was incorrect, resulting in incorrect error messages. (Bug#47597)

  • On WIndows, when an idle named pipe connection was forcibly closed with a KILL statement or because the server was being shut down, the thread that was closing the connection would hang infinitely. (Bug#47571, Bug#31621)

  • On Mac OS X or Windows, sending a SIGHUP signal to the server or an asynchronous flush (triggered by flush_time) caused the server to crash. (Bug#47525)

  • Debug builds could not be compiled with the Sun Studio compiler. (Bug#47474)

  • Queries of the form SELECT SUM(DISTINCT varchar_key) FROM tbl_name caused a server crash. (Bug#47421)

  • A function call could end without throwing an error or setting the return value. For example, this could happen when an error occurred while calculating the return value. This is fixed by setting the value to NULL when an error occurs during evaluation of an expression. (Bug#47412)

  • mysqladmin debug could crash on 64-bit systems. (Bug#47382)

  • A simple SELECT with implicit grouping could return many rows rather than a single row if the query was ordered by the aggregated column in the select list. (Bug#47280)

  • An assertion could be raised for CREATE TABLE if there was a pending INSERT DELAYED or REPLACE DELAYED for the same table. (Bug#47274)

  • InnoDB raised errors in some cases in a manner not compatible with SIGNAL and RESIGNAL. (Bug#47233)

  • A multiple-table UPDATE involving a natural join and a mergeable view raised an assertion. (Bug#47150)

  • On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139)

  • Solaris binary packages now are compiled with -g0 rather than -g. (Bug#47137)

  • If an InnoDB table was created with the AUTO_INCREMENT table option to specify an initial auto-increment value, and an index was added in a separate operation later, the auto-increment value was lost (subsequent inserts began at 1 rather than the specified value). (Bug#47125)

  • Incorrect handling of predicates involving NULL by the range optimizer could lead to an infinite loop during query execution. (Bug#47123)

  • EXPLAIN caused a server crash for certain valid queries. (Bug#47106)

  • Repair by sort or parallel repair of MyISAM tables could fail to fail over to repair with key cache. (Bug#47073)

  • InnoDB Plugin did not compile on some Solaris systems. (Bug#47058)

  • On WIndows, when a failed I/O operation occurred with return code of ERROR_WORKING_SET_QUOTA, InnoDB intentionally crashed the server. Now InnoDB sleeps for 100ms and retries the failed operation. (Bug#47055)

  • The mysql_config script contained a reference to @innodb_system_libs@ that was not replaced with the corresponding library flags during the build process and ended up in the output of mysql_config --libs. (Bug#47007)

  • The configure option --without-server did not work. (Bug#46980)

  • Failed multiple-table DELETE statements could raise an assertion. (Bug#46958)

  • When MySQL crashed (or a snapshot was taken that simulates a crash), it was possible that internal XA transactions (used to synchronize the binary log and InnoDB) could be left in a PREPARED state, whereas they should be rolled back. This occurred when the server_id value changed before the restart, because that value was used to construct XID values.

    Now the restriction is relaxed that the server_id value be consistent for XID values to be considered valid. The rollback phase should then be able to clean up all pending XA transactions. (Bug#46944)

  • When creating a new instance on Windows using mysqld-nt and the --install parameter, the value of the service would be set incorrectly, resulting in a failure to start the configured service. (Bug#46917)

  • The test suite was missing from RPM packages. (Bug#46834)

  • For InnoDB tables, an unnecessary table rebuild for ALTER TABLE could sometimes occur for metadata-only changes. (Bug#46760)

  • The server could crash for queries with the following elements: 1. An “impossible where” in the outermost SELECT; 2. An aggregate in the outermost SELECT; 3. A correlated subquery with a WHERE clause that includes an outer field reference as a top-level WHERE sargable predicate; (Bug#46749)

  • InnoDB Plugin did not compile using gcc 4.1 on PPC systems. (Bug#46718)

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

    See also Bug#18828.

  • Concurrent INSERT INTO ... SELECT statements for an InnoDB table could cause an AUTO_INCREMENT assertion failure. (Bug#46650)

  • The Serbian locale name 'sr_YU' is obsolete. It is still recognized for backward compatibility, but 'sr_RS' now should be used instead. (Bug#46633)

  • On Solaris and HP-UX systems with the environment set to the default C locale, MySQL client programs issued an Unknown OS character set error. (Bug#46619)

  • SHOW CREATE TRIGGER for a MERGE table trigger caused an assertion failure. (Bug#46614)

  • If a transaction was rolled back inside InnoDB due to a deadlock or lock wait timeout, and a statement in the transaction had an IGNORE clause, the server could crash at the end of the statement or on shutdown. (Bug#46539)

  • TRUNCATE TABLE for a table that was opened with HANDLER did not close the handler and left it in an inconsistent state that could lead to a server crash. Now TRUNCATE TABLE for a table closes all open handlers for the table. (Bug#46456)

  • Trailing spaces were not ignored for user-defined collations that mapped spaces to a character other than 0x20. (Bug#46448)

    See also Bug#29468.

  • The server crashed if a shutdown occurred while a connection was idle. This happened because of a NULL pointer dereference while logging to the error log. (Bug#46267)

  • Dropping an InnoDB table that used an unknown collation (created on a different server, for example) caused a server crash. (Bug#46256)

  • The GPL and commercial license headers had different sizes, so that error log, backtrace, core dump, and cluster trace file line numbers could be off by one if they were not checked against the version of the source used for the build. (For example, checking a GPL build backtrace against commercial sources.) (Bug#46216)

  • A query containing a subquery in the FROM clause and PROCEDURE ANALYSE() caused a server crash. (Bug#46184)

    See also Bug#48293.

  • After an error such as a table-full condition, INSERT IGNORE could cause an assertion failure for debug builds. (Bug#46075)

  • InnoDB did not disallow creation of an index with the name GEN_CLUST_INDEX, which is used internally. (Bug#46000)

  • CREATE TABLE ... SELECT could cause a server crash if no default database was selected. (Bug#45998)

  • Configuring MySQL for DTrace support resulted in a build failure on Solaris if the directory for the dtrace executable was not in PATH. (Bug#45810)

  • An infinite hang and 100% CPU usage occurred after handler tried to open a merge table.

    If the command mysqladmin shutdown was executed during the hang, the debug server generated the following assert:

    mysqld: table.cc:407: void free_table_share(TABLE_SHARE*): Assertion `share->ref_count ==
    0' failed.
    090610 14:54:04 - mysqld got signal 6 ;
    

    (Bug#45781)

  • During the build of the Red Hat IA64 MySQL server RPM, the system library link order was incorrect. This made the resulting Red Hat IA64 RPM depend on "libc.so.6.1(GLIBC_PRIVATE)(64bit)", thus preventing installation of the package. (Bug#45706)

  • The caseinfo member of the CHARSET_INFO structure was not initialized for user-defined Unicode collations, leading to a server crash. (Bug#45645)

  • Appending values to an ENUM or SET definition is a metadata change for which ALTER TABLE need not rebuild the table, but it was being rebuilt anyway. (Bug#45567)

  • The socket system variable was unavailable on Windows. (Bug#45498)

  • The combination of MIN() or MAX() in the select list with WHERE and GROUP BY clauses could lead to incorrect results. (Bug#45386)

  • Truncation of DECIMAL values could lead to assertion failures; for example, when deducing the type of a table column from a literal DECIMAL value. (Bug#45261)

    See also Bug#48370.

  • Client flags were incorrectly initialized for the embedded server, causing several tests in the jp test suite to fail. (Bug#45159)

  • Concurrent execution of statements requiring a table-level lock and statements requiring a non-table-level write lock for a table could deadlock. (Bug#45143)

  • For settings of lower_case_table_names greater than 0, some queries for INFORMATION_SCHEMA tables left entries with incorrect lettercase in the table definition cache. (Bug#44738)

  • mysqld_safe could fail to find the logger program. (Bug#44736)

  • The have_community_features system variable was renamed to have_profiling.

    Previously, to enable profiling, it was necessary to run configure with the --enable-community-features and --enable-profiling options. Now only --enable-profiling is needed. (Bug#44651)

  • Some Perl scripts in AIX packages contained an incorrect path to the perl executable. (Bug#44643)

  • With InnoDB Plugin, renaming a table column and then creating an index on the renamed column caused a server crash to the .frm file and the InnoDB data directory going out of sync. Now InnoDB Plugin 1.0.5 returns an error instead: ERROR 1034 (HY000): Incorrect key file for table 'tbl_name'; try to repair it. To work around the problem, create another table with the same structure and copy the original table to it. (Bug#44571)

  • For debug builds, executing a stored procedure as a prepared statement could sometimes cause an assertion failure. (Bug#44521)

  • Using mysql_stmt_execute() to call a stored procedure could cause a server crash. (Bug#44495)

  • InnoDB did not always disallow creating tables containing columns with names that match the names of internal columns, such as DB_ROW_ID, DB_TRX_ID, DB_ROLL_PTR, and DB_MIX_ID. (Bug#44369)

  • An InnoDB error message incorrectly referred to the nonexistent innodb_max_files_open variable rather than to innodb_open_files. (Bug#44338)

  • SELECT ... WHERE ... IN (NULL, ...) was executed using a full table scan, even if the same query without the NULL used an efficient range scan. (Bug#44139)

    See also Bug#18360.

  • InnoDB use of SELECT MAX(autoinc_column) could cause a crash when MySQL data dictionaries went out of sync. (Bug#44030)

  • LOAD DATA INFILE statements were written to the binary log in such a way that parsing problems could occur when re-executing the statement from the log. (Bug#43746)

  • Selecting from the process list in the embedded server caused a crash. (Bug#43733)

    See also Bug#47304.

  • Attempts to enable large_pages with a shared memory segment larger than 4GB caused a server crash. (Bug#43606)

  • For ALTER TABLE, renaming a DATETIME or TIMESTAMP column unnecessarily caused a table copy operation. (Bug#43508)

  • The weekday names for the Romanian lc_time_names locale 'ro_RO' were incorrect. Thanks to Andrei Boros for the patch to fix this bug. (Bug#43207)

  • XA START could cause an assertion failure or server crash when it is called after a unilateral rollback issued by the Resource Manager (both in a regular transaction and after an XA transaction). (Bug#43171)

  • Redefining a trigger could cause an assertion failure. (Bug#43054)

  • The FORCE INDEX FOR ORDER BY index hint was ignored when join buffering was used. (Bug#43029)

  • DROP DATABASE did not clear the message list. (Bug#43012, Bug#43138)

  • The NUM_FLAG bit of the MYSQL_FIELD.flags member now is set for columns of type MYSQL_TYPE_NEWDECIMAL. (Bug#42980)

  • Incorrect handling of range predicates combined with OR operators could yield incorrect results. (Bug#42846)

  • Failure to treat BIT values as unsigned could lead to unpredictable results. (Bug#42803)

  • For the embedded server on Windows, InnoDB crashed when innodb_file_per_table was enabled and a table name was in full path format. (Bug#42383)

  • SHOW ERRORS returned an empty result set after an attempt to drop a nonexistent table. (Bug#42364)

  • If the server was started with an option that had a missing or invalid value, a subsequent error that would cause normally the server to shut down could cause it to crash instead. (Bug#42244)

  • Some queries with nested outer joins could lead to crashes or incorrect results because an internal data structure was handled improperly. (Bug#42116)

  • The server used the wrong lock type (always TL_READ instead of TL_READ_NO_INSERT when appropriate) for tables used in subqueries of UPDATE statements. This led in some cases to replication failure because statements were written in the wrong order to the binary log. (Bug#42108)

  • A Valgrind warning in open_tables() was corrected. (Bug#41759)

  • In a replication scenario with innodb_locks_unsafe_for_binlog enabled on the slave, where rows were changed only on the slave (not through replication), in some rare cases, many messages of the following form were written to the slave error log: InnoDB: Error: unlock row could not find a 4 mode lock on the record. (Bug#41756)

  • After renaming a user, granting that user privileges could result in the user having additional privileges other than those granted. (Bug#41597)

  • The mysql-stress-test.pl test script was missing from the noinstall packages on Windows. (Bug#41546)

  • With a nonstandard InnoDB page size, some error messages became inaccurate.

    Note

    Changing the page size is not a supported operation and there is no guarantee that InnoDB will function normally with a page size other than 16KB. Problems compiling or running InnoDB may occur. In particular, ROW_FORMAT=COMPRESSED in the InnoDB Plugin assumes that the page size is at most 16KB and uses 14-bit pointers.

    A version of InnoDB built for one page size cannot use data files or log files from a version built for a different page size.

    (Bug#41490)

  • In some cases, the server did not recognize lettercase differences between GRANT attributes such as table name or user name. For example, a user was able to perform operations on a table with privileges of another user with the same user name but in a different lettercase.

    In consequence of this bug fix, the collation for the Routine_name column of the mysql.proc table is changed from utf8_bin to utf8_general_ci. (Bug#41049)

    See also Bug#48872.

  • When a storage engine plugin failed to initialize before allocating a slot number, it would acidentally unplug the engine in slot 0. (Bug#41013)

  • Optimized builds of mysqld crashed when built with Sun Studio on SPARC platforms. (Bug#40244)

  • CREATE TABLE failed if a column name in a FOREIGN KEY clause was given in a lettercase different from the corresponding index definition. (Bug#39932)

  • The mysql_stmt_close() C API function did not flush all pending data associated with the prepared statement. (Bug#39519)

  • INFORMATION_SCHEMA access optimizations did not work properly in some cases. (Bug#39270)

  • ALTER TABLE neglected to preserve ROW_FORMAT information from the original table, which could cause subsequent ALTER TABLE and OPTIMIZE TABLE statements to lose the row format for InnoDB tables. (Bug#39200)

  • Simultaneous ANALYZE TABLE operations for an InnoDB tables could be subject to a race condition. (Bug#38996)

  • mysqlbinlog had a memory leak in its option-processing code. (Bug#38468)

  • The ALTER ROUTINE privilege incorrectly allowed SHOW CREATE TABLE. (Bug#38347)

  • Setting the general_log_file or slow_query_log_file system variable to a nonconstant expression caused the variable to become unset. (Bug#38124)

  • For certain SELECT statements using ref access, MySQL estimated an incorrect number of rows, which could lead to inefficient query plans. (Bug#38049)

  • A workload consisting of CREATE TABLE ... SELECT and DML operations could cause deadlock. (Bug#37433)

  • The client library mishandled EINPROGRESS errors for connections in nonblocking mode. (Bug#37267)

  • Previously, InnoDB performed REPLACE INTO T SELECT ... FROM S WHERE ... by setting shared next-key locks on rows from S. Now InnoDB selects rows from S with shared locks or as a consistent read, as for INSERT ... SELECT. This reduces lock contention between sessions. (Bug#37232)

  • Some warnings were being reported as errors. (Bug#36777)

  • Privileges for SHOW CREATE VIEW were not being checked correctly. (Bug#35996)

  • Different invocations of CHECKSUM TABLE could return different results for a table containing columns with spatial data types. (Bug#35570)

  • Result set metadata for columns retrieved from INFORMATION_SCHEMA tables did not have the db or org_table members of the MYSQL_FIELD structure set. (Bug#35428)

  • SHOW CREATE EVENT output did not include the DEFINER clause. (Bug#35297)

  • For its warning count, the mysql_info() C API function could print the number of truncated data items rather than the number of warnings. (Bug#34898)

  • Concurrent execution of FLUSH TABLES along with SHOW FUNCTION STATUS or SHOW PROCEDURE STATUS could cause a server crash. (Bug#34895)

  • Executing SHOW MASTER LOGS as a prepared statement without binary logging enabled caused a crash for debug builds. (Bug#34741)

  • There were spurious warnings about "Truncated incorrect DOUBLE value" in queries with MATCH ... AGAINST and > or < with a constant (which was reported as an incorrect DOUBLE value) in the WHERE condition. (Bug#34374)

  • A COMMENT longer than 64 characters caused CREATE PROCEDURE to fail. (Bug#34197)

  • mysql_real_connect() did not check whether the MYSQL connection handler was already connected and connected again even if so. Now an CR_ALREADY_CONNECTED error occurs. (Bug#33831)

  • INSTALL PLUGIN and UNINSTALL PLUGIN did not handle plugin identifiers consistently with respect to lettercase. (Bug#33731)

  • The default values for the general query log and slow query log file are documented to be based on the server host name and located in the data directory. However, they were in fact being based on the basename and location of the process ID (PID) file. The name and location defaults for the PID file are based on the server host name and data directory, so if it was not assigned a different name explicitly, its defaults were used and the general query log and slow query log file defaults were as documented. But if the PID file was assigned a value with the --pid-file option, the defaults for the general query log and slow query log file were incorrect. This has been rectified so that the defaults for all three files are based on the server host name and data directory.

    A remaining problem is that the binary log and relay log .NNNNNN and .index basename defaults are based on the PID file basename, contrary to the documentation. This issue is to be addressed as Bug#45359. (Bug#33693)

  • The SHOW FUNCTION CODE and SHOW PROCEDURE CODE statements are not present in nondebug builds, but attempting to use them resulted in a “syntax error” message. Now the error message indicates that the statements are disabled and that you must use a debug build. (Bug#33637)

  • The LAST_DAY() and MAKEDATE() functions could return NULL, but the result metadata indicated NOT NULL. Thanks to Hiromichi Watari for the patch to fix this bug. (Bug#33629)

  • Instance Manager (mysqlmanager) has been removed, but a reference to it still appeared in the mysql.server script. (Bug#33472)

  • There was a race condition between the event scheduler and the server shutdown thread. (Bug#32771)

  • When an InnoDB tablespace filled up, an error was logged to the client, but not to the error log. Also, the error message was misleading and did not indicate the real source of the problem. (Bug#31183)

  • ALTER TABLE statements that added a column and added a nonpartial index on the column failed to add the index. (Bug#31031)

  • For const tables that were optimized away EXPLAIN EXTENDED displayed them in the FROM clause. Now they are not displayed. If all tables are optimized away, FROM DUAL is displayed. (Bug#30302)

  • There were cases where string-to-number conversions would produce warnings for CHAR values but not for VARCHAR values. (Bug#28299)

  • In mysql, using Control-C to kill the current query resulted in a ERROR 1053 (08S01): Server shutdown in progress" message if the query was waiting for a lock. (Bug#28141)

  • When building MySQL on Windows from source, the WITH_BERKELEY_STORAGE_ENGINE option would fail to configure BDB support correctly. (Bug#27693)

  • The default database is no longer changed to NULL (“no database”) if DROP DATABASE for that database failed. (Bug#26704)

  • DROP TABLE for INFORMATION_SCHEMA tables produced an Unknown table error rather than the more appropriate Access denied. (Bug#24062)

  • Referring to a stored function qualified with the name of one database and tables in another database caused a “table doesn't exist” error. (Bug#18444)

  • A Table ... doesn't exist error could occur for statements that called a function defined in another database. (Bug#17199)

C.2. MySQL Enterprise Monitor Change History

This appendix lists the changes to the MySQL Enterprise Monitor, beginning with the most recent release. Each release section covers added or changed functionality, bug fixes, and known issues, if applicable. All bug fixes are referenced by bug number and include a link to the bug database. Bugs are listed in order of resolution. To find a bug quickly, search by bug number.

C.2.1. Changes in MySQL Enterprise Monitor 2.0.7 (Not yet released)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.6.

Bugs fixed:

  • The agent did not start because the file share/mysql-proxy/items/custom.xml was missing from the build, but referred to in the configuration file. The log recorded the following error:

     Default log:
     ------------
     2009-09-18 16:25:12: (critical) chassis.c:1097: could not raise RLIMIT_NOFILE to 8192,
    Invalid argument (22). Current limit still 1024.
     2009-09-18 16:25:13: (critical) job_collect_mysql.c.1894: opening
    '/data0/merlin/agent/2.0.7.7163/openSUSE10.3-x86-64bit/qa-merlin/share/mysql-proxy/items/c
    ustom.xml' failed with: Failed to open file
    '/data0/merlin/agent/2.0.7.7163/openSUSE10.3-x86-64bit/qa-merlin/share/mysql-proxy/items/c
    ustom.xml': No such file or directory
     2009-09-18 16:25:13: ((error)) scheduler.c:318: register_classes() for plugin
    collect_mysql failed
    

    If the reference to share/mysql-proxy/items/custom.xml was removed from the “agent-item-files = ...” entry in the configuration file, then the agent started as expected. (Bug#47443)

  • After upgrading to Mac OS X Snow Leopard, the following error was generated when starting an agent:

    Macintosh-6:replication ligaya$
    ./Master.5.1.34sp1/MEM_agent/etc/init.d/mysql-monitor-agent start
    Starting MySQL Enterprise agent service...
    ./Master.5.1.34sp1/MEM_agent/etc/init.d/mysql-monitor-agent: line 175:   861 Trace/BPT
    trap          nohup $MERLIN_AGENT_ROOTDIR/bin/mysql-monitor-agent $MERLIN_AGENT_OPTIONS >
    /dev/null
     ERROR! MySQL Enterprise agent failed to start.
    

    Further, when attempting to display the agent version the following error was generated:

    Macintosh-6:replication ligaya$ ./Master.5.1.34sp1/MEM_agent/bin/mysql-monitor-agent -v
    dyld: Library not loaded: /usr/lib/libxml2.2.dylib
      Referenced from:
    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices
    .framework/Versions/A/DictionaryServices
      Reason: Incompatible library version: DictionaryServices requires version 10.0.0 or
    later, but libxml2.2.dylib provides version 9.0.0
    Trace/BPT trap
    

    (Bug#47042)

C.2.2. Changes in MySQL Enterprise Monitor 2.0.6 (27th August 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.5.

Functionality added or changed:

  • Events used a GMT timestamp for the event time within email notifications, rather than the local time for the server generating the event.

    MySQL Enterprise Monitor has been changed so that it displays the time using the server's locale and GMT. (Bug#43739)

Bugs fixed:

  • Initial setup and registration of MySQL Enterprise Monitor could fail on Mac OS X when communicating with the MySQL Enterprise website. (Bug#46571)

  • If a migration from 1.3 to 2.0 was initiated and a new server created during the migration, but then deleted before migration was finished, the new server delete operation failed with an Null Pointer Exception (NPE). (Bug#44991)

  • The Rule “InnoDB Buffer Cache Hit Rate Not Optimal” in the “Memory Usage” Advisor did not contain an uptime check. This resulted in premature firing of an info event. (Bug#44770)

  • In the Advisor “Administration” the Rule “InnoDB Redo Logs Not Sized Correctly” did not fire correctly. The rule contained the expression:

    (%have_innodb% == "YES") && ((%innodb_log_file_size% * %innodb_log_files_in_group%) <
    LEAST(1073741824, (%innodb_buffer_pool_size% / 2))) 
    

    This was incorrect and needed to be changed to:

    (%have_innodb% == "YES") && ((%innodb_log_file_size% * %innodb_log_files_in_group%) <=
    LEAST(1073741824, (%innodb_buffer_pool_size% / 2)))
    

    (Bug#44734)

  • The recommendation for the rule Table Cache Not Optimal says:

    Recommended Action
    SET GLOBAL table_cache = (64 + 16);

    But an error was generated on executing that query:

    mysql> SET GLOBAL table_cache = (64 + 16);
    ERROR 1193 (HY000): Unknown system variable 'table_cache'
    
    mysql> select version();
    +------------+
    | version()  |
    +------------+
    | 5.1.31-log |
    +------------+
    1 row in set (0.01 sec)

    (Bug#44602)

  • When running the shutdown script for Enterprise Dashboard, it took an unacceptably long time for Tomcat to terminate completely, the java process eventually had to be killed manually. (Bug#44327)

  • The upgrade installer overwrote any custom settings stored in WEB-INF/config.properties. For example it set the database host back to localhost. (Bug#44003)

  • When updating an Agent from 2.0 to 2.1 the mysql-monitor-agent.ini was incorrectly updated.

    This happened if the Agent was configured to use SSL to connect to the Enterprise Dashboard, on a port other than 18443. The update installer caused any value specified for the port to be changed to 18443. This did not happen if the Agent was not using SSL. (Bug#43900)

  • An error was generated when an attempt was made to rename a Replication Group to one that had previously been deleted. (Bug#43846)

  • A new topology was not discovered after the previous replication group was renamed. (Bug#43815)

  • On Unix systems, executing the command:

    ./mysqlmonitorctl.sh stop

    did not make sure that mysqld was shutdown before finishing.

    This resulted in a situation such as the following:

    # /opt/mysql/enterprise/monitor-2.0.0.7092/mysqlmonitorctl.sh stop
    Using CATALINA_BASE:   /opt/mysql/enterprise/monitor/apache-tomcat
    Using CATALINA_HOME:   /opt/mysql/enterprise/monitor/apache-tomcat
    Using CATALINA_TMPDIR: /opt/mysql/enterprise/monitor/apache-tomcat/temp
    Using JRE_HOME:       /opt/mysql/enterprise/monitor-2.0.0.7092/java
    Stopping tomcat service ... [ OK ]
    /opt/mysql/enterprise/monitor-2.0.0.7092/mysqlmonitorctl.sh : mysql stopped
    

    However, running the following command a few minutes later showed that the MySQL server was still running:

    # /opt/mysql/enterprise/monitor-2.0.0.7092/mysqlmonitorctl.sh status
    MySQL Network MySQL is running
    MySQL Network Tomcat is not running
    

    (Bug#43803)

  • The MySQL Enterprise Monitor upgrade installer incorrectly replaced the AdvisorScript.jar in <instDir>/apache-tomcat/webapps/ROOT/WEB-INF/lib/ with the default Advisor JAR. (Bug#43773)

  • The agent created the mysql.inventory table with an engine type of InnoDB, instead of MyISAM, when InnoDB was specified as the default engine type in my.cnf. This happened because the agent did not explicitly specify the table engine type to be of MyISAM. (Bug#43551)

  • The MySQL Enterprise Monitor installer failed to install correctly due to insufficient disk space, even though the installer calculated there was suffcient disk space for the installation. This was due to the installer having out of date information regarding disk space requirements. (Bug#43538)

  • After removing enough servers to bring the host count back down to the number covered in the subscription, the Subscription Warnings reflected the new number. However, the warning message displayed:

    You are currently monitoring 1 host, however your subscription covers only 1. Your
    subscription needs to be updated to cover at least 0 additional hosts.
    

    Instead of displaying:

    Your subscription is up-to-date
    You have no warnings at this time.
    

    The former message resulted in confusion. (Bug#43163)

  • If a host was not a slave during the initial discovery phase, then it would not be displayed in the Replication tab if it subsequently became a slave.

    This was because after the initial discovery phase, if a host did not have slavestatus present, no subsequent checks were made to check for the host being a slave. It was therefore missed for the purposes of replication discovery and never showed in the Replication tab. (Bug#42997)

  • The advisor “User Has Rights To Database That Does Not Exist” generated erroneous alerts.

    If a database was created with an “_” character in the name, and then user privileges granted to this database using the escaped character sequence “\_” to prevent wildcards, then the advisor generates an error stating there is no database for the privilege.

    For example, if the following is carried out on the monitored server:

    CREATE DATABASE test_foo;
    GRANT SELECT ON `test\_foo`.* to testuser@'localhost' identified by 'test';

    then the advisor warns that these users have rights to a database that does not exist:

    ''@'%' on DB test_%,
    'test'@'localhost' on DB test_foo,
    'testuser'@'localhost' on DB test_foo

    (Bug#41717)

  • The generic Linux IA64 glibc2.3 Agent installer was missing from the build. (Bug#41224)

  • The Enterprise Dashboard displayed a blank entry for Disk Space in the Meta Info area. This happened on Open Solaris 2008.05. This problem only occurred when using the ZFS file system. (Bug#40907)

  • The graphs for Thread Cache, Connections and Temporary Tables contained incorrect Japanese translations on their Y axis. The Japanese displayed “total connection time (min)” when it should have displayed something else. For example, the Thread Cache graph should have displayed “total/min”. (Bug#40413)

  • When the Agent was started as a service on Windows for the first time, the name in the Task Manager window was MYSQL-~1.EXE. This occurred whether the Agent was started from within the installer or from the Start Menu.

    If the service was restarted, the Agent's name changed to the correct value, mysql-service-agent.exe. (Bug#30166)

C.2.3. Changes in MySQL Enterprise Monitor 2.0.5 (18th March 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.4.

Bugs fixed:

  • The FreeBSD 7 Agent was inadvertently a Linux binary.

    shell> file mysqlmonitoragent-2.0.5.7153-freebsd7-x86-32bit-installer.bin
    mysqlmonitoragent-2.0.5.7153-freebsd7-x86-32bit-installer.bin: ELF 32-bit LSB executable,
    Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs),
    stripped

    (Bug#44263)

  • Calling the Agent with the option --agent-run-os-tests resulted in a crash. This happened on Linux x86-64 systems. The resultant stack trace was:

    (qa-merlin)
    2009-03-04 16:39:42: (critical) chassis.c:1097: could not raise RLIMIT_NOFILE to 8192,
    Invalid argument (22). Current limit still 1024.
    sigar-test-all.c.124 (test_sigar_pid_get):
      pid = 5188
    sigar-test-all.c.106 (test_sigar_mem_get):
    ...cut...
    sigar-test-all.c.427 (test_sigar_file_system_list_get): (items = 13)
    [0]
      fs.dirname = /
      fs.devname = /dev/mapper/vg00-root
      fs.typename = local
      fs.sys-type-name = ext3
      fs.type = 2
      fsusage.total = 15481840
      fsusage.free = 14116140
      fsusage.used = 1365700
      fsusage.avail = 13329708
      fsusage.files = 1966080
      fsusage.use_percent = 0.100000
    [0]
      diskusage.reads = 315302
      diskusage.writes = 6318240
      diskusage.write_bytes = 25879511040
      diskusage.read_bytes = 6561092608
      diskusage.queue = 47457530080206
    Segmentation fault
    

    On some systems no output was shown, other than the message “Segmentation fault”. (Bug#43381)

  • Following a change in the replication configuration, MySQL Enterprise Monitor did not display the new topology correctly. (Bug#43240)

  • When a data collection became invalid, the agent sent NULLs for those collection values. However, the timestamps that it sent with the values were the timestamps from the last valid value that was collected.

    Due to key constraints on the Service Manager side, MySQL Enterprise Monitor disregarded anything sent with duplicate timestamps, thus the NULLs received from the agent were never processed. Some mechanisms, such as replication discovery, depend on the NULLs to identify a situation where data has become invalid. (Bug#43239)

  • MySQL Enterprise Monitor did not add a log entry each time data was purged. The log entry should have noted how many rows of each type of data were purged (historical data, logs, quan data). (Bug#43159)

  • MySQL Enterprise Monitor generated a stack overflow. This was as a result of a bug in Hibernate, which caused Hibernate to enter infinite recursion while trying to load a relationship. (Bug#43107)

  • The “Table Cache Set Too Low For Startup” and “Table Cache Not Optimal” rules were not supported on MySQL 5.1 because the table_cache system variable was deprecated and replaced with table_open_cache. (Bug#42663)

  • Migrated server was not completely deleted.

    In a Monitor that had been updated from 1.3.2 to 2.0.4, with 2 database servers queued for migration, if a server being migrated was deleted, or a migrated server was deleted, this would not be reflected in the user interface or in the license count, until Tomcat was restarted. (Bug#42604)

  • The installer used to upgrade from version 1.3 corrupted passwords containing the “?” character. (Bug#42452)

  • The replication status of a server was displayed as “unknown”. However, the agent logged no errors and the server showed no other event problems. The server status was displayed as “up” and the database connection was also displayed as “up”. (Bug#42407)

  • Sun multi-core processors caused all cores to be reported on the meta information page.

    The larger T-series SPARC processors have 32+ cores. This caused the meta information page in the Dashboard to scroll as it reported each one. (Bug#42355)

  • If an attempt was made to disable a rule using the link next to the rule, the following error message was generated:

    U0002 You must log in to access the requested resource. Go to login page.

    However, clicking on the link did not prompt the user to login again. (Bug#42313)

  • Changing ssh-agent from OpenSSH or specifying a malevolent value of agent-host-id, could inject data into the monitored MySQL Server.

    For example, setting agent-host-id to the value “I'm a test” would result in the following message in the error log:

    2009-01-23 15:45:11: ((error)) agent_mysqld.c:281: mysql_real_query('INSERT INTO
    mysql.inventory  (name, value) VALUES ( 'hostid', 'I'm a test' )') on 'mysql' failed: 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 'm a test' )' at line 1 (mysql-errno = 1064)
    

    (Bug#42306)

  • When SHOW GLOBAL STATUS returned a value greater than 214748364, it was sent to the Service Manager as 214748364. (Bug#42245)

  • The Agent failed to identify local sockets as local on Mac OS X 10.4.

    If the Agent was configured to use a Unix domain socket on Mac OS X 10.4, it did not treat the connection as local and failed to provide CPU and memory information to MySQL Enterprise Monitor. This is shown in the log file:

    2009-01-20 18:15:02: (message) network-socket.c:752: is-local family 0 != 1
    2009-01-20 18:15:02: (message) agent_mysqld.c:322: [mysql] mysqld is not local or not
    directly connected

    However, this problem did not happen on Mac OS X 10.5. (Bug#42220)

  • Some graphs on the Graph tab were not updated after the page was refreshed, or Update was clicked.

    The only way to get an updated graph was to change the graph size (in pixels) and then click Update. (Bug#42162)

  • The my.cnf file for the Enterprise Monitor internal database had the following configuration item:

    innodb_autoextend_increment = 50M
    

    This generated the error:

    16:36:23 [Warning] option 'innodb_autoextend_increment': unsigned value 52428800
    adjusted to 1000
    

    This variable is interpreted as being specified in MB, so 50M would be 50 TB. Such a high value results in the variable being adjusted to 1000 MB.

    The value in the configuration file should be:

    innodb_autoextend_increment = 50
    

    (Bug#42096)

  • A number of Advisor rules had advice text that had not been translated into Japanese. The Advisors that contained untranslated rules included Performance, Schema and Security. (Bug#42067)

  • The Service Manager did not handle the case where the agent failed to supply a valid master_ip. The Service Manager would then not restart. The logs contained the following:

    2009-01-09 14:39:50,472 ERROR [main:org.springframework.web.context.ContextLoader] Context
    initialization failed
    org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with
    name 'serverConnectionMonitor' defined in ServletContext resource
    [/WEB-INF/applicationContext.xml]: Unsatisfied dependency expressed through constructor
    argument with index 2 of type [com.mysql.etools.monitor.bo.Manager]: Error creating bean
    with name 'manager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]:
    Invocation of init method failed; nested exception is
    com.mysql.etools.monitor.pom.UnsupportedAttributeException:
    101c6b5b-15eb-49aa-916c-843c51b28d38: mysql.slavestatus.Master_ip

    (Bug#42005)

  • Having too many users with strong privileges generated Service Manager errors and events failed to be triggered.

    If there were approximately 1000 users with full privileges and the value of group_concat_max_len was set to 100001, the size of the data that the agent sent to the Service Manager was too large and caused Service Manager errors. Also, the Security event “Account has Strong MySQL privileges” did not trigger. (Bug#41987)

  • Query Analyzer's Query Type filter for SELECT ignored statements starting with parenthesis.

    If you sent a statement through Query Analyzer starting with parenthesis, such as:

    (SELECT 1 FROM dual);

    and then attempted to filter for SELECT queries only, queries starting with parenthesis were not displayed. (Bug#41968)

  • The agent angel process was spawning too soon, which caused a duplicate UUID error.

    g_error() logged a fatal error, and called abort(). This terminated the program. Then the angel respawned with the same UUID, but with a -1 session resync request, which the MEM server denied because the old session was still active. This resulted in a permissions denied error (1142) on the mysql.inventory table.

    2008-12-17 18:58:58: (message) agent_mysqld.c:313: [mysql] mysqld is local and directly connected
    2008-12-17 18:58:58: ((error)) agent_mysqld.c:444: [mysql] mysql_real_query("SELECT value
    FROM mysql.inventory WHERE name = 'uuid'") failed: SELECT command denied to user
    'ent_agent'@'127.0.0.1' for table 'inventory' (errno=1142)
    2008-12-17 18:58:58: (debug) chassis.c:282: 15134 returned: 15134
    2008-12-17 18:58:58: (message) chassis.c:304: [angel] PID=15134 died on signal=6 (it used
    0 kBytes max) ... waiting 3min before restart
    2008-12-17 18:59:00: (debug) chassis.c:244: we are the child: 15149
    2008-12-17 18:59:00: (message) chassis.c:259: [angel] we try to keep PID=15149 alive
    2008-12-17 18:59:00: (debug) chassis.c:277: waiting for 15149
    2008-12-17 18:59:00: (message) mysql-proxy 0.7.0 started
    2008-12-17 18:59:00: (message) MySQL Monitor Agent 2.0.0.7111 started.
    

    (Bug#41600)

  • master_uuid discovery did not work with MySQL Server versions prior to 5.1. master_uuid did not show in any Agent to Monitor communications, and no log or error messages were generated.

    However, now the bug has been fixed, an Agent monitoring a 5.0 MySQL Server would register the following in its logs:

    ...
     <classname>slavestatus</classname>
     <instance>12515cdc-8c00-4223-9d2a-2666a403512c</instance>
     <attribute>Master_uuid</attribute>
    </target>
    <utc>2009-03-03T19:58:05.700Z</utc>
    <value>b2fd9f86-6e42-49f2-b930-e8fb3e728179</value>
    

    Note the presence of master_uuid. (Bug#41525)

  • The master_uuid was not used for replication topology discovery.

    The agent collected master_uuid by reading the master.info file, and then running a SELECT directly against its master. This was to try and read the mysql.inventory table on the master to obtain the instance master_uuid.

    However, this was not being used correctly by the replication topology discovery within the server. (Bug#41519)

  • Queries such as SELECT against the master mysql.inventory was not logged on slave-based agents. This made diagnosing topology discovery issues difficult. (Bug#41518)

  • After an error was generated due to an incorrect password while trying to create a new user, the following error was obtained when subsequently attempting to create a valid new user:

    U0002 You must log in to access the requested resource

    (Bug#41384)

  • Agent startup failed on Solaris 10. The error generated was:

    # ./mysql-monitor-agent start
    Bad string
    ERROR! /opt/mysql/enterprise/agent/etc/mysql-monitor-agent.ini has to have a
    [mysql-proxy].pid-file setting
    

    This was caused by unexpected behavior of the tr command. (Bug#41260)

  • On the Query Analysis page, if a query was clicked the minimum displayed was greater than the average. (Bug#41259)

  • In some circumstances the agent/proxy ran out of file descriptors, causing secondary failures. It could not recover from that state. The relevant part of the log file is shown here:

    2008-11-27 11:11:00: (critical) last message repeated 2 times
    2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
    2008-11-27 11:11:30: (critical) network-socket.c.292: socket(127.0.0.1:3306) failed: Too many open files (24)
    2008-11-27 11:11:30: (critical) proxy-plugin.c.1532: Cannot connect, all backends are down.
    2008-11-27 11:20:22: (critical) last message repeated 4 times
    2008-11-27 11:20:22: (critical) network-io.c:215:
    curl_easy_perform('https://user:password@merlin-dashboard:443/heartbeat') failed:
    SSL connection timeout (curl-error = 'Timeout was reached' (28), os-error = 'Connection refused' (111))
    

    (Bug#41068)

  • If an installation of Service Manager 2.0.0.7102 included a backup directory, due to a previous upgrade, and was upgraded using at least Service Manager 2.0.0.7103, then the installer displayed an error message and exited.

    The error message displayed was:

    There has been an error.
    Error renaming /Applications/mysql/enterprise/monitor/apache-tomcat to
    /Applications/mysql/enterprise/monitor/backup/apache-tomcat
    The application will exit now
    

    (Bug#40996)

  • The Agent started without problems and connected to the master. But it was unable to perform a SELECT from the table mysql.inventory in order to obtain server information. (Bug#40933)

  • Canonical Query Text for Select -1 was displayed as SELECT -? instead of SELECT ? on the Query Analyzer tab. (Bug#40435)

  • The agent installer for Solaris 8 x86 32-bit was missing. (Bug#40248)

  • The MySQL Enterprise Monitor Dashboard did not display the subscribed notification group(s) on the Advisor Current Scheduled and Add to Schedule pages. (Bug#36007)

  • The startup scripts supplied with MySQL Network Monitoring and Advisory tool did not supply all of the LSB init.d script options required. A list of the required options can be found at the following website http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html

    The required options missing include status and force-reload. The option status is used by monitoring tools and cluster software such as Red Hat Cluster, to ensure that the service is still running. The force-reload option is an alias for restart. (Bug#29848)

  • Multiple errors showed in the agent log after issuing a SHOW INNODB STATUS statement. The InnoDB Buffer Poolgraph also went blank. (Bug#27372)

C.2.4. Changes in MySQL Enterprise Monitor 2.0.4 (5th February 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.3.

Bugs fixed:

  • The Monitor Agent did not log connections to, and disconnects from, the monitored database.

    This meant it was not possible to check if the Agent was connected to the database by simply looking at the log file. (Bug#42403)

  • The Monitor Agent failed to create the mysql.inventory table. The logs displayed the following error message:

    (critical) (share/mysql-proxy/quan.lua:711) [proxy] please add SELECT permissions for
    this user on mysql.inventory to enable the QUAN feature, got Table 'mysql.inventory'
    doesn't exist

    This happened even though the Monitor Agent used the root account. (Bug#42389)

  • After installing Monitor Agent 2.0.4.7138 and then starting it with --version, the incorrect version was displayed. Although 2.0.4.7138 was installed, the Monitor Agent displayed the version number as 2.0.2.7138. (Bug#42263)

  • An invalid path was shown in the error message if the upgrade installer failed to find the previous install location.

    The error message is shown below, note that the error message displays a different path to that provided by the user:

    Please specify the directory that contains the previous installation of the MySQL
    Enterprise Monitor Agent
    
    Installation directory [/home/mysql/mysql/enterprise/agent]: /var/lib/mysql/agent
    
    Warning: The directory /home/mysql/mysql/enterprise/agent does not contain a
    previous installation. Please select the right installation directory.
    Press [Enter] to continue :
    ----------------------------------------------------------------------------
    Please specify the directory that contains the previous installation of the MySQL
    Enterprise Monitor Agent

    (Bug#42200)

  • The agent password error in the Service Manager did not log the originating host, making it impossible to determine the agent that failed to log in:

    ErrorJan 5, 2009 4:56:08 PM<?xml version='1.0'?><exceptions><error><![CDATA[E1702:
    IncorrectPasswordException: [agent]]]></error></exceptions>

    (Bug#42139)

  • The Service Manager's JDBC connections did not have sql_mode set to include NO_ENGINE_SUBSTITUTION. This resulted in the failure of Data Definition Language (DDL) if the Service Manager was inadvertently pointed to an incorrect mysqld instance. (Bug#42137)

  • A number of Advisor rules had advice text that had not been translated into Japanese. The Advisors that contained untranslated rules included Performance, Schema and Security. (Bug#42067)

  • Monitor Agent configuration files had global read privileges on the filesystem. (Bug#41794)

  • When the log files rotated to the maximum allowed by the log4j configuration, the metadata contained in the FileAppender became out of synchronization due to a logic bug. This caused an assertion error on any subsequent request for the logs tab or data. (Bug#41593)

  • SNMP trap messages were sending 127.0.0.1 as the IP address, and there was no feature to allow the user to configure the IP address contained in the SNMP message, which would have been useful for troubleshooting. (Bug#41361)

  • On all available test systems, including SUSE Linux Enterprise Server (SLES) 9 and 10 x86-32, x86-64, IA64, and Ubuntu 6.10 x86-64, the agent memory grew incrementally within ~3 hours to ~25M.

    The agents then switched to the 'red' condition on the dashboard and no more data was reported. The agent processes were still alive.

    This was also present in MySQL Enterprise Monitor version 2.0.0.7111 on Suse 7.3, with the glibc2.2 x86 agent.

    There was no load on the monitored servers, and the problem also occurred when the “self-quan” was not configured. (Bug#41244)

  • Although the Monitor tab loaded initially, after a 64-bit MySQL server running a 32-bit MySQL Monitor Agent was clicked, a Null Pointer Exception was generated. (Bug#41164)

  • The Monitor Agent startup configuration did not seem to work and did not generate a log file. (Bug#40583)

  • An error generated by a rule failed to clear.

    When a rule was created with the os:disk:fs_used data item, if the instance was not a valid mount point then the Monitor Agent reported the error:

    2008-08-11 17:57:00: (critical) disk-get failed for all: 2

    Note the above instance was for “all”, and similar results occurred for instance “disk”.

    The issue was that upon editing the rule, or even deleting the rule, the agent still showed the above error type. Restarting the agent and the monitoring service failed to remove the error. (Bug#38709)

  • If the “On Save send test trap” checkbox was checked when the Save button was clicked and the locale was set to Japanese, an error occurred. The orange error banner was displayed at the top of the page with the error message in Japanese. (Bug#32069)

C.2.5. Changes in MySQL Enterprise Monitor 2.0.3 (23rd January 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.2.

Bugs fixed:

  • The Monitor Agent failed to connect to the server, and no error message was displayed in the log file.

    However, when the log verbosity level was set to message, the following message was recorded:

    2009-01-12 13:34:43: (warning) agent_mysqld.c:600: agent connecting to mysql-server
    failed: mysql_real_connect(host = '127.0.0.1', port = 3306, socket = ''): Lost connection
    to MySQL server at 'reading initial communication packet', system error: 0 (mysql-errno =
    2013)

    (Bug#42044)

  • There was a mismatch between the contents of an SNMP Trap from MySQL Enterprise Monitor and the definition given in the file MONITOR.MIB. (Bug#41912)

  • If a copy was made of a standard rule, the resulting Wiki markup was incorrect, resulting in the display of user-interface text containing HTML markup. (Bug#41375)

  • Allowing the heat chart rules to be set to unscheduled caused the user interface to appear broken. (Bug#41312)

  • When a custom rule requiring disk information was created, for example:

    [Expression]
    %disk_reads%> THRESHOLD
    
    [Thresholds]
    Critical Alert: 9000
    Warning Alert: 3000
    Info Alert: 1000
    
    [Variable Assignment]
    variables: %disk_reads%
    Data Item: os:disk:disk_reads
    Instance: /

    The following error was written to the file mysql-service-agent.log:

    2007-09-05 17:11:00: (critical) disk-get failed for c0d0p1: 2

    It therefore appeared that the Monitor Agent was not able to obtain the required information. (Bug#30820)

C.2.6. Changes in MySQL Enterprise Monitor 2.0.2 (14th January 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.1.

Bugs fixed:

  • The Complete Setup button was missing from the Setup page you were taken to after the current subscription expired. (Bug#41685)

  • If the host-id of the monitored instance and the host-id of the current agent did not match, the agent generated the following error message:

    Please TRUNCATE TABLE mysql.inventory on this mysql-instance and restart the agent.

    However, it did not suggest using sql_log_bin = 0. This is used for all other actions against this table so that they are not replicated to slaves, each of which has their own copy of this table. (Bug#41673)

  • The Agent did not start up when the monitored server had many databases and tables, and was under heavy load. This was because the trigger_schema query was taking too long on agent start up. (Bug#41555)

  • The Monitor Agent failed to install on Solaris 10 x86. The following error was generated:

    Installing
    0% ______________ 50% ______________ 100%
    ########################################
    Warning: Problem running post-install step.
    Installation may not complete correctly
    Error running /usr/local/mysqlagent/bin/mysql-monitor-agent
    --defaults-file=/usr/local/mysqlagent/etc/mysql-monitor-agent.ini
    --plugins=agent --agent-generate-uuid=true : 2008-12-12 13:06:02: (critical)
    Conversion from character set '646' to 'UTF-8' is not supported
    2008-12-12 13:06:02: (message) shutting down normally

    (Bug#41445)

  • The console/stdout appender remained in the log4j configuration, which meant that all the MySQL Enterprise Monitor server logs were duplicated to Catalina's stdout, and thus catalina.out, which was wasteful, especially as that file was not rotated or managed. (Bug#41439)

  • When creating new multiple user accounts, the first attempt worked fine. However, following attempts to create new users did not show the Query Analyzer Options in the Create User popup until the role field was changed. (Bug#41430)

  • When login privileges were required the Service Manager did not redirect the user to the login page. This resulted in error messages being displayed rather than simply redirecting the user to the login page. This problem typically occurred if it was necessary to restart Tomcat. (Bug#41320)

  • The monitor 2.0.0.7105 and 2.0.0.7122 Solaris Intel update installer quits unexpectedly. The installer exits from the GUI in the Backup of Previous Installation screen, when OpenSolaris is running on top of Sun xVM.

    The console output for both installer versions is given below:

    shell> ./mysqlmonitor-2.0.0.7105-solaris-intel-update-installer.bin
    X Error of failed request:  BadMatch (invalid parameter attributes)
      Major opcode of failed request:  73 (X_GetImage)
      Serial number of failed request:  21161
      Current serial number in output stream:  21161
    shell> ./mysqlmonitor-2.0.0.7122-solaris-intel-update-installer.bin
    X Error of failed request:  BadMatch (invalid parameter attributes)
      Major opcode of failed request:  73 (X_GetImage)
      Serial number of failed request:  21148
      Current serial number in output stream:  21148

    (Bug#41315)

  • The Rename Group function failed if the new group name was different to the current one only in the case used; for example, if “Merlin” was changed to “MERLIN”.

    The error generated was:

    U0105 This group name is already in use. Enter a different name.

    (Bug#41266)

  • The Agent returned an inventory list of all databases and tables. This information was not used by MySQL Enterprise Monitor, other than to populate the inv_databases and inv_tables tables. For large-scale deployments, where there were many databases and tables, this resulted in redundant XML messages being sent from the Agent to the Service Manager. (Bug#33150)

C.2.7. Changes in MySQL Enterprise Monitor 2.0.1 (15th December 2008)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.0.

Bugs fixed:

  • Having an installation with over 420 master binlogs resulted in the mysql::status graph not being plotted. (Bug#41314)

  • The MySQL Enterprise Monitor installer generated a segfault on RedHat Fedora 10:

    shell> ./mysqlmonitor-2.0.0.7105-linux-x86-installer.bin
    Segmentation fault

    (Bug#41196)

C.2.8. Changes in MySQL Enterprise Monitor 2.0.0 (11th December 2008)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 1.3.3.

Functionality added or changed:

  • Important Change: The server-name configuration parameter is deprecated. For compatibility, during an upgrade, the information will be migrated to a displayname configuration parameter within the individual instance configuration files. This configuration parameter is provided only for compatibility, as display name information is now stored within the main repository. Support for displayname is also deprecated and will be removed in a future release.

  • Important Note: The rules “32-Bit Binary Running on 64-Bit AMD Or Intel System” and “Key Buffer Size Greater Than 4 GB” occasionally do not evaluate correctly due to timing issues. This causes them to be displayed with the Severity level of “Unknown”. This is a known issue and will be resolved in future versions of MySQL Enterprise Monitor.

  • Important Note: When you start the Merlin 2.0 agent from the command line on Windows, you get the following error dialog:

    "mysql-proxy.exe - Entry Point Not Found"
    "The procedure entry point libiconv_set_relocation_prefix could not be located in the
    dynamic link library iconv.dll"

    If you click OK the agent works fine after that.

    This only occurs when starting the agent from the command line, and only when there is another version of one of the DLLs that the agent uses somewhere on the current path. This error can be avoided by opening a command prompt, typing SET PATH= to clear the path, and then starting the agent.

  • The following has been added to the Tomcat config.properties properties file:

         # max connections in the pool for the repository
         default.maxActive=70
    

    (Bug#40652)

  • The dashboard could be used to change the agent password to one containing the @ character, or other special characters, which subsequently caused errors. To fix this problem, special characters in passwords are now prevented by the dashboard. The list of disallowed special characters can be found at the following location: http://en.wikipedia.org/wiki/Percent-encoding#Types_of_URI_characters (Bug#37172)

  • The Query Analysis page was missing the Refresh dropdown control that the Monitor, Events, and Graphs pages had at the top. (Bug#36831)

  • The User Interface only returned error strings, without any associated error codes. This meant that if the error string was in a language that the user did not understand, it would be very difficult to determine which error actually occurred.

    The User Interface now supports error codes, as well as error strings. This change allows easier testing of multiple locales. (Bug#32131)

  • The wording was changed on the fading popup subscription alert. The text “account” was changed to “subscription”. (Bug#31492)

  • The alert thresholds for the Query Cache Advisor were changed:

     Information Warning Critical
    From 95 85 75
    To 60 50 40

    (Bug#30969)

  • The agent log file name has changed from mysql-service-agent.log to mysql-monitor-agent.log. The old log file will be retained during a upgrade install.

Bugs fixed:

  • Starting a new agent against an instance that contained many databases broke up the initial discovery packet, causing collections such as CPU usage and their graphs to fail. See also Bug#33150 and Bug#41314. (Bug#41933)

  • When altering an existing rule you had to add an empty string, "", to any threshold level that was empty. Otherwise, the rule failed to run and the resulting exceptions caused the Events page to be unusable due to duplicate key exceptions. (Bug#41310)

  • After installing the 2.0.0.7119 Dashboard the following error was generated in the logs:

    com.opensymphony.xwork2.util.OgnlValueStack  Warning  Dec 5, 2008 10:41:26 AM  Caught
    an Ognl exception while getting property titleAddition

    (Bug#41252)

  • The dc_ng_long_now table became very large partly due to an unused column begin_time. (Bug#41093)

  • Although there was a unique constraint on the user name, it was not enforced during first-time setup. This resulted in a stack trace being produced, rather than a more user-friendly error message, if the same name was used for the admin and agent accounts. (Bug#40870)

  • MySQL Enterprise Monitor server had stopped sending up/down SNMP traps. (Bug#40861)

  • The Query Analyzer's Explain Query tab did not have pop up text or a link to the documentation regarding SELECT queries. (Bug#40841)

  • When you tried to import a Trial-level advisor JAR using a Trial user account, one of the following error messages was generated:

    U0009 The uploaded Advisor jar was invalid
    U0161 Please import a Platinum level Advisor .jar to use with this Platinum level product key

    (Bug#40834)

  • Meta Info on the Dashboard did not display information for the meta data os_description. (Bug#40830)

  • Attempting to create an alias of statements such as COMMIT, ROLLBACK, BEGIN, resulted in the error:

    Can't find template commitTnx.st; group hierarchy is [HTMLFormatting]
    org.antlr.stringtemplate.StringTemplateGroup.lookupTemplate(StringTemplateGroup.java:507)
    

    (Bug#40736)

  • Trying to upgrade from 2.0.0.7088 to 2.0.0.7092 failed as there was a missing file. When the update program mysqlmonitor-2.0.0.7092-solaris-intel-update-installer.bin was run, the file /tmp/com/mysql/merlin/server/version.props could not be found. (Bug#40692)

  • On OS X with Java 1.5, Tomcat crashed on launch with the error:

    Invalid memory access of location 00000007 eip=013df179
    

    (Bug#40689)

  • When the agent was installed using the command line installer and --enableproxy 0 was specified, the installer should have removed quan.lua from the agent-item-files option in the INI file. (Bug#40551)

  • The Agent could not connect to a database with the hostname set to localhost. Doing so resulted in the error:

    (critical) the MySQL server could not be reached at socket '(null)', we will check in 10 seconds
    

    (Bug#40530)

  • The update installer for the 2.0 Monitor did not have an Is SSL support required? checkbox. Therefore, the appropriate SSL connector definition was commented out in the conf/server.xml file. (Bug#40414)

  • The Service Manager installer did not uninstall or wipe out the previous installation if you answered “Yes” to the question:

    The directory you selected already contains a MySQL installation. If you continue installation all data will be lost. Do you wish to continue?” (Bug#40410)

  • If you unchecked the Enable Proxy checkbox on the Query Analysis Configuration screen, the agent's INI file still contained proxy configuration data and was not commented out. (Bug#40272)

  • As different queries were sent through the agent it used increasing amounts of memory. (Bug#40260)

  • The Service Manager installer set the Java Virtual Machine option HeapDumpPath to <install_root>\temp on Windows and /tmp on other platforms. For consistency the HeapDumpPath directory should have been set to <install_root>\tmp on Windows. (Bug#40215)

  • When using the command line agent setup program, a socket file was not accepted for the monitored instance. (Bug#40085)

  • The language option when installing the MySQL Enterprise Monitor in Japanese using the command-line instllaer has been changed from jp to ja. (Bug#40082)

  • When monitoring MySQL 5.1.24 and above, the user used by the agent to connect to the MySQL server for monitoring must have the PROCESS privilege. (Bug#40050)

  • The check box option string “Is SSL support required?”, on the Tomcat Server Option dialog of the Monitor installation, was not correctly translated into Japanese. (Bug#39814)

  • The base application directory for the MySQL Enterprise Dashboard has been updated from http://localhost:18080/merlin to http://localhost:18080/. (Bug#39403)

  • If the Service Manager or the MySQL Server running the Repository crashed, they did not restart automatically. (Bug#39377)

  • If the agent crashed, there was no watchdog, angel or keep-alive mechanism to restart the agent and keep it running. (Bug#39374)

  • If the MySQL client libraries were located in a nonstandard location, the agent 2.0.0.7042 installer failed with a “library not found” error. (Bug#39317)

  • For the rule “Server-Enforced Data Integrity Checking Not Strict”, the Recommended Action did not display correctly. It displayed as SET sql_mode=modes, rather than SET [GLOBAL|SESSION] sql_mode=modes. (Bug#39261)

  • A query that was issued through the proxy, and that had an auto-explain performed on that query, did not give the correct response to a subsequent query of SELECT FOUND_ROWS(). (Bug#39223)

  • It was not possible to establish a connection with the Dashboard using the SSL protocol (https://). (Bug#39198)

  • When a 1.3 MySQL Enterprise Monitor installation with many rules scheduled was upgraded to 2.0, the upgraded installation was then found to have only the heat chart rules scheduled. (Bug#39043)

  • The agent installer did not allow a second agent to be installed on Windows. (Bug#38976)

  • The Dashboard incorrectly diplayed that insufficient licenses were available, even though sufficient licenses had been purchased. (Bug#38514)

  • After running the MySQL Service Agent uninstall program, the file /etc/init.d/mysql-service-agent remained present on the server. (Bug#38490)

  • The notice fader continued to display English text after you changed the locale to Japanese. (Bug#38460)

  • The Subscription Expired pop-up window referred to the “Global Preferences” page, instead of the “Global Settings” page. (Bug#38358)

  • An inappropriate time zone was used to parse user-entered date and time strings. (Bug#38323)

  • A sigar network stats error was generated on the Solaris platform:

    # /opt/mysql/enterprise/agent/bin/mysql-service-agent --version
    MySQL Service Agent - 1.2.0.7879, (glib lib=2.8.5, headers=2.8.5)
    
    SunOS mysqlprd01 5.10 Generic_127127-11 sun4v sparc SUNW,T5240
    
    2008-07-21 10:07:24: (critical) sigar_net_interface_config_primary_get() failed: 6
    2008-07-21 10:08:00: (critical) sigar_net_interface_config_primary_get() failed: 6
    
    # /opt/mysql/enterprise/agent/bin/sigar-test-all >/tmp/test.txt
    sigar_net_interface_stat_get(e1000g0:2) failed#

    (Bug#38302)

  • After deleting a server from the Settings, Manage Servers tab, at the very bottom of the page the Monitoring x instances on x host values did not reflect the deletion. (Bug#38225)

  • The MySQL Enterprise Monitor alert “INFO Alert - Users Can View All Databases On MySQL Server (v 1.5 *)” from the Security advisor was incorrect. This is because the default server behavior allows users to see databases for which they have privileges, not “all databases on server” as suggested by the alert. (Bug#38052)

  • The “Maximum Connection Limit Nearing Or Reached” advisor did not generate a new Critical Alert event when there was an open info success event. (Bug#37816)

  • The Linux IA64 installer appeared to crash. The installer appeared to crash on RH4_IA64 if called with option "--version":

    -------------------------------------------------------------------------------
    <INSTALLER> --version
    mysqlmonitorage(30704): unaligned access to 0x6000000000a8413c, ip=0x2000000003ddd5f0
    mysqlmonitorage(30704): unaligned access to 0x6000000000a84144, ip=0x2000000003ddd5f1
    mysqlmonitorage(30704): unaligned access to 0x6000000000a8414c, ip=0x2000000003ddd600
    mysqlmonitorage(30704): unaligned access to 0x6000000000a84154, ip=0x2000000003ddd601
    MySQL Enterprise Monitor Agent 0.7.0.1737 --- Built on 2008-06-25 19:31:53
    
    -------------------------------------------------------------------------------

    However, this warning is harmless and will not impact the operation of the agent. (Bug#37496)

  • If the log-level option in the agent configuration file was set to an unknown level by mistake, the init.d script appeared to enter an infinite loop. (Bug#37108)

  • Malformatted server meta information appeared on the Dashboard; RAM and Disk Space appeared under the CPU category. (Bug#36740)

  • A “rename” link incorrectly appeared next to the Upgrade category on the Manage Rules page. (Bug#36584)

  • In the case where exceptions were passed through to the User Interface, the substituted arguments in the message contained developer-only information. (Bug#36580)

  • Agent Version, Last MySQL Contact, OS Info, CPU Info, and IP Addresses were all blank on the dashboard when the agent for the selected server was not functioning. (Bug#36301)

  • mysql-monitor-agent became confused by the .DS_Store files that are created on Mac OS X. (Bug#36216)

  • The rule “Key Buffer Size Greater Than 4 GB” incorrectly triggered the following alert:

    CRITICAL Alert - Key Buffer Size Greater Than 4 GB

    However, on non-Windows systems, a key buffer size greater than 4 GB is supported. (Bug#36143)

  • Since the repository database for MySQL Enterprise Monitor uses InnoDB there was no way to reduce the size of the data files after an old log/event data purge operation. Further, the purge data operation executed once per day, and had no option to trigger the purge operation manually. (Bug#35971)

  • On the Graphs page, if all graphs were expanded, then the Time Display interval updated, the page was refreshed with the Expand All button displayed, even though all the graphs were already expanded. (Bug#35917, Bug#35133)

  • The Meta Info area of the Monitor page incorrectly reported the operating system version number for the MySQL version. (Bug#35836)

  • The rule “XA Distributed Transaction Support Enabled For InnoDB” incorrectly sent a warning when the binary log was on. (Bug#35786)

  • On the Monitor page, the time displayed for Last MySQL Contact lagged behind that for Last Agent Contact by a large amount. (Bug#35774)

  • MySQL Enterprise Monitor did not update replication settings correctly. After a slave became the master, the Adviser still referred to it as a slave. (Bug#35771)

  • The Adviser email suggested using the --log-queries-not-using-indexes option. However, this option is not available in MySQL Server versions prior to 4.1. (Bug#35770)

  • Thumbnail graphs did not update properly after a time zone change. (Bug#35756)

  • If a system had a global wait_timeout lower than the general activity of the agent, the agent was disconnected. The monitored server then logged an error and incremented Aborted_clients. (Bug#35648)

  • Alerts fired after a blackout period based on data collections that happened during the blackout. (Bug#35617)

  • The translation of the Add Row button on the Rule Definition window was incorrect. (Bug#35495)

  • An uninstallation message asked about removing Apache files, even though Apache is no longer used. (Bug#35154)

  • After updating from a previous version to the latest 1.3 version, the Query Cache Has Sub-Optimal Hit Rate was still displayed in English after setting the locale to Japanese. Note, the rule was translated correctly if the full installer was used. (Bug#35134)

  • The MySQL Enterprise Monitor uninstall dialog box had missing text when using the Japanese locale. (Bug#34982)

  • Running the installer with the --help option caused an incorrect message to be displayed. (Bug#34200)

  • When using the unattended unInstall script on Linux together with the option --env deleteUserData=yes the correct warning text was displayed. However, this text should not be displayed in unattended mode. Further, the option --env deleteUserData=yes was not displayed by the --help output. (Bug#34071)

  • Platinum Unlimited customers sometimes received a warning stating incorrectly that their subscription supported zero hosts. (Bug#34010)

  • Clicking on the resolution notes link for a closed event on the events tab showed incorrect behavior. The popup initially showed the resolution notes, but when the resolution tab was clicked the notes disappeared and were replaced by an edit box. (Bug#33935)

  • The status on the product information page was not translated when the user locale was set to Japanese. (Bug#32785)

  • When the locale was set to Japanese, the date picker still had English month titles. (Bug#32741)

  • Flashing display of a pop-up used while saving outgoing email settings was caused by problematic initial placement calculations. (Bug#32579)

  • AIX 5.2 Agent did not work on AIX 5.3. (Bug#32414)

  • When the First Time Setup program was run it did not prompt the user to allow importing an Advisor bundle. (Bug#32199)

  • Agent on MacOSX did not read IP addresses for network interfaces correctly, so the monitor displayed empty host IP addresses. (Bug#32188)

  • HTML code in queries was not escaped when reporting replication errors, causing the code to be rendered into the page. (Bug#32186)

  • The First Run pop-up defaulted to English rather than to the locale set in the browser. (Bug#32129)

  • The error dialog box flashed in the upper left corner before being positioned in the center of the screen. This error dialog box now opens in the center of the screen. (Bug#32068)

  • The Events list did not take into account Daylight Time and Standard Time when listing events that happened during 1:00am-1:59am. An event that occurred at 1:10am Standard Time was listed before an event that occurred 50 minutes before it at 1:20am Daylight Time. (Bug#32016)

  • The pop-up for editing log levels failed to load due to bad instantiation data. (Bug#32013)

  • During the repeated hour of Daylight Savings Time (when 2am turns back into 1am), the graphs were not drawing data. Instead, there was a straight line from the point at 1:00 to the second 1:00, which is what happens if there is no data. The repository did, however, have data for this hour. (Bug#31997)

  • Only US English was supported for a locale setting. Other English variants are now available for the locale setting on the General Settings or the User Preferences pages. (Bug#31801)

  • If the user locale was changed the graph cache would continue to display the graph in the last locale until it timed out. (Bug#31680)

  • No init script was installed for the MySQL Network Monitoring Service Manager, and so it did not restart automatically on reboot. (Bug#31676)

  • The graph's displayed time was not the local time of the Dashboard corresponding to the requested time on the monitored server. (Bug#31656)

  • Saving a rule with a name that already existed resulted in a stack trace in the window, instead of a more user-friendly error message. (Bug#30925)

  • The network.mysql.com error messages were remapped thereby causing confusion. For example, the following error message:

    E9000: MySQL Enterprise Customer Center is having difficulties fetching your contract information. Please contact enterprise-feedback@mysql.com for assistance.

    Was remapped to:

    Unable to connect to verify credentials (Bug#30873)

  • A newly added server showed as “down” in the user interface, and could potentially have sent a false alarm notification. (Bug#30735)

  • The information on the Advisors, Check For Updates page did not accurately reflect how many rules and graphs were actually in the database and available to the user. (Bug#29623)

  • The agent did not process SIGHUP. (Bug#29380)

  • Monitor did not have a facility to stop or downgrade an agent collection frequency. (Bug#28589)

  • After an agent installation was updated from 1.0.1.4391 to 1.1.0.4899, the version in the Add/Remove Programs menu was incorrectly displayed as 1.0.1.4391, even though the update was successful and the file version of agent.exe was correctly displayed as 1.1.0.4899. (Bug#27447)

  • When viewing the Results of an Event in the Events tab of the Dashboard, the Notifications section did not reflect the Notifications settings at the time the Event was triggered, but rather the Notifications settings at the time the Event Results were viewed. (Bug#26349)

  • When the Monitor Agent was remotely monitoring a MySQL server it incorrectly reported that it could collect operating system information. (Bug#22497)

  • The Account Without Password advisor did not report all users who were without a password, it only reported one. (Bug#15165)

C.3. MySQL Connector/ODBC (MyODBC) Change History

C.3.1. Changes in MySQL Connector/ODBC 5.1.7 (Not yet released)
C.3.2. Changes in MySQL Connector/ODBC 5.1.6 (09 November 2009)
C.3.3. Changes in MySQL Connector/ODBC 5.1.5 (18 August 2008)
C.3.4. Changes in MySQL Connector/ODBC 5.1.4 (15 April 2008)
C.3.5. Changes in MySQL Connector/ODBC 5.1.3 (26 March 2008)
C.3.6. Changes in MySQL Connector/ODBC 5.1.2 (13 February 2008)
C.3.7. Changes in MySQL Connector/ODBC 5.1.1 (13 December 2007)
C.3.8. Changes in MySQL Connector/ODBC 5.1.0 (10 September 2007)
C.3.9. Changes in MySQL Connector/ODBC 5.0.12 (Never released)
C.3.10. Changes in MySQL Connector/ODBC 5.0.11 (31 January 2007)
C.3.11. Changes in MySQL Connector/ODBC 5.0.10 (14 December 2006)
C.3.12. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)
C.3.13. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)
C.3.14. Changes in MySQL Connector/ODBC 5.0.7 (08 November 2006)
C.3.15. Changes in MySQL Connector/ODBC 5.0.6 (03 November 2006)
C.3.16. Changes in MySQL Connector/ODBC 5.0.5 (17 October 2006)
C.3.17. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)
C.3.18. Changes in Connector/ODBC 5.0.2 (Never released)
C.3.19. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)
C.3.20. Changes in MySQL Connector/ODBC 3.51.28 (Not yet released)
C.3.21. Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008)
C.3.22. Changes in MySQL Connector/ODBC 3.51.26 (07 July 2008)
C.3.23. Changes in MySQL Connector/ODBC 3.51.25 (11 April 2008)
C.3.24. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)
C.3.25. Changes in MySQL Connector/ODBC 3.51.23 (09 January 2008)
C.3.26. Changes in MySQL Connector/ODBC 3.51.22 (13 November 2007)
C.3.27. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)
C.3.28. Changes in MySQL Connector/ODBC 3.51.20 (10 September 2007)
C.3.29. Changes in MySQL Connector/ODBC 3.51.19 (10 August 2007)
C.3.30. Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)
C.3.31. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)
C.3.32. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)
C.3.33. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)
C.3.34. Changes in MySQL Connector/ODBC 3.51.14 (08 March 2007)
C.3.35. Changes in MySQL Connector/ODBC 3.51.13 (Never released)
C.3.36. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)
C.3.37. Changes in MySQL Connector/ODBC 3.51.11 (28 January 2005)

C.3.1. Changes in MySQL Connector/ODBC 5.1.7 (Not yet released)

Bugs fixed:

  • If NO_BACKSLASH_ESCAPES mode was used on a server, escaping binary data led to server query parsing errors. (Bug#49029)

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

C.3.2. 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 allowing 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)

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

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

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

C.3.6. 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 allows 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)

C.3.7. 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: Disallow SET NAMES in initial statement and in executed statements.

  • A wrapper for the SQLGetPrivateProfileStringW() function, which is required for Unicode support, has been created. This function is missing from the unixODBC driver manager. (Bug#32685)

  • Added MSI installer for Windows 64-bit. (Bug#31510)

  • Implemented support for SQLCancel(). (Bug#15601)

  • Added support for SQL_NUMERIC_STRUCT. (Bug#3028, Bug#24920)

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

C.3.8. 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.

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

C.3.10. 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.

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

C.3.12. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)

Connector/ODBC 5.0.9 is the fifth BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Functionality added or changed:

  • Added support for column binding as SQL_NUMBERIC_STRUCT.

  • Added recognition of SQL_C_SHORT and SQL_C_TINYINT as C types.

Bugs fixed:

  • Fixed wildcard handling of and listing of catalogs and tables in SQLTables.

  • Added limit of display size when requested via SQLColAttribute/SQL_DESC_DISPLAY_SIZE.

  • Fixed buffer length return for SQLDriverConnect.

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

C.3.13. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)

Connector/ODBC 5.0.8 is the fourth BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Functionality added or changed:

  • Also made SQL_DESC_NAME only fill in the name if there was a data pointer given, otherwise just the length.

  • Fixed display size to be length if max length isn’t available.

  • Made distinction between CHAR/BINARY (and VAR versions).

  • Wildcards now support escaped chars and underscore matching (needed to link tables with underscores in access).

Bugs fixed:

  • Fixed binding using SQL_C_LONG.

  • Fixed using wrong pointer for SQL_MAX_DRIVER_CONNECTIONS in SQLGetInfo.

  • Set default return to SQL_SUCCESS if nothing is done for SQLSpecialColumns.

  • Fixed MDiagnostic to use correct v2/v3 error codes.

  • Allow SQLDescribeCol to be called to retrieve the length of the column name, but not the name itself.

  • Length now used when handling bind parameter (needed in particular for SQL_WCHAR) - this enables updating char data in MS Access.

  • Updated retrieval of descriptor fields to use the right pointer types.

  • Fixed hanlding of numeric pointers in SQLColAttribute.

  • Fixed type returned for MYSQL_TYPE_LONG to SQL_INTEGER instead of SQL_TINYINT.

  • Fix size return from SQLDescribeCol.

  • Fixed string length to chars, not bytes, returned by SQLGetDiagRec.

C.3.14. 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.

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

C.3.16. 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.

C.3.17. 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

C.3.18. Changes in Connector/ODBC 5.0.2 (Never released)

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

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

C.3.20. Changes in MySQL Connector/ODBC 3.51.28 (Not yet released)

Bugs fixed:

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

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

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

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

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

C.3.24. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)

Bugs fixed:

  • Security Enhancement: Accessing a parameer with the type of SQL_C_CHAR, but with a numeric type and a length of zero, the parameter marker would get stropped 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)

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

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

C.3.27. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)

Bugs fixed:

  • When using a rowset/cursor and add a new row with a number of fields, subsequent rows with fewer fields will include the original fields from the previous row in the final INSERT statement. (Bug#31246)

  • Uninitiated memory could be used when C/ODBC internally calls SQLGetFunctions(). (Bug#31055)

  • The wrong SQL_DESC_LITERAL_PREFIX would be returned for date/time types. (Bug#31009)

  • The wrong COLUMN_SIZE would be returned by SQLGetTypeInfo for the TIME columns (SQL_TYPE_TIME). (Bug#30939)

  • Clicking outside the character set selection box when configuring a new DSN could cause the wrong character set to be selected. (Bug#30568)

  • Not specifying a user in the DSN dialog would raise a warning even though the parameter is optional. (Bug#30499)

  • SQLSetParam() caused memory allocation errors due to driver manager's mapping of deprecated functions (buffer length -1). (Bug#29871)

  • When using ADO, a column marked as AUTO_INCREMENT could incorrectly report that the column allowed NULL values. This was dur to an issue with NULLABLE and IS_NULLABLE return values from the call to SQLColumns(). (Bug#26108)

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

C.3.28. 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 checkbox in setup dialog for FLAG_FIELD_LENGTH (identified as Don't Optimize Column Width within the GUI dialog), which was removed from the driver in 3.51.18.

C.3.29. 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 C.3.30, “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.

C.3.30. 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. In order to enable cached statement support you must switch enable the batched statement option (FLAG_MULTI_STATEMENTS, 67108864, or Allow multiple statements within a GUI configuration). Be aware that batched statements create an increased chance of SQL injection attacks and you must ensure that your application protects against this scenario. (Bug#7445)

  • The SQL_ATTR_ROW_BIND_OFFSET_PTR is now supported for row bind offsets. (Bug#6741)

  • The TRACE and TRACEFILE DSN options have been removed. Use the ODBC driver manager trace options instead.

Bugs fixed:

  • When using a table with multiple TIMESTAMP columns, the final TIMESTAMP column within the table definition would not be updateable. Note that there is still a limitation in MySQL server regarding multiple TIMESTAMP columns . (Bug#9927) (Bug#30081)

  • Fixed an issue where the myodbc3i would update the 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.

C.3.31. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)

Platform specific notes:

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • Binary packages for Sun Solaris are now available as PKG packages.

  • Binary packages as disk images with installers are now available for Mac OS X.

  • A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.

Functionality added or changed:

  • It is now possible to specify a different character set as part of the DSN or connection string. This must be used instead of the SET NAMES statement. You can also configure the character set value from the GUI configuration. (Bug#9498, Bug#6667)

  • Fixed calling convention ptr and wrong free in myodbc3i, and fixed the null terminating (was only one, not two) when writing DSN to string.

  • Dis-allow NULL ptr for null indicator when calling SQLGetData() if value is null. Now returns SQL_ERROR w/state 22002.

  • The setup library has been split into its own RPM package, to allow installing the driver itself with no GUI dependencies.

Bugs fixed:

  • myodbc3i did not correctly format driver info, which could cause the installation to fail. (Bug#29709)

  • 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 allowed ODBC date (XXXX-01-01). Added another option (FLAG_MIN_DATE_TO_ZERO) to mirror this but for bound parameters. FLAG_MIN_DATE_TO_ZERO only changes 0000-01-01 to 0000-00-00. (Bug#13766)

  • If there was more than one unique key on a table, the correct fields were not used in handling SQLSetPos(). (Bug#10563)

  • When inserting a large BLOB field, 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.

C.3.32. 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 curors on results sets with multi-column keys could select the wrong value. (Bug#28255)

  • SQLForeignKeys does not escape _ and % in the table name arguments. (Bug#27723)

  • When using stored procedures, making a SELECT or second stored procedure call after an initial stored procedure call, the second statement will fail. (Bug#27544)

  • SQLTables() did not distinguish tables from views. (Bug#23031)

  • Data in TEXT columns would fail to be read correctly. (Bug#16917)

  • Specifying strings as parameters using the adBSTR or adVarWChar types, (SQL_WVARCHAR and SQL_WLONGVARCHAR) would be incorrectly quoted. (Bug#16235)

  • SQL_WVARCHAR and SQL_WLONGVARCHAR parameters were not properly quoted and escaped. (Bug#16235)

  • Using BETWEEN with date values, the wrong results could be returned. (Bug#15773)

  • When using the Don't Cache Results (option value 1048576) with Microsoft Access, the connection will fail using DAO/VisualBasic. (Bug#4657)

  • Return values from SQLTables() may be truncated. (Bugs #22797)

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

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

C.3.35. Changes in MySQL Connector/ODBC 3.51.13 (Never released)

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

C.3.36. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)

Functionality added or changed:

  • N/A

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)

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

C.4. MySQL Connector/NET Change History

C.4.1. Changes in MySQL Connector/NET Version 6.3.x

C.4.1.1. Changes in MySQL Connector/NET 6.3.2 (Not yet released alpha)

Fixes bugs since 6.3.1.

Bugs fixed:

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

C.4.1.2. Changes in MySQL Connector/NET 6.3.1 (2nd March 2010 alpha)

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

C.4.1.3. Changes in MySQL Connector/NET 6.3.0 (16th 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 in order 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)

C.4.2. Changes in MySQL Connector/NET Version 6.2.x

C.4.2.1. Changes in MySQL Connector/NET 6.2.3 (Not yet released GA)

This release fixes bugs since 6.2.2.

Bugs fixed:

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

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

C.4.2.2. Changes in MySQL Connector/NET 6.2.2 (22nd 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)

C.4.2.3. Changes in MySQL Connector/NET 6.2.1 (16th 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 21.2.6, “Connector/NET Connection String Options Reference” and the tutorial Section 21.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)

C.4.2.4. Changes in MySQL Connector/NET 6.2.0 (21st 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)

C.4.3. Changes in MySQL Connector/NET Version 6.1.x

C.4.3.1. Changes in MySQL Connector/NET 6.1.4 (Not yet released GA)

This release fixes bugs since 6.1.3.

Bugs fixed:

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

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

C.4.3.2. Changes in MySQL Connector/NET 6.1.3 (16th 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)

C.4.3.3. Changes in MySQL Connector/NET 6.1.2 (8th September 2009 GA)

This is the first GA release of 6.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)

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

C.4.3.5. 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 5.4 servers and 6.0.8 and later servers.

  • Session State Provider - This allows 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.

C.4.4. Changes in MySQL Connector/NET Version 6.0.x

C.4.4.1. Changes in MySQL Connector/NET 6.0.6 (Not yet released)

Fixes bugs since 6.0.5.

Bugs fixed:

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

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

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

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

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

C.4.4.3. 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 via 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)

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

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

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

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

C.4.5. Changes in MySQL Connector/NET Version 5.3.x

C.4.5.1. Changes in MySQL Connector/NET 5.3.0 (Not yet 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)

C.4.6. Changes in MySQL Connector/NET Version 5.2.x

C.4.6.1. Changes in MySQL Connector/NET 5.2.8 (Not yet 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 a 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)

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

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

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

C.4.6.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 via 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)

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

C.4.6.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, PublicKeyTopen=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)

C.4.6.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 via 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)

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

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

C.4.6.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 datatype 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 retreiving 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 procedured, the new parameter code which allows 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.

C.4.6.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 issues were identified in the case, connection and scema 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 memvership 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.

C.4.6.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 deifned within the connection string being used. (Bug#31185)

  • Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)

  • Commands executed from within the state change handeler would fail with a NULL exception. (Bug#30964)

  • When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug#30116)

  • Using compression in the MySQL connection with 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)

C.4.7. Changes in MySQL Connector/NET Version 5.1.x

C.4.7.1. Changes in MySQL Connector/NET 5.1.8 (Not yet 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)

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

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

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

C.4.7.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 datatype 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)

C.4.7.4. Changes in MySQL Connector/NET 5.1.5 (Not yet 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)

C.4.7.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 MySqlDataTime.ToString() when the date returned by MySQL was 0000-00-00 00:00:00. (Bug#32010)

  • A syntax error in a set of batch statements could leave the data adapter in a state that appears hung. (Bug#31930)

  • Installing over a failed uninstall of a previous version could result in multiple clients being registered in the machine.config. This would prevent certain aspects of the MySQL connection within Visual Studio to work properly. (Bug#31731)

  • 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 deifned within the connection string being used. (Bug#31185)

  • Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)

  • Commands executed from within the state change handeler would fail with a NULL exception. (Bug#30964)

  • Extracting data through XML functions within a query returns the data as System.Byte[]. This was due to 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)

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

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

C.4.7.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.

C.4.7.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!).

C.4.8. Changes in MySQL Connector/NET Version 5.0.x

C.4.8.1. Changes in MySQL Connector/NET 5.0.10 (Not yet 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)

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

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

C.4.8.2. Changes in MySQL Connector/NET 5.0.9 (Not yet 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 MySqlDataTime.ToString() when the date returned by MySQL was 0000-00-00 00:00:00. (Bug#32010)

  • A syntax error in a set of batch statements could leave the data adapter in a state that appears hung. (Bug#31930)

  • Installing over a failed uninstall of a previous version could result in multiple clients being registered in the machine.config. This would prevent certain aspects of the MySQL connection within Visual Studio to work properly. (Bug#31731)

  • Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug#31433)

  • Column name metadata was not using the character set as deifned within the connection string being used. (Bug#31185)

  • Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)

  • Commands executed from within the state change handeler would fail with a NULL exception. (Bug#30964)

  • When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug#30116)

  • The server error code was not updated in the Data[] hash, which prevented DbProviderFactory users from accessing the server error code. (Bug#27436)

  • Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug#13991)

C.4.8.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.

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

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

C.4.8.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 allow 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 correctl CLR Datatype. (Bug#25907)

  • GetSchema and DataTypes would throw an exception due to an incorrect table name. (Bug#25906)

  • MySqlConnection throws an exception when connecting to MySQL v4.1.7. (Bug#25726)

  • SELECT did not work correctly when using a WHERE clause containing a UTF-8 string. (Bug#25651)

  • When closing and then re-opening a connection to a database, the character set specification is lost. (Bug#25614)

  • Filling a table schema through a stored procedure triggers a runtime error. (Bug#25609)

  • BINARY and VARBINARY columns would be returned as a string, not binary, datatype. (Bug#25605)

  • A critical ConnectionPool error would result in repeated System.NullReferenceException. (Bug#25603)

  • The UpdateRowSource.FirstReturnedRecord method does not work. (Bug#25569)

  • When connecting to a MySQL Server earlier than version 4.1, the connection would hang when reading data. (Bug#25458)

  • Using ExecuteScalar() with more than one query, where one query fails, will hang the connection. (Bug#25443)

  • When a MySqlConversionException is raised on a remote object, the client application would receive a SerializationException instead. (Bug#24957)

  • When connecting to a server, the return code from the connection could be zero, even though the 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.

C.4.8.7. Changes in MySQL Connector/NET 5.0.4 (Not released)

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

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

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

C.4.8.10. Changes in MySQL Connector/NET 5.0.1 (01 October 2006)

Bugs fixed:

  • MySQL Connector/NET on a Tukish operating system, may fail to execute certain SQL statements correctly. (Bug#22452)

  • Starting a transaction on a connection created by MySql.Data.MySqlClient.MySqlClientFactory, using BeginTransaction without specifying an isolation level, causes the SQL statement to fail with a syntax error. (Bug#22042)

  • The MySqlexception class is now derived from the DbException class. (Bug#21874)

  • The # would not be accepted within column/table names, even though it was valid. (Bug#21521)

  • You can now install the 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)

  • Using ExecuteScalar with a datetime field, where the value of the field is "0000-00-00 00:00:00", a MySqlConversionException exception would be raised. (Bug#11991)

  • An MySql.Data.Types.MySqlConversionException would be raised when trying to update a row that contained a date field, where the date field contained a zero value (0000-00-00 00:00:00). (Bug#9619)

  • Executing multiple queries as part of a transaction returns There is already an openDataReader associated with this Connection which must be closed first. (Bug#7248)

  • Incorrect field/data lengths could be returned for VARCHAR UTF8 columns. Bug (#14592)

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

C.4.9. Changes in MySQL Connector/NET Version 1.0.x

C.4.9.1. Changes in MySQL Connector/NET 1.0.11 (Not yet 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)

C.4.9.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, datatype. (Bug#25605)

  • A critical ConnectionPool error would result in repeated System.NullReferenceException. (Bug#25603)

  • When a MySqlConversionException is raised on a remote object, the client application would receive a SerializationException instead. (Bug#24957)

  • High CPU utilization would be experienced when there is no idle connection waiting when using pooled connections through MySqlPool.GetConnection. (Bug#24373)

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

  • Nested transactions do not raise an error or warning. (Bug#22400)

  • An System.OverflowException would be raised when accessing a varchar field over 255 bytes. Bug (#23749)

  • Within Mono, using the PreparedStatement interface could result in an error due to a BitArray copying error. (Bug 18186)

C.4.9.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 procedured 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 Tukish operating system, may fail to execute certain SQL statements correctly. (Bug#22452)

  • The # would not be accepted within column/table names, even though it was valid. (Bug#21521)

  • Calling Close on a connection after calling a stored procedure would trigger a NullReferenceException. (Bug#20581)

  • You can now install the 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 allow single or double quotes in the password. (Bug#16659)

  • The MySqlDateTime class did not contain constructors. (Bug#15112)

  • Called MySqlCommandBuilder.DeriveParameters for a stored procedure that has no paramers would cause an application crash. (Bug#15077)

  • Using ExecuteScalar with a datetime field, where the value of the field is "0000-00-00 00:00:00", a MySqlConversionException exception would be raised. (Bug#11991)

  • An MySql.Data.Types.MySqlConversionException would be raised when trying to update a row that contained a date field, where the date field contained a zero value (0000-00-00 00:00:00). (Bug#9619)

  • When using MySqlDataAdapter, connections to a MySQL server may remain open and active, even though the use of the connection has been completed and the data received. (Bug#8131)

  • Executing multiple queries as part of a transaction returns There is already an openDataReader associated with this Connection which must be closed first. (Bug#7248)

  • Incorrect field/data lengths could be returned for VARCHAR UTF8 columns. Bug (#14592)

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

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

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

C.4.9.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.

C.4.9.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.

C.4.9.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.

C.4.9.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 datatype (Bug#6036)

  • Fixed MySqlDateTime sets IsZero property on all subseq.records after first zero found (Bug#6006)

  • Fixed serializing of floating point parameters (double, numeric, single, decimal) (Bug#5900)

  • Fixed missing Reference in DbType setter (Bug#5897)

  • Fixed Parsing the ';' char (Bug#5876)

  • Fixed DBNull Values causing problems with retrieving/updating queries. (Bug#5798)

  • IsNullable error (Bug#5796)

  • Fixed problem where MySqlParameterCollection.Add() would throw unclear exception when given a null value (Bug#5621)

  • Fixed construtor initialize problems in MySqlCommand() (Bug#5613)

  • Fixed Yet Another "object reference not set to an instance of an object" (Bug#5496)

  • Fixed Can't display Chinese correctly (Bug#5288)

  • Fixed MySqlDataReader and 'show tables from ...' behavior (Bug#5256)

  • Fixed problem in PacketReader where it could try to allocate the wrong buffer size in EnsureCapacity

  • Fixed problem where using old syntax while using the interfaces caused problems

  • Fixed Bug#5458 Calling GetChars on a longtext column throws an exception

  • Added test case for resetting the command text on a prepared command

  • Fixed Bug#5388 DataReader reports all rows as NULL if one row is NULL

  • Fixed problem where connection lifetime on the connect string was not being respected

  • Fixed Bug#5602 Possible bug in MySqlParameter(string, object) constructor

  • Field buffers being reused to decrease memory allocations and increase speed

  • Fixed Bug#5392 MySqlCommand sees "?" as parameters in string literals

  • Added Aggregate function test (wasn't really a bug)

  • Using PacketWriter instead of Packet for writing to streams

  • Implemented SequentialAccess

  • Fixed problem with ConnectionInternal where a key might be added more than once

  • Fixed Russian character support as well

  • Fixed Bug#5474 cannot run a stored procedure populating mysqlcommand.parameters

  • Fixed problem where connector was not issuing a CMD_QUIT before closing the socket

  • Fixed problem where Min Pool Size was not being respected

  • Refactored compression code into CompressedStream to clean up NativeDriver

  • CP1252 is now used for Latin1 only when the server is 4.1.2 and later

  • Fixed Bug#5469 Setting DbType throws NullReferenceException

  • Virtualized driver subsystem so future releases could easily support client or embedded server support

C.4.9.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.

C.4.10. 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 allow use of @ parameter marker.

  • MySqlCommandBuilder. (Bug#4658)

  • ByteFX.MySqlClient caches passwords if Persist Security Info is false. (Bug#4864)

  • Updated license banner in all source files to include FLOSS exception.

  • Added new .Types namespace and implementations for most current MySql types.

  • Added MySqlField41 as a subclass of MySqlField.

  • Changed many classes to now use the new .Types types.

  • Changed type enum int to Int32, short to Int16, and bigint to Int64.

  • Added dummy types UInt16, UInt32, and UInt64 to allow an unsigned parameter to be made.

  • Connections are now reset when they are pulled from the connection pool.

  • Refactored auth code in driver so it can be used for both auth and reset.

  • Added UserReset test in PoolingTests.cs.

  • Connections are now reset using COM_CHANGE_USER when pulled from the pool.

  • Implemented SingleResultSet behavior.

  • Implemented support of unicode.

  • Added char set mappings for utf-8 and ucs-2.

  • Time fields overflow using bytefx .net mysql driver (Bug#4520)

  • Modified time test in data type test fixture to check for time spans where hours > 24.

  • Wrong string with backslash escaping in ByteFx.Data.MySqlClient.MySqlParameter. (Bug#4505)

  • Added code to Parameter test case TestQuoting to test for backslashes.

  • MySqlCommandBuilder fails with multi-word column names. (Bug#4486)

  • Fixed bug in TokenizeSql where underscore would terminate character capture in parameter name.

  • Added test case for spaces in column names.

  • MySqlDataReader.GetBytes 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".

  • Allow reading multiple resultsets from a single query.

  • Added flags attribute to ServerStatusFlags enum.

  • Changed name of ServerStatus enum to ServerStatusFlags.

  • Inserted data row doesn't update properly.

  • Error processing show create table. (Bug#4074)

  • Change Packet.ReadLenInteger to ReadPackedLong and added packet.ReadPackedInteger that always reads integers packed with 2,3,4.

  • Added syntax.cs test fixture to test various SQL syntax bugs.

  • Improper handling of time values. Now time value of 00:00:00 is not treated as null. (Bug#4149)

  • Moved all test suite files into TestSuite folder.

  • Fixed bug where null column would move the result packet pointer backward.

  • Added new nant build script.

  • Clear tablename so it will be regen'ed properly during the next GenerateSchema. (Bug#3917)

  • GetValues was always returning zero and was also always trying to copy all fields rather than respecting the size of the array passed in. (Bug#3915)

  • Implemented shared memory access protocol.

  • Implemented prepared statements for MySQL 4.1.

  • Implemented stored procedures for MySQL 5.0.

  • Renamed MySqlInternalConnection to InternalConnection.

  • SQL is now parsed as chars, fixes problems with other languages.

  • Added logging and allow batch connection string options.

  • RowUpdating event not set when setting the DataAdapter property. (Bug#3888)

  • Fixed bug in char set mapping.

  • Implemented 4.1 authentication.

  • Improved open/auth code in driver.

  • Improved how connection bits are set during connection.

  • Database name is now passed to server during initial handshake.

  • Changed namespace for client to MySql.Data.MySqlClient.

  • Changed assembly name of client to MySql.Data.dll.

  • Changed license text in all source files to GPL.

  • Added the MySqlClient.build Nant file.

  • Removed the mono batch files.

  • Moved some of the unused files into notused folder so nant build file can use wildcards.

  • Implemented shared memory access.

  • Major revamp in code structure.

  • Prepared statements now working for MySql 4.1.1 and later.

  • Finished implementing auth for 4.0, 4.1.0, and 4.1.1.

  • Changed namespace from MySQL.Data.MySQLClient back to MySql.Data.MySqlClient.

  • Fixed bug in CharSetMapping where it was trying to use text names as ints.

  • Changed namespace to MySQL.Data.MySQLClient.

  • Integrated auth changes from UC2004.

  • Fixed bug where calling any of the GetXXX methods on a datareader before or after reading data would not throw the appropriate exception (thanks Luca Morelli).

  • Added TimeSpan code in parameter.cs to properly serialize a timespan object to mysql time format (thanks Gianluca Colombo).

  • Added TimeStamp to parameter serialization code. Prevented DataAdatper updates from working right (thanks Michael King).

  • Fixed a misspelling in MySqlHelper.cs (thanks Patrick Kristiansen).

C.4.11. Changes in MySQL Connector/NET Version 0.76

  • Driver now using charset number given in handshake to create encoding.

  • Changed command editor to point to MySqlClient.Design.

  • Fixed bug in Version.isAtLeast.

  • Changed DBConnectionString to support changes done to MySqlConnectionString.

  • Removed SqlCommandEditor and DataAdapterPreviewDialog.

  • Using new long return values in many places.

  • Integrated new CompressedStream class.

  • Changed ConnectionString and added attributes to allow it to be used in MySqlClient.Design.

  • Changed packet.cs to support newer lengths in ReadLenInteger.

  • Changed other classes to use new properties and fields of MySqlConnectionString.

  • ConnectionInternal is now using PING to see whether the server is alive.

  • Moved toolbox bitmaps into resource folder.

  • Changed field.cs to allow values to come directly from row buffer.

  • Changed to use the new driver.Send syntax.

  • Using a new packet queueing system.

  • Started work handling the "broken" compression packet handling.

  • Fixed bug in StreamCreator where failure to connect to a host would continue to loop infinitly (thanks Kevin Casella).

  • Improved connectstring handling.

  • Moved designers into Pro product.

  • Removed some old commented out code from command.cs.

  • Fixed a problem with compression.

  • Fixed connection object where an exception throw prior to the connection opening would not leave the connection in the connecting state (thanks Chris Cline).

  • Added GUID support.

  • Fixed sequence out of order bug (thanks Mark Reay).

C.4.12. Changes in MySQL Connector/NET Version 0.75

  • Enum values now supported as parameter values (thanks Philipp Sumi).

  • Year datatype now supported.

  • Fixed compression.

  • Fixed bug where a parameter with a TimeSpan as the value would not serialize properly.

  • Fixed bug where default constructor would not set default connection string values.

  • Added some XML comments to some members.

  • Work to fix/improve compression handling.

  • Improved ConnectionString handling so that it better matches the standard set by SqlClient.

  • A MySqlException is now thrown if a 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).

C.4.13. Changes in MySQL Connector/NET Version 0.74

  • Added Unix socket support (thanks Mohammad DAMT).

  • Only calling Thread.Sleep when no data is available.

  • Improved escaping of quote characters in parameter data.

  • Removed misleading comments from parameter.cs.

  • Fixed pooling bug.

  • Fixed ConnectionString editor dialog (thanks marco p (pomarc)).

  • UserId now supported in connection strings (thanks Jeff Neeley).

  • Attempting to create a parameter that is not input throws an exception (thanks Ryan Gregg).

  • Added much documentation.

  • Checked in new MultiHostStream capability. Big thanks to Dan Guisinger for this. he originally submitted the code and idea of supporting multiple machines on the connect string.

  • Added a lot of documentation.

  • Fixed speed issue with 0.73.

  • Changed to Thread.Sleep(0) in MySqlDataStream to help optimize the case where it doesn't need to wait (thanks Todd German).

  • Prepopulating the idlepools to MinPoolSize.

  • Fixed MySqlPool deadlock condition as well as stupid bug where CreateNewPooledConnection was not ever adding new connections to the pool. Also fixed MySqlStream.ReadBytes and ReadByte to not use TicksPerSecond which does not appear to always be right. (thanks Matthew J. Peddlesden)

  • Fix for precision and scale (thanks Matthew J. Peddlesden).

  • Added Thread.Sleep(1) to stream reading methods to be more cpu friendly (thanks Sean McGinnis).

  • Fixed problem where ExecuteReader would sometime return null (thanks Lloyd Dupont).

  • Fixed major bug with null field handling (thanks Naucki).

  • Enclosed queries for max_allowed_packet and characterset inside try catch (and set defaults).

  • Fixed problem where socket was not getting closed properly (thanks Steve!).

  • Fixed problem where ExecuteNonQuery was not always returning the right value.

  • Fixed InternalConnection to not use @@session.max_allowed_packet but use @@max_allowed_packet. (Thanks Miguel)

  • Added many new XML doc lines.

  • Fixed sql parsing to not send empty queries (thanks Rory).

  • Fixed problem where the reader was not unpeeking the packet on close.

  • Fixed problem where user variables were not being handled (thanks Sami Vaaraniemi).

  • Fixed loop checking in the MySqlPool (thanks Steve M. Brown)

  • Fixed ParameterCollection.Add method to match SqlClient (thanks Joshua Mouch).

  • Fixed ConnectionString parsing to handle no and yes for boolean and not lowercase values (thanks Naucki).

  • Added InternalConnection class, changes to pooling.

  • Implemented Persist Security Info.

  • Added security.cs and version.cs to project

  • Fixed DateTime handling in Parameter.cs (thanks Burkhard Perkens-Golomb).

  • Fixed parameter serialization where some types would throw a cast exception.

  • Fixed DataReader to convert all returned values to prevent casting errors (thanks Keith Murray).

  • Added code to Command.ExecuteReader to return null if the initial SQL statement throws an exception (thanks Burkhard Perkens-Golomb).

  • Fixed ExecuteScalar bug introduced with restructure.

  • Restructure to allow for LOCAL DATA INFILE and better sequencing of packets.

  • Fixed several bugs related to restructure.

  • Early work done to support more secure passwords in Mysql 4.1. Old passwords in 4.1 not supported yet.

  • Parameters appearing after system parameters are now handled correctly (Adam M. (adammil)).

  • Strings can now be assigned directly to blob fields (Adam M.).

  • Fixed float parameters (thanks Pent).

  • Improved Parameter constructor and ParameterCollection.Add methods to better match SqlClient (thanks Joshua Mouch).

  • Corrected Connection.CreateCommand to return a MySqlCommand type.

  • Fixed connection string designer dialog box problem (thanks Abraham Guyt).

  • Fixed problem with sending commands not always reading the response packet (thanks Joshua Mouch).

  • Fixed parameter serialization where some blobs types were not being handled (thanks Sean McGinnis).

  • Removed spurious MessageBox.show from DataReader code (thanks Joshua Mouch).

  • Fixed a nasty bug in the split sql code (thanks everyone!).

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

C.4.15. Changes in MySQL Connector/NET Version 0.70

  • Updated some of the character code pages to be more accurate.

  • Fixed problem where readers could be opened on connections that had readers open.

  • Moved test to separate assembly MySqlClientTests.

  • Fixed stupid problem in driver with sequence out of order (Thanks Peter Belbin).

  • Added some pipe tests.

  • Increased default max pool size to 50.

  • Compiles with Mono 0-24.

  • Fixed connection and data reader dispose problems.

  • Added String datatype handling to parameter serialization.

  • Fixed sequence problem in driver that occurred after thrown exception (thanks Burkhard Perkens-Golomb).

  • Added support for CommandBehavior.SingleRow to DataReader.

  • Fixed command sql processing so quotes are better handled (thanks Theo Spears).

  • Fixed parsing of double, single, and decimal values to account for non-English separators. You still have to use the right syntax if you using hard coded sql, but if you use parameters the code will convert floating point types to use '.' appropriately internal both into the server and out.

  • Added MySqlStream class to simplify timeouts and driver coding.

  • Fixed DataReader so that it is closed properly when the associated connection is closed. [thanks smishra]

  • Made client more SqlClient compliant so that DataReaders have to be closed before the connection can be used to run another command.

  • Improved DBNull.Value handling in the fields.

  • Added several unit tests.

  • Fixed MySqlException base class.

  • Improved driver coding

  • Fixed bug where NextResult was returning false on the last resultset.

  • Added more tests for MySQL.

  • Improved casting problems by equating unsigned 32bit values to Int64 and unsigned 16bit values to Int32, and so forth.

  • Added new constructor for MySqlParameter for (name, type, size, srccol)

  • Fixed bug in MySqlDataReader where it didn't check for null fieldlist before returning field count.

  • Started adding MySqlClient unit tests (added MySqlClient/Tests folder and some test cases).

  • Fixed some things in Connection String handling.

  • Moved INIT_DB to MySqlPool. I may move it again, this is in preparation of the conference.

  • Fixed bug inside CommandBuilder that prevented inserts from happening properly.

  • Reworked some of the internals so that all three execute methods of Command worked properly.

  • Fixed many small bugs found during benchmarking.

  • The first cut of CoonectionPooling is working. "min pool size" and "max pool size" are respected.

  • Work to enable multiple resultsets to be returned.

  • Character sets are handled much more intelligently now. The driver queries MySQL at startup for the default character set. That character set is then used for conversions if that code page can be loaded. If not, then the default code page for the current OS is used.

  • Added code to save the inferred type in the name,value constructor of Parameter.

  • Also, inferred type if value of null parameter is changed using Value property.

  • Converted all files to use proper Camel case. MySQL is now MySql in all files. PgSQL is now PgSql.

  • Added attribute to PgSql code to prevent designer from trying to show.

  • Added MySQLDbType property to Parameter object and added proper conversion code to convert from DbType to MySQLDbType).

  • Removed unused ObjectToString method from MySQLParameter.cs.

  • Fixed Add(..) method in ParameterCollection so that it doesn't use Add(name, value) instead.

  • Fixed IndexOf and Contains in ParameterCollection to be aware that parameter names are now stored without @.

  • Fixed Command.ConvertSQLToBytes so it only allows characters that can be in MySQL variable names.

  • Fixed DataReader and Field so that blob fields read their data from Field.cs and GetBytes works right.

  • Added simple query builder editor to CommandText property of MySQLCommand.

  • Fixed CommandBuilder and Parameter serialization to account for Parameters not storing @ in their names.

  • Removed MySQLFieldType enum from Field.cs. Now using MySQLDbType enum.

  • Added Designer attribute to several classes to prevent designer view when using VS.Net.

  • Fixed Initial catalog typo in ConnectionString designer.

  • Removed 3 parameter constructor for MySQLParameter that conflicted with (name, type, value).

  • Changed MySQLParameter so paramName is now stored without leading @ (this fixed null inserts when using designer).

  • Changed TypeConverter for MySQLParameter to use the constructor with all properties.

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

C.4.17. 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.

C.4.18. 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.

C.4.19. 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.

C.5. MySQL Visual Studio Plugin Change History

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 C.4, “MySQL Connector/NET Change History”.

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

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

C.5.3. Changes in MySQL Visual Studio Plugin 1.0.1 (4 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"/>
 

C.5.4. Changes in MySQL Visual Studio Plugin 1.0.0 (4 October 2006)

Bugs fixed:

  • Ability to work with MySQL objects (tables, views, stored procedures, etc) from within Server Explorer.

  • DDEX (Data Designer Extensibility) compatibility.

C.6. MySQL Connector/J Change History

C.6.1. Changes in MySQL Connector/J 5.1.x

C.6.1.1. Changes in MySQL Connector/J 5.1.13 (Not yet released)

Fixes bugs found since release 5.1.12.

Bugs fixed:

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

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

C.6.1.3. 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 in order 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 via 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 allows for 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)

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

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

C.6.1.6. 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 quotes. With the parser not detecting that the regular expression was in quotes, 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)

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

C.6.1.8. 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 paramaters. (Bug#33678)

  • XAConnections and datasources have been updated to the JDBC-4.0 standard.

  • The profiler event handling has been made extensible via the profilerEventHandler connection property.

  • Add the verifyServerCertificate propery. If set to "false" the driver will not verify the server's certificate when useSSL is set to "true"

    When using this feature, the keystore parameters should be specified by the clientCertificateKeyStore* properties, rather than system properties, as the JSSE doesn't it straightforward to have a 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 does'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 via 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.

C.6.1.9. Changes in MySQL Connector/J 5.1.5 (09 October 2007)

The following features are new, compared to the 5.0 series of Connector/J

  • Support for JDBC-4.0 NCHAR, NVARCHAR and NCLOB types.

  • JDBC-4.0 support for setting per-connection client information (which can be viewed in the comments section of a query via SHOW PROCESSLIST on a MySQL server, or can be extended to support custom persistence of the information via a public interface).

  • Support for JDBC-4.0 XML processing via JAXP interfaces to DOM, SAX and StAX.

  • JDBC-4.0 standardized unwrapping to interfaces that include vendor extensions.

Functionality added or changed:

  • Added autoSlowLog configuration property, overrides slowQueryThreshold* properties, driver determines slow queries by those that are slower than 5 * stddev of the mean query time (outside the 96% percentile).

Bugs fixed:

  • When a connection is in read-only mode, queries that are wrapped in parentheses were incorrectly identified DML statements. (Bug#28256)

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

C.6.1.10. Changes in MySQL Connector/J 5.1.4 (Not Released)

Only released internally.

C.6.1.11. Changes in MySQL Connector/J 5.1.3 (10 September 2007)

The following features are new, compared to the 5.0 series of Connector/J

  • Support for JDBC-4.0 NCHAR, NVARCHAR and NCLOB types.

  • JDBC-4.0 support for setting per-connection client information (which can be viewed in the comments section of a query via SHOW PROCESSLIST on a MySQL server, or can be extended to support custom persistence of the information via a public interface).

  • Support for JDBC-4.0 XML processing via JAXP interfaces to DOM, SAX and StAX.

  • JDBC-4.0 standardized unwrapping to interfaces that include vendor extensions.

Functionality added or changed:

  • Connector/J now connects using an initial character set of utf-8 solely for the purpose of authentication to allow user names or database names in any character set to be used in the JDBC connection URL. (Bug#29853)

  • Added two configuration parameters:

    • blobsAreStrings — Should the driver always treat BLOBs as Strings. Added specifically to work around dubious metadata returned by the server for GROUP BY clauses. Defaults to false.

    • functionsNeverReturnBlobs — Should the driver always treat data from functions returning BLOBs as Strings. Added specifically to work around dubious metadata returned by the server for GROUP BY clauses. Defaults to false.

  • Setting rewriteBatchedStatements to true now causes CallableStatements with batched arguments to be re-written in the form "CALL (...); CALL (...); ..." to send the batch in as few client-server round trips as possible.

  • The driver now picks appropriate internal row representation (whole row in one buffer, or individual byte[]s for each column value) depending on heuristics, including whether or not the row has BLOB or TEXT types and the overall row-size. The threshold for row size that will cause the driver to use a buffer rather than individual byte[]s is configured by the configuration property largeRowSizeThreshold, which has a default value of 2KB.

  • The data (and how it is stored) for ResultSet rows are now behind an interface which allows us (in some cases) to allocate less memory per row, in that for "streaming" result sets, we re-use the packet used to read rows, since only one row at a time is ever active.

  • Added experimental support for statement "interceptors" via the com.mysql.jdbc.StatementInterceptor interface, examples are in com/mysql/jdbc/interceptors. Implement this interface to be placed "in between" query execution, so that it can be influenced (currently experimental).

  • The driver will automatically adjust the server session variable net_write_timeout when it determines its been asked for a "streaming" result, and resets it to the previous value when the result set has been consumed. (The configuration property is named netTimeoutForStreamingResults, with a unit of seconds, the value '0' means the driver will not try and adjust this value).

  • JDBC-4.0 ease-of-development features including auto-registration with the DriverManager via the service provider mechanism, standardized Connection validity checks and categorized SQLExceptions based on recoverability/retry-ability and class of the underlying error.

  • Statement.setQueryTimeout()s now affect the entire batch for batched statements, rather than the individual statements that make up the batch.

  • Errors encountered during Statement/PreparedStatement/CallableStatement.executeBatch() when rewriteBatchStatements has been set to true now return BatchUpdateExceptions according to the setting of continueBatchOnError.

    If continueBatchOnError is set to true, the update counts for the "chunk" that were sent as one unit will all be set to EXECUTE_FAILED, but the driver will attempt to process the remainder of the batch. You can determine which "chunk" failed by looking at the update counts returned in the BatchUpdateException.

    If continueBatchOnError is set to "false", the update counts returned will contain all updates up-to and including the failed "chunk", with all counts for the failed "chunk" set to EXECUTE_FAILED.

    Since MySQL doesn't return multiple error codes for multiple-statements, or for multi-value INSERT/REPLACE, it is the application's responsibility to handle determining which item(s) in the "chunk" actually failed.

  • New methods on com.mysql.jdbc.Statement: setLocalInfileInputStream() and getLocalInfileInputStream():

    • setLocalInfileInputStream() sets an InputStream instance that will be used to send data to the MySQL server for a LOAD DATA LOCAL INFILE statement rather than a FileInputStream or URLInputStream that represents the path given as an argument to the statement.

      This stream will be read to completion upon execution of a LOAD DATA LOCAL INFILE statement, and will automatically be closed by the driver, so it needs to be reset before each call to execute*() that would cause the MySQL server to request data to fulfill the request for LOAD DATA LOCAL INFILE.

      If this value is set to NULL, the driver will revert to using a FileInputStream or URLInputStream as required.

    • getLocalInfileInputStream() returns the InputStream instance that will be used to send data in response to a LOAD DATA LOCAL INFILE statement.

      This method returns NULL if no such stream has been set via setLocalInfileInputStream().

  • Setting useBlobToStoreUTF8OutsideBMP to true tells the driver to treat [MEDIUM/LONG]BLOB columns as [LONG]VARCHAR columns holding text encoded in UTF-8 that has characters outside the BMP (4-byte encodings), which MySQL server can't handle natively.

    Set utf8OutsideBmpExcludedColumnNamePattern to a regex so that column names matching the given regex will still be treated as BLOBs The regex must follow the patterns used for the java.util.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 PreparedStatmentWrapper delegates to wrong method. (Bug#30892)

  • NPE with null column values when padCharsWithSpace is set to true. (Bug#30851)

  • Collation on VARBINARY column types would be misidentified. A fix has been added, but this fix only works for MySQL server versions 5.0.25 and newer, since earlier versions didn't consistently return correct metadata for functions, and thus results from subqueries and functions were indistinguishable from each other, leading to type-related bugs. (Bug#30664)

  • An ArithmeticException or NullPointerException would be raised when the batch had zero members and rewriteBatchedStatements=true when addBatch() was never called, or executeBatch() was called immediately after clearBatch(). (Bug#30550)

  • Closing a load-balanced connection would cause a ClassCastException. (Bug#29852)

  • Connection checker for JBoss didn't use same method parameters via reflection, causing connections to always seem "bad". (Bug#29106)

  • DatabaseMetaData.getTypeInfo() for the types DECIMAL and NUMERIC will return a precision of 254 for server versions older than 5.0.3, 64 for versions 5.0.3–5.0.5 and 65 for versions newer than 5.0.5. (Bug#28972)

  • CallableStatement.executeBatch() doesn't work when connection property noAccessToProcedureBodies has been set to true.

    The fix involves changing the behavior of noAccessToProcedureBodies,in that the driver will now report all paramters as "IN" paramters but allow callers to call registerOutParameter() on them without throwing an exception. (Bug#28689)

  • DatabaseMetaData.getColumns() doesn't contain SCOPE_* or IS_AUTOINCREMENT columns. (Bug#27915)

  • Schema objects with identifiers other than the connection character aren't retrieved correctly in ResultSetMetadata. (Bug#27867)

  • Connection.getServerCharacterEncoding() doesn't work for servers with version >= 4.1. (Bug#27182)

  • The automated SVN revisions in DBMD.getDriverVersion(). The SVN revision of the directory is now inserted into the version information during the build. (Bug#21116)

  • Specifying a "validation query" in your connection pool that starts with "/* ping */" _exactly_ will cause the driver to instead send a ping to the server and return a fake result set (much lighter weight), and when using a ReplicationConnection or a LoadBalancedConnection, will send the ping across all active connections.

C.6.1.12. 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.

C.6.1.13. Changes in MySQL Connector/J 5.1.1 (22 June 2007)

This is a new Alpha development release, adding new features and fixing recently discovered bugs.

Functionality added or changed:

  • Incompatible Change: Pulled vendor-extension methods of Connection implementation out into an interface to support java.sql.Wrapper functionality from ConnectionPoolDataSource. The vendor extensions are javadoc'd in the com.mysql.jdbc.Connection interface.

    For those looking further into the driver implementation, it is not an API that is used for plugability of implementations inside our driver (which is why there are still references to ConnectionImpl throughout the code).

    We've also added server and client prepareStatement() methods that cover all of the variants in the JDBC API.

    Connection.serverPrepare(String) has been re-named to Connection.serverPrepareStatement() for consistency with Connection.clientPrepareStatement().

  • Row navigation now causes any streams/readers open on the result set to be closed, as in some cases we're reading directly from a shared network packet and it will be overwritten by the "next" row.

  • Made it possible to retrieve prepared statement parameter bindings (to be used in StatementInterceptors, primarily).

  • Externalized the descriptions of connection properties.

  • The data (and how it is stored) for ResultSet rows are now behind an interface which allows us (in some cases) to allocate less memory per row, in that for "streaming" result sets, we re-use the packet used to read rows, since only one row at a time is ever active.

  • Similar to Connection, we pulled out vendor extensions to Statement into an interface named com.mysql.Statement, and moved the Statement class into com.mysql.StatementImpl. The two methods (javadoc'd in com.mysql.Statement are enableStreamingResults(), which already existed, and disableStreamingResults() which sets the statement instance back to the fetch size and result set type it had before enableStreamingResults() was called.

  • Driver now picks appropriate internal row representation (whole row in one buffer, or individual byte[]s for each column value) depending on heuristics, including whether or not the row has BLOB or TEXT types and the overall row-size. The threshold for row size that will cause the driver to use a buffer rather than individual byte[]s is configured by the configuration property largeRowSizeThreshold, which has a default value of 2KB.

  • Added experimental support for statement "interceptors" via the com.mysql.jdbc.StatementInterceptor interface, examples are in com/mysql/jdbc/interceptors.

    Implement this interface to be placed "in between" query execution, so that you can influence it. (currently experimental).

    StatementInterceptors are "chainable" when configured by the user, the results returned by the "current" interceptor will be passed on to the next on in the chain, from left-to-right order, as specified by the user in the JDBC configuration property statementInterceptors.

  • See the sources (fully javadoc'd) for com.mysql.jdbc.StatementInterceptor for more details until we iron out the API and get it documented in the manual.

  • Setting rewriteBatchedStatements to true now causes CallableStatements with batched arguments to be re-written in the form CALL (...); CALL (...); ... to send the batch in as few client-server round trips as possible.

C.6.1.14. Changes in MySQL Connector/J 5.1.0 (11 April 2007)

This is the first public alpha release of the current Connector/J 5.1 development branch, providing an insight to upcoming features. Although some of these are still under development, this release includes the following new features and changes (in comparison to the current Connector/J 5.0 production release):

Important change: Due to a number of issues with the use of server-side prepared statements, Connector/J 5.0.5 has disabled their use by default. The disabling of server-side prepared statements does not affect the operation of the connector in any way.

To enable server-side prepared statements you must add the following configuration property to your connector string:

useServerPrepStmts=true

The default value of this property is false (that is, Connector/J does not use server-side prepared statements).

Note

The disabling of server-side prepared statements does not affect the operation of the connector. However, if you use the useTimezone=true connection option and use client-side prepared statements (instead of server-side prepared statements) you should also set useSSPSCompatibleTimezoneShift=true.

Functionality added or changed:

  • Refactored CommunicationsException into a JDBC-3.0 version, and a JDBC-4.0 version (which extends SQLRecoverableException, now that it exists).

    Note

    This change means that if you were catching com.mysql.jdbc.CommunicationsException in your applications instead of looking at the SQLState class of 08, and are moving to Java 6 (or newer), you need to change your imports to that exception to be com.mysql.jdbc.exceptions.jdbc4.CommunicationsException, as the old class will not be instantiated for communications link-related errors under Java 6.

  • Added support for JDBC-4.0 categorized SQLExceptions.

  • Added support for JDBC-4.0's NCLOB, and NCHAR/NVARCHAR types.

  • com.mysql.jdbc.java6.javac — full path to your Java-6 javac executable

  • Added support for JDBC-4.0's SQLXML interfaces.

  • Re-worked Ant buildfile to build JDBC-4.0 classes separately, as well as support building under Eclipse (since Eclipse can't mix/match JDKs).

    To build, you must set JAVA_HOME to J2SDK-1.4.2 or Java-5, and set the following properties on your Ant command line:

    • com.mysql.jdbc.java6.javac — full path to your Java-6 javac executable

    • com.mysql.jdbc.java6.rtjar — full path to your Java-6 rt.jar file

  • New feature — driver will automatically adjust session variable net_write_timeout when it determines it has been asked for a "streaming" result, and resets it to the previous value when the result set has been consumed. (configuration property is named netTimeoutForStreamingResults value and has a unit of seconds, the value 0 means the driver will not try and adjust this value).

  • Added support for JDBC-4.0's client information. The backend storage of information provided via Connection.setClientInfo() and retrieved by Connection.getClientInfo() is pluggable by any class that implements the com.mysql.jdbc.JDBC4ClientInfoProvider interface and has a no-args constructor.

    The implementation used by the driver is configured using the clientInfoProvider configuration property (with a default of value of com.mysql.jdbc.JDBC4CommentClientInfoProvider, an implementation which lists the client information as a comment prepended to every query sent to the server).

    This functionality is only available when using Java-6 or newer.

  • com.mysql.jdbc.java6.rtjar — full path to your Java-6 rt.jar file

  • Added support for JDBC-4.0's Wrapper interface.

C.6.2. Changes in MySQL Connector/J 5.0.x

C.6.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 PreparedStatmentWrapper delegates to wrong method. (Bug#30892)

  • NPE with null column values when padCharsWithSpace is set to true. (Bug#30851)

  • Collation on VARBINARY column types would be misidentified. A fix has been added, but this fix only works for MySQL server versions 5.0.25 and newer, since earlier versions didn't consistently return correct metadata for functions, and thus results from subqueries and functions were indistinguishable from each other, leading to type-related bugs. (Bug#30664)

  • An ArithmeticException or NullPointerException would be raised when the batch had zero members and rewriteBatchedStatements=true when addBatch() was never called, or executeBatch() was called immediately after clearBatch(). (Bug#30550)

  • Closing a load-balanced connection would cause a ClassCastException. (Bug#29852)

  • Connection checker for JBoss didn't use same method parameters via reflection, causing connections to always seem "bad". (Bug#29106)

  • DatabaseMetaData.getTypeInfo() for the types DECIMAL and NUMERIC will return a precision of 254 for server versions older than 5.0.3, 64 for versions 5.0.3–5.0.5 and 65 for versions newer than 5.0.5. (Bug#28972)

  • CallableStatement.executeBatch() doesn't work when connection property noAccessToProcedureBodies has been set to true.

    The fix involves changing the behavior of noAccessToProcedureBodies,in that the driver will now report all paramters as "IN" paramters but allow callers to call registerOutParameter() on them without throwing an exception. (Bug#28689)

  • When a connection is in read-only mode, queries that are wrapped in parentheses were incorrectly identified DML statements. (Bug#28256)

  • UNSIGNED types not reported via DBMD.getTypeInfo(), and capitalization of type names is not consistent between DBMD.getColumns(), RSMD.getColumnTypeName() and DBMD.getTypeInfo().

    This fix also ensures that the precision of UNSIGNED MEDIUMINT and UNSIGNED BIGINT is reported correctly via DBMD.getColumns(). (Bug#27916)

  • DatabaseMetaData.getColumns() doesn't contain SCOPE_* or IS_AUTOINCREMENT columns. (Bug#27915)

  • Schema objects with identifiers other than the connection character aren't retrieved correctly in ResultSetMetadata. (Bug#27867)

  • Cached metadata with PreparedStatement.execute() throws NullPointerException. (Bug#27412)

  • Connection.getServerCharacterEncoding() doesn't work for servers with version >= 4.1. (Bug#27182)

  • The automated SVN revisions in DBMD.getDriverVersion(). The SVN revision of the directory is now inserted into the version information during the build. (Bug#21116)

  • Specifying a "validation query" in your connection pool that starts with "/* ping */" _exactly_ will cause the driver to instead send a ping to the server and return a fake result set (much lighter weight), and when using a ReplicationConnection or a LoadBalancedConnection, will send the ping across all active connections.

C.6.2.2. Changes in MySQL Connector/J 5.0.7 (20 July 2007)

Functionality added or changed:

  • The driver will now automatically set useServerPrepStmts to true when useCursorFetch has been set to true, since the feature requires server-side prepared statements in order to function.

  • tcpKeepAlive - Should the driver set SO_KEEPALIVE (default true)?

  • Give more information in EOFExceptions thrown out of MysqlIO (how many bytes the driver expected to read, how many it actually read, say that communications with the server were unexpectedly lost).

  • Driver detects when it is running in a ColdFusion MX server (tested with version 7), and uses the configuration bundle coldFusion, which sets useDynamicCharsetInfo to false (see previous entry), and sets useLocalSessionState and autoReconnect to true.

  • tcpNoDelay - Should the driver set SO_TCP_NODELAY (disabling the Nagle Algorithm, default true)?

  • Added configuration property slowQueryThresholdNanos - if useNanosForElapsedTime is set to true, and this property is set to a 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 allow tuning of TCP/IP socket parameters:

    • tcpNoDelay - Should the driver set SO_TCP_NODELAY (disabling the Nagle Algorithm, default true)?

    • tcpKeepAlive - Should the driver set SO_KEEPALIVE (default true)?

    • tcpRcvBuf - Should the driver set SO_RCV_BUF to the given value? The default value of '0', means use the platform default value for this property.

    • tcpSndBuf - Should the driver set SO_SND_BUF to the given value? The default value of '0', means use the platform default value for this property.

    • tcpTrafficClass - Should the driver set traffic class or type-of-service fields? See the documentation for java.net.Socket.setTrafficClass() for more information.

  • Setting the configuration parameter useCursorFetch to true for MySQL-5.0+ enables the use of cursors that allow Connector/J to save memory by fetching result set rows in chunks (where the chunk size is set by calling setFetchSize() on a Statement or ResultSet) by using fully-materialized cursors on the server.

  • tcpSndBuf - Should the driver set SO_SND_BUF to the given value? The default value of '0', means use the platform default value for this property.

  • tcpTrafficClass - Should the driver set traffic class or type-of-service fields? See the documentation for java.net.Socket.setTrafficClass() for more information.

  • Added new debugging functionality - Setting configuration property includeInnodbStatusInDeadlockExceptions to true will cause the driver to append the output of SHOW ENGINE INNODB STATUS to deadlock-related exceptions, which will enumerate the current locks held inside InnoDB.

  • Added configuration property useNanosForElapsedTime - for profiling/debugging functionality that measures elapsed time, should the driver try to use nanoseconds resolution if available (requires JDK >= 1.5)?

    Note

    If useNanosForElapsedTime is set to true, and this property is set to "0" (or left default), then elapsed times will still be measured in nanoseconds (if possible), but the slow query threshold will be converted from milliseconds to nanoseconds, and thus have an upper bound of approximately 2000 milliseconds (as that threshold is represented as an integer, not a long).

Bugs fixed:

  • Don't send any file data in response to LOAD DATA LOCAL INFILE if the feature is disabled at the client side. This is to prevent a malicious server or man-in-the-middle from asking the client for data that the client is not expecting. Thanks to Jan Kneschke for discovering the exploit and Andrey "Poohie" Hristov, Konstantin Osipov and Sergei Golubchik for discussions about implications and possible fixes. (Bug#29605)

  • Parser in client-side prepared statements runs to end of statement, rather than end-of-line for '#' comments. Also added support for '--' single-line comments. (Bug#28956)

  • Parser in client-side prepared statements eats character following '/' if it 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)

C.6.2.3. Changes in MySQL Connector/J 5.0.6 (15 May 2007)

Functionality added or changed:

  • Added an experimental load-balanced connection designed for use with SQL nodes in a MySQL Cluster/NDB environment (This is not for master-slave replication. For that, we suggest you look at ReplicationConnection or lbpool).

    If the JDBC URL starts with jdbc:mysql:loadbalance://host-1,host-2,...host-n, the driver will create an implementation of java.sql.Connection that load balances requests across a series of MySQL JDBC connections to the given hosts, where the balancing takes place after transaction commit.

    Therefore, for this to work (at all), you must use transactions, even if only reading data.

    Physical connections to the given hosts will not be created until needed.

    The driver will invalidate connections that it detects have had communication errors when processing a request. A new connection to the problematic host will be attempted the next time it is selected by the load balancing algorithm.

    There are two choices for load balancing algorithms, which may be specified by the loadBalanceStrategy JDBC URL configuration property:

    • random — the driver will pick a random host for each request. This tends to work better than round-robin, as the randomness will somewhat account for spreading loads where requests vary in response time, while round-robin can sometimes lead to overloaded nodes if there are variations in response times across the workload.

    • bestResponseTime — the driver will route the request to the host that had the best response time for the previous transaction.

  • bestResponseTime — the driver will route the request to the host that had the best response time for the previous transaction.

  • Added configuration property padCharsWithSpace (defaults to false). If set to true, and a result set column has the CHAR type and the value does not fill the amount of characters specified in the DDL for the column, the driver will pad the remaining characters with space (for ANSI compliance).

  • When useLocalSessionState is set to true and connected to a MySQL-5.0 or later server, the JDBC driver will now determine whether an actual commit or rollback statement needs to be sent to the database when Connection.commit() or Connection.rollback() is called.

    This is especially helpful for high-load situations with connection pools that always call Connection.rollback() on connection check-in/check-out because it avoids a round-trip to the server.

  • Added configuration property useDynamicCharsetInfo. If set to false (the default), the driver will use a per-connection cache of character set information queried from the server when necessary, or when set to true, use a built-in static mapping that is more efficient, but isn't aware of custom character sets or character sets implemented after the release of the JDBC driver.

    Note

    This only affects the padCharsWithSpace configuration property and the ResultSetMetaData.getColumnDisplayWidth() method.

  • New configuration property, enableQueryTimeouts (default true).

    When enabled, query timeouts set via Statement.setQueryTimeout() use a shared java.util.Timer instance for scheduling. Even if the timeout doesn't expire before the query is processed, there will be memory used by the TimerTask for the given timeout which won't be reclaimed until the time the timeout would have expired if it hadn't been cancelled by the driver. High-load environments might want to consider disabling this functionality. (this configuration property is part of the maxPerformance configuration bundle).

  • Give better error message when "streaming" result sets, and the connection gets clobbered because of exceeding net_write_timeout on the server.

  • random — the driver will pick a random host for each request. This tends to work better than round-robin, as the randomness will somewhat account for spreading loads where requests vary in response time, while round-robin can sometimes lead to overloaded nodes if there are variations in response times across the workload.

  • com.mysql.jdbc.[NonRegistering]Driver now understands URLs of the format jdbc:mysql:replication:// and jdbc:mysql:loadbalance:// which will create a ReplicationConnection (exactly like when using [NonRegistering]ReplicationDriver) and an experimental load-balanced connection designed for use with SQL nodes in a MySQL Cluster/NDB environment, respectively.

    In an effort to simplify things, we're working on deprecating multiple drivers, and instead specifying different core behavior based upon JDBC URL prefixes, so watch for [NonRegistering]ReplicationDriver to eventually disappear, to be replaced with com.mysql.jdbc[NonRegistering]Driver with the new URL prefix.

  • Fixed issue where a failed-over connection would let an application call setReadOnly(false), when that call should be ignored until the connection is reconnected to a writable master unless failoverReadOnly had been set to false.

  • Driver will now use INSERT INTO ... VALUES (DEFAULT)form of statement for updatable result sets for ResultSet.insertRow(), rather than pre-populating the insert row with values from DatabaseMetaData.getColumns()(which results in a SHOW FULL COLUMNS on the server for every result set). If an application requires access to the default values before insertRow() has been called, the JDBC URL should be configured with populateInsertRowWithDefaultValues set to true.

    This fix specifically targets performance issues with ColdFusion and the fact that it seems to ask for updatable result sets no matter what the application does with them.

  • More intelligent initial packet sizes for the "shared" packets are used (512 bytes, rather than 16K), and initial packets used during handshake are now sized appropriately as to not require reallocation.

Bugs fixed:

  • More useful error messages are generated when the driver thinks a result set is not updatable. (Thanks to Ashley Martens for the patch). (Bug#28085)

  • Connection.getTransactionIsolation() uses "SHOW VARIABLES LIKE" which is very inefficient on MySQL-5.0+ servers. (Bug#27655)

  • Fixed issue where calling getGeneratedKeys() on a prepared statement after calling execute() didn't always return the generated keys (executeUpdate() worked fine however). (Bug#27655)

  • CALL /* ... */ some_proc() doesn't work. As a side effect of this fix, you can now use /* */ and # comments when preparing statements using client-side prepared statement emulation.

    If the comments happen to contain parameter markers (?), they will be treated as belonging to the comment (that is, not recognized) rather than being a parameter of the statement.

    Note

    The statement when sent to the server will contain the comments as-is, they're not stripped during the process of preparing the PreparedStatement or CallableStatement.

    (Bug#27400)

  • ResultSet.get*() with a column index < 1 returns misleading error message. (Bug#27317)

  • Using ResultSet.get*() with a column index less than 1 returns a misleading error message. (Bug#27317)

  • Comments in DDL of stored procedures/functions confuse procedure parser, and thus metadata about them can not be created, leading to inability to retrieve said metadata, or execute procedures that have certain comments in them. (Bug#26959)

  • Fast date/time parsing doesn't take into account 00:00:00 as a legal value. (Bug#26789)

  • PreparedStatement is not closed in BlobFromLocator.getBytes(). (Bug#26592)

  • When the configuration property useCursorFetch was set to true, sometimes server would return new, more exact metadata during the execution of the server-side prepared statement that enables this functionality, which the driver ignored (using the original metadata returned during prepare()), causing corrupt reading of data due to type mismatch when the actual rows were returned. (Bug#26173)

  • CallableStatements with OUT/INOUT parameters that are "binary" (BLOB, BIT, (VAR)BINARY, JAVA_OBJECT) have extra 7 bytes. (Bug#25715)

  • Whitespace surrounding storage/size specifiers in stored procedure parameters declaration causes NumberFormatException to be thrown when calling stored procedure on JDK-1.5 or newer, as the Number classes in JDK-1.5+ are whitespace intolerant. (Bug#25624)

  • Client options not sent correctly when using SSL, leading to stored procedures not being able to return results. Thanks to Don Cohen for the bug report, testcase and patch. (Bug#25545)

  • Statement.setMaxRows() is not effective on result sets materialized from cursors. (Bug#25517)

  • BIT(> 1) is returned as java.lang.String from ResultSet.getObject() rather than byte[]. (Bug#25328)

C.6.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 via 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 via correctly named mutator/accessor, causing data source implementations that use JavaBean naming conventions to set properties to fail to set the property (and in the case of SJAS, fail silently when trying to set this parameter). (Bug#26326)

  • A query execution which timed out did not always throw a MySQLTimeoutException. (Bug#25836)

  • Storing a java.util.Date object in a BLOB column would not be serialized correctly during setObject. (Bug#25787)

  • Timer instance used for Statement.setQueryTimeout() created per-connection, rather than per-VM, causing memory leak. (Bug#25514)

  • EscapeProcessor gets confused by multiple backslashes. We now push the responsibility of syntax errors back on to the server for most escape sequences. (Bug#25399)

  • INOUT parameters in CallableStatements get doubly-escaped. (Bug#25379)

  • When using the rewriteBatchedStatements connection option with PreparedState.executeBatch() an internal memory leak would occur. (Bug#25073)

  • Fixed issue where field-level for metadata from DatabaseMetaData when using INFORMATION_SCHEMA didn't have references to current connections, sometimes leading to Null Pointer Exceptions (NPEs) when introspecting them via ResultSetMetaData. (Bug#25073)

  • StringUtils.indexOfIgnoreCaseRespectQuotes() isn't case-insensitive on the first character of the target. This bug also affected rewriteBatchedStatements functionality when prepared statements did not use uppercase for the VALUES clause. (Bug#25047)

  • Client-side prepared statement parser gets confused by in-line comments /*...*/ and therefore cannot rewrite batch statements or reliably detect the type of statements when they are used. (Bug#25025)

  • Results sets from UPDATE statements that are part of multi-statement queries would cause an SQLException error, "Result is from UPDATE". (Bug#25009)

  • Specifying US-ASCII as the character set in a connection to a MySQL 4.1 or newer server does not map correctly. (Bug#24840)

  • Using DatabaseMetaData.getSQLKeywords() does not return a all of the of the reserved keywords for the current MySQL version. Current implementation returns the list of reserved words for MySQL 5.1, and does not distinguish between versions. (Bug#24794)

  • Calling Statement.cancel() could result in a Null Pointer Exception (NPE). (Bug#24721)

  • Using setFetchSize() breaks prepared SHOW and other commands. (Bug#24360)

  • Calendars and timezones are now lazily instantiated when required. (Bug#24351)

  • Using DATETIME columns would result in time shifts when useServerPrepStmts was true. The reason was due to different behavior when using client-side compared to server-side prepared statements and the useJDBCCompliantTimezoneShift option. This is now fixed if moving from server-side prepared statements to client-side prepared statements by setting useSSPSCompatibleTimezoneShift to true, as the driver can't tell if this is a new deployment that never used server-side prepared statements, or if it is an existing deployment that is switching to client-side prepared statements from server-side prepared statements. (Bug#24344)

  • Connector/J now returns a better error message when server doesn't return enough information to determine stored procedure/function parameter types. (Bug#24065)

  • A connection error would occur when connecting to a MySQL server with certain character sets. Some collations/character sets reported as "unknown" (specifically cias variants of existing character sets), and inability to override the detected server character set. (Bug#23645)

  • Inconsistency between getSchemas and INFORMATION_SCHEMA. (Bug#23304)

  • DatabaseMetaData.getSchemas() doesn't return a TABLE_CATALOG column. (Bug#23303)

  • When using a JDBC connection URL that is malformed, the NonRegisteringDriver.getPropertyInfo method will throw a Null Pointer Exception (NPE). (Bug#22628)

  • Some exceptions thrown out of StandardSocketFactory were needlessly wrapped, obscuring their true cause, especially when using socket timeouts. (Bug#21480)

  • When using a server-side prepared statement the driver would send timestamps to the server using nanoseconds instead of milliseconds. (Bug#21438)

  • When using server-side prepared statements and timestamp columns, value would be incorrectly populated (with nanoseconds, not microseconds). (Bug#21438)

  • ParameterMetaData throws NullPointerException when prepared SQL has a syntax error. Added generateSimpleParameterMetadata configuration property, which when set to true will generate metadata reflecting VARCHAR for every parameter (the default is false, which will cause an exception to be thrown if no parameter metadata for the statement is actually available). (Bug#21267)

  • Fixed an issue where XADataSources couldn't be bound into JNDI, as the DataSourceFactory didn't know how to create instances of them.

Other changes:

  • Avoid static synchronized code in JVM class libraries for dealing with default timezones.

  • Performance enhancement of initial character set configuration, driver will only send commands required to configure connection character set session variables if the current values on the server do not match what is required.

  • Re-worked stored procedure parameter parser to be more robust. Driver no longer requires BEGIN in stored procedure definition, but does have requirement that if a stored function begins with a label directly after the "returns" clause, that the label is not a quoted identifier.

  • Throw exceptions encountered during timeout to thread calling Statement.execute*(), rather than RuntimeException.

  • Changed cached result set metadata (when using cacheResultSetMetadata=true) to be cached per-connection rather than per-statement as previously implemented.

  • Reverted back to internal character conversion routines for single-byte character sets, as the ones internal to the JVM are using much more CPU time than our internal implementation.

  • When extracting foreign key information from SHOW CREATE TABLE in DatabaseMetaData, ignore exceptions relating to tables being missing (which could happen for cross-reference or imported-key requests, as the list of tables is generated first, then iterated).

  • Fixed some Null Pointer Exceptions (NPEs) when cached metadata was used with UpdatableResultSets.

  • Take localSocketAddress property into account when creating instances of CommunicationsException when the underyling exception is a java.net.BindException, so that a friendlier error message is given with a little internal diagnostics.

  • Fixed cases where ServerPreparedStatements weren't using cached metadata when cacheResultSetMetadata=true was used.

  • Use a java.util.TreeMap to map column names to ordinal indexes for ResultSet.findColumn() instead of a HashMap. This allows us to have case-insensitive lookups (required by the JDBC specification) without resorting to the many transient object instances needed to support this requirement with a normal HashMap with either case-adjusted keys, or case-insensitive keys. (In the worst case scenario for lookups of a 1000 column result set, TreeMaps are about half as fast wall-clock time as a HashMap, however in normal applications their use gives many orders of magnitude reduction in transient object instance creation which pays off later for CPU usage in garbage collection).

  • When using cached metadata, skip field-level metadata packets coming from the server, rather than reading them and discarding them without creating com.mysql.jdbc.Field instances.

C.6.2.5. Changes in MySQL Connector/J 5.0.4 (20 October 2006)

Bugs fixed:

  • DBMD.getColumns() does not return expected COLUMN_SIZE for the SET type, now returns length of largest possible set disregarding whitespace or the "," delimitters to be consistent with the ODBC driver. (Bug#22613)

  • Added new _ci collations to CharsetMapping - utf8_unicode_ci not working. (Bug#22456)

  • Driver was using milliseconds for Statement.setQueryTimeout() when specification says argument is to be in seconds. (Bug#22359)

  • Workaround for server crash when calling stored procedures via a server-side prepared statement (driver now detects prepare(stored procedure) and substitutes client-side prepared statement). (Bug#22297)

  • Driver issues truncation on write exception when it shouldn't (due to sending big decimal incorrectly to server with server-side prepared statement). (Bug#22290)

  • Newlines causing whitespace to span confuse procedure parser when getting parameter metadata for stored procedures. (Bug#22024)

  • When using information_schema for metadata, COLUMN_SIZE for getColumns() is not clamped to range of java.lang.Integer as is the case when not using information_schema, thus leading to a truncation exception that isn't present when not using information_schema. (Bug#21544)

  • Column names don't match metadata in cases where server doesn't return original column names (column functions) thus breaking compatibility with applications that expect 1–1 mappings between findColumn() and rsmd.getColumnName(), usually manifests itself as "Can't find column ('')" exceptions. (Bug#21379)

  • Driver now sends numeric 1 or 0 for client-prepared statement setBoolean() calls instead of '1' or '0'.

  • Fixed configuration property jdbcCompliantTruncation was not being used for reads of result set values.

  • DatabaseMetaData correctly reports true for supportsCatalog*() methods.

  • Driver now supports {call sp} (without "()" if procedure has no arguments).

C.6.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 via SHOW CREATE PROCEDURE or selecting from mysql.proc instead of throwing an exception. The default value for this option is false

Bugs fixed:

  • Fixed Statement.cancel() causes NullPointerException if underlying connection has been closed due to server failure. (Bug#20650)

  • If the connection to the server has been closed due to a server failure, then the cleanup process will call Statement.cancel(), triggering a NullPointerException, even though there is no active connection. (Bug#20650)

C.6.2.7. Changes in MySQL Connector/J 5.0.2 (11 July 2006)

Bugs fixed:

  • MysqlXaConnection.recover(int flags) now allows combinations of XAResource.TMSTARTRSCAN and TMENDRSCAN. To simulate the “scanning” nature of the interface, we return all prepared XIDs for TMSTARTRSCAN, and no new XIDs for calls with TMNOFLAGS, or TMENDRSCAN when not in combination with TMSTARTRSCAN. This change was made for API compliance, as well as integration with IBM WebSphere's transaction manager. (Bug#20242)

  • Fixed MysqlValidConnectionChecker for JBoss doesn't work with MySQLXADataSources. (Bug#20242)

  • Added connection/datasource property pinGlobalTxToPhysicalConnection (defaults to false). When set to true, when using XAConnections, the driver ensures that operations on a given XID are always routed to the same physical connection. This allows the XAConnection to support XA START ... JOIN after XA END has been called, and is also a workaround for transaction managers that don't maintain thread affinity for a global transaction (most either always maintain thread affinity, or have it as a configuration option). (Bug#20242)

  • Better caching of character set converters (per-connection) to remove a bottleneck for multibyte character sets. (Bug#20242)

  • Fixed ConnectionProperties (and thus some subclasses) are not serializable, even though some J2EE containers expect them to be. (Bug#19169)

  • Fixed driver fails on non-ASCII platforms. The driver was assuming that the platform character set would be a superset of MySQL's latin1 when doing the handshake for authentication, and when reading error messages. We now use Cp1252 for all strings sent to the server during the handshake phase, and a hard-coded mapping of the language systtem variable to the character set that is used for error messages. (Bug#18086)

  • Fixed can't use XAConnection for local transactions when no global transaction is in progress. (Bug#17401)

C.6.2.8. Changes in MySQL Connector/J 5.0.1 (Not Released)

Not released due to a packaging error

C.6.2.9. Changes in MySQL Connector/J 5.0.0 (22 December 2005)

Bugs fixed:

  • Added support for Connector/MXJ integration via url subprotocol jdbc:mysql:mxj://.... (Bug#14729)

  • Idle timeouts cause XAConnections to whine about rolling themselves back. (Bug#14729)

  • When fix for Bug#14562 was merged from 3.1.12, added functionality for CallableStatement's parameter metadata to return correct information for .getParameterClassName(). (Bug#14729)

  • Added service-provider entry to META-INF/services/java.sql.Driver for JDBC-4.0 support. (Bug#14729)

  • Fuller synchronization of Connection to avoid deadlocks when using multithreaded frameworks that multithread a single connection (usually not recommended, but the JDBC spec allows it anyways), part of fix to Bug#14972). (Bug#14729)

  • Moved all SQLException constructor usage to a factory in SQLError (ground-work for JDBC-4.0 SQLState-based exception classes). (Bug#14729)

  • Removed Java5-specific calls to BigDecimal constructor (when result set value is '', (int)0 was being used as an argument indirectly via method return value. This signature doesn't exist prior to Java5.) (Bug#14729)

  • Implementation of Statement.cancel() and Statement.setQueryTimeout(). Both require MySQL-5.0.0 or newer server, require a separate connection to issue the KILL QUERY statement, and in the case of setQueryTimeout() creates an additional thread to handle the timeout functionality.

    Note: Failures to cancel the statement for setQueryTimeout() may manifest themselves as RuntimeExceptions rather than failing silently, as there is currently no way to unblock the thread that is executing the query being cancelled due to timeout expiration and have it throw the exception instead. (Bug#14729)

  • Return "[VAR]BINARY" for RSMD.getColumnTypeName() when that is actually the type, and it can be distinguished (MySQL-4.1 and newer). (Bug#14729)

  • Attempt detection of the MySQL type BINARY (it 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 ...}").

  • Don't allow .setAutoCommit(true), or .commit() or .rollback() on an XA-managed connection as per the JDBC specification.

  • XADataSource implemented (ported from 3.2 branch which won't be released as a product). Use com.mysql.jdbc.jdbc2.optional.MysqlXADataSource as your datasource class name in your application server to utilize XA transactions in MySQL-5.0.10 and newer.

  • Moved -bin-g.jar file into separate debug subdirectory to avoid confusion.

  • Return original column name for RSMD.getColumnName() if the column was aliased, alias name for .getColumnLabel() (if aliased), and original table name for .getTableName(). Note this only works for MySQL-4.1 and newer, as older servers don't make this information available to clients.

  • Setting useJDBCCompliantTimezoneShift=true (it 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).

C.6.3. Changes in MySQL Connector/J 3.1.x

C.6.3.1. Changes in MySQL Connector/J 3.1.15 (Not yet released)

Important change: Due to a number of issues with the use of server-side prepared statements, Connector/J 5.0.5 has disabled their use by default. The disabling of server-side prepared statements does not affect the operation of the connector in any way.

To enable server-side prepared statements you must add the following configuration property to your connector string:

useServerPrepStmts=true

The default value of this property is false (that is, Connector/J does not use server-side prepared statements).

Bugs fixed:

  • Specifying US-ASCII as the character set in a connection to a MySQL 4.1 or newer server does not map correctly. (Bug#24840)

C.6.3.2. Changes in MySQL Connector/J 3.1.14 (10-19-2006)

Bugs fixed:

  • Check and store value for continueBatchOnError property in constructor of Statements, rather than when executing batches, so that Connections closed out from underneath statements don't cause NullPointerExceptions when it is required to check this property. (Bug#22290)

  • Fixed Bug#18258 - DatabaseMetaData.getTables(), columns() with bad catalog parameter threw exception rather than return empty result set (as required by spec). (Bug#22290)

  • Driver now sends numeric 1 or 0 for client-prepared statement setBoolean() calls instead of '1' or '0'. (Bug#22290)

  • Fixed bug where driver would not advance to next host if roundRobinLoadBalance=true and the last host in the list is down. (Bug#22290)

  • Driver issues truncation on write exception when it shouldn't (due to sending big decimal incorrectly to server with server-side prepared statement). (Bug#22290)

  • Fixed bug when calling stored functions, where parameters weren't numbered correctly (first parameter is now the return value, subsequent parameters if specified start at index "2"). (Bug#22290)

  • Removed logger autodetection altogether, must now specify logger explicitly if you want to use a logger other than one that logs to STDERR. (Bug#21207)

  • DDriver throws NPE when tracing prepared statements that have been closed (in asSQL()). (Bug#21207)

  • ResultSet.getSomeInteger() doesn't work for BIT(>1). (Bug#21062)

  • Escape of quotes in client-side prepared statements parsing not respected. Patch covers more than bug report, including NO_BACKSLASH_ESCAPES being set, and stacked quote characters forms of escaping (that is, '' or ""). (Bug#20888)

  • Fixed can't pool server-side prepared statements, exception raised when re-using them. (Bug#20687)

  • Fixed Updatable result set that contains a BIT column fails when server-side prepared statements are used. (Bug#20485)

  • Fixed updatable result set throws ClassCastException