[
https://issues.apache.org/jira/browse/DERBY-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-837:
----------------------------------
Attachment: enableOptimizerTraceHacksvnstat.txt
enableOptimizerTraceHacksvndiff.txt
Brian, actually I found these over 6 and 1/2 yr old svn diff and svn stat on my
computer for this jira. Can't recall much what I did without looking into it
but I thought I would share it anyways if it is of any help.
> Enable optimizer trace in Derby
> -------------------------------
>
> Key: DERBY-837
> URL: https://issues.apache.org/jira/browse/DERBY-837
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.2.1.6
> Reporter: Mamta A. Satoor
> Attachments: enableOptimizerTraceHacksvndiff.txt,
> enableOptimizerTraceHacksvnstat.txt
>
>
> Derby engine has code to produce trace for optimization phase ie various
> plans considered by the optimizer for a query. This trace however does not
> get produced because there is no way to turn the trace on. When someone does
> work on providing a way to enable the optimizer trace, we will also need to
> decide in what format this trace should be presented. Further information on
> this issue can be found at
> http://article.gmane.org/gmane.comp.apache.db.derby.devel/12288
--
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
