dotConnect for MySQL 8.7 is released!

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Site Admin
Posts: 3282
Joined: Tue 26 Oct 2004 13:51

dotConnect for MySQL 8.7 is released!

Post by Devart » Fri 09 Dec 2016 12:57

Dear users,

Devart is glad to announce the release of dotConnect for MySQL 8.7, Devart ADO.NET data provider for MySQL with support for Entity Framework, LinqConnect (LINQ to MySQL) and NHibernate. The new version offers you support for Database-First approach in Entity Framework Core via Package Manager Console, support for JSON functionality of MySQL in Entity Framework, and other features.

Entity Framework Core Database-First Support

Entity Framework Core supports the Database-First approach via the Scaffold-DbContext command of Package Manager Console. This command scaffolds a DbContext and entity type classes for a specified database.

Now dotConnect for MySQL also supports this command allowing you to quickly generate context and entity classes for an existing schema. In order for the database-first functionality to work, add the Devart.Data.Mysql.Entity.EFCore.Design.dll assembly to the project references in addition to other necessary provider assemblies.

JSON Functionality Support in Entity Framework

dotConnect for MySQL now supports the JSON functionality of the MySQL database in Entity Framework v4 - v6.

With the new provider version you will be able to use JSON-specific functions in your LINQ to Entities queries. For the list of the supported functions and examples of how to use them, you can read our blog article: JSON Support in Entity Framework v4 - v6 in dotConnect for Oracle, MySQL, and PostgreSQL

Other Improvements

Additionally, dotConnect for MySQL can now be installed without adding its assemblies to the GAC automatically. We also have added Batch Updates support in Entity Framework Core, which will improve dotConnect for MySQL performance.

Here is the complete list of dotConnect for MySQL 8.7.794 features:
  • The 'Do not install assemblies in the GAC' check box that allows disabling placing the provider assemblies to the GAC is added to the Install Wizard
  • The bug with looking up a column with decimal(19,4) type for MySQL is fixed
  • The bug with generating an error when using MySqlMonitor on Linux is fixed
  • The bug with the "Query execution was interrupted" exception after invoking the Cancel method of MySqlCommand is fixed
  • The bug with not using parameters value in ParentRelation data in MySqlDataTable.SelectCommand is fixed
  • The bug with looking up a column with decimal(19,4) type for MySQL is fixed
LinqConnect (formerly known as LINQ to MySQL)
  • The exception message for invoking CreateDatabase() for the model which includes an association with missing end is improved
  • The bug with submitting records to the database via a TPT inheritance is fixed
  • The bug with throwing System.InvalidCastException when inserting / updating the System.Object properties is fixed
Entity Developer
  • The possibility to choose whether to add new entities to a diagram or not in Update From Database Wizard is implemented
  • The behaviour is changed: now the DbContext template generates an additional partial class for the context class when "File Per Class" and "Generate Partial Class" are set to True (Entity Framework models)
Entity Framework support
  • Entity Framework Core 1.1.0 is supported
  • The Scaffold-DbContext NuGet command of Package Manager Console for generating a model basing on the existing database schema is supported in EF Core
  • Batch Updates support in EF Core is added
  • The MySqlJsonFunctions class is implemented in EF4/EF5/EF6 to use JSON functions in LINQ to Entities queries
  • The JSON datetype is supported in EF mapping
  • Signed versions of NetTopologySuite GIS library are supported in EF5/EF6
  • NetTopologySuite 1.14 is supported in EF5/EF6
  • GeoAPI 1.7.4 is supported in EF5/EF6
  • The NetTopologySuiteSigned and NetTopologySuiteUnsigned members are added to the SpatialServiceType enum in EF5/EF6
  • The config.DatabaseScript.Schema.DeleteDatabaseBehaviour option is supported in EF Core
  • The behaviour is changed: now by default System.DateTimeOffset is mapped to the datetime MySQL data type using CreateDatabase()/Code-First approach
  • The behaviour is changed: the functionality of SpatialServiceType.NetTopologySuiteSigned is moved to Devart.Data.MySql.Entity.EF5.dll / Devart.Data.MySql.Entity.EF6.dll
  • The bug with generating incorrect data types for 'tinytext', 'text', 'mediumtext' columns set via attribute / fluent mapping in the Code-First CreateDatabase/CreateDatabaseScript functionality is fixed
  • The bug with shortening PK, FK, IX, UX names in the Code-First CreateDatabase/CreateDatabaseScript functionality when config.CodeFirstOptions.TruncateLongDefaultNames=True is fixed
  • The bug with comparison in LINQ query when config.QueryOptions.UseCSharpNullComparisonBehavior=true is fixed
  • The bug with setting binary data types via Code-First mapping in EF4/EF5/EF6 is fixed
  • The bug with requesting extra privileges when preparing stored procedure is fixed
  • The bugs with logical expressions in EF Core are fixed
Devart development team