[
https://issues.apache.org/jira/browse/DERBY-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596538#action_12596538
]
Dag H. Wanvik commented on DERBY-2457:
--------------------------------------
Extra tests are good, thanks Bryan!
WHERE clauses cannot reference the select list column aliases either, AFAICT,
so it might be good
to add tests for that, too, if it is not already done somewhere.
Bryan> Would "won't fix" be more appropriate?
I tend to agree; since this issue is not a misunderstanding, to some this
would be an "improvement" (it is not marked as a bug);
we are merely deciding that we don't want to do it,
in this case because it is not standard compliant as far as we can tell.
Andrew> Should we also then resolve DERBY-84 as invalid (or won't fix)? It's
essentially the same issue.
+1
> Use of column aliases in group by / having clauses can cause queries to fail
> ----------------------------------------------------------------------------
>
> Key: DERBY-2457
> URL: https://issues.apache.org/jira/browse/DERBY-2457
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.3.1.4
> Reporter: Andrew McIntyre
> Assignee: Bryan Pendleton
> Priority: Minor
> Attachments: 1624_repro.sql, additionalTests.diff
>
>
> Some use of column aliases in group by / having clauses can cause queries to
> fail with error 42X04. The queries can sometimes be made to work by also
> aliasing the table or rewriting the query to use a subselect. Attached is a
> simple sql script which reproduces the issue, originally found as part of
> DERBY-1624.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
