db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: [jira] Commented: (DERBY-147) ERROR 42X79 not consistant ? - same column name specified twice
Date Mon, 28 Mar 2005 19:14:01 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I will work to get this into 10.1 release. Patch may have to be changed
to address some issues raised by Jack.<br>
<br>
Satheesh<br>
<br>
Bernd Ruehlicke (JIRA) wrote:
<blockquote
 cite="mid1915566671.1112029457391.JavaMail.jira@ajax.apache.org"
 type="cite">
  <pre wrap="">     [ <a class="moz-txt-link-freetext" href="http://issues.apache.org/jira/browse/DERBY-147?page=comments#action_61646">http://issues.apache.org/jira/browse/DERBY-147?page=comments#action_61646</a>
]
     
Bernd Ruehlicke commented on DERBY-147:
---------------------------------------

So - how do I make sure this stuff makes it into the 10.1 release ?

  </pre>
  <blockquote type="cite">
    <pre wrap="">ERROR 42X79 not consistant ? - same column name specified twice
---------------------------------------------------------------

         Key: DERBY-147
         URL: <a class="moz-txt-link-freetext" href="http://issues.apache.org/jira/browse/DERBY-147">http://issues.apache.org/jira/browse/DERBY-147</a>
     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&gt;
ij version 10.0 
CONNECTION0* - 	jdbc:derby:phsDB 
* = current connection 
ij&gt; 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&gt; 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&gt; 
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.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>


Mime
View raw message