[
https://issues.apache.org/jira/browse/CALCITE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939838#comment-17939838
]
Mihai Budiu commented on CALCITE-6933:
--------------------------------------
Unfortunately there is currently no API to manufacture a case-sensitive matcher
given a validator.
I will wait for a confirmation that this is a bug before I start working on
this.
> Quoted identifiers should be looked up using case sensitive matching
> --------------------------------------------------------------------
>
> Key: CALCITE-6933
> URL: https://issues.apache.org/jira/browse/CALCITE-6933
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.39.0
> Reporter: Mihai Budiu
> Priority: Minor
>
> Consider the following example:
> {code:sql}
> CREATE TABLE "T" (COL1 INT NOT NULL);
> CREATE TABLE "t" (COL1 INT NOT NULL, COL2 DOUBLE NOT NULL);
> CREATE VIEW V AS SELECT COL1, rlike(COL2, 'asf') FROM "t";
> {code}
> There are two tables with the same name, but different casing. I believe that
> the lookup in the schema should use case-sensitive lookup when the looked-up
> identifier is quoted. (This example used to work, but fails after we have
> merged the fix to https://issues.apache.org/jira/browse/CALCITE-6728).
> I am assuming this is a bug, but perhaps my understanding is wrong.
> Today the IdentifierNamespace.resolveImpl uses a nameMatcher whose case
> sensitivity is fixed by the configuration, but I think it should take into
> consideration the quoting as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
