Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <758820750.1210697755864.JavaMail.jira@brutus>
Date: Tue, 13 May 2008 09:55:55 -0700 (PDT)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-2457) Use of column aliases in group by /
 having clauses can cause queries to fail
In-Reply-To: <4170688.1173999609456.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton resolved DERBY-2457.
------------------------------------

    Resolution: Invalid

I committed the additional test cases to the trunk as revision 655947.

Since we believe that the current behavior of Derby is correct
according to the SQL Standard, I'm resolving the issue as invalid.
(Would "won't fix" be more appropriate?)

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