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 "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2005/08/17 01:18:05 UTC
[jira] Updated: (DERBY-147) ERROR 42X79 not consistant ? - same column name specified twice
[ http://issues.apache.org/jira/browse/DERBY-147?page=all ]
Mike Matrigali updated DERBY-147:
---------------------------------
Component: SQL
Description:
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.
was:
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.
Environment:
> 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
> 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