[
https://issues.apache.org/jira/browse/CALCITE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-4847.
----------------------------------
Resolution: Fixed
Fixed in
[c2d0d66|https://github.com/apache/calcite/commit/c2d0d66722212f3cc674bcac26376195bfe6f1af].
> Parse SQL with BigQuery-style quoted identifiers and character literals
> -----------------------------------------------------------------------
>
> Key: CALCITE-4847
> URL: https://issues.apache.org/jira/browse/CALCITE-4847
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Priority: Major
> Fix For: 1.28.0
>
>
> Parse SQL with BigQuery-style quoted identifiers and character literals.
> BigQuery quotes identifiers using backticks, escaping interior backticks
> using backslash. In CALCITE-4767 we added {{Quoting.BACK_TICK_BACKSLASH}} to
> distinguish this style from what MySQL does, namely {{Quoting.BACK_TICK}}.
> BigQuery quotes character literals using double quotes, escaping interior
> double quotes using backslash. In CALCITE-4767 we added
> {{Quoting.DOUBLE_QUOTE_BACKSLASH}} to distinguish this style from
> {{Quoting.DOUBLE_QUOTE}}.
> After this change, we should be able to parse the following query if we
> invoke the parser with {{lex=BIG_QUERY}} or {{dialect=BIG_QUERY}}:
> {code}
> SELECT "a \"quoted\" char literal"
> FROM `a \`quoted\` table`
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
