[ http://issues.apache.org/jira/browse/DERBY-837?page=all ]
Mike Matrigali updated DERBY-837:
---------------------------------
Component: SQL
> Enable optimizer trace in Derby
> -------------------------------
>
> Key: DERBY-837
> URL: http://issues.apache.org/jira/browse/DERBY-837
> Project: Derby
> Type: New Feature
> Components: SQL
> Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
>
> 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 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
