Enhance functions for operator-free environments like Supabase #103
Conversation
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
…wrap the ordered column
auxesis
changed the title
calvinbrewer
approved these changes
May 9, 2025
tobyhede
added a commit
that referenced
this pull request
Oct 27, 2025
Enhance functions for operator-free environments like Supabase
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
EQL documentation for working with Supabase without operators.
Couple of small quality of life changes to functions that emerged while documenting:
order_byfunction that wraps the ore index term function for better DX.matchtolike, to reflect the actual PostgreSQL usage.