What's New in EF Core 5

Search…
​Improve EF Core performance with EF Extensions​
 ​
​​
What's New in EF Core 5
EF Core 5.0 is currently in development, and here is the list of all the interesting changes introduced so far in each preview.
Preview 1
Simple logging
The simple logging feature adds functionality similar to Database.Log in EF6 by providing a simple way to get logs from EF Core without the need to configure any kind of external logging framework.
Simple way to get generated SQL
EF Core 5.0 introduces the ToQueryString extension method, which will return the SQL that EF Core will generate when executing a LINQ query.
Use a C# attribute to indicate that an entity has no key
An entity type can now be configured as having no key using the new KeylessAttribute.
[Keyless]
public class Address
{
    public string Street { get; set; }
    public string City { get; set; }
    public int Zip { get; set; }
}
Connection or connection string can be changed on initialized DbContext
It is now easier to create a DbContext instance without any connection or connection string. 
The connection or connection string can now be mutated on the context instance. 
This feature allows the same context instance to dynamically connect to different databases.
Change-tracking proxies
EF Core can now generate runtime proxies that automatically implement INotifyPropertyChanging and INotifyPropertyChanged. 
These then report value changes on entity properties directly to EF Core, avoiding the need to scan for changes. 
However, proxies come with their own set of limitations, so they are not for everyone.
Enhanced debug views
Debug views are an easy way to look at the internals of EF Core when debugging issues. A debug view for the Model was implemented some time ago. For EF Core 5.0, we have made the model view easier to read and added a new debug view for tracked entities in the state manager.
Improved handling of database null semantics
Relational databases typically treat NULL as an unknown value and therefore not equal to any other NULL. 
While C# treats null as a defined value, which compares equal to any other null. 
EF Core by default translates queries so that they use C# null semantics. EF Core 5.0 greatly improves the efficiency of these translations.
Indexer properties
EF Core 5.0 supports the mapping of C# indexer properties. These properties allow entities to act as property bags where columns are mapped to named properties in the bag.
Generation of check constraints for enum mappings
EF Core 5.0 migrations can now generate CHECK constraints for enum property mappings.
MyEnumColumn VARCHAR(10) NOT NULL CHECK (MyEnumColumn IN ('Useful', 'Useless', 'Unknown'))
IsRelational
A new IsRelational method has been added in addition to the existing IsSqlServer, IsSqlite and IsInMemory. This method can be used to test if the DbContext is using any relational database provider.
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    if (Database.IsRelational())
    {
        // Do relational-specific model configuration.
    }
}
Cosmos optimistic concurrency with ETags
The Azure Cosmos DB database provider now supports optimistic concurrency using ETags. Use the model builder in OnModelCreating to configure an ETag.
builder.Entity<Customer>().Property(c => c.ETag).IsEtagConcurrency();
The SaveChanges will then throw a DbUpdateConcurrencyException on a concurrency conflict, which can be handled to implement retries, etc.
Query translations for more DateTime constructs
Queries containing new DateTime construction is now translated.
Also, the following SQL Server functions are now mapped:
DateDiffWeek
DateFromParts
For example:
var count = context.Orders.Count(c => date > EF.Functions.DateFromParts(DateTime.Now.Year, 12, 25));
Query translations for more byte array constructs
Queries using Contains, Length, SequenceEqual, etc. on byte[] properties are now translated to SQL.
Query translation for Reverse
Queries using Reverse are now translated.
context.Employees.OrderBy(e => e.EmployeeID).Reverse()
Query translation for bitwise operators
Queries using bit-wise operators are now translated in more cases.
context.Orders.Where(o => ~o.OrderID == negatedId)
Query translation for strings on Cosmos
Queries that use the string methods such as, Contains, StartsWith, and EndsWith are now translated when using the Azure Cosmos DB provider.
Preview 2
Use a C# attribute to specify a property backing field
A C# attribute can now be used to specify the backing field for a property. This attribute allows EF Core to still write to and read from the backing field as would normally happen, even when the backing field cannot be found automatically.
public class Blog
{
    private string _mainTitle;
​
    public int Id { get; set; }
​
    [BackingField(nameof(_mainTitle))]
    public string Title
    {
        get => _mainTitle;
        set => _mainTitle = value;
    }
}
Complete discriminator mapping
EF Core uses a discriminator column for TPH mapping of an inheritance hierarchy.
Some performance enhancements are possible as long as EF Core knows all possible values for the discriminator. 
EF Core 5.0 now implements these enhancements.
For example, previous versions of EF Core would always generate this SQL for a query returning all types in a hierarchy.
SELECT [a].[Id], [a].[Discriminator], [a].[Name]
FROM [Animal] AS [a]
WHERE [a].[Discriminator] IN (N'Animal', N'Cat', N'Dog', N'Human')
EF Core 5.0 will now generate the following when a complete discriminator mapping is configured
SELECT [a].[Id], [a].[Discriminator], [a].[Name]
FROM [Animal] AS [a]
It will be the default behavior starting with preview 3.
Performance improvements in Microsoft.Data.Sqlite
The following two performances improvements are made for SQLite:
Retrieving binary and string data with GetBytes, GetChars, and GetTextReader is now more efficient by making use of SqliteBlob and streams.
The initialization of SqliteConnection is now lazy.
These improvements are in the ADO.NET Microsoft.Data.Sqlite provider and hence also improve performance outside of EF Core.
Preview 3
Filtered Include
The Include method now supports filtering of the entities included.
var blogs = context.Blogs
    .Include(e => e.Posts.Where(p => p.Title.Contains("Cheese")))
    .ToList();
This query will return blogs together with each associated post, but only when the post title contains "Cheese".
Skip and Take can also be used to reduce the number of included entities.
var blogs = context.Blogs
    .Include(e => e.Posts.OrderByDescending(post => post.Title).Take(5)))
    .ToList();
This query will return blogs with at most five posts included on each blog.
New ModelBuilder API for navigation properties
Navigation properties are primarily configured when defining relationships. However, the new Navigation method can be used in cases where navigation properties need an additional configuration. For example, to set a backing field for the navigation when the field would not be found by convention.
modelBuilder.Entity<Blog>().Navigation(e => e.Posts).HasField("_myposts");
Note that the Navigation API does not replace relationship configuration. Instead, it allows additional configuration of navigation properties in already discovered or defined relationships.
New command-line parameters for namespaces and connection strings
Migrations and scaffolding now allow namespaces to be specified on the command line. For example, to reverse engineer a database putting the context and model classes in different namespaces.
dotnet ef dbcontext scaffold "connection string" Microsoft.EntityFrameworkCore.SqlServer --context-namespace "My.Context" --namespace "My.Model"
Also, a connection string can now be passed to the database-update command.
dotnet ef database update --connection "connection string"
Equivalent parameters have also been added to the PowerShell commands used in the VS Package Manager Console.
EnableDetailedErrors has returned
For performance reasons, EF doesn't do additional null-checks when reading values from the database. This can result in exceptions that are hard to root-cause when an unexpected null is encountered.
Using EnableDetailedErrors will add extra null checking to queries such that, for a small performance overhead, these errors are easier to trace back to a root cause.
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    => optionsBuilder
        .EnableDetailedErrors()
        .EnableSensitiveDataLogging() // Often also useful with EnableDetailedErrors 
        .UseSqlServer(Your.SqlServerConnectionString);
Cosmos partition keys
The partition key to use for a given query can now be specified in the query.
await context.Set<Customer>()
             .WithPartitionKey(myPartitionKey)
             .FirstAsync();
Support for the SQL Server DATALENGTH function
This can be accessed using the new EF.Functions.DataLength method.
var count = context.Orders.Count(c => 100 < EF.Functions.DataLength(c.OrderDate));
Preview 4
Configure database precision/scale in model
Precision and scale for a property can now be specified using the model builder.
modelBuilder
    .Entity<Blog>()
    .Property(b => b.Numeric)
    .HasPrecision(16, 4);
Precision and scale can still be set via the full database type, such as "decimal(16,4)".
Specify SQL Server index fill factor
The fill factor can now be specified when creating an index on SQL Server. For example.
modelBuilder
    .Entity<Customer>()
    .HasIndex(e => e.Name)
    .HasFillFactor(90);
Preview 5
Database collations
The default collation for a database can now be specified in the EF model. It will flow through to generated migrations to set the collation when the database is created.
modelBuilder.UseCollation("German_PhoneBook_CI_AS");
When you create migrations then it generates the following to create the database on SQL Server.
CREATE DATABASE [Test]
COLLATE German_PhoneBook_CI_AS;
You can also specify the collation to use for specific database columns.
modelBuilder
    .Entity<User>()
    .Property(e => e.Name)
    .UseCollation("German_PhoneBook_CI_AS");
For those not using migrations, collations are now reverse-engineered from the database when scaffolding a DbContext.
Finally, the EF.Functions.Collate() allows for ad-hoc queries using different collations.
context.Users.Single(e => EF.Functions.Collate(e.Name, "French_CI_AS") == "Jean-Michel Jarre");
This will generate the following query for SQL Server.
SELECT TOP(2) [u].[Id], [u].[Name]
FROM [Users] AS [u]
WHERE [u].[Name] COLLATE French_CI_AS = N'Jean-Michel Jarre'
The ad-hoc collations should be used with care as they can negatively impact database performance.
Flow arguments into IDesignTimeDbContextFactory
Arguments now flow from the command line into the CreateDbContext method of IDesignTimeDbContextFactory. For example, to indicate this is a dev build, a custom argument (e.g. dev) can be passed on the command line.
dotnet ef migrations add two --verbose --dev
This argument will then flow into the factory, where it can be used to control how the context is created and initialized.
public class MyDbContextFactory : IDesignTimeDbContextFactory<SomeDbContext>
{
    public SomeDbContext CreateDbContext(string[] args)
        => new SomeDbContext(args.Contains("--dev"));
}
No-tracking queries with identity resolution
No-tracking queries can now be configured to perform identity resolution. For example, the following query will create a new Blog instance for each Post, even if each Blog has the same primary key.
context.Posts.AsNoTracking().Include(e => e.Blog).ToList();
However, at the expense of usually being slightly slower and always using more memory, this query can be changed to ensure only a single Blog instance is created.
context.Posts.AsNoTracking().PerformIdentityResolution().Include(e => e.Blog).ToList();
It is only useful for no-tracking queries since all tracking queries already exhibit this behavior. Also, following the API review, the PerformIdentityResolution the syntax will be changed.
Stored Computed columns
Most databases allow computed column values to be stored after computation.
The computed column is calculated only once on the update, instead of each time its value is retrieved it takes up disk space. 
This also allows the column to be indexed for some databases.
EF Core 5.0 allows computed columns to be configured as stored.
modelBuilder
    .Entity<User>()
    .Property(e => e.SomethingComputed)
    .HasComputedColumnSql("my sql", stored: true);
SQLite computed columns
EF Core now supports computed columns in SQLite databases.
Preview 6
Split queries for related collections
Starting with EF Core 3.0, EF Core always generates a single SQL query for each LINQ query.
It ensures consistency of the data returned within the constraints of the transaction mode in use.
However, it can become very slow when the query uses Include or a projection to bring back multiple related collections.
EF Core 5.0 now allows a single LINQ query including related collections to be split into multiple SQL queries.
It can significantly improve performance but can result in inconsistency in the results returned if the data changes between the two queries. 
The serializable or snapshot transactions can be used to mitigate this and achieve consistency with split queries, but that may bring other performance costs and behavioral differences.
Split queries with Include
For example, consider a query that pulls in two levels of related collections using Includemethod.
var artists = context.Artists
    .Include(e => e.Albums).ThenInclude(e => e.Tags)
    .ToList();
By default, EF Core will generate the following SQL when using the SQLite provider.
SELECT "a"."Id", "a"."Name", "t0"."Id", "t0"."ArtistId", "t0"."Title", "t0"."Id0", "t0"."AlbumId", "t0"."Name"
FROM "Artists" AS "a"
LEFT JOIN (
    SELECT "a0"."Id", "a0"."ArtistId", "a0"."Title", "t"."Id" AS "Id0", "t"."AlbumId", "t"."Name"
    FROM "Album" AS "a0"
    LEFT JOIN "Tag" AS "t" ON "a0"."Id" = "t"."AlbumId"
) AS "t0" ON "a"."Id" = "t0"."ArtistId"
ORDER BY "a"."Id", "t0"."Id", "t0"."Id0"
The new AsSplitQuery API can be used to change this behavior.
var artists = context.Artists
    .AsSplitQuery()
    .Include(e => e.Albums).ThenInclude(e => e.Tags)
    .ToList();
The AsSplitQuery is available for all relational database providers and can be used anywhere in the query, just like AsNoTracking. EF Core will now generate the following three SQL queries.
SELECT "a"."Id", "a"."Name"
FROM "Artists" AS "a"
ORDER BY "a"."Id"
​
SELECT "a0"."Id", "a0"."ArtistId", "a0"."Title", "a"."Id"
FROM "Artists" AS "a"
INNER JOIN "Album" AS "a0" ON "a"."Id" = "a0"."ArtistId"
ORDER BY "a"."Id", "a0"."Id"
​
SELECT "t"."Id", "t"."AlbumId", "t"."Name", "a"."Id", "a0"."Id"
FROM "Artists" AS "a"
INNER JOIN "Album" AS "a0" ON "a"."Id" = "a0"."ArtistId"
INNER JOIN "Tag" AS "t" ON "a0"."Id" = "t"."AlbumId"
ORDER BY "a"."Id", "a0"."Id"
All operations on the query root are supported including OrderBy, Skip, Take, Join, FirstOrDefault and similar single result selecting operations.
The filtered Includes with OrderBy, Skip, Take are not supported in preview 6, but are available in the daily builds and will be included in preview 7.
Split queries with collection projections
The AsSplitQuery method can also be used when collections are loaded in projections.
context.Artists
    .AsSplitQuery()
    .Select(e => new
    {
        Artist = e,
        Albums = e.Albums,
    }).ToList();
The above LINQ query generates the following two SQL queries when using the SQLite provider
SELECT "a"."Id", "a"."Name"
FROM "Artists" AS "a"
ORDER BY "a"."Id"
​
SELECT "a0"."Id", "a0"."ArtistId", "a0"."Title", "a"."Id"
FROM "Artists" AS "a"
INNER JOIN "Album" AS "a0" ON "a"."Id" = "a0"."ArtistId"
ORDER BY "a"."Id"
Only materialization of the collection is supported. Any composition after e.Albums in the above case won't result in a split query.
IndexAttribute
The new IndexAttribute can be placed on an entity type to specify an index for a single column.
[Index(nameof(FullName), IsUnique = true)]
public class User
{
    public int Id { get; set; }
​
    [MaxLength(128)]
    public string FullName { get; set; }
}
For SQL Server, Migrations will then generate the following SQL.
CREATE UNIQUE INDEX [IX_Users_FullName]
    ON [Users] ([FullName])
    WHERE [FullName] IS NOT NULL;
IndexAttribute can also be used to specify an index spanning multiple columns.
[Index(nameof(FirstName), nameof(LastName), IsUnique = true)]
public class User
{
    public int Id { get; set; }
​
    [MaxLength(64)]
    public string FirstName { get; set; }
​
    [MaxLength(64)]
    public string LastName { get; set; }
}
For SQL Server, the result is as shown below.
CREATE UNIQUE INDEX [IX_Users_FirstName_LastName]
    ON [Users] ([FirstName], [LastName])
    WHERE [FirstName] IS NOT NULL AND [LastName] IS NOT NULL;
Improved query translation exceptions
We are continuing to improve the exception messages generated when query translation fails. For example, this query uses the IsSignedunmapped property.
var artists = context.Artists.Where(e => e.IsSigned).ToList();
EF Core will throw the following exception indicating that translation failed because IsSigned is not mapped.
Unhandled exception. System.InvalidOperationException: The LINQ expression 'DbSet<Artist>()
   .Where(a => a.IsSigned)' could not be translated. Additional information: Translation of member 'IsSigned' on entity type 'Artist' failed. Possibly the specified member is not mapped. Either rewrite the query in a form that can be translated, or switch to client evaluation explicitly by inserting a call to either AsEnumerable(), AsAsyncEnumerable(), ToList(), or ToListAsync(). See <https://go.microsoft.com/fwlink/?linkid=2101038> for more information.
Similarly, better exception messages are now generated when attempting to translate string comparisons with culture-dependent semantics. For example, the following query attempts to use StringComparison.CurrentCulture.
var artists = context.Artists
    .Where(e => e.Name.Equals("The Unicorns", StringComparison.CurrentCulture))
    .ToList();
EF Core will now throw the following exception.
Unhandled exception. System.InvalidOperationException: The LINQ expression 'DbSet<Artist>()
     .Where(a => a.Name.Equals(
         value: "The Unicorns",
         comparisonType: CurrentCulture))' could not be translated. Additional information: Translation of 'string.Equals' method which takes 'StringComparison' argument is not supported. See <https://go.microsoft.com/fwlink/?linkid=2129535> for more information. Either rewrite the query in a form that can be translated, or switch to client evaluation explicitly by inserting a call to either AsEnumerable(), AsAsyncEnumerable(), ToList(), or ToListAsync(). See <https://go.microsoft.com/fwlink/?linkid=2101038> for more information.
Specify transaction ID
EF Core exposes a transaction ID for the correlation of transactions across calls.
This ID is typically set by EF Core when a transaction is started. 
If the application starts the transaction instead, then this feature allows the application to explicitly set the transaction ID so it is correlated correctly everywhere it is used. 
using (context.Database.UseTransaction(myTransaction, myId))
{
   ...
}
IPAddress mapping
The standard .NET IPAddress class is now automatically mapped to a string column for databases that do not already have native support. For example, consider mapping this entity type.
public class Host
{
    public int Id { get; set; }
    public IPAddress Address { get; set; }
}
On SQL Server, the migration will create the following table.
CREATE TABLE [Host] (
    [Id] int NOT NULL,
    [Address] nvarchar(45) NULL,
    CONSTRAINT [PK_Host] PRIMARY KEY ([Id]));
Entities can then be added in the normal way.
context.AddRange(
    new Host { Address = IPAddress.Parse("127.0.0.1")},
    new Host { Address = IPAddress.Parse("0000:0000:0000:0000:0000:0000:0000:0001")});
And the resulting SQL will insert the normalized IPv4 or IPv6 address.
Executed DbCommand (14ms) [Parameters=[@p0='1', @p1='127.0.0.1' (Size = 45), @p2='2', @p3='::1' (Size = 45)], CommandType='Text', CommandTimeout='30']
      SET NOCOUNT ON;
      INSERT INTO [Host] ([Id], [Address])
      VALUES (@p0, @p1), (@p2, @p3);
Exclude OnConfiguring when scaffolding
When a DbContext is scaffolded from an existing database, EF Core by default creates an OnConfiguring overload with a connection string so that the context is immediately usable. However, this is not useful if you already have a partial class with OnConfiguring, or if you are configuring the context some other way.
To address this, the scaffolding commands can now be instructed to omit the generation of OnConfiguring.
dotnet ef dbcontext scaffold "Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=Chinook" Microsoft.EntityFrameworkCore.SqlServer --no-onconfiguring
Or in the Package Manager Console.
Scaffold-DbContext 'Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=Chinook' Microsoft.EntityFrameworkCore.SqlServer -NoOnConfiguring
It is recommended to use a named connection string and secure storage like User Secrets.
Translations for FirstOrDefault on strings
The FirstOrDefault and similar operators for characters in strings are now translated in a LINQ query.
context.Customers.Where(c => c.ContactName.FirstOrDefault() == 'A').ToList();
It will be translated to the following SQL when using SQL Server.
SELECT [c].[Id], [c].[ContactName]
FROM [Customer] AS [c]
WHERE SUBSTRING([c].[ContactName], 1, 1) = N'A'
Simplify case blocks
EF Core now generates better queries with CASE blocks. Let's consider the following LINQ query.
context.Weapons
    .OrderBy(w => w.Name.CompareTo("Marcus' Lancer") == 0)
    .ThenBy(w => w.Id)
Previously, the above LINQ would be translated to the following query on SQL Server.
SELECT [w].[Id], [w].[AmmunitionType], [w].[IsAutomatic], [w].[Name], [w].[OwnerFullName], [w].[SynergyWithId]
FROM [Weapons] AS [w]
ORDER BY CASE
    WHEN (CASE
        WHEN [w].[Name] = N'Marcus'' Lancer' THEN 0
        WHEN [w].[Name] > N'Marcus'' Lancer' THEN 1
        WHEN [w].[Name] < N'Marcus'' Lancer' THEN -1
    END = 0) AND CASE
        WHEN [w].[Name] = N'Marcus'' Lancer' THEN 0
        WHEN [w].[Name] > N'Marcus'' Lancer' THEN 1
        WHEN [w].[Name] < N'Marcus'' Lancer' THEN -1
    END IS NOT NULL THEN CAST(1 AS bit)
    ELSE CAST(0 AS bit)
END, [w].[Id]");
But it is now translated to the following query.
SELECT [w].[Id], [w].[AmmunitionType], [w].[IsAutomatic], [w].[Name], [w].[OwnerFullName], [w].[SynergyWithId]
FROM [Weapons] AS [w]
ORDER BY CASE
    WHEN ([w].[Name] = N'Marcus'' Lancer') AND [w].[Name] IS NOT NULL THEN CAST(1 AS bit)
    ELSE CAST(0 AS bit)
END, [w].[Id]");
Preview 7
DbContextFactory
EF Core 5.0 introduces AddDbContextFactory and AddPooledDbContextFactory to register a factory for creating DbContext instances in the application's dependency injection container.
services.AddDbContextFactory<SomeDbContext>(b =>
    b.UseSqlServer(@"Server=(localdb)\mssqllocaldb;Database=Test"));
Application services such as ASP.NET Core controllers can then depend on IDbContextFactory<TContext> in the service constructor.
public class MyController
{
    private readonly IDbContextFactory<SomeDbContext> _contextFactory;
​
    public MyController(IDbContextFactory<SomeDbContext> contextFactory)
    {
        _contextFactory = contextFactory;
    }
}
DbContext instances can then be created and used as needed.
public void DoSomeThing()
{
    using (var context = _contextFactory.CreateDbContext())
    {
        // ...
    }
}
The DbContext instances created in this way are not managed by the application's service provider and therefore must be disposed of by the application.
This decoupling is very useful for Blazor applications, where using IDbContextFactory is recommended, but may also be useful in other scenarios.
DbContext instances can be pooled by calling AddPooledDbContextFactory. 
This pooling works the same way as for AddDbContextPool, and also has the same limitations.
Reset DbContext state
EF Core 5.0 introduces ChangeTracker.Clear() which clears the DbContext of all tracked entities.
This should usually not be needed when using the best practice of creating a new, short-lived context instance for each unit-of-work. 
However, if there is a need to reset the state of a DbContext instance, then using the new Clear() method is more performant and robust than mass-detaching all entities.
New pattern for store-generated defaults
EF Core allows an explicit value to be set for a column that may also have default value constraints.
EF Core uses the CLR default of type property type as a sentinel for this; if the value is not the CLR default, then it is inserted, otherwise, the database default is used.
This creates problems for types where the CLR default is not a good sentinel--most notably, bool properties. 
EF Core 5.0 now allows the backing field to be nullable for cases like this.
public class Blog
{
    private bool? _isValid;
​
    public bool IsValid
    {
        get => _isValid ?? false;
        set => _isValid = value;
    }
}
The backing field is nullable, but the publicly exposed property is not.
It allows the sentinel value to be null without impacting the public surface of the entity type. 
In this case, if the IsValid is never set, then the database default will be used since the backing field remains null. 
If either true or false are set, then this value is saved explicitly to the database.
Cosmos partition keys
EF Core allows the Cosmos partition key is included in the EF model.
modelBuilder.Entity<Customer>().HasPartitionKey(b => b.AlternateKey)
Starting with preview 7, the partition key is included in the entity type's PK and is used to improved performance in some queries.
Cosmos configuration
EF Core 5.0 improves the configuration of Cosmos and Cosmos connections.
Previously, EF Core required the end-point and key to be specified explicitly when connecting to a Cosmos database. 
EF Core 5.0 allows the use of a connection string instead. 
In addition, EF Core 5.0 allows the WebProxy instance to be explicitly set. 
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    => optionsBuilder
        .UseCosmos("my-cosmos-connection-string", "MyDb",
            cosmosOptionsBuilder =>
            {
                cosmosOptionsBuilder.WebProxy(myProxyInstance);
            });
Many other timeout values, limits, etc. can now also be configured.
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    => optionsBuilder
        .UseCosmos("my-cosmos-connection-string", "MyDb",
            cosmosOptionsBuilder =>
            {
                cosmosOptionsBuilder.LimitToEndpoint();
                cosmosOptionsBuilder.RequestTimeout(requestTimeout);
                cosmosOptionsBuilder.OpenTcpConnectionTimeout(timeout);
                cosmosOptionsBuilder.IdleTcpConnectionTimeout(timeout);
                cosmosOptionsBuilder.GatewayModeMaxConnectionLimit(connectionLimit);
                cosmosOptionsBuilder.MaxTcpConnectionsPerEndpoint(connectionLimit);
                cosmosOptionsBuilder.MaxRequestsPerTcpConnection(requestLimit);
            });
Finally, the default connection mode is now ConnectionMode.Gateway, which is generally more compatible.
Scaffold-DbContext now singularizes
Previously when scaffolding a DbContext from an existing database, EF Core will create entity type names that match the table names in the database. For example, tables People and Addresses resulted in entity types named People and Addresses.
In previous releases, this behavior was configurable through the registration of a pluralization service. Now in EF Core 5.0, the Humanizer package is used as a default pluralization service. This means tables People and Addresses will now be reverse engineered to entity types named Person and Address.
Savepoints
EF Core now supports savepoints for greater control over transactions that execute multiple operations.
Savepoints can be manually created, released, and rolled back.
context.Database.CreateSavepoint("MySavePoint");
In addition, EF Core will now roll back to the last savepoint when executing SaveChanges fails. This allows SaveChanges to be re-tried without re-trying the entire transaction.
Preview 8
Table-per-type (TPT) mapping
By default, EF Core maps an inheritance hierarchy of .NET types to a single database table. This is known as table-per-hierarchy (TPH) mapping. EF Core 5.0 also allows mapping each .NET type in an inheritance hierarchy to a different database table; known as table-per-type (TPT) mapping.
For example, consider this model with a mapped hierarchy.
public class Animal
{
    public int Id { get; set; }
    public string Species { get; set; }
}
​
public class Pet : Animal
{
    public string Name { get; set; }
}
​
public class Cat : Pet
{
    public string EducationLevel { get; set; }
}
​
public class Dog : Pet
{
    public string FavoriteToy { get; set; }
}
By default, EF Core will map this to a single table.
CREATE TABLE [Animals] (
    [Id] int NOT NULL IDENTITY,
    [Species] nvarchar(max) NULL,
    [Discriminator] nvarchar(max) NOT NULL,
    [Name] nvarchar(max) NULL,
    [EdcuationLevel] nvarchar(max) NULL,
    [FavoriteToy] nvarchar(max) NULL,
    CONSTRAINT [PK_Animals] PRIMARY KEY ([Id])
);
However, mapping each entity type to a different table will instead result in one table per type.
CREATE TABLE [Animals] (
    [Id] int NOT NULL IDENTITY,
    [Species] nvarchar(max) NULL,
    CONSTRAINT [PK_Animals] PRIMARY KEY ([Id])
);
​
CREATE TABLE [Pets] (
    [Id] int NOT NULL,
    [Name] nvarchar(max) NULL,
    CONSTRAINT [PK_Pets] PRIMARY KEY ([Id]),
    CONSTRAINT [FK_Pets_Animals_Id] FOREIGN KEY ([Id]) REFERENCES [Animals] ([Id]) ON DELETE NO ACTION
);
​
CREATE TABLE [Cats] (
    [Id] int NOT NULL,
    [EdcuationLevel] nvarchar(max) NULL,
    CONSTRAINT [PK_Cats] PRIMARY KEY