dotConnect for MySQL 7.1 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 7.1 is released!

Post by Devart » Wed 18 Jul 2012 16:31

Dear users,

Devart is glad to announce the release of the new version of dotConnect for MySQL, enhanced database connectivity solution, built over the ADO.NET architecture, that supports Entity Framework and LinqConnect ORM solutions. New dotConnect for MySQL offers you advanced Entity Framework support.

Full-text Search Functionality Support

New dotConnect for MySQL version supports full-text search functionality of MySQL server and implements classes for working with full-text search functions in LINQ to Entities. Full-text indexing was supported in Code-First Migrations. The corresponding classes were created to customize CreateTable and CreateIndex operations. You can find more information on using the full-text search and indexing functionality in our blog article Using MySQL Full-Text Search in Entity Framework.

Entity Framework Provider Configuration

Entity Framework provider behaviour can now be configured not only in code but also in the config file of the application. The corresponding xsd file is added to the dotConnect for MySQL installation package to allow using Visual Studio intellisense and validation when editing the corresponding config file sections. Configuring Entity Framework provider through the config file provides you more flexibility than configuring with code because you don't need to recompile your solution to apply new configuration.

Code-First Support Improvements

A new config.Workarounds.IgnoreDboSchemaName option for configuring Entity Framework providers is added. This option is for ignoring the dbo schema name and is enabled by default when using Code-First Migrations, thus allowing you to use Code-First Migrations out-of-the-box without the need to add or remove any conventions manually in your solutions. This also allows you to specify the schema (database) for a table in Code-First Migrations.

Here is the complete list of dotConnect for MySQL 7.1.40 features:

LinqConnect (formerly known as LINQ to MySQL)
  • The bug with enumerating queries that have empty result sets is fixed
  • The bug with materializing query results into invalid object properties is fixed
  • The query cache bug with distinguishing compiled queries that have nullable parameters is fixed
  • The bug with deleting many-to-many links of entity having multiple many-to-many associations is fixed
Entity Developer
  • The behaviour is changed: the warning, related to the missing property setter, is disabled (LinqConnect models)
  • The behaviour is changed: for the association, in which the many-side entity hasn't the primary key, the code and the mapping are not generated (LinqConnect models)
  • The behaviour is changed: the properties, that correspond autoincrement fields, are generated with a ReadOnly keyword in VB.NET (LinqConnect models)
Entity Framework support
  • The support of the MySQL full-text search functionality is implemented
  • The MySqlTextFunctions class for working with full-text search functions in LINQ to Entities is added
  • The MySqlCreateIndexConfiguration class for creating full-text indexes in CreateIndex operation in Code-First Migrations is added
  • The MySqlCreateTableConfiguration class for customizing the CreateTable operation (setting storage engine) in Code-First Migrations is added
  • The possibility of setting configuration options via the application config file is implemented
  • The Devart.Data.MySql.Entity.xsd file is added to the installation in order to simplify setting and validating the application config file settings when using the XML Editor
  • Code-First Migrations now supports specifying which schema (database) a table belongs to
  • The config.Workarounds.IgnoreDboSchemaName configuration option is added. The option is automatically set to True, if Code-First (Migrations) EF v4.x/5.x is used
  • CASE generation is improved
  • The behaviour is changed: in case of using Code-First (Migrations) EF v4.x/5.x the schema name 'dbo' will be ignored by default
Devart development team