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 Version 8.x  /  Changes in MySQL Connector/NET 8.0.18 (2019-10-14, General Availability)

Changes in MySQL Connector/NET 8.0.18 (2019-10-14, 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 for .NET Core 3.0 was added. (WL #13114)

  • In tandem with Microsoft, Connector/NET ends support for .NET Core 1.0 and 1.1 (and also for Entity Framework Core 1.1, which depends on .NET Core 1.1). (WL #13387)

  • Previously, if the server restricted a classic Connector/NET session to sandbox mode and the password on the account expired, the session continued to permit the use of SET statements. Now, SET statements in sandbox mode with an expired password are prohibited and will return an error message if used. The one exception is SET PASSWORD, which is still permitted (see Server Handling of Expired Passwords). (WL #13305)

Bugs Fixed

  • The Renci.SshNet.dll deployment was problematic for Connector/NET 8.0.17 MSI installations. Some applications, such as Microsoft Excel, were unable to read MySQL data as a result. This fix removes unnecessary dependencies on the DLL and also ensures that the MSI installation deploys the correct Renci.SshNet.dll to the GAC. (Bug #30215984, Bug #96614)

  • Connector/NET returned an inaccurate value for the YEAR type when a prepared command was used. (Bug #28383721, Bug #91751)

  • 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)