db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3141) ResultSetMetaData reports extra column if "order by colname" used.
Date Thu, 30 Oct 2008 23:38:44 GMT

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

Kathey Marsden commented on DERBY-3141:

Do you have a test program that reproduces this problem?  If not we should probably resolve
it CannotReproduce.

> 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