Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1000109274.1225413644324.JavaMail.jira@brutus>
Date: Thu, 30 Oct 2008 17:40:44 -0700 (PDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-3141) ResultSetMetaData reports extra
 column if "order by colname" used.
In-Reply-To: <4185422.1192840550747.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden resolved DERBY-3141.
-----------------------------------

    Resolution: Cannot Reproduce

Resolving this CNR. If we get a reproduction we can reopen it.


> 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.