db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6263) Make the Visitor support in CursorNodes support ORDER BY lists, FETCH, and OFFSET clauses
Date Fri, 14 Jun 2013 15:41:20 GMT

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

ASF subversion and git services commented on DERBY-6263:

Commit 1493123 from [~rhillegas]
[ https://svn.apache.org/r1493123 ]

DERBY-6263: Make the Visitor logic inspect ORDER BY, FETCH, and OFFSET CLAUSES. Tests passed
cleanly for me on derby-6263-01-aa-visit-ignored-clauses.diff.
> Make the Visitor support in CursorNodes support ORDER BY lists, FETCH, and OFFSET clauses
> -----------------------------------------------------------------------------------------
>                 Key: DERBY-6263
>                 URL: https://issues.apache.org/jira/browse/DERBY-6263
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>            Reporter: Rick Hillegas
>         Attachments: derby-6263-01-aa-visit-ignored-clauses.diff
> If you call treePrint() on a CursorNode, you will see information on ORDER BY, FETCH,
and OFFSET clauses. However, these clauses are not visited by CursorNode.acceptChildren().
This looks like an omission. This defect was brought to our attention by this email thread:
You can see the difference in treePrint() and acceptChildren() behavior by running the following
query through the ASTParser and TreePrinter tools attached to DERBY-3946:
>     select tablename from sys.systables where 1=2 order by tablename;

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

View raw message