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

[Apache Derby Developers mailing list]

Expose api for printing Abstract Syntax Trees in production (non-debug) servers
-------------------------------------------------------------------------------

         Key: DERBY-791
         URL: http://issues.apache.org/jira/browse/DERBY-791
     Project: Derby
        Type: Improvement
    Reporter: Rick Hillegas


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 contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Apache Derby Developers mailing list]

    [ http://issues.apache.org/jira/browse/DERBY-791?page=comments#action_12361765 ]

Daniel John Debrunner commented on DERBY-791:
---------------------------------------------

I was thinking about something similar over the holiday period. I don't think the current mechanism should be used, but instead the tree could be represented as an XML document. It would be great to tie this into the runtime statistics output, so that there was a common XML format for displaying query information.
It would be good to also make this optional in a production server, rather than increasing the footprint for every deployment. If the node factory was not removed (see DERBY-673) then a debugging node factory option could return nodes that provide the tree printing. This debugging code could be in a separate jar file to the base engine, thus only incurring a footprint cost when runtime debugging is required.

> Expose api for printing Abstract Syntax Trees in production (non-debug) servers
> -------------------------------------------------------------------------------
>
>          Key: DERBY-791
>          URL: http://issues.apache.org/jira/browse/DERBY-791
>      Project: Derby
>         Type: Improvement
>     Reporter: Rick Hillegas

>
> 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 contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Apache Derby Developers mailing list]

     [ http://issues.apache.org/jira/browse/DERBY-791?page=all ]

Mike Matrigali updated DERBY-791:
---------------------------------

    Component: SQL

> Expose api for printing Abstract Syntax Trees in production (non-debug) servers
> -------------------------------------------------------------------------------
>
>          Key: DERBY-791
>          URL: http://issues.apache.org/jira/browse/DERBY-791
>      Project: Derby
>         Type: Improvement
>   Components: SQL
>     Reporter: Rick Hillegas

>
> 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 contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

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

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

For more context on this issue, see the following email threads:

http://www.nabble.com/Optimizer-work-issues-discussions....-td6573100.html#a6605675

http://www.nabble.com/Having-trouble-finding-a-JIRA-issue-td21733256.html#a21733256

> 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
>
> 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.

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

Rick Hillegas updated DERBY-791:
--------------------------------

    Attachment: XmlTreeWalker.java

Attaching XmlTreeWalker.java. This is a simple Visitor which prints out the parsed AST in xml. You invoke it like so:

   java XmlTreeWalker "select r.a from r, s where r.b = s.c"

The program prints out an xml representation of the AST to standard out. Here's the output from the above command:

<?xml version="1.0" encoding="UTF-8"?>
<queryTree>
    <queryText>select r.a from r, s where r.b = s.c</queryText>
    <node>
        <nodeType>org.apache.derby.impl.sql.compile.CursorNode</nodeType>
        <contents>
            <member>name: null</member>
            <member>updateMode: UNSPECIFIED (0)</member>
            <member>statementType: SELECT</member>
        </contents>
        <node>
            <nodeType>org.apache.derby.impl.sql.compile.SelectNode</nodeType>
            <contents>
                <member>isDistinct: false</member>
                <member>groupByList: null</member>
                <member>orderByList: null</member>
                <member>resultSetNumber: 0</member>
                <member>referencedTableMap: null</member>
                <member>statementResultSet: false</member>
            </contents>
            <node>
                <nodeType>org.apache.derby.impl.sql.compile.ResultColumnList</nodeType>
                <contents>
                    <member>exposedName: A</member>
                    <member>name: A</member>
                    <member>tableName: null</member>
                    <member>isDefaultColumn: false</member>
                    <member>wasDefaultColumn: false</member>
                    <member>isNameGenerated: false</member>
                    <member>sourceTableName: null</member>
                    <member>type: null</member>
                    <member>columnDescriptor: null</member>
                    <member>isGenerated: false</member>
                    <member>isGeneratedForUnmatchedColumnInInsert: false</member>
                    <member>isGroupingColumn: false</member>
                    <member>isReferenced: false</member>
                    <member>isRedundant: false</member>
                    <member>virtualColumnId: 1</member>
                    <member>resultSetNumber: -1</member>
                    <member>dataTypeServices: null</member>
                    <member>; </member>
                </contents>
                <node>
                    <nodeType>org.apache.derby.impl.sql.compile.ResultColumn</nodeType>
                    <contents>
                        <member>exposedName: A</member>
                        <member>name: A</member>
                        <member>tableName: null</member>
                        <member>isDefaultColumn: false</member>
                        <member>wasDefaultColumn: false</member>
                        <member>isNameGenerated: false</member>
                        <member>sourceTableName: null</member>
                        <member>type: null</member>
                        <member>columnDescriptor: null</member>
                        <member>isGenerated: false</member>
                        <member>isGeneratedForUnmatchedColumnInInsert: false</member>
                        <member>isGroupingColumn: false</member>
                        <member>isReferenced: false</member>
                        <member>isRedundant: false</member>
                        <member>virtualColumnId: 1</member>
                        <member>resultSetNumber: -1</member>
                        <member>dataTypeServices: null</member>
                    </contents>
                    <node>
                        <nodeType>org.apache.derby.impl.sql.compile.ColumnReference</nodeType>
                        <contents>
                            <member>columnName: A</member>
                            <member>tableNumber: -1</member>
                            <member>columnNumber: 0</member>
                            <member>replacesAggregate: false</member>
                            <member>tableName: R</member>
                            <member>nestingLevel: -1</member>
                            <member>sourceLevel: -1</member>
                            <member>dataTypeServices: null</member>
                        </contents>
                    </node>
                </node>
            </node>
            <node>
                <nodeType>org.apache.derby.impl.sql.compile.FromBaseTable</nodeType>
                <contents>
                    <member>tableName: R</member>
                    <member>tableDescriptor: null</member>
                    <member>updateOrDelete: 0</member>
                    <member>null</member>
                    <member>existsBaseTable: false</member>
                    <member>dependencyMap: null</member>
                    <member>correlation Name: null</member>
                    <member>null</member>
                    <member>tableNumber -1</member>
                    <member>level 0</member>
                    <member>resultSetNumber: 0</member>
                    <member>referencedTableMap: null</member>
                    <member>statementResultSet: false</member>
                </contents>
            </node>
            <node>
                <nodeType>org.apache.derby.impl.sql.compile.FromBaseTable</nodeType>
                <contents>
                    <member>tableName: S</member>
                    <member>tableDescriptor: null</member>
                    <member>updateOrDelete: 0</member>
                    <member>null</member>
                    <member>existsBaseTable: false</member>
                    <member>dependencyMap: null</member>
                    <member>correlation Name: null</member>
                    <member>null</member>
                    <member>tableNumber -1</member>
                    <member>level 0</member>
                    <member>resultSetNumber: 0</member>
                    <member>referencedTableMap: null</member>
                    <member>statementResultSet: false</member>
                </contents>
            </node>
            <node>
                <nodeType>org.apache.derby.impl.sql.compile.BinaryRelationalOperatorNode</nodeType>
                <contents>
                    <member>operator: =</member>
                    <member>methodName: equals</member>
                    <member>dataTypeServices: null</member>
                </contents>
                <node>
                    <nodeType>org.apache.derby.impl.sql.compile.ColumnReference</nodeType>
                    <contents>
                        <member>columnName: B</member>
                        <member>tableNumber: -1</member>
                        <member>columnNumber: 0</member>
                        <member>replacesAggregate: false</member>
                        <member>tableName: R</member>
                        <member>nestingLevel: -1</member>
                        <member>sourceLevel: -1</member>
                        <member>dataTypeServices: null</member>
                    </contents>
                </node>
                <node>
                    <nodeType>org.apache.derby.impl.sql.compile.ColumnReference</nodeType>
                    <contents>
                        <member>columnName: C</member>
                        <member>tableNumber: -1</member>
                        <member>columnNumber: 0</member>
                        <member>replacesAggregate: false</member>
                        <member>tableName: S</member>
                        <member>nestingLevel: -1</member>
                        <member>sourceLevel: -1</member>
                        <member>dataTypeServices: null</member>
                    </contents>
                </node>
            </node>
        </node>
    </node>
</queryTree>

> 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.

    [ 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.

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

Rick Hillegas updated DERBY-791:
--------------------------------

    Attachment: derby-791-01-aa-fromListAndResultColumnList.diff

Attaching derby-791-01-aa-fromListAndResultColumnList.diff. This experimental patch fixes up FromList.accept(), FromList.toString(), and ResultColumnList.toString() as mentioned above. This makes the output of XmlTreeWalker more useful.

> 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
>
>
> 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.

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

Knut Anders Hatlen commented on DERBY-791:
------------------------------------------

This looks very useful, and it's even relatively easy to read. Perhaps it would be even easier to process the output (at least for a machine) if we split the name:value string into two separate tags. That is, instead of

<member>replacesAggregate: false</member>

something like

<member><name>replacesAggregate</name><value>false</value></member>

or perhaps even better

<member name="replacesAggregate">false</member>

> 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
>
>
> 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.

     [ 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.

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

Rick Hillegas updated DERBY-791:
--------------------------------

    Attachment: XmlTreeWalker.java

Attaching a second rev of the XmlTreeWalker. This version uses an in-memory database.

> 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, 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.

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

Rick Hillegas edited comment on DERBY-791 at 8/14/09 9:17 AM:
--------------------------------------------------------------

Attaching another rev of the XmlTreeWalker. This version uses an in-memory database.

      was (Author: rhillegas):
    Attaching a second rev of the XmlTreeWalker. This version uses an in-memory database.
 

> 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, 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.

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

Kay Röpke updated DERBY-791:
----------------------------

    Attachment: ASTGrapher.java
                XmlTreeWalker.java

Attached are an updated XmlTreeWalker and a Eclipse Zest visualization of the short class names of the AST.
They are laid out in a tree fashion.
Even though this mini application is far from perfect, it might be useful to someone. It should be trivial to add more information to the graph (like operator names, literal values, etc).

For XmlTreeWalker the only difference to Rick's version is that its execute method will accept a visitor object instead of always using this (well, and the method is now public so ASTGrapher can access it).

To compile this you need Zest from the Eclipse GEF project (and the RCP features). The easiest way to set up the Eclipse project is to create a new Eclipse RCP plugin project and then dropping in these two Java files. Run ASTGrapher.java as an Application (you do not need to start an entire RCP instance).
The RCP project only serves to properly set up the build path, nothing more.

> 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, 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.

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

Rick Hillegas updated DERBY-791:
--------------------------------

    Attachment: XmlTreeWalker.java

Attaching a new version of XmlTreeWalker, which implements the visitChildrenFirst() method which was added to the Visitor interface recently.

> 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, 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.

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

Rick Hillegas updated DERBY-791:
--------------------------------

    Attachment: derby-791-02-aa-printTargetColumnList.diff

Attaching derby-791-02-aa-printTargetColumnList.diff. This patch adds some more accept methods so that InsertNodes walk their targetColumnLists in addition to the children they share with their superclasses. Touches the following files:

M      java/engine/org/apache/derby/impl/sql/compile/DMLModStatementNode.java
M      java/engine/org/apache/derby/impl/sql/compile/InsertNode.java

> 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.

    [ 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.