db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Radzinski (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-855) Document optimizer overrides which were introduced in 10.2
Date Fri, 27 Jan 2006 21:34:06 GMT
    [ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364265 ] 

Eric Radzinski commented on DERBY-855:

Regarding your first point, do you suggest to remove the description about the default optimizer
behaviour, and just include something like this:

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.

And regarding your second point, would updating the syntax at the top of the topic resolve
this issue:

The syntax for FROM clause properties is:
         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 = NESTED LOOP | HASH ]

> 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:
>     Reporter: Mamta A. Satoor
>     Assignee: Eric Radzinski
>      Fix For:
>  Attachments: ctundepthoptover.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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message