feat(electric-db-collection): support nested property references in SQL queries#1514
Open
miguelrk wants to merge 1 commit intoTanStack:mainfrom
Open
Conversation
…QL queries - Implemented support for nested property references in WHERE and ORDER BY clauses by compiling to PostgreSQL JSON operators. - Added new utility functions for escaping and quoting SQL string literals. - Updated tests to cover various scenarios for nested JSON/jsonb references.
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
1 participant
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.
🎯 Changes
Extends
@tanstack/electric-db-collectionSQL compilation so multi-segment IR (intermediate representation) refs (nested property paths) work inWHEREandORDER BYinstead of throwing. Paths compile to PostgreSQL JSON / jsonb operators (->for intermediate keys,->>for the final key so the compared value is text).Scope / limitations: nested paths assume JSON / jsonb extraction from a single root column; if the physical column isn’t JSON / jsonb, SQL may fail at runtime.
✅ Checklist
pnpm test.🚀 Release Impact