Known limitation of this release:
The use of the SSL protocol is restricted to TCP and Unix socket connections. Connections using named pipes and shared memory do not support SSL mode.
The following methods are available for use with EF Core in asynchronous command and connection operations:
Support for connections using Unix domain socket files was extended to include MySQL servers deployed on the Linux hosts in .NET Core scenarios. To specify a Unix domain socket connection, set the value of the
Serverconnection-string option to the path of the socket file and the
unix. For example:
IncludeSecurityAssertsconnection-string options are not appropriate for use by applications that target .NET Core and now return an error when used.
EF Core: Support for explicit loading was added. Explicit loading is an object-relational mapper (O/RM) pattern introduced in EF Core 1.1.0, which enables .NET developers to explicitly load related data from the database at a later time.
EF Core: Support for scaffolding a DbContext from multiple databases was added. With multiple databases (or schemas of tables) specified, the resulting entity classes are created within a single context.
EF Core CLI usage example:
dotnet ef dbcontext scaffold "connection-string" MySql.Data.EntityFrameworkCore --schema world --schema sakila
Package Manager Console (Visual Studio) usage example:
Scaffold-DbContext "connection-string" MySql.Data.EntityFrameworkCore -Schemas world,sakila
The following connection-string options are not currently supported for use by applications that target .NET Core and now return an error when used:
EF Core: Some methods in the
DbContextclass were not supported for use with asynchronous operations. (Bug #26448321, Bug #84814)
EF Core: When attempting to commit a transaction in which the
FirstOrDefaultAsyncmethod was called, the connector returned
System.InvalidOperationException: Connection must be valid and open to commit transactioninstead of committing the transaction. (Bug #26026972, Bug #86199)