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] Commented: (DERBY-573) Provider support for optimizer overrides in Derby.
Date Tue, 20 Sep 2005 17:37:28 GMT
    [ http://issues.apache.org/jira/browse/DERBY-573?page=comments#action_12330031 ] 

Mamta A. Satoor commented on DERBY-573:
---------------------------------------

I can look into modifying the RunTimeStatistics to indicate that user overrides are being
used. Also, I will see how parser can be modified to look for --DERBY-HINTS rather than just
--PROPERTIES. If people prefer DERBY-PROPERTIES over DERBY-HINTS, please put comment stating
so to this JIRA entry.

> Provider 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: 10.2.0.0
>     Reporter: Mamta A. Satoor
>     Assignee: Mamta A. Satoor
>  Attachments: 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message