[
https://issues.apache.org/jira/browse/OPTIQ-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved OPTIQ-316.
-------------------------------
Resolution: Fixed
Fixed in
https://git-wip-us.apache.org/repos/asf?p=incubator-optiq.git;a=commit;h=8a91027c157e8c34ee1944faabb1353ec866d72a.
> SqlRun: Match output regardless of order if ORDER BY not present
> ----------------------------------------------------------------
>
> Key: OPTIQ-316
> URL: https://issues.apache.org/jira/browse/OPTIQ-316
> Project: optiq
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> If ORDER BY is not present, a compliant implementation may return rows in any
> order. SqlRun should detect this, output the rows in the original order, not
> the actual order.
> This feature makes it much easier to handle unsorted data. The previous
> workaround, adding an ORDER BY clause, may trigger a different execution path
> and mask bugs. And it was common to forget an ORDER BY and have to go back to
> add the ORDER BY and correct the data some weeks later.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
