[
http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364849 ]
Eric Radzinski commented on DERBY-855:
--------------------------------------
There's three open issues on derby-855. I've summarized them here:
--- Does this text adequately address your concern about the description of the
constraint property:
constraint
To force the use of the index that enforces a primary key, a foreign key, or
unique constraint, use the constraint property and specify the
unqualified name of the constraint. The constraint property can be used only
within a TableExpression, and it
can be specified only on base tables; it cannot be specified on views or
derived tables.
--- I haven't seen a response about my proposal to modify the syntax to include
the properties in the syntax. Here's what I proposed on 1/27:
The syntax for FROM clause properties is:
FROM [ -- DERBY-PROPERTIES joinOrder = FIXED | UNFIXED ]
TableExpression [,TableExpression]*
The syntax for table optimizer override properties, which must be included at
the end of a TableExpression, is:
{TableName | ViewName }
[ [ AS ] CorrelationName
[ (SimpleColumnName [ , SimpleColumnName]* ) ] ]
[ -- DERBY-PROPERTIES constraint=<constraint-name> |
index=<index-name> | joinStrategy = NESTEDLOOP | HASH ]
--- Regarding the comment about runstats output, is there a doc to-do in this
comment? or does this apply only to the output when a foreign key is
specified? If there is a doc to-do, can you provide me some details about what
it should include?
> 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
