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.1 is supported
- The bug with using nullable enum properties with default mapping to integers in LINQ query in EF Core 3.1 is fixed (MySQL, Oracle, PostgreSQL, SQLite, DB2)
- The bug with using value converters detected automatically by .HasConversion<string>() in EF Core 3 is fixed (MySQL, Oracle, PostgreSQL, SQLite, DB2)
- The bug with using NULL constant values in EF Core 3 is fixed (MySQL, Oracle, PostgreSQL, SQLite, DB2)
- The bug with using binary operators AND, OR in EF Core 3 is fixed (MySQL, Oracle, PostgreSQL, SQLite, DB2)
- The bug with using a discriminator in EF Core 3 is fixed (Oracle)
- The bug with querying types in inheritance hierarchy via EF Core 3 is fixed (Oracle)
- The bug with generating a subselect within the CASE clause in EF Core 3 is fixed (Oracle)
- The bug with using .All in the .Where expression in EF Core 2 and EF Core 3 is fixed (Oracle)
- The bug with detecting string parameter data type in EF Core 3 expressions is fixed (Oracle)
- The bug with paging in EF Core 3, when using JOINs and subqueries to Oracle 11.2 and below, is fixed (Oracle)
- The bug with missing GENERATED BY DEFAULT AS IDENTITY in the script created by EF Core Migrations for the property with .HasColumnType(@"NUMBER").ValueGeneratedOnAdd() is fixed (Oracle)
- The bug with setting a default value for DateTime and TimeSpan properties via EF Core Code-First Migrations is fixed (SQLite)
http://www.devart.com/dotconnect/entityframework.html