db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-573) Provide support for optimizer overrides in Derby.
Date Tue, 13 Dec 2005 18:30:45 GMT
    [ http://issues.apache.org/jira/browse/DERBY-573?page=comments#action_12360326 ] 

Satheesh Bandaram commented on DERBY-573:

This patch has been committed to trunk.

Transmitting file data ........................................
Committed revision 356562.

It seems you have also resolved DERBY-727 along with this change, so please mark both of them
as RESOLVED and close them after testing on trunk build. You figured out several hard issues
here 1) Ability to extract hints provided in comments 2) Soft upgrade issues and 3) adding
upgrade infrastructure for 10.2. Good job!

> 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
>  Attachments: derby572OptimizerOverridesAndUpgrade120605.txt, derby572OptimizerOverridesAndUpgrade121105.txt,
derby572OptimizerOverridesAndUpgrade121205.txt, derby573OptimierOverrides110805.txt, 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