[ http://issues.apache.org/jira/browse/DERBY-573?page=comments#action_12331607 ]
Daniel John Debrunner commented on DERBY-573: --------------------------------------------- Thinking more about this DERBY-HINTS was a bad name since you are providing overrides, not hints. The generic DERBY-PROPERTIES seems a good choice, that could support hints being added in the future by the name of the property containing the name 'hint'. > Provider support for optimizer overrides in Derby. > -------------------------------------------------- > > Key: DERBY-573 > URL: http://issues.apache.org/jira/browse/DERBY-573 > Project: Derby > Type: New Feature > Components: SQL > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Mamta A. Satoor > Attachments: optimizeroverrides.html > > Derby's query optimizer usually makes the best choice of join order and > access path. The default join strategy ususally works the best too. However, > there are some cases in which user may want to override the optimizer or the > default values. Providing support for optimizer overrides will allow users to > hand-tune the optimizer for queries. -- 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
