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] [Commented] (DERBY-6103) Improve documentation of ROW_NUMBER function
Date Wed, 01 May 2013 05:24:16 GMT

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

Dag H. Wanvik commented on DERBY-6103:
--------------------------------------

Thanks, Kim! +1
                
> 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
>    Affects Versions: 10.10.1.1
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-6103-2.diff, DERBY-6103-2.stat, DERBY-6103-2.zip, DERBY-6103-3.diff,
DERBY-6103-3.zip, DERBY-6103-4.diff, DERBY-6103-4.zip, DERBY-6103-5.diff, DERBY-6103-5.zip,
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