db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-84) Column aliasing could simplify queries
Date Tue, 13 May 2008 22:37:55 GMT

    [ https://issues.apache.org/jira/browse/DERBY-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596553#action_12596553

Bryan Pendleton commented on DERBY-84:

I intend to add a few more tests to the test suite, to demonstrate the
current handling of column aliases in WHERE clauses, and then to
resolve this issue as "won't fix". 

See the discussion in DERBY-2457 for some additional comments
regarding the reasoning behind this proposal.

> Column aliasing could simplify queries
> --------------------------------------
>                 Key: DERBY-84
>                 URL: https://issues.apache.org/jira/browse/DERBY-84
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions:
>            Reporter: Bob Gibson
>            Assignee: Bryan Pendleton
>            Priority: Minor
> Currently, one can not use an alias to simplify queries.  For example, being able to
alias "LongDescriptiveColumnName" AS LDCN would allow one to use the alias elsewhere in the
query, e.g., the WHERE clause:
> SELECT LongDescriptiveColumnName AS LDCN FROM MyTable WHERE LDCN LIKE '%testing%';
> The current result is a message like:
> ERROR 42X04: Column 'LDCN' is not in any table in the FROM list or it appears within
a join specification and is outside the scope of the join specification or it appears in a
HAVING clause and is not in the GROUP BY list.  If this is a CREATE or ALTER TABLE statement
then 'LDCN' 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.

View raw message