Add EF Core 11 query improvements community article - #26211
Merged
Merged
Conversation
Adds a new Community Article for 2026-09-27 covering EF Core 11 query translation improvements using a music “Wrapped” demo. The post documents FullJoin, GroupBy with MaxBy/MinBy, split-query join behavior, and edge-case verification with captured SQL and interceptor-based tests, along with supporting screenshots and diagrams.
Clarify the introduction and FullJoin background in the EF Core 11 query improvements article. The update makes the release-notes comparison more precise and removes an unnecessary preview-specific reference while keeping the focus on generated SQL and query behavior.
Contributor
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 64.4%, saving 2.9 MB.
|
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The article contains unresolved test, SQL-output, and reported-count inconsistencies.
Review effort: Lite
Findings: 1
Open (2)
What changed in this PR
Adds a community article demonstrating EF Core 11 query translation improvements with a SQL Server-backed music reporting sample.
Changes:
- Covers joins, grouping,
MaxBy/MinBy, aggregations, and split-query improvements. - Includes SQL output, tests, diagrams, screenshots, adoption guidance, and references.
| File | Description |
|---|---|
docs/en/Community-Articles/2026-09-27-ef-core-11-query-improvements/post.md |
New EF Core 11 query improvements article. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
|  | ||
|
|
||
| In the seeded dataset this returns 10 "dropped" artists, 22 "stayed loyal" and 10 "newly discovered". The UI above renders each bucket as its own single-artist carousel, backed by this one query. |
Comment on lines
+275
to
+288
| ### The generated SQL | ||
|
|
||
| Both compile to a `TOP(1) ... ORDER BY` query with the comparison key computed as a correlated subquery. No client evaluation is involved: | ||
|
|
||
| ```sql | ||
| DECLARE @p int = 1; | ||
| SELECT TOP(@p) [a].[Id], [a].[Country], [a].[Genre], [a].[Name] | ||
| FROM [Artists] AS [a] | ||
| ORDER BY ( | ||
| SELECT COUNT(*) | ||
| FROM [Tracks] AS [t] | ||
| INNER JOIN [PlayEvents] AS [p] ON [t].[Id] = [p].[TrackId] | ||
| WHERE [a].[Id] = [t].[ArtistId]) DESC | ||
| ``` |
Update the EF Core 11 query improvements article to reflect the final demo dataset and add concrete SQL examples for the MinByAsync/MaxByAsync query behavior. This also refreshes the article's home image to match the revised content.
ahmetcelik05
approved these changes
Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a community article that tests EF Core 11 query translation improvements against a real SQL Server database, using a music "year in review" report as the sample domain.
Covers:
Includes captured SQL for each query, app screenshots, data model and split-query diagrams, an adoption checklist and references.