db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1733) Redesign dynamic subquery materialization optimization to be based on cost analysis during compile/optimization phases.
Date Sun, 06 May 2007 21:20:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-1733:
----------------------------------

    Component/s: SQL

> Redesign dynamic subquery materialization optimization to be based on cost analysis during
compile/optimization phases.
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1733
>                 URL: https://issues.apache.org/jira/browse/DERBY-1733
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1
>         Environment: All platforms
>            Reporter: Satheesh Bandaram
>
> Separating this issue from DERBY-634. DERBY-634 addressed a specific bug (that causes
stack overflow for some queries with subqueries) in dynamic subquery materialization optimization.
I am filing this IMPROVEMENT request to redesign  the optimization to be cost based decision
during compile/optimization phases of query compilation, instead of being a runtime decision.
> Much more info present in DERBY-634, which includes Jeff Lichman's analysis. Also note
DERBY-781 added subquery materialization framework that is more generic approach that works
for SELECT subqueries. A similar mechanism is needed for WHERE clause subqueries as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message