when filtering related collection need to include nested fields in comparison #171
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.
This comes up when filtering on a nested field in a related collection. For example, where there is a relation from
comments
tomovie
:In this example no records are returned because
imdb.rating
is not in scope when during filtering where thatwhere
predicate is applied.We already have logic in place to include columns in joins if they are needed for an expression. But that logic did not account for nested fields. This PR updates the query planner to recursively include nested fields as needed if they are used in expressions.