You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f98235d
Browse filesBrowse the repository at this point in the historyBrowse files
fix: read Databricks and DuckDB strings with their own escape rules (#1502)
SQLBuild's lexical rules gave Databricks and DuckDB one shared entry
with no backslash escapes, no raw strings and flat block comments.
SQLQuack and both adapters read them differently: Databricks honours a
backslash in '...' and "..." outside r'...' raw strings, DuckDB honours
it inside E'...', and both nest block comments.
The expression-macro dedent in sqb format reads the formatted body with
these rules. A multi-line string after a backslash-escaped quote looked
closed early, so its next line lost two spaces on every run and the
string's value changed.
Databricks now has its own entry, and DuckDB uses the PostgreSQL rules
its adapter already declares. The same rules decide quoted text for
semantic-validation normalisation, fast lineage, dynamic pivot, SQL
tree nodes and query-facts shapes.
0 commit comments