[release/10.0] Fix primitive/complex collection handling on subtypes #37488
+66
−0
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.
Fixes #37478
Simplified/targeted backport of: #37482
Description
As part of the JSON complex type work in 10.0, the navigation expansion logic for binding properties/navigations changed; unfortunately, a bug slipped in where we no longer properly take into account inheritance subtypes.
Customer impact
Queries which perform subqueries over primitive collection properties on an inheritance subtype in EF queries now fail:
This isn't an uncommon scenario, and there's unfortunately no good workaround.
How found
Customer reported on EF 10.0.0.
Regression
Yes.
Testing
Test added.
Risk
Very low. The fix is very targeted and in code modified in 10.0, quirk added.