db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-147) ERROR 42X79 not consistant ? - same column name specified twice
Date Fri, 21 Jul 2006 13:56:16 GMT
    [ http://issues.apache.org/jira/browse/DERBY-147?page=comments#action_12422647 ] 
            
Kathey Marsden commented on DERBY-147:
--------------------------------------

Hi  Bernd,

When you resubmit your patch,  please 
1) Assign yourself
2) Mark the patch available checkbox.  (which probably didn't exist when you originally submitted
your patch)
3)  Ping the list if you don't get a response after a week.

I thought we were doing bad with a 3 and 4 month turnaround  on independent contributor patches
but at *16 months*, this one certainly takes the prize.
There has been discussion about mailing the patch list to the developer list and being more
attentive to patches and hopefully we will get that under control, but  meanwhile there is
a lot you can do streamline your  own patch and drive it to commit.  Please take a look at:
http://wiki.apache.org/db-derby/PatchAdvice

Thanks for all your patience.

Kathey


> ERROR 42X79 not consistant ? - same column name specified twice
> ---------------------------------------------------------------
>
>                 Key: DERBY-147
>                 URL: http://issues.apache.org/jira/browse/DERBY-147
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Bernd Ruehlicke
>         Attachments: derby-147-10.0.2.1.diff, derby-147.diff
>
>
> This happens from JDBC or ij. Here the output form ij>
> ij version 10.0 
> CONNECTION0* - 	jdbc:derby:phsDB 
> * = current connection 
> ij> select a1.XXX_foreign, a1.native, a1.kind, a1.XXX_foreign FROM slg_name_lookup
a1 ORDER BY a1.XXX_foreign;
> ERROR 42X79: Column name 'XXX_FOREIGN' appears more than once in the result of the query
expression. 
> But when removing the ORDER BY and keeping the 2 same column names it works
> ij> select a1.XXX_foreign, a1.native, a1.kind, a1.XXX_foreign FROM slg_name_lookup
a1;
> XXX_FOREIGN                                                                     |NATIVE
                                                                         |KIND           
                        |XXX_FOREIGN                                                     
                -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
> 0 rows selected 
> ij> 
> So - it seams to be OK to specify the same column twice - as long as you do not add the
ORDER BY clause.  
> I woul dof course like that the system allows this - but at leats it should be consistant
and either allow both or none of the two queries above.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message