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] Updated: (DERBY-573) Provide support for optimizer overrides in Derby.
Date Mon, 12 Dec 2005 08:17:47 GMT
     [ http://issues.apache.org/jira/browse/DERBY-573?page=all ]

Mamta A. Satoor updated DERBY-573:

    Attachment: derby572OptimizerOverridesAndUpgrade121105.txt

I have addressed Dan's comments with the latest patch attached to the JIRA entry. 

In addition, I have also added a master file for the phaseTester test in java\testing\org\apache\derbyTesting\functionTests\master
Output of the manual run of this test can be diffed against the master that I am checking
in. In future, if anyone changes this test such that it's output will change, then they should
change the master file accordingly. This way, we can make sure that the test is still running
correctly as it is evolving. Once this test is run as part of a suite like other tests, we
will not have to run this test manually and any changes to master will be caught easily,

> 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,
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