db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-791) Expose api for printing Abstract Syntax Trees in production (non-debug) servers
Date Thu, 12 Nov 2009 15:33:39 GMT

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

Rick Hillegas commented on DERBY-791:
-------------------------------------

Committed derby-791-02-aa-printTargetColumnList.diff at subversion revision 835417.

> 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: ASTGrapher.java, derby-791-01-aa-fromListAndResultColumnList.diff,
derby-791-02-aa-printTargetColumnList.diff, XmlTreeWalker.java, XmlTreeWalker.java, XmlTreeWalker.java,
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.


Mime
View raw message