db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3141) ResultSetMetaData reports extra column if "order by colname" used.
Date Sat, 20 Oct 2007 00:59:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536386

Bryan Pendleton commented on DERBY-3141:

I thought I saw this myself a couple times, but when I tried to write
a test program to reproduce this problem, it seemed to start working again.

Do you have a test program which reproduces the problem? If so, can you 
attach it?  That would be very helpful, thanks.

> ResultSetMetaData reports extra column if "order by colname" used.
> ------------------------------------------------------------------
>                 Key: DERBY-3141
>                 URL: https://issues.apache.org/jira/browse/DERBY-3141
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions:
>         Environment: Windows, JRE 1.5, Network Server/Client
>            Reporter: Ali Demir
>            Priority: Minor
> for a query like: 
> select col1 from table1 where col1=? order by id
> Derby network server returns ResultSetMetaData that contains 2 columns: col1, id, where
as it should return only col1.
> It works correctly (returns only col1) if query does not have order by:
> select col1 from table1 where col1=?
> It seems that to get the "order by" working, Derby silently appends id column to the
select projection but forgets to remove it from ResultSetMetaData.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message