From c538afcc86e6a52f0d33e2f930e05209f9a1cd35 Mon Sep 17 00:00:00 2001 From: Shay Rojansky Date: Thu, 2 Jan 2025 13:51:01 -0500 Subject: [PATCH] Add link with more information on Contains perf Addresses https://github.com/dotnet/efcore/issues/32394#issuecomment-2567564097 --- .../core/what-is-new/ef-core-8.0/breaking-changes.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/entity-framework/core/what-is-new/ef-core-8.0/breaking-changes.md b/entity-framework/core/what-is-new/ef-core-8.0/breaking-changes.md index b6e2ad4559..9826b7b892 100644 --- a/entity-framework/core/what-is-new/ef-core-8.0/breaking-changes.md +++ b/entity-framework/core/what-is-new/ef-core-8.0/breaking-changes.md @@ -151,7 +151,9 @@ WHERE [b].[Name] IN ( ) ``` -However, after the release of EF 8 it turned out that while the new SQL is more efficient for most cases, it can be dramatically less efficient in a minority of cases, even causing query timeouts in some cases +However, after the release of EF 8 it turned out that while the new SQL is more efficient for most cases, it can be dramatically less efficient in a minority of cases, even causing query timeouts in some cases. + +Please see [this comment](https://github.com/dotnet/efcore/issues/32394#issuecomment-2266634632) for a summary of the change in EF 8, the partial mitigations provided in EF 9, and the plan going forward for EF 10. #### Mitigations