db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-573) Provide support for optimizer overrides in Derby.
Date Mon, 23 Jan 2006 06:54:12 GMT
     [ http://issues.apache.org/jira/browse/DERBY-573?page=all ]
Mamta A. Satoor resolved DERBY-573:

    Fix Version:
     Resolution: Fixed

All the code changes for this feature are already checked in. Have entered Derby-855 as a
subtask for the documentation changes

> Provide support for optimizer overrides in Derby.
> -------------------------------------------------
>          Key: DERBY-573
>          URL: http://issues.apache.org/jira/browse/DERBY-573
>      Project: Derby
>         Type: New Feature
>   Components: SQL
>     Versions:
>     Reporter: Mamta A. Satoor
>     Assignee: Mamta A. Satoor
>      Fix For:
>  Attachments: Derby573OptimizerOverridesAndRunTimeStatistics011206.txt, derby572OptimizerOverridesAndUpgrade120605.txt,
derby572OptimizerOverridesAndUpgrade121105.txt, derby572OptimizerOverridesAndUpgrade121205.txt,
derby573OptimierOverrides110805.txt, optimizeroverrides.html, optimizeroverrides.html
> Derby's query optimizer usually makes the best choice of join order and access path.
The default join strategy ususally works the best too. However, there are some cases in which
user may want to override the optimizer or the default values. Providing support for optimizer
overrides will allow users to hand-tune the optimizer for queries. 

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