You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem
When running a query with a compound filter like _and that includes a relation (i.e. filtering on a related type) it panics with this call stack:
## Relevant issue(s)
Resolves#1808
## Description
Any time a filter with `_and` or `_or` operator that includes relations
is applied it will fail.
There were 2 problems:
- filter is not recursively analysed during mapping phase which would
result in some relational fields not being mapped and later panic upon
attempt to access them.
- the filter is not properly split between the scan and select nodes. It
would just analyse and split top-level fields.
These problems are fixed.
## Relevant issue(s)
Resolvessourcenetwork#1808
## Description
Any time a filter with `_and` or `_or` operator that includes relations
is applied it will fail.
There were 2 problems:
- filter is not recursively analysed during mapping phase which would
result in some relational fields not being mapped and later panic upon
attempt to access them.
- the filter is not properly split between the scan and select nodes. It
would just analyse and split top-level fields.
These problems are fixed.
Describe the problem
When running a query with a compound filter like
_and
that includes a relation (i.e. filtering on a related type) it panics with this call stack:To Reproduce
TestQueryFromSingleSideWithEqFilterOnRelatedType
testExpected behavior
It should not panic and return the same result as the test with the original query.
Platform
mac
The text was updated successfully, but these errors were encountered: