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-4397) Allow ORDER BY in subqueries
Date Thu, 17 Dec 2009 22:24:18 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dag H. Wanvik updated DERBY-4397:

    Attachment: derby-4397-2.stat

Committed derby-4397-2 as svn 891952. This version of the patch
is the same as #1, except some cleanup in the new test, OrderByInSubqueries.
I am not totally comfortable with the level of testing for this feature yet, but I will probably
need to get OFFSET/FETCH in subqueries working before I can tease out
more bugs, so I chose to commit this patch now.

> Allow ORDER BY in subqueries
> ----------------------------
>                 Key: DERBY-4397
>                 URL: https://issues.apache.org/jira/browse/DERBY-4397
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>         Attachments: derby-4397-1.diff, derby-4397-1.stat, derby-4397-2.diff, derby-4397-2.stat,
derby-4397-all-subqueries.diff, derby-4397-all-subqueries.stat, derby-4397-insert-from-exists.diff,
derby-4397-insert-from-exists.stat, orderBySpec.html, orderBySpec.html, orderBySpec.html,
orderBySpec.html, orderBySpec.html
> SQL 2008 allows ORDER BY to be specified in subqueries. In conjunction with OFFSET/FETCH
> meaningful subqueries with row ordering may be formulated. Cf. MySQL's LIMIT may be used
in subqueries as well.
> Note that OFFSET/FETCH is currently not allowed in subqueries, either.

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

View raw message