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 2017/01/13 19:30:26 UTC

[jira] [Resolved] (CALCITE-1549) Improve error message when table or column not found

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

Julian Hyde resolved CALCITE-1549.
----------------------------------
    Resolution: Fixed

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

New errors include:
* Object 'SALEX' not found (usually for schemas)
* Object 'SALES' not found; did you mean 'Sales'? (if you got the case of a schema wrong)
* Object 'EMPX' not found in 'SALES' (if you got a table wrong, or possibly a sub-schema)
* Object 'EMP' not found in 'SALES'; did you mean 'Emp'? (if you got the case of a table wrong)
* Table 'E' not found (if you got a table alias wrong)
* Column 'SALX' not found in table 'EMP' (if you got a column wrong)
* Column 'SAL' not found in table 'EMP'; did you mean 'Sal' (if you got the case of a column wrong)

We switch terminology from 'table' to 'object' because we're not sure whether you intended a table, view, schema or something else.

> Improve error message when table or column not found
> ----------------------------------------------------
>
>                 Key: CALCITE-1549
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1549
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>             Fix For: 1.12.0
>
>
> When a table is not found in a query, the current message makes it difficult to tell among several possibilities: the schema was incorrect, the schema was correct but had wrong case, the table was incorrect, the table was correct but had wrong case. Given a query, say
> {code}
> select * from schema1.table1, schema2.table2, table3
> {code}
> we should give an error that discriminates between those possibilities for "schema1.table1", and also for "table3" looking in the default schema.



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