New Versions of dotConnect ADO.NET Providers with Improved Entity Framework Support!

July 18, 2012

Devart is glad to announce the release of the new versions of ADO.NET data providers, enhanced database connectivity solutions, built over the ADO.NET architecture, that support Entity Framework and LinqConnect ORM solutions. New versions of dotConnect data providers for Oracle, MySQL, PostgreSQL, and SQLite offer you advanced Entity Framework support.

Full-text Search Functionality Support

New dotConnect versions support full-text search functionality of the corresponding databases and implement 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, CreateIndex, and DropIndex operations. You can find more information on using the full-text search and indexing functionality in our blog articles:

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 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. See more information in the documentation of our providers for Oracle, MySQL, PostgreSQL, and SQLite.

Code-First Support Improvements

Creating indexes for foreign key columns is implemented in Code-First CreateDatabase functionality for Oracle, PostgreSQL, and SQLite (MySQL creates such indexes implicitly by default). The config.DatabaseScript.ForeignKey.IndexCreation option is used to control the creation of these indexes.

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.

In dotConnect for Oracle we have implemented some specific functionality for Code-First Migrations. The ColumnTypeCasingConventionCompatibility convention is now set to true by default. We have also added the TruncateLongDefaultNames option to truncate the long default names of indexes, primary keys, foreign keys, triggers, and sequences generated by Code-First Migrations. These changes allow you to use not only code-based Code-First Migrations, but also automatic Code-First Migrations with dotConnect for Oracle.

If you wish to provide feedback on the new versions, you can do it in our forums or with contact form. There is also a feedback form in the support zone of every product. We are always glad to hear your comments and take into account your development needs.