[
https://issues.apache.org/jira/browse/DERBY-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510046#comment-13510046
]
Dag H. Wanvik commented on DERBY-6004:
--------------------------------------
Seems straight forward, although my intuition would have have it as "ORDERED
BY", since its a description of what comes out rather than a "work order" to
the SQL... but that would introduce another keyword, so...
What about collation? Even if the table function did its sort as per the
contract, would it necessarily be aware of the data base collation?
> Make it possible for table functions to declare that they return sorted
> results and make the optimizer exploit this information.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6004
> URL: https://issues.apache.org/jira/browse/DERBY-6004
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
>
> A derby-dev discussion has highlighted the need for table functions to return
> sorted results which the optimizer can exploit. See
> http://old.nabble.com/Have-Derby-Network-Server-having-an-out-of-memory-%28PermGen%29-to34704415.html#a34706722
--
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
