-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More complete support for Pure queries in the Rel transpiler #2622
More complete support for Pure queries in the Rel transpiler #2622
Conversation
…to Rel, better logging, and refactoring.
I have merged |
This PR can be closed because it is superseded by PR#2702 which has now been merged. |
This PR can be closed because it is superseded by #2702. Apologies for the noise. |
This PR is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days. |
This PR was closed because it has been inactive for 35 days. Please re-open if this PR is still relevant. |
Various improvements to the Rel transpiler including:
match
functions which are now routed.in
operator.at
when used along a property path.match
functions are routed.What type of PR is this?
Improvement
What does this PR do / why is it needed ?
Support for more types of query by the Rel backend. This PR also improves the logging of errors when a Pure query is not supported by the Rel transpiler.
Does this PR introduce a user-facing change?
This PR is backwards compatible in the sense that existing queries will continue to be supported without any changes.