Query: SubQueryMemberPushdown doesn't work for chained navigation properties #8526
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
punted-for-2.0
type-bug
Milestone
SubQueryMemberPushdown optimization can only optimize one member per pass. We should consider making it work for more complex scenarios with multiple properties chained off one another.
example:
initial QM:
after first pushdown:
after nav rewite:
after second pushdown:
This query ends up throwning NRE - we should be able to fully translate it though, push all the members inside the selector and only then run nav rewrite
The text was updated successfully, but these errors were encountered: