New features in the Entity Framework support!

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Locked
Devart
Site Admin
Posts: 3276
Joined: Tue 26 Oct 2004 13:51

New features in the Entity Framework support!

Post by Devart » Thu 24 Apr 2014 13:25

Dear users,

We are glad to announce the new features that are available in the Entity Framework support in the latest version:
  • The datetimeoffset pseudo type of SSDL, which corresponds to System.DateTimeOffset, is implemented (MySQL, SQLite)
  • The database server version is added to the generated Code-First Migrations script (MySQL, Oracle, PostgreSQL, SQLite, DB2)
  • 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 (Oracle)
  • 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 (Oracle)
  • 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 (Oracle)
  • 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 (MySQL, Oracle, PostgreSQL, SQLite, DB2)
  • The bug with generating SQL for EntitySQL ANYELEMENT is fixed (MySQL, Oracle, PostgreSQL, SQLite, DB2, Salesforce)
  • The bug with generation of the XMLTYPE columns in Code-First Migrations is fixed (Oracle)
  • 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 (Oracle)
  • The bug related to the "Constructor on type 'System.Data.Entity.Migrations.History.HistoryContext' not found." error in Code-First Migrations after upgrading Entity Framework from 5 to 6 is fixed (SQLite)
Devart development team
http://www.devart.com/dotconnect/entityframework.html

Locked