[
https://issues.apache.org/jira/browse/DERBY-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew McIntyre resolved DERBY-1624.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Assignee: Manish Khettry
Fixed by changes committed for DERBY-681. Will open a new issue for the column
aliasing issues remaining in the repro script attached to this issue.
> use of direct column name rather than alias make aggregation fail (Hibernate
> depends on that)
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-1624
> URL: https://issues.apache.org/jira/browse/DERBY-1624
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.1.1.0, 10.1.3.1
> Reporter: Emmanuel Bernard
> Assigned To: Manish Khettry
> Fix For: 10.3.0.0
>
> Attachments: 1624_repro.sql
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
