fix(client): encode double-quoted identifiers in encodeWhereClause #3611
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.
Summary
Fix
encodeWhereClauseto encode double-quoted identifiers. This addresses TanStack/db#927.Problem
Query builders like
@tanstack/electric-db-collectiongenerate WHERE clauses (forsubset__where) with double-quoted identifiers:Quoting is a SQL best practice to handle reserved words and preserve case. However,
encodeWhereClausewas intentionally skipping quoted identifiers (line 258 tracks both'and"as ranges to skip), presumably assuming that if you quoted it, you meant it literally.This breaks
columnMapperfor any query builder that quotes identifiers - the column names never get transformed (e.g.,userId→user_id).Solution
Pre-process double-quoted identifiers before the existing logic runs:
This should be safe because in PostgreSQL, double quotes are exclusively for identifiers (column/table names), never string literals (which use single quotes). So any
"something"is a column name that should be encoded.The rest of the function continues to handle unquoted identifiers and skip single-quoted string literals as before.