[
https://issues.apache.org/jira/browse/DERBY-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630236#comment-13630236
]
Dag H. Wanvik commented on DERBY-6103:
--------------------------------------
Thanks, Kim. This is very close. As far as I can see, you still lack the
<windows_specification> in the new section on <window clause>:
It reads:
WINDOW window_name
but should be:
WINDOW window_name window_specification
Currently, the only valid window_specification is an empty pair of
parentheses (()), which indicates that the function is evaluated over the
entire result set.
Notice that we now have a definition for window specification in two places. As
long as we only allow "()" it's OK I think. Later we may want to factor this
out as a new topic.
Btw: you use underscore concatenation for new meta_symbols. I thought we has
switched to CamelCase?
> 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.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
