On 7/27/13 3:45 PM, Dag H. Wanvik wrote:
...
That is, we the user specified a value, use it, else use default. I
love would for all the possible usages ofr --DERBY-PROPERTIES to ne
documented in one place...!
+1. https://issues.apache.org/jira/browse/DERBY-6305 may be a place to
work through
I believe I have seen overrides that specify the Derby property
"derby.storage.pageSize"
is there are long columns, cf. this code in CreateTableNode (which uses
properties collected from --DERBY-PROPERIES):
if (table_has_long_column || (approxLength >
Property.TBL_PAGE_SIZE_BUMP_THRESHOLD))
Hi,
When optimizer overrides was originally added, following overrides were
supported
1) constraint – The Derby optimizer chooses an index, including the indexes
that enforce constraints, as the access path for query execution if it is
useful. If there is more than one useful index, in most cases
On 7/25/13 11:39 AM, Rick Hillegas wrote:
Hi Mike,
This is an attempt to answer your questions based on my recent work in
this code area. Other people may know more than I do.
On 7/25/13 8:41 AM, mike matrigali wrote:
Is there an optimizer override in 10.8 to force a multi-probe query
plan?
Hi Mike,
This is an attempt to answer your questions based on my recent work in
this code area. Other people may know more than I do.
On 7/25/13 8:41 AM, mike matrigali wrote:
Is there an optimizer override in 10.8 to force a multi-probe query plan?
Not that I'm aware of. Some of the optimize
Is there an optimizer override in 10.8 to force a multi-probe query plan?
If not, is there an override in the new work being done in trunk to
force it?
Also if not, is there any suggestion of what the right syntax would be
to add it to the old style optimizer override?
It seems recently there
