[
https://issues.apache.org/jira/browse/DERBY-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden closed DERBY-364.
--------------------------------
Resolution: Invalid
The original error was because a reserved word was encountered, not because it
was a VTI. If we want to improve the message when a reserved word is
encountered we should open a separate issue for that.
> Provide a more helpful message when the incorrect column name is given in a
> SELECT statement for a VTI
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-364
> URL: https://issues.apache.org/jira/browse/DERBY-364
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0
> Reporter: David Van Couvering
> Priority: Trivial
>
> If you specify a column name incorrectly in a SELECT statement from a VTI,
> you get a fairly unhelpful error message
> ij> SELECT SQLSTATE FROM new org.apache.derby.diag.ErrorMessages() vti;
> ERROR 42X01: Syntax error: Encountered "SQLSTATE" at line 1, column 8.
> ij> SELECT SQL_STATE FROM new org.apache.derby.diag.ErrorMessages() vti;
> -- list of SQL States returned --
> If you do the same thing from a regular table, the error message is much more
> clear:
> ij> create table foo(id integer);
> 0 rows inserted/updated/deleted
> ij> select ixd from foo;
> ERROR 42X04: Column 'IXD' is either not in any table in the FROM list or
> appears
> within a join specification and is outside the scope of the join
> specification
> or appears in a HAVING clause and is not in the GROUP BY list. If this is a
> CREA
> TE or ALTER TABLE statement then 'IXD' is not a column in the target table.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
