[ 
https://issues.apache.org/jira/browse/DERBY-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722393#comment-13722393
 ] 

Rick Hillegas commented on DERBY-6305:
--------------------------------------

The following email thread lists many of the --derby-properties and suggests 
that we should consolidate the documentation of these properties in one place: 
http://apache-database.10148.n7.nabble.com/is-there-an-optimizer-override-to-force-multi-probe-query-plan-td132838.html

There appear to be at least 2 kinds of --derby-properties:

1) Properties which appear in queries.

2) Properties which appear in DDL.

(1) includes:

  index
  constraint
  joinStrategy
  hashInitialCapacity
  hashLoadFactor
  hashMaxCapacity
  bulkFetch
  joinOrder
  useStatistics

(2) includes some of the derby.storage.* properties such as 
derby.storage.pageSize
                
> Tuning Derby information on optimizer overrides needs improvement
> -----------------------------------------------------------------
>
>                 Key: DERBY-6305
>                 URL: https://issues.apache.org/jira/browse/DERBY-6305
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.10.1.1
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>         Attachments: ctundepthoptover.html, DERBY-6305.diff
>
>
> The topic "Optimizer overrides" in the Tuning Derby manual talks about using 
> the "-- DERBY-PROPERTIES" clause to specify overrides but doesn't include a 
> link to the topic later in the manual, "Overriding the default optimizer 
> behavior", that explains how to use the clause. This undoubtedly results in 
> user confusion.
> The first topic is 
> http://db.apache.org/derby/docs/10.10/tuning/ctundepthoptover.html; the 
> second is 
> http://db.apache.org/derby/docs/10.10/tuning/ctunoptimzoverride.html.
> I'll add the link, and I welcome additional suggestions on how to improve 
> these topics.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to