[
https://issues.apache.org/jira/browse/DERBY-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-4398:
---------------------------------
Attachment: derby-4398-2.stat
derby-4398-2.diff
Uploading version 2 of this patch; which extends the support for offset/fetch to
all subqueries, and adds test cases.
Missing is still informing the optimizer with hints on cardinality if
offset/fetch is used.
I also need to investigate more if sort avoidance still works in presence of
offset/fetch.
Flattening is prohibited in the presence of offset/fetch, similarly to what is
done for order by in subqueries.
Running regressions.
> Allow OFFSET/FETCH in subqueries
> --------------------------------
>
> Key: DERBY-4398
> URL: https://issues.apache.org/jira/browse/DERBY-4398
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Attachments: derby-4398-2.diff, derby-4398-2.stat,
> derby-4398-insert.diff, derby-4398-insert.stat
>
>
> SQL 2008 specifies that OFFSET/FETCH (<result offset clause>, <fetch first
> clause>) may be used in subqueries.
> Currently, Derby only allows this at the outer (cursor) level. Cf. also
> DERBY-4397 on allowing ORDER BY in subqueries
> for this extension to be portable and useful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
