You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bernd Ruehlicke (JIRA)" <de...@db.apache.org> on 2005/03/25 00:27:20 UTC
[jira] Updated: (DERBY-147) ERROR 42X79 not consistant ? - same column name specified twice
[ http://issues.apache.org/jira/browse/DERBY-147?page=history ]
Bernd Ruehlicke updated DERBY-147:
----------------------------------
Attachment: derby-147.diff
Fixes made from TRUNK revision 158945 (Not for 10.0.2.1 release !!) Fixes applied to java/engine/org/apache/derby/impl/sql/compile/ResultColumnList.java
ALL test have been run (derbyall) successfull after this.
No new tests have been added to the harness - Satheesh I hope you can teach me ;-) - I.e. in case you add a test - tell me which and where so I can see howto.
Else I have not understood how to submit a patch to the trunk - I tried different options with svn but do not understand - would be nice with a workflow
1) How to check out a file - I got that
2) How to change a file - I got that
3) How to commit it back to the trunk - No idea how - or do you need to be "committer" for that ?
> 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
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira