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] Closed: (DERBY-4397) Allow ORDER BY in subqueries
Date Mon, 10 May 2010 23:51:36 GMT

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

Dag H. Wanvik closed DERBY-4397.

> 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, derby-4397-sortavoidance-a.diff, derby-4397-sortavoidance-a.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