[DERBY-84] Column aliasing could simplify queries

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 10.0.2.0
• Component/s: SQL
• Assignee: Bryan Pendleton
• Reporter: Bob Gibson
• Created: 28/Nov/04 15:25
• Updated: 21/Jan/11 17:48
• Resolved: 16/May/08 19:25

Description

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.

Issue Links

• is duplicated by: DERBY-3066 WHERE clause not accepted on derived expression columns
• relates to: DERBY-2457 Use of column aliases in group by / having clauses can cause queries to fail
• relates to: DERBY-3066 WHERE clause not accepted on derived expression columns