Skip to content

Document parameterized collection translation as breaking change in EF Core 10 #5224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roji merged 4 commits into from
Jan 13, 2026
Merged

Document parameterized collection translation as breaking change in EF Core 10 #5224

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
308c0de
Initial plan
Copilot Jan 6, 2026
4afee8c
Add note about potential performance impact for parameterized collect…
Copilot Jan 6, 2026
354e4ae
Improve readability of performance impact note with multiple paragraphs
Copilot Jan 6, 2026
5a33a49
Add comma for better readability in performance note
Copilot Jan 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,6 +227,13 @@ The new default translation provides the query planner with cardinality informat

However, different workloads may benefit from different translation strategies depending on collection sizes, query patterns, and database characteristics.

> [!NOTE]
> While the new default translation will not cause any behavioral change or performance regression in the majority of cases, the change in how queries are translated to SQL may have adverse consequences in some scenarios.
>
> Applications that were built with EF Core 8 or 9, and rely on the performance characteristics of the JSON array parameter translation (using `OPENJSON` or similar database-specific functions) may experience performance differences when upgrading to EF Core 10. This is especially relevant for queries with large collections or specific query patterns that benefited from the previous translation strategy.
>
> If you experience performance regressions after upgrading, consider using the mitigation strategies below to revert to the previous behavior globally or for specific queries.

#### Mitigations

If you encounter issues with the new default behavior (such as performance regressions), you can configure the translation mode globally:
Expand Down