Redesign dynamic subquery materialization optimization to be based on cost
analysis during compile/optimization phases.
-----------------------------------------------------------------------------------------------------------------------
Key: DERBY-1733
URL: http://issues.apache.org/jira/browse/DERBY-1733
Project: Derby
Issue Type: Improvement
Affects Versions: 10.1.3.1, 10.1.3.0, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0
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.
-
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
