[
https://issues.apache.org/jira/browse/DERBY-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669037#action_12669037
]
Rick Hillegas commented on DERBY-791:
-------------------------------------
Looking at the output of XmlTreeWalker, the following jumps out at me: The
subclasses of QueryTreeNodeVector could use a little upgrading of their
accept() and toString() methods. In particular:
1) FromList.accept() should start out by calling v.visit( this ) as the other
accept() implementations do.
2) FromList and ResultColumnList should have their own overrides for
toString()--right now they rely on the toString() method in their superclass,
which is too generic to be useful for tree printing.
> Expose api for printing Abstract Syntax Trees in production (non-debug)
> servers
> -------------------------------------------------------------------------------
>
> Key: DERBY-791
> URL: https://issues.apache.org/jira/browse/DERBY-791
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Rick Hillegas
> Attachments: XmlTreeWalker.java
>
>
> Currently you can print Abstract Syntax Trees to derby.log by setting the
> DumpParseTree tracepoint at server startup. E.g.:
> java -cp $CLASSPATH -Dderby.debug.true=DumpParseTree
> -Dderby.stream.error.logSeverityLevel=0 org.apache.derby.tools.ij z.sql
> This can be a useful debugging tool. However, it only works on debug servers
> built with the following flags:
> sanity=true
> debug=true
> We should provide some mechanism for printing these trees in production
> (non-debug) servers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
