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 Sat, 19 Dec 2009 03:18:18 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-insert.stat
                derby-4398-insert.diff

Uploading a first patch (derby-4398-insert) which enables offset/fetch
first in INSERT subquery context.  This modifies the previous
implementation for offset fetch which only had to consider a top level
cursor context. Instead of wrapping the row count result set node from
CursorNode#optimizeStatement, the offset/fetch info is now pushed to
the underlying result set, similar to what is done for order by.

Added test cases to the now renamed test OrderByAndOffsetFetchInSubqueries.
The patch is not yet for commit, needs some cleanups still.

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


Mime
View raw message