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 18 Sep 2020 14:20

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 3.1.8 is supported
  • Support for spatial data types in EF Core 3 is implemented (MySQL, Oracle, PostgreSQL, SQLite)
  • The new names of spatial functions in MySQL Server 8 are supported in EF5/EF6 provider
  • The new NuGet package Devart.Data.MySql.EFCore.NetTopolosySuite with a .NET Standard 2.1 assembly, that is compatible with .NET Core 3, is added
  • The new NuGet package Devart.Data.Oracle.EFCore.NetTopolosySuite with a .NET Standard 2.1 assembly, that is compatible with .NET Core 3, is added
  • The new NuGet package Devart.Data.PostgreSql.EFCore.NetTopolosySuite with a .NET Standard 2.1 assembly, that is compatible with .NET Core 3, is added
  • The new NuGet package Devart.Data.SQLite.EFCore.NetTopolosySuite with a .NET Standard 2.1 assembly, that is compatible with .NET Core 3, is added
  • The new \Entity\EFCore3\Devart.Data.MySql.Entity.EFCore.NetTopolosySuite.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
  • The new \Entity\EFCore3\Devart.Data.Oracle.Entity.EFCore.NetTopolosySuite.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
  • The new \Entity\EFCore3\Devart.Data.PostgreSql.Entity.EFCore.NetTopolosySuite.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
  • The new \Entity\EFCore3\Devart.Data.SQLite.Entity.EFCore.NetTopolosySuite.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
  • The MySqlFunctions class, which allows using MySQL-specific functions in LINQ to Entities, is supported in EF Core
  • The MySqlTextFunctions class, which allows using MySQL full-text search functionality in LINQ to Entities, is supported in EF Core
  • The OracleFunctions class, which allows using Oracle-specific functions in LINQ to Entities, is supported in EF Core
  • The OracleTextFunctions class, which allows using Oracle full-text search functionality in LINQ to Entities, is supported in EF Core
  • The PgSqlFunctions class, which allows using PostgreSQL-specific functions in LINQ to Entities, is supported in EF Core
  • The PgSqlTextFunctions class, which allows using PostgreSQL full-text search functionality in LINQ to Entities, is supported in EF Core
  • The SQLiteFunctions class, which allows using SQLite-specific functions in LINQ to Entities, is supported in EF Core
  • The SQLiteTextFunctions class, which allows using SQLite full-text search functionality in LINQ to Entities, is supported in EF Core
  • The bug with generating invalid SQL when filtering on a boolean property that is assigned with .Any() in EF Core 3.1 is fixed (Oracle)
  • The bug with generating invalid SQL when filtering on a boolean property that is assigned with comparing to Count() in EF Core 3.1 is fixed (Oracle)
  • The bug with throwing "The method or operation is not implemented." when using the DbContext template / Fluent Mapping=True in EF4/EF6 is fixed (cloud providers)
Devart development team
http://www.devart.com/dotconnect/entityframework.html

Locked