[
https://issues.apache.org/jira/browse/DERBY-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240648#comment-13240648
]
Rick Hillegas commented on DERBY-5499:
--------------------------------------
Hi Kim,
Thanks for catching that blooper. The limit/offset escape clause can appear
wherever the OFFSET and FETCH FIRST clauses can appear. You are right, those
clauses do not appear in the WHERE clause. Instead, they appear after the WHERE
clause and after the ORDER BY clause. Sorry for the confusion. Thanks.
> Document the new JDBC limit/offset escape syntax
> ------------------------------------------------
>
> Key: DERBY-5499
> URL: https://issues.apache.org/jira/browse/DERBY-5499
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
>
> The work on DERBY-5488 adds new JDBC escape syntax for the limit/offset
> clauses. These should be documented, probably in the Reference Guide as a
> subsection of JDBC escape syntax.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
