feat: render the range expressions to their Postgres operators - #248
Merged
zachdaniel merged 2 commits intoAug 20, 2026
Conversation
This was referenced Aug 19, 2026
Contributor
|
🚀 Thank you for your contribution! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Contributor checklist
Part of ash-project/ash_postgres#821
Single commit, adds rendering clauses for: RangeAdjacent, RangeContains, RangeLower, RangeOverlaps, RangeUpper.
Note that RangeOverlaps uses
Ash.Range.intersects?/2Operands are typed rather than interpolated . This is because a plain fragment renders a range literal as an inspected
%Ash.Range{}instead of a parameter.Requires ash to release with recent merges to main and ash-project/ash#2877.
Tests will be a separate ash_postgres PR.