Re: [jira] Commented: (DERBY-147) ERROR 42X79 not consistant ? - same column name specified twice

[Satheesh Bandaram]

Great... A good starting point for patch making is: http://incubator.apache.org/derby/derby_comm.html Satheesh Bernd Ruehlicke (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-147?page=comments#action_59963 ] Bernd Ruehlicke commented on DERBY-147: --------------------------------------- I would like to make that patch. Give me some time to figure out the procedures how to submit such patch. Also I will need to make soem JUnit tests to see if this is actually working in all cases. B-) ERROR 42X79 not consistant ? - same column name specified twice --------------------------------------------------------------- Key: DERBY-147 URL: http://issues.apache.org/jira/browse/DERBY-147 Project: Derby Type: Bug Reporter: Bernd Ruehlicke 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.