[DERBY-1624] use of direct column name rather than alias make aggregation fail (Hibernate depends on that)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.1.0, 10.1.3.1
• Fix Version/s: 10.3.1.4
• Component/s: SQL
• Assignee: Manish Khettry
• Reporter: Emmanuel Bernard
• Created: 01/Aug/06 18:00
• Updated: 21/Jan/11 17:49
• Resolved: 15/Mar/07 22:45

Description

Error: org.apache.derby.client.am.SqlException: Column 'MODEL0_.COL_0_0_' 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 CREATE or ALTER TABLE statement then 'MODEL0_.COL_0_0_' is not a column in the target table., SQL State: 42X04, Error Code: -1

for

select
model0_.balance as col_0_0_,
count as col_1_0_
from
account model0_
group by
model0_.balance
having
count > 1

Issue Links

• is related to: DERBY-681 Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses
• relates to: DERBY-3094 Grouping of expressions causes NullPointerException
• relates to: DERBY-681 Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses
• relates to: DERBY-2457 Use of column aliases in group by / having clauses can cause queries to fail