[release/10.0] Fix complex collection within left join subquery#37239
Merged
roji merged 1 commit intodotnet:release/10.0from Nov 26, 2025
Merged
[release/10.0] Fix complex collection within left join subquery#37239roji merged 1 commit intodotnet:release/10.0from
roji merged 1 commit intodotnet:release/10.0from
Conversation
cincuranet
approved these changes
Nov 25, 2025
artl93
approved these changes
Nov 25, 2025
Member
artl93
left a comment
There was a problem hiding this comment.
New feature, customer reported - feature doesn't work, simple fix. Approved.
This was referenced Nov 26, 2025
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.
Backports #37238
Fixes #37205
Description
Complex JSON collection support was added for 10.0, including full querying capabilities. Unfortunately, a bug slipped into the implementation, where projecting an entity having a JSON collection out of a left join subquery causes the wrong SQL to get generated.
Customer impact
When a LINQ query meeting certain non-contrived conditions is executed, the SQL is incorrect and the query fails.
How found
Customer reported on 10.0.0
Regression
No.
Testing
Added.
Risk
Very low, one-line trivial targeted fix. Quirk added.