Experiment with supporting full-body query functions #4
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.
For now
cond
statements are supported, but it can uncleanly fail if there is unsupported construct in the query function body.Up to discussion:
case
s (with the constants as the match patters) as PostgreSQL supports such constructif
andunless
, but it will make them work slightly different from the Elixir one, as PostgreSQL is statically typed, so there is no way to simulate it for non-bool conditionThings needed to be done before merging:
Goal of this PR is to add support for more complex query functions, for example support conditionals like:
Which then can be used in the query just as you would expect: