db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Klebanoff (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-84) Column aliasing could simplify queries
Date Fri, 03 Jun 2005 14:43:58 GMT
    [ http://issues.apache.org/jira/browse/DERBY-84?page=comments#action_67015 ] 

Jack Klebanoff commented on DERBY-84:

I think that this issue can be closed.

The Hibernate/Derby issue that Micah Spears referred to in his comment is different than this
Jira entry's issue. I believe that that issue was a Derby bug and that it has been fixed.

> Column aliasing could simplify queries
> --------------------------------------
>          Key: DERBY-84
>          URL: http://issues.apache.org/jira/browse/DERBY-84
>      Project: Derby
>         Type: New Feature
>   Components: SQL
>     Versions:
>     Reporter: Bob Gibson
>     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.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message