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 » Thu 14 Jan 2021 19:04

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 5.0.2 is supported (MySQL, Oracle, PostgreSQL, SQLite)
  • Entity Framework Core 3.1.11 is supported
  • The new metadata to describe autoincremental columns via annotations in EF Core Code-First Migrations are implemented (MySQL, Oracle, PostgreSQL, SQLite, DB2)
  • The new config.DatabaseScript.Index.UseCurrentSchema option (default value is false) is added for ability to ignore schema set for indexes via EF Core Code-First Migrations (Oracle)
  • The behavior is changed: config.DatabaseScript.Index.UseCurrentSchema is set to false by default; as a result, the schema argument in CreateIndex(), DropIndex(), AddUniqueConstraint(), DropUniqueConstraint() operations is now applied not only to the table name, but also to the index name, i.e. previously, the index was always created in the current schema, and now it is created in the schema of the table to which the index belongs (Oracle)
  • The bug with ignoring schema set for indexes via CreateIndex(), DropIndex(), AddUniqueConstraint(), DropUniqueConstraint() operations of EF Core Code-First Migrations is fixed (Oracle)

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

Locked