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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/10/31 00:38:44 UTC
[jira] Commented: (DERBY-3141) ResultSetMetaData reports extra
column if "order by colname" used.
[ 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: 10.3.1.4
> 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.