EF Core 5.0.1

This is a patch release of EF Core 5.0 containing only important bug fixes.

EF Core 5.0.1

• Query
  • Properly generate expression to read provider-specific types from BufferedDataReader
  • Owned collection when owner has composite PK throws translation failure
  • ArgumentOutOfRangeException for split query with owned types
  • Incorrect SQL generated when applying group by over a group by
  • KeyNotFoundException when adding a single projection
  • Incorrect result when doing owner + Include collection + split query + owned type mapped to different table + single
  • InvalidCastException on entities referencing Owned types containing NetTopologySuite Point properties
  • Exception when using inheritance with owned properties in the in-memory database
  • Ternary operator with DateTimes in select gives ArgumentException
  • Object reference not set to an instance of an object exception when using NET Topology Suite in Select projection
  • Provider specific plugin method translator never gets called for indexer property
• Model building
  • Mapping exception with property called FooId on base type Foo in TPT
  • Foreign keys are removed from owned tables when excludedFromMigrations set to true
  • Exception in TPT models with default values
  • Default schema has no effect on views in EF Core 5.0
  • The entity type is part of a relationship cycle involving its primary key
  • StackOverflowException when using same collection navigation twice
  • StackOverflowException with EFCore 5 many-to-many mapping using many-to-one via self
• DbContext
  • Events aren't reset when pooled context is reset asynchronously
• Scaffolding
  • The string argument 'name' cannot be empty when scaffolding a SQLite database
  • System.ArgumentException: The collection argument 'propertyNames' must contain at least one element
  • Collations aren't scaffolded correctly
• SaveChanges
  • SaveChanges fails for SQL Server because of savepoints are not supported when MultipleActiveResultSets is enabled
• Migrations
  • SQL generated for migrations is incorrect when DbContext has TVF mapped using DbFunctionAttribute
  • SQLite Spatial Migrations: Columns with Z and M created incorrectly

Microsoft.Data.Sqlite 5.0.1

• Starting with Microsoft.Data.Sqlite.Core 5.0.0 it is no longer possible to set cipher key options