New build of dotConnect for Oracle 8.3.146 is available!

New build of dotConnect for Oracle 8.3.146 is available!

Postby Devart » Thu 24 Apr 2014 13:13

Dear users,

New build of dotConnect for Oracle 8.3.146 is available for download now.

In this version:

  • The ADO.NET implementation of ASP.NET Identity 2.0 support is added
    • The new \Web\ASP.NET Identity 2\Devart.Data.Oracle.Web.Identity.dll assembly (its revision number is 2) is added to the provider installation folder
    • The new \Web\ASP.NET Identity 2\Install_identity_tables.sql and \Web\ASP.NET Identity 2\Uninstall_identity_tables.sql files are added to the provider installation folder
    • The new \Web\ASP.NET Identity 2\Upgrade_identity_tables_from_v1_to_v2.sql file is added to the provider installation folder
    • The new IUserEmailStore, IUserPhoneNumberStore, IUserTwoFactorStore, IUserLockoutStore interfaces are implemented in the UserStore class
  • The IDataReader interface is implemented in the OracleCursor class
  • The implementation of the OracleCommand.CommandTimeout property in the Direct mode is improved
  • The \Web\ASP.NET Identity 1\Install_identity_tables.sql file is updated: now user-friendly foreign key names are used
  • The bug with 'Load Test Editor' is fixed
  • The bug with the initialization of the OracleConnection.ShortServerVersion property, when connecting to Oracle 11g Release 2 or Oracle 12c, is fixed
LinqConnect (formerly known as LINQ to Oracle)
  • The behaviour is changed: the new "OUTER APPLY is not supported by Oracle Database 11g and lower. Oracle 12c or higher is required to run this LINQ statement correctly. If you need to run this statement with Oracle Database 11g or lower, rewrite it so that it can be converted to SQL, supported by the version of Oracle you use." exception is added
  • The bug related to wrong order of the insert/delete operations on SubmitChanges when the autogenerated primary keys are used is fixed
Entity Developer
  • The behaviour is changed: now a property in the generated code is initialized basing on the default value in CSDL only (instead of default values in any of SSDL and CSDL; Entity Framework models)
  • The bug related to the incorrect value setting for the "Has Stream" property when working with the WCF Data Services projects is fixed (Entity Framework models)
Entity Framework support
  • The database server version is added to the generated Code-First Migrations script
  • The behaviour is changed: now Database.Delete(DbConnection), when config.DatabaseScript.Schema.DeleteDatabaseBehaviour = AllSchemaObjects, removes sequences in the current schema of Oracle 12c only if config.DatabaseScript.Column.NumericIdentityBehavior = ExplicitTriggerAndSequence
  • The behaviour is changed: now Database.Exists(DbConnection), when config.DatabaseScript.Schema.DeleteDatabaseBehaviour = AllSchemaObjects, checks an existence of sequences in the current schema of Oracle 12c only if config.DatabaseScript.Column.NumericIdentityBehavior = ExplicitTriggerAndSequence
  • The behaviour is changed: now by default the Code-First CreateDatabase()/CreateDatabaseScript()/Code-First Migrations functionality generates the VARCHAR2(4000) and NVARCHAR2(2000) columns for Oracle 12c if the size of the corresponding columns is not set explicitly
  • The bug with generation of the XMLTYPE columns in Code-First Migrations is fixed
  • The bug with the explicitly named primary keys in Code-First Migrations, when the primary key is defined via the PrimaryKey() method of the CreateTable() operation, is fixed
  • The bug with generating SQL for EntitySQL ANYELEMENT is fixed
  • The bug with checking an existence of system-generated sequences by Database.Exists(DbConnection), when config.DatabaseScript.Schema.DeleteDatabaseBehaviour = AllSchemaObjects and config.DatabaseScript.Column.NumericIdentityBehavior = ExplicitTriggerAndSequence, is fixed

Devart development team
http://www.devart.com/dotconnect/oracle/
Devart
Devart Team
 
Posts: 3125
Joined: Tue 26 Oct 2004 13:51

Return to dotConnect for Oracle