[ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364698 ]
Daniel John Debrunner commented on DERBY-855: --------------------------------------------- The suggestion for constraint was constraint Use the constraint property to override the index that the optimizer selects and force the use of a particular index or force a table scan. To force the use of the index that enforces a primary key or unique constraint, use the constraint property and specify the unqualified name of the constraint. I think the first sentence is not required. Some of it is duplicated in the second sentence, and the comment about 'force a table scan is wrong'. > 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 > > 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
