Julian Hyde created CALCITE-1549:
------------------------------------
Summary: Improve error message when table 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
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)