[
https://issues.apache.org/jira/browse/DERBY-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5933:
--------------------------------------
Attachment: d5933-remap.diff
Good detective work, Dag!
I noticed that ColumnReference.remapColumnReferencesToExpressions() had a fix
for DERBY-3023 which made it use getVirtualColumnId() instead of
getColumnPosition() if the source of the result column was a VirtualColumnNode.
remapColumnReferences() does not have this fix.
Adding a similar fix to remapColumnReferences() (see the attached
d5933-remap.diff) also makes the results come out in the right order. It does
essentially the same thing as the poc patch, only that it narrows down the
change to only affect remapping.
All the regression tests ran cleanly with the remap patch, FWIW.
> SQL sorting error
> -----------------
>
> Key: DERBY-5933
> URL: https://issues.apache.org/jira/browse/DERBY-5933
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.0.2.1, 10.1.1.0, 10.2.1.6, 10.3.1.4, 10.4.1.3,
> 10.5.1.1, 10.6.1.0, 10.7.1.1, 10.8.1.2, 10.9.1.0
> Environment: Windows 7 Netbeans JDBC GUI
> Reporter: Vlasov Igor
> Labels: derby_triage10_10
> Attachments: 5933.log, d5933-pof.diff, d5933-remap.diff,
> Helpdesk.zip, repro.sql, right_sorting.png, wrong_sorting.png
>
>
> Hello
> I have a simple database with 100 records.
> I am running a SQL query from Netbeans GUI though JDBC
> This query was generated by Hibernate ORM.
> In certain circumstances the result rowset is not sorting.
> When I use condition morefld2_.mf_id in (5) the result is unsortable.
> When I use condition morefld2_.mf_id in (5,0) the result is sorting properly.
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
