[ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364115 ]
Eric Radzinski commented on DERBY-855: -------------------------------------- I have a few outstanding questions about documenting this issue: --I need some help extracting relevant examples from the source that you provided, which is located in: db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/optimizerOverrides.out. Which specific ones would be best to use? --Satheesh mentioned that we need to let the users know that they can see their optimizer overrides in RUNSTAT output. I'm assuming that this update would go in the tuning guide as a separate topic in the "Working with RunTimeStatistics" section. Can you confirm this? --I need to mention whether the four properties belong after FROM or after table. Can you confirm my understanding of where the four properties can be used: joinOrder can be used with a FROM clause; index, constraint, and joinStrategy can be used only within a TableExpression. Is that correct? > Document optimizer overrides which were introduced in 10.2 > ---------------------------------------------------------- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- 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
