[jira] [Resolved] (CALCITE-1563) In case-insensitive connection, non-existent tables use alphabetically preceding table

["Julian Hyde (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CALCITE-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-1563.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.12.0

Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/40e5b884.

> In case-insensitive connection, non-existent tables use alphabetically preceding table
> --------------------------------------------------------------------------------------
>
>                 Key: CALCITE-1563
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1563
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>             Fix For: 1.12.0
>
>
> In case-insensitive connection, non-existent tables use alphabetically preceding table. For example, in JdbcTest, the following test passes
> {code}
>   @Test public void testLexCaseInsensitiveFindsNonExistentTable() {
>     final CalciteAssert.AssertThat with =
>         CalciteAssert.that().with(Lex.MYSQL);
>     with.query("select COUNT(*) as c from `metaData`.`zoo`")
>         .returns("c=2\n");
>   }
> {code}
> even though there is no table called "zoo", because it finds the "tables" table instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)