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

Mike Matrigali updated DERBY-147:
---------------------------------

    Fix Version/s: 10.2.3.0

Rick merged this into the 10.2 branch with change 448966, not sure what version 
of 10.2 that was, so just marking it fixed in latest unreleased version of 10.2.

> ERROR 42X79 not consistant ? - same column name specified twice
> ---------------------------------------------------------------
>
>                 Key: DERBY-147
>                 URL: https://issues.apache.org/jira/browse/DERBY-147
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Bernd Ruehlicke
>            Assignee: Bryan Pendleton
>             Fix For: 10.2.3.0, 10.3.1.4
>
>         Attachments: derby-147-10.0.2.1.diff, derby-147.diff, 
> patch_with_tests.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.
-
You can reply to this email to add a comment to the issue online.

Reply via email to