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 15 May 2014 14:09

Dear users,

We are glad to announce the new features that are available in the Entity Framework support in the latest version:
  • The behaviour is changed: now a semicolon (;) after the very last statement is generated in the Code-First CreateDatabaseScript() functionality (MySQL, PostgreSQL, SQLite, DB2)
  • The functionality of setting the CodeFirstOptions.ColumnTypeCasingConventionCompatibility option via provider manifest token for a particular Entity Framework model is implemented for possibility of using both Database-First/Model-First model with XML mapping and Code-First model with fluent/attribute mapping in the same AppDomain (Oracle)
  • The config.DatabaseScript.Column.MaxStringSize configuration option (default value is OracleMaxStringSize.Standard) is added to provide the possibility of determining a default size of the VARCHAR2 and NVARCHAR2 columns for Oracle 12c if it was not set explicitly in the Code-First CreateDatabase()/Code-First Migrations functionality (Oracle)
  • The NumericIdentityBehavior.ImplicitSequence enumeration value of config.DatabaseScript.Column.NumericIdentityBehavior for Oracle 12c is now deprecated and not recommended to use; use the new NumericIdentityBehavior.GeneratedAlwaysAsIdentity, NumericIdentityBehavior.GeneratedByDefaultAsIdentity, NumericIdentityBehavior.GeneratedByDefaultOnNullAsIdentity values instead (Oracle)
  • The behaviour is changed: now a slash after the very last statement is generated in the Code-First CreateDatabaseScript() functionality (Oracle)
  • The behaviour is changed: now the Code-First CreateDatabase()/CreateDatabaseScript()/Code-First Migrations functionality for Oracle 12c generates 'GENERATED BY DEFAULT ON NULL AS IDENTITY' instead of 'GENERATED ALWAYS AS IDENTITY' for autoincrement identity columns when config.DatabaseScript.Column.NumericIdentityBehavior = Default (Oracle)
  • The behaviour is changed: the constraint name is ignored if a table primary key is deleted when running Code-First Migrations, that allows successful removing of automatically named primary key in PostgreSQL 9 or higher (PostgreSQL)
  • The bug related to the "ORA-01790: expression must have same datatype as corresponding expression" error when trying to map RAW to Binary and using multiple Include() is fixed (Oracle)
  • The bug with setting the config.DatabaseScript.Column.NumericIdentityBehavior option via application config file is fixed (Oracle)
  • The bug with setting the default size (2000) of raw type with fluent mapping for Oracle 12c is fixed (Oracle)
  • The bug with adding a primary key to the existing table when using Code-First Migrations is fixed (PostgreSQL)
Devart development team
http://www.devart.com/dotconnect/entityframework.html

Locked