[ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12365767 ]
Mamta A. Satoor commented on DERBY-855: --------------------------------------- Eric, how about rather than "less-than-optimal results", we say "less-than-optimal performance"? The results word many be mistaken with the query result. If you/anyone else has better wording, please suggest. Also, in order to have our example match what we recommend, for joinStrategy example, we should use joinOrder in it. As shown below SELECT * FROM --DERBY-PROPERTIES joinOrder=FIXED t1 a, t1 b --DERBY-PROPERTIES joinStrategy=nestedloop WHERE a.c1=b.c1 ; > 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 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > ctunoptimzoverride.html, derby855-2.diff, derby855.diff, > derby855_html_files.zip, tuning_guide.zip > > 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
