Skip to content

fix(calcite): quote SQL identifiers with double quotes, as SQL tools generate them - #588

Open
dfa1 wants to merge 1 commit into
mainfrom
fix/sql-double-quote-identifiers
Open

dfa1 wants to merge 1 commit into
mainfrom
fix/sql-double-quote-identifiers

Conversation

@dfa1

@dfa1 dfa1 commented Oct 20, 2026

Copy link
Copy Markdown
Owner

IntelliJ's table editor opens a table with ORDER BY "date"; the connection only parsed back-ticks, so double-clicking ohlc failed. The connection now uses Calcite's DOUBLE_QUOTE quoting (case sensitivity unchanged), so getIdentifierQuoteString() reports ".

Breaking: back-ticked identifiers no longer parse; docs and tests moved to double quotes. Verified against the rebuilt -all jar: ORDER BY "date" DESC runs, date is a lexical error.

Tests: calcite 206, jdbc-driver 19, CalciteInteropIntegrationTest 55 (vortex-jni cross-check) pass.

🤖 Generated with Claude Code

…generate them

IntelliJ opens a table with ORDER BY "date" (it quotes a reserved-word column
with the standard double quote), which a back-tick-only connection could not
parse. getIdentifierQuoteString now reports the quote the parser accepts.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@dfa1
dfa1 force-pushed the fix/sql-double-quote-identifiers branch from 4ca8059 to 9cc7d16 Compare October 20, 2026 20:14

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant