You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2008/05/08 01:51:56 UTC

[jira] Commented: (DERBY-2457) Use of column aliases in group by / having clauses can cause queries to fail

    [ https://issues.apache.org/jira/browse/DERBY-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595094#action_12595094 ] 

Bryan Pendleton commented on DERBY-2457:
----------------------------------------

It appears that, while ORDER BY items are bound to the select's
result column list, GROUP BY and HAVING items are bound to
the select's "from list". 

So one approach might be to change GroupByColumn.bindExpression
and similar places to be more like OrderByColumn.bindOrderByColumn;
that is, to bind against the select RCL, rather than against the from list.


> 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
>
>
> 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.