db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Nielsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2998) Add support for ROW_NUMBER() window function
Date Tue, 04 Mar 2008 12:54:40 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574962#action_12574962

Thomas Nielsen commented on DERBY-2998:

Wrt allowing order by in a subquery select:
I did the limited changes needed to allow order by in a subquery select, and have a working
proto in my sandbox. Enables ordering and restriction on the window function column like we
would like.

ij> select * from (select row_number() over () as r, t.* from t order by b desc) tr  where
R                   |A          |B          
1                   |50         |500        
2                   |40         |400

Is this something we would like to support?
Do you think it's worth making a new jira for this? 

The closest I could find was DERBY-4, but it's not identical as it centers around a INSERT
INTO ... SELECT FROM ... query. And it is currently veto'ed. Looking at the patch for DERBY-4
now, I see it does more or less the same thing as my changes, only for insert statements.

> Add support for ROW_NUMBER() window function
> --------------------------------------------
>                 Key: DERBY-2998
>                 URL: https://issues.apache.org/jira/browse/DERBY-2998
>             Project: Derby
>          Issue Type: Sub-task
>          Components: SQL
>            Reporter: Thomas Nielsen
>            Assignee: Thomas Nielsen
>            Priority: Minor
>         Attachments: d2998-10.diff, d2998-10.stat, d2998-11.diff, d2998-12.diff, d2998-12.stat,
d2998-13.diff, d2998-13.stat, d2998-14.diff, d2998-14.stat, d2998-15.diff, d2998-15.stat,
d2998-16.diff, d2998-16.stat, d2998-17.diff, d2998-17.stat, d2998-18.diff, d2998-18.stat,
d2998-19.diff, d2998-19.stat, d2998-4.diff, d2998-4.stat, d2998-5.diff, d2998-5.stat, d2998-6.diff,
d2998-6.stat, d2998-7.diff, d2998-7.stat, d2998-8.diff, d2998-8.stat, d2998-9-derby.log, d2998-9.diff,
d2998-9.stat, d2998-doc-1.diff, d2998-doc-1.stat, d2998-doc-2.diff, d2998-doc-2.stat, d2998-followup-2.diff,
d2998-followup-2.stat, d2998-followup-distinct.diff, d2998-followup-distinct.stat, d2998-followup-doc3.diff,
d2998-followup-doc3.stat, d2998-followup-issue1.diff, d2998-followup-issue1.stat, d2998-followup-issue4.diff,
d2998-followup-issue4.stat, d2998-followup-testsuite.diff, d2998-followup-testsuite.stat,
d2998-test.diff, d2998-test.stat, d2998-test2.diff, d2998-test2.stat, d2998-test3.diff, d2998-test3.stat,
d2998-test4.diff, d2998-test4.stat, d2998-test6.diff, d2998-test7.diff, d2998-test8.diff,
d2998-test9.diff, rreffuncrownumber.html
> As part of implementing the overall OLAP Operations features of SQL (DERBY-581), implement
the ROW_NUMBER() window function.
> More information about this feature is available at http://wiki.apache.org/db-derby/OLAPRowNumber

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

View raw message