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 2010/01/28 17:01:35 UTC
[jira] Issue Comment Edited: (DERBY-4398) Allow OFFSET/FETCH in
subqueries
[ https://issues.apache.org/jira/browse/DERBY-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805969#action_12805969 ]
Dag H. Wanvik edited comment on DERBY-4398 at 1/28/10 4:01 PM:
---------------------------------------------------------------
Resolving this issue. Optimizer tie-in will be handled in a separate issue if/when we get to that.
was (Author: dagw):
Resolving this issue.
> 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
> Fix For: 10.6.0.0
>
> Attachments: derby-4398-2.diff, derby-4398-2.stat, derby-4398-3.diff, derby-4398-3.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.
> SQL features:
> F856 Nested <fetch first clause> in <query expression>
> F857 Top-level <fetch first clause> in <query expression> (already present in 10.5)
> F858 <fetch first clause> in subqueries
> F859 Top-level <fetch first clause> in views
> F860 dynamic <fetch first row count> in <fetch first clause> (already present in 10.5)
> F861 Top-level <result offset clause> in <query expression> (already present in 10.5)
> F862 <result offset clause> in subqueries
> F863 Nested <result offset clause> in <query expression>
> F864 Top-level <result offset clause> in views
> F865 dynamic <offset row count> in <result offset clause> (already present in 10.5)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.