[
https://issues.apache.org/jira/browse/DERBY-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680222#action_12680222
]
Dag H. Wanvik commented on DERBY-4087:
--------------------------------------
I could imagine printing already seen subtrees something like this:
resultColumns:
org.apache.derby.impl.sql.compile.resultcolumnl...@1e1be92
org.apache.derby.impl.sql.compile.resultcol...@1038de7
***truncated***
org.apache.derby.impl.sql.compile.resultcol...@1490eb5
***truncated***
Is this helpful? Searching backward in the printout would then reveal these
subtrees fully printed.
Do we want a new knob to enable this, or could it be done always?
> Clean up debug printing of the abstract syntax trees after parsing, binding
> and optimization
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-4087
> URL: https://issues.apache.org/jira/browse/DERBY-4087
> Project: Derby
> Issue Type: Improvement
> Components: Miscellaneous, SQL
> Reporter: Dag H. Wanvik
> Priority: Trivial
>
> Currently, the printing is often inconsistent:
> - some subtrees not printed
> - wrong indentation due to missing newlines, or lacking level increments
> - redundant printing of subtrees (AST is really a DAG, would be nice to print
> only once and then refer back to show aliasing)
> - some items printed twice due to inconsistent usage of pattern
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
