MySQL Connector/NET Release Notes

4.1 Changes in MySQL Connector/NET 6.10.9 (2019-07-29, General Availability)

Functionality Added or Changed

  • Connector/NET now supports IPV6 connections made using the classic MySQL protocol when the operating system on the server host also supports IPV6. (Bug #29682333)

  • Support was added for .NET Core 2.2, which is a cross-platform version of .NET for building applications that run on Linux, macOS and Windows (see Connector/NET Versions). (WL #12337)

Bugs Fixed

  • The InvariantCulture property was missing from some data types, which created issues during platform migration operations. Thanks to Effy Teva for the patch. (Bug #29262195, Bug #94045)

  • Connector/NET connections executed SHOW VARIABLES unnecessarily. (Bug #28928543, Bug #93202)

  • An exception was generated when the MySqlDbType enumeration was given an explicit value and then passed as a parameter to the MySqlCommand.Prepare method. (Bug #28834253, Bug #92912)

  • The CreateCommandBuilder and CreateDataAdapter methods were added to MySqlClientFactory class. Thanks to Cédric Luthi for the patch. (Bug #28560189, Bug #92206)

  • Validation was added to ensure that when a column is of type TIME and the value is 00:00:00, it takes the value instead of setting NULL. (Bug #28383726, Bug #91752)

  • Connector/NET returned the wrong time zone when the TIMESTAMP column was read from a MySQL table. (Bug #28156187)

  • Entity Framework Core: A syntax error was generated during an operation attempting to rename a table that was previously migrated from code. Now, the primary key constraint for an existing table can be dropped without errors when the follow-on migration operation is performed. (Bug #28107555, Bug #90958)

  • The implementation of DbProviderFactory prevented an application from connecting to MySQL in a generic way. Now, invoking the CreateDataAdapter method returns a valid adapter instead of returning the null value. (Bug #27292344, Bug #88660)

  • Connector/NET access to MySQL stopped working after the computer hosting the server was started and continued to operate uninterrupted for a defined period of time. (Bug #26930306, Bug #75604)