You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/06/14 15:27:20 UTC
[jira] [Created] (DERBY-6263) Make the Visitor support in
CursorNodes support ORDER BY lists, FETCH, and OFFSET clauses
Rick Hillegas created DERBY-6263:
------------------------------------
Summary: 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: 10.11.0.0
Reporter: Rick Hillegas
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: http://apache-database.10148.n7.nabble.com/Using-ASTParser-and-TreeWalker-for-parsing-SQL-query-td131219.html. 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