You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2016/07/06 05:36:10 UTC
[jira] [Resolved] (CALCITE-319) Table aliases should follow
case-sensitivity policy
[ https://issues.apache.org/jira/browse/CALCITE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Hyde resolved CALCITE-319.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/54d29dc1.
> Table aliases should follow case-sensitivity policy
> ---------------------------------------------------
>
> Key: CALCITE-319
> URL: https://issues.apache.org/jira/browse/CALCITE-319
> Project: Calcite
> Issue Type: Test
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Fix For: 1.9.0
>
>
> Table aliases should follow case-sensitivity policy. For example,
> {code:sql}
> SELECT * FROM dept "d", dept "D"
> {code}
> should be allowed if identifiers are case-sensitive, should give error if identifiers are case-insensitive. Currently it is allowed under all policies, and that is wrong.
> See unit test in SqlValidatorTest.testCaseSensitive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)