[
https://issues.apache.org/jira/browse/DERBY-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-3997:
--------------------------------------
Attachment: d3997.stat
d3997.diff
Here's a patch with a fix and a test case. Both suites.All and derbyall ran
cleanly.
Thanks for the suggestion about * in the select list, Bryan. I tested that
manually, and I didn't find any problem.
ResultColumnList.removeOrderByColumns() should only remove columns that have
been added for the order by, and it should leave the original select list
intact. I haven't added any test case to ensure that elimination of the order
by clause doesn't remove columns that should have been in the result, as that
seems to be tested already.
> ORDER BY causes column to be returned
> -------------------------------------
>
> Key: DERBY-3997
> URL: https://issues.apache.org/jira/browse/DERBY-3997
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.4.1.3
> Environment: Mac OS 10.4, JDK 1,6
> Reporter: geoff hendrey
> Assignee: Knut Anders Hatlen
> Attachments: d3997.diff, d3997.stat
>
>
> The ORDER BY is causing the ordered column to be retrieved even though it is
> not part of the SELECT clause. Here is a script to create a table, insert a
> row, and perform the select:
> CREATE TABLE "REVIEWS"."GEOFF__REVIEWS__REVIEW"
> (
> PK INTEGER PRIMARY KEY not null,
> numstars BIGINT,
> body VARCHAR(32672),
> title VARCHAR(32672),
> authoremail VARCHAR(32672)
> );
> INSERT INTO "REVIEWS"."GEOFF__REVIEWS__REVIEW"
> (PK,numstars,body,title,authoremail) VALUES (0 /*not
> nullable*/,0,'s','s','s');
> SELECT "review"."numstars"
> FROM
> "GEOFF__REVIEWS__REVIEW" AS "review"
> WHERE
> "review"."PK" = 1
> ORDER BY
> "review".PK
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
