db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-765) Valid query fails with ERROR X0A00: The select list mentions column 'A' twice...
Date Mon, 28 May 2007 06:53:15 GMT

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

Myrna van Lunteren resolved DERBY-765.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.2.2.0
         Assignee: Rick Hillegas
       Derby Info: [Existing Application Impact, Regression, Release Note Needed]  (was: [Regression,
Release Note Needed, Existing Application Impact])

I am closing this issue as being resolved with 10.2.2.0 (could be 10.2.1.6).
>From the comments, it appears this was specifically entered to get a release note.
Also from the comments, it appears the actual bug was DERBY-681, which has been fixed (in
10.3-trunk).
I'm assigning it to Rick, as he's the one who added the release note comment.

> Valid query fails with ERROR X0A00: The select list mentions column 'A' twice...
> --------------------------------------------------------------------------------
>
>                 Key: DERBY-765
>                 URL: https://issues.apache.org/jira/browse/DERBY-765
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.2.1.6
>            Reporter: Kathey Marsden
>            Assignee: Rick Hillegas
>            Priority: Minor
>             Fix For: 10.2.2.0
>
>
> The following query is valid but fails with 10.2 
> ij> create table bug280
> (
>    a int,
>    b int
> );
> 0 rows inserted/updated/deleted
> ij> insert into bug280( a, b )
> values ( 1, 1 ), ( 1, 2 ), ( 1, 3 ), ( 2, 1 ), ( 2, 2 );
> 5 rows inserted/updated/deleted
> ij> select a+1 as a, a+1 as a from bug280 group by a;
> ERROR X0A00: The select list mentions column 'A' twice. This is not allowed in queries
with GROUP BY or HAVING clauses. Try aliasing one of the conflicting columns to a unique name.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message