[
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-2.zip
DERBY-6103-2.stat
DERBY-6103-2.diff
Thanks for all your patience and clarifications, Dag.
Attaching DERBY-6103-2.diff, DERBY-6103-2.stat, and DERBY-6103-2.zip, with
these changes:
M src/ref/rreffuncrownumber.dita
M src/ref/refderby.ditamap
M src/ref/rrefkeywords29722.dita
A src/ref/rrefsqljwindow.dita
M src/ref/rrefselectexpression.dita
I hope this is a bit closer to what is needed!
> 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
