[release/7.0] Query: Don't fail translation of aggregate when owned navigations #29243
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.
Resolves #29201
Description
Regression in a relatively important case where aggregate functions are used over owned type mapped to the same table as the owner. For example:
This was due to a significant change in the design for aggregate functions, enabling a lot of new functionality in EF7. We were missing test cases for this.
Customer impact
Exception in a relatively common query case that worked in EF Core 6.0.
How found
Found writing docs for new features.
Regression
Yes. from 6.0.
Testing
New testing added; will also investigate additional testing in this area.
Risk
Low, since the test removes an incorrect check when looking for errors.