[
https://issues.apache.org/jira/browse/DERBY-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-791:
--------------------------------
Attachment: z.xml
XmlTreeWalker.java
Thanks for the feedback, Knut. Attaching a new version of XmlTreeWalker
together with the corresponding output: z.xml. This new version formats the
node contents as member elements with name and value attributes, much as Knut
suggested. The node type is also formatted as an attribute. This makes the xml
a little more compact and readable.
If you are using Firefox, you make be interested in this feature of the
browser: By default, mysterious xml documents are presented as a directory
tree, with each element being a separately collapsible level. This is a very
handy way to view our ASTs. I think that Internet Explorer may do something
similar. Safari, however, doesn't present xml files in this useful way.
> 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: derby-791-01-aa-fromListAndResultColumnList.diff,
> XmlTreeWalker.java, XmlTreeWalker.java, z.xml
>
>
> 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.
