db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6103) Improve documentation of ROW_NUMBER function
Date Thu, 21 Mar 2013 15:11:15 GMT

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

Kim Haase updated DERBY-6103:
-----------------------------

    Attachment: DERBY-6103.zip
                DERBY-6103.stat
                DERBY-6103.diff

I'm attaching DERBY-6103.diff, DERBY-6103.stat, and DERBY-6103.zip, with changes to the following:

M       src/ref/rreffuncrownumber.dita
M       src/ref/rrefkeywords29722.dita

I'm sure more work is needed -- I think the sentence "Derby does not currently allow the named
or unnamed window specification to be specified in the OVER() clause, but requires an empty
parenthesis" is not right any more, and the description of the new example is probably not
quite right. All edits are welcome. Thanks!
                
> Improve documentation of ROW_NUMBER function
> --------------------------------------------
>
>                 Key: DERBY-6103
>                 URL: https://issues.apache.org/jira/browse/DERBY-6103
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-6103.diff, DERBY-6103.stat, DERBY-6103.zip
>
>
> The current documentation doesn't mention that we allow the window definition to be explicit.
> The restriction on WHERE clause no longer applies, nor does the sentence about ORDER
BY not being allowed in subqueries. Cf. rreffuncrownumber.dita. Also, the documentation mentions
that we don't support LIMIT, but not that we now support the FETCH/OFFSET clause, which is
often a better option than ROW_NUMBER.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message