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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2013/06/25 17:10:22 UTC

[jira] [Updated] (DERBY-791) Expose api for printing Abstract Syntax Trees in production (non-debug) servers

     [ https://issues.apache.org/jira/browse/DERBY-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-791:
----------------------------------

    Urgency: Normal
     Labels: derby_triage10_11  (was: )
    
> 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
>              Labels: derby_triage10_11
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira