Documentation Home
MySQL Connector/NET Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 0.8Mb
PDF (A4) - 0.8Mb


MySQL Connector/NET Release Notes  /  Changes in MySQL Connector/Net 6.9  /  Changes in MySQL Connector/NET 6.9.12 (2018-04-30, General Availability)

Changes in MySQL Connector/NET 6.9.12 (2018-04-30, General Availability)

Functionality Added or Changed

  • Connections made to MySQL 8.0 (up to and including version 8.0.3) and compatibility with the new data dictionary are now supported. For information about the data dictionary, see MySQL Data Dictionary. (WL #11325, WL #11326)

  • Support for the caching_sha2_password authentication plugin through the classic MySQL protocol was added. In addition, the sha256_password plugin was extended to support authentication when RSA keys are available through non-secure connections. Caching SHA-2 pluggable authentication offers faster authentication than basic SHA-256 authentication. (WL #11285)

  • Support was added for the new caching_sha2_password padding mechanism introduced in the MySQL 8.0 release series. The new padding mechanism is enabled when all of the following conditions apply:

    • The user account is set with the caching_sha2_password authentication plugin.

    • SSL is disabled explicitly (SslMode=none).

    • The AllowPublicKeyRetrieval connection option is enabled (AllowPublicKeyRetrieval=true).

    When enabled, the new padding mechanism is used to encode the password during RSA key encryption, which applies the correct padding to match the server. (WL #11618)

Bugs Fixed

  • The MySqlConnection.GetSchema("PROCEDURES", restrictions) method call generated an error message, instead of returning stored procedures, when the server connection was to the MySQL 8.0 release series. (Bug #25961782, WL #11325)

  • Attempting to generate an Entity Framework model from a MySQL 5.7 database using either EF5 or EF6 produced an exception that prevented the operation from generating the expected model. (Bug #22173048, Bug #79163)