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: 3974
Joined: Tue 26 Oct 2004 13:51

New features in the Entity Framework support!

Post by Devart » Fri 25 May 2018 13:23

Dear users,

We are glad to announce the new features that are available in the Entity Framework support in the latest version:

  • Entity Framework Core 1.1.5 is supported
  • Entity Framework Core 2.0.3 is supported
  • The generation of the idempotent script in EF Core 2 Code-First Migrations for PostgreSQL 9.0 and higher is supported (PostgreSQL)
  • The DeleteDatabaseBehaviour.Database value of the config.DatabaseScript.Schema.DeleteDatabaseBehaviour option in EF Core 2 is supported (PostgreSQL)
  • The config.Workarounds.ProviderManifestToken option is added for setting provider manifest token for all contexts within application domain (SQLite)
  • The generation of the idempotent script in EF Core 2 Code-First Migrations is supported (Oracle)
  • The behavior is changed: now the EF Core Code-First Migrations script checks the existence of the MigrationHistory table not to try to create it if not necessary (Oracle)
  • The bug with missing Devart.Data.Oracle.Entity namespace in *.Designer.cs generated by EF Core 2 Code-First Migrations via Devart NuGet package is fixed (Oracle)
  • The bug with the "ORA-00920: invalid relational operator" error in the WHERE clause in EF Core 2 is fixed (Oracle)
  • The bug with the DateTime? properties, when config.CodeFirstOptions.UseDateTimeAsDate is set to True, in EF Core is fixed (Oracle)
  • The bug with generating command separators in the EF Core 2 Code-First Migrations script is fixed (MySQL, PostgreSQL)
  • The bug with missing Devart.Data.MySql.Entity namespace in *.Designer.cs generated by EF Core 2 Code-First Migrations via Devart NuGet package is fixed (MySQL)
  • The bug with missing Devart.Data.PostgreSql.Entity namespace in *.Designer.cs generated by EF Core 2 Code-First Migrations via Devart NuGet package is fixed (PostgreSQL)
  • The bug with using EnsureSchema in EF Core against PostgreSQL 9.2 and earlier, if schema names should be quoted when the schema exists but the required tables are missing, is fixed (PostgreSQL)
  • The bug with generating Guid literals in SQL statements, when a connection string includes "BinaryGUID=False;", is fixed (SQLite)
  • The bug with missing Devart.Data.SQLite.Entity namespace in *.Designer.cs generated by EF Core 2 Code-First Migrations via Devart NuGet package is fixed (SQLite)

Devart development team
http://www.devart.com/dotconnect/entityframework.html

Locked