Remove query splitting when the includes fallback loads no collection - #1424
Merged
Merged
Conversation
#1422 removed a resolver's AsSplitQuery only when the projection could be built as a select. When it cannot, as for a type with derived types, ApplyProjection falls back to includes and left the split in place, so a connection over such a type that selected no collection still threw under Verify.EntityFramework 16. The includes come from the same projection, so the check now runs before either path.
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
1 participant
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.
Remove query splitting when the includes fallback loads no collection
#1422 removed a resolver's AsSplitQuery only when the projection could be
built as a select. When it cannot, as for a type with derived types,
ApplyProjection falls back to includes and left the split in place, so a
connection over such a type that selected no collection still threw under
Verify.EntityFramework 16. The includes come from the same projection, so the
check now runs before either path.