You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2013/09/05 15:44:53 UTC
[jira] [Created] (DERBY-6335) Improve performance of FETCH
NEXT/OFFSET with ORDER BY
Dag H. Wanvik created DERBY-6335:
------------------------------------
Summary: Improve performance of FETCH NEXT/OFFSET with ORDER BY
Key: DERBY-6335
URL: https://issues.apache.org/jira/browse/DERBY-6335
Project: Derby
Issue Type: Improvement
Components: SQL
Reporter: Dag H. Wanvik
We can utilize information about the number of rows to be retrieved to
a) optimize any sorting imposed by the ORDER BY by keeping only the top <next> rows in memory,
b) inform the optimizer with more precise information about the number of rows in those cases where such a constrict is a join participant.
For b) this would only work if <next> were known statically at compile time. For a) this could work even with ? parameters,
--
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