Bump Microsoft.EntityFrameworkCore.InMemory from 3.1.7 to 6.0.3

[dependabot[bot]]

Bumps Microsoft.EntityFrameworkCore.InMemory from 3.1.7 to 6.0.3.

Release notes

Sourced from Microsoft.EntityFrameworkCore.InMemory's releases.

EF Core 6.0.3

This is a patch release of EF Core 6.0 containing only important bug fixes:

• FirstOrDefault after custom projection == null cannot be translated
• DbContext scaffolding creates reference error CS0120 in nameof() for InverseProperty in certain conditions
• EF core 6 selecting null values despite where clause asking for not null
• Query: Rownumber conversion needs better logic to figure out partitions
• Suboptimal SQL generation for query with optional navigation, its collection navigation and lateral join
• Aggregates on multiple child tables produces invalid SQL
• ServiceProviderCache keeps initially created IServiceProvider indefinitely
• Setting a Nullable Foreign Key property to Null triggers cascade delete
• Optimize hangs and stops responding

EF Core 6.0.2

This is a patch release of EF Core 6.0 containing only important bug fixes:

• Exception when creating new migration after updating from 6.0-rc.1 to 6.0-rc.2 or 6.0-rtm
• efcore6 produces wrong SELECT SQL when Where/OrderBy clauses are applied to Owned properties followed by .Take
• Proxies using Records with a base class broken since .NET 6
• Parentheses put around IS NULL only if operand is of type boolean
• Self-referencing entity circular dependency happening just on EF Core 6.0
• Many To Many Exception when adding and removing same entity
• RelationalConnection.Close calls async function
• Circular dependency while creating tables with DatabaseFacade.EnsureCreated on EF Core 6
• EF Core Migration Bundles: no way to passthrough custom args to generated efbundle
• Did the naming convention change for HasCheckConstraint in v.6? Is this a breaking change?
• Generated JOIN for multiple MIN is wrong
• StackOverflowException in nested GroupBy query
• When trimming, queries fail because of missing System.Math
• GroupBy with outer reference not translating properly, causing data loss
• EF 6.0.0 and 6.0.1: sub-lists are no longer loaded

EF Core 6.0.1

This is a patch release of EF Core 6.0 containing only important bug fixes:

• DateTime with z suffix is not respected when reading entities
• 'The object has been removed from the model.' when building model
• EF Core 6.0 regression when using HasDefaultSchema() with ToTable(null)
• Variable names must be unique within a query batch or stored procedure
• Stack overflow when using circular composite key dependencies
• SqliteConnectionFactory.cs is not thread-safe
• EF Core 6.0 InvalidOperationException: The object has been removed from the model
• Subquery.Contains throws when the type of item is value type
• Query with n:m relation adds non-existent column
• InvalidOperationException "sequence contains no matching element" in TableReferenceExpression.get_Table
• Update from 5.0.1 to 6.0breaks all SqliteConnection
• Scaffolder throws error if junction table foreign key columns have identical names
• EFCore 6 - NullReferenceException upon EnsureDeleted
• Non-nullable value comparer can't be applied on nullable type
• Exception in SQL server query in EF Core 6, looks related to HasQueryFilter(), worked in EF Core 5

... (truncated)

Commits

• 0257e5c [internal/release/6.0] Update dependencies from dnceng/internal/dotnet-runtime
• 348a3ca [internal/release/6.0] Update dependencies from dnceng/internal/dotnet-runtime
• e803be5 [internal/release/6.0] Update dependencies from dnceng/internal/dotnet-runtime
• a0ff4dc Merge in 'release/6.0' changes
• baeae44 Merge branch 'release/5.0' into release/6.0
• ba7ac92 [internal/release/6.0] Update dependencies from dnceng/internal/dotnet-runtime
• 6cdd55d [internal/release/6.0] Update dependencies from dnceng/internal/dotnet-runtime
• 8e1b7dc [internal/release/6.0] Update dependencies from dnceng/internal/dotnet-runtime
• 941b6a2 [internal/release/6.0] Update dependencies from dnceng/internal/dotnet-runtime
• c35ea78 [internal/release/6.0] Update dependencies from dnceng/internal/dotnet-runtime
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #285.