Analyze sql to postgrest conversion code#3
Draft
xcono wants to merge 1 commit into
Draft
Conversation
Co-authored-by: reg <reg@xcono.com>
|
Cursor Agent can help with this pull request. Just |
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.
Add PostgREST compatibility analysis and recommendations to align our Go builder with PostgREST expectations.
This document provides a detailed comparison between our Go builder's PostgREST URL to SQL conversion and the
sql-to-restTypeScript project's SQL to PostgREST parameter conversion. It identifies key compatibility gaps and offers concrete recommendations for improving features such as JOIN ON conditions, ORDER BY nulls policy, NOT operator support, regex/FTS operators, and aggregates, aiming to simplify and enhance compatibility for PostgREST clients.