Related Documentation Download these Release Notes
PDF (US Ltr) - 0.7Mb
PDF (A4) - 0.7Mb


MySQL Connector/NET Release Notes  /  Changes in MySQL Connector/Net 6.10  /  Changes in MySQL Connector/NET 6.10.4 (2017-10-25, General Availability)

Changes in MySQL Connector/NET 6.10.4 (2017-10-25, General Availability)

Functionality Added or Changed

  • Online API reference documentation is now available for MySQL Connector/NET. This new format replaces the files compressed and deployed in a binary format with the extension .CHM (Compiled HTML) that previously shipped with each connector release.

  • The deprecated UseProcedureBodies connection-string option was removed. Instead, the CheckParameters option can be used to check stored parameters against the server.

  • EF Core: Character set and collation now are independently configurable in EF Core models. The values can be set at both the entity and entity-property levels by using either data annotation (new attributes) or new methods added to the code-first fluent API using the MySql.Data.EntityFrameworkCore.Extensions namespace. Specifically, the new items added for setting character set and collation are:

    • Attributes:[MySqlCharset] and [MySqlCollation]

    • Methods: ForMySQLHasCharset() and ForMySQLHasCollation()

Bugs Fixed

  • Assemblies within NuGet packages were not fully signed. (Bug #26739307)

  • EF Core: Inserting a date of '0000-00-00' into a column when also setting Convert Zero Datetime=True in the connection string of a class that derives from DbContext produced an exception, instead of performing the expected conversion. (Bug #26552753, Bug #87120)

  • EF Core: Foreign key relations were not consistently created within the entity model generated by scaffolding a MySQL database. (Bug #26339430)

  • Invoking the MySql.Web.Security.MySqlWebSecurity.CreateUserAndAccount method with valid arguments, including additionalUserAttributes as an object with key/value pairs, returned an out-of-range exception. Thanks to Stein Setvik for contributing to the fix. (Bug #25046364)

  • The default character set and encoding were not set properly when making a connection to MySQL 5.6 and 5.7 servers configured to use the utf8 character set. (Bug #23257011)