Could you beef up the description in this JIRA a little to say exactly what unit of work has been done before closing it. If you have implemented exactly what the web page says and don't plan on changing
the web page to reflect future changes associated with a different
JIRA then that is fine, just say that.

For instance i think this JIRA only supports row_number() on an empty
over() clause, which I believe was a good 1st unit of work.

maybe what i am looking for is a release note, so much info is probably
in the extensive comments but would be nice to have a single paragraph
that explains what is being provided and note the limitations.


Thomas Nielsen (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575593#action_12575593 ]
Thomas Nielsen commented on DERBY-2998:
---------------------------------------

Thanks Army!

I do not have any more work lined up on this for 10.4. Given that there's only 
two days until feature freeze, I don't think there's time to do much else :)

I suggest we resolve and close this one as completed, and do any followup work 
in new jiras.

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.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-removeunused.diff, 
d2998-followup-testsuite.diff, d2998-followup-testsuite.stat, d2998-test.diff, 
d2998-te
st.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


Reply via email to