Smit Patel

https://docs.microsoft.com/en-us/ef/core/querying/client-eval#potential-memory-leak-in-client-evaluation

Also mention somewhere that EF Core 5.0 is netstandard2.1 only

We need to do this in this release. Earlier the better as it would be breaking change.

I wonder if we should just convert to `OrderBy(e => e)` in pre-translation phase.

May be we should let users do that through interceptors. :trollface:

This API is in .NET 7 only and we are still on net6.0 tfm

This issue is lacking enough information for us to effectively reproduce. Please post a runnable project/solution or complete code listing that demonstrates the behavior you are seeing.

This stems from a different code path. Suppose your owned entities are mapped to a different table then delete should be fine. But currently it would fail because we check...

Fixed in #29023

@sir-boformer - nullable owned entities are covered by #9005 If you map them to different table then they can work.