db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4398) Allow OFFSET/FETCH in subqueries
Date Mon, 11 Jan 2010 12:42:54 GMT

     [ 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-3.stat

Uploading derby-4398-3, similar to rev 2, but cleaned up a little, including moving bindOffsetFetch
to QueryTreeNode from CursorNode. Will commit this version if regression spass.

> 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-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.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message