MySQL Connector/NET Release Notes  /  Changes in MySQL Connector/Net 5.2  /  Changes in MySQL Connector/NET 5.2.0 (2008-02-11)

Changes in MySQL Connector/NET 5.2.0 (2008-02-11)

Functionality Added or Changed

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

  • Added support for DbDataAdapter UpdateBatchSize. Batching is fully supported including collapsing inserts down into the multi-value form if possible.

  • DDEX provider now works under Visual Studio 2008 beta 2.

  • Added ClearPool and ClearAllPools features.

Bugs Fixed

  • Some speed improvements have been implemented in the TokenizeSql process used to identify elements of SQL statements. (Bug #34220)

  • When accessing tables from different databases within the same TransactionScope, the same user/password combination would be used for each database connection. MySQL Connector/NET does not handle multiple connections within the same transaction scope. An error is now returned if you attempt this process, instead of using the incorrect authorization information. (Bug #34204)

  • The status of connections reported through the state change handler was not being updated correctly. (Bug #34082)

  • Incorporated some connection string cache optimizations sent to us by Maxim Mass. (Bug #34000)

  • In an open connection where the server had disconnected unexpectedly, the status information of the connection would not be updated properly. (Bug #33909)

  • Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug #31433)

  • Column name metadata was not using the character set as defined within the connection string being used. (Bug #31185)

  • Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug #31090)

  • Commands executed from within the state change handler 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)