[
https://issues.apache.org/jira/browse/CALCITE-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608443#comment-17608443
]
Julian Hyde commented on CALCITE-5291:
--------------------------------------
BigQuery has peculiar rules about case-sensitivity. Per [this
table|https://cloud.google.com/bigquery/docs/reference/standard-sql/lexical#case_sensitivity],
keywords, built-in functions, column names and aliases are case-insensitive,
but dataset and table names are case-sensitive unless the
{{is_case_insensitive}} option is set to TRUE.
(I presume that by 'aliases' they mean both table and column aliases, e.g. 'e'
and 'x' in 'select e.deptno as x from emp as e group by x'.)
Calcite cannot currently support a hybrid scheme where columns and alias are
case-insensitive and tables are case-sensitive. Unless and until that support
is added, case-insensitive seems the best approximation. [~tjbanghart], I you
agree with this, I'll add a note to {{testCalciteCaseJoinBigQuery}} and then
merge to main.
> Make BigQuery lexical policy case insensitive
> ---------------------------------------------
>
> Key: CALCITE-5291
> URL: https://issues.apache.org/jira/browse/CALCITE-5291
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.26.0, 1.27.0, 1.28.0, 1.30.0, 1.31.0, 1.32.0
> Reporter: TJ Banghart
> Assignee: TJ Banghart
> Priority: Trivial
>
> [c1052b34|https://github.com/apache/calcite/commit/c1052b343724c4a95bcf25419b70bc6032e0846b]
> introduced a {{BIG_QUERY}} lexical policy which set {{caseSensitive}} to
> {{{}true{}}}. This should be {{false}} as BigQuery is not case-sensitive:
> [https://cloud.google.com/bigquery/docs/reference/standard-sql/lexical#case_sensitivity]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
