dotConnect for Oracle 7.1 is released!

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

dotConnect for Oracle 7.1 is released!

Post by Devart » Wed 18 Jul 2012 16:19

Dear users,

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

Full-text Search Functionality Support

New dotConnect for Oracle version supports full-text search functionality of Oracle database 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 article Using Oracle 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 Oracle 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

Creating indexes for foreign key columns is implemented in Code-First CreateDatabase functionality. 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.

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.

Here is the complete list of dotConnect for Oracle 7.1.40 features:
  • The bug with ORA-01460 in the Direct Mode when the Unicode connection string parameter equals true is fixed
  • The bug with the multiple usage of the same parameter in the query containing returning in the Direct Mode is fixed
  • The bug with NullReferenceException under the transaction rollback of a connection placed into the pool is fixed
LinqConnect (formerly known as LINQ to Oracle)
  • 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 overloaded stored procedures and functions are supported
  • 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 Oracle Text full-text search functionality is implemented
  • The OracleTextFunctions class for working with Oracle Text functions in LINQ to Entities is added
  • The OracleCtxDdlPackage class for working with Oracle Text stored procedures of the CTX_DDL package is added
  • The OracleCreateIndexConfiguration class for customizing the CreateIndex operation in Code-First Migrations is improved
  • The OracleDropIndexConfiguration class is added for customizing the DropIndex operation (deleting Oracle Text indexes) in Code-First Migrations
  • The existing configuration classes for customizing the Code-First Migrations operations are renamed - the "Oracle" prefix is added (for example, the CreateTableConfiguration class was renamed to OracleCreateTableConfiguration); derived classes with the old names are added for backward compatibility
  • Creating indexes for FK columns in Code-First CreateDatabase functionality is implemented
  • The config.DatabaseScript.ForeignKey.IndexCreation configuration option is added (default value is True)
  • The config.DatabaseScript.ForeignKey.IndexTablespace configuration option is added to provide the possibility of setting the TABLESPACE, in which the index, created for the columns being parts of the foreign key, should be placed
  • The option of setting ConcurrencyCheck for CLOB/NCLOB columns (for better support of LightSwitch) is implemented
  • Overloads for the ToChar/ToNchar methods of the OracleFunctions class are added
  • The possibility of setting configuration options via the application config file is implemented
  • The Devart.Data.Oracle.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 the schema (database) the 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
  • The ColumnTypeCasingConventionCompatibility configuration option is moved from Workarounds to CodeFirstOptions (now it is config.CodeFirstOptions.ColumnTypeCasingConventionCompatibility). For the backward compatibility a wrapper property remains in Workarounds
  • The config.CodeFirstOptions.UseNonUnicodeStrings configuration option (default value is False) is added in order to treat string properties without an explicitly specified server data type, as non-unicode
  • The config.CodeFirstOptions.TruncateLongDefaultNames configuration option is added (default value is False) to provide the possibility of truncating long default names of indexes, primary keys, foreign keys, triggers, and sequences generated by Code-First Migrations
  • The overloaded stored procedures and functions are supported in Entity Framework runtime
  • CASE generation is improved
  • The behaviour is changed: the ColumnTypeCasingConventionCompatibility configuration option is automatically set to True for EF v4.3.x & 5.x. If you use DbContext with XML mapping (in EF v4.1 & v4.2), from now on you should explicitly set ColumnTypeCasingConventionCompatibility=False
  • 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
  • The bug with inserting data into MigrationHistory table when working with Oracle 10g is fixed
Devart development team