You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "A B (JIRA)" <de...@db.apache.org> on 2006/09/13 21:00:23 UTC
[jira] Updated: (DERBY-781) Materialize subqueries in select list
where possible to avoid creating invariant resultsets many times.
[ http://issues.apache.org/jira/browse/DERBY-781?page=all ]
A B updated DERBY-781:
----------------------
Summary: Materialize subqueries in select list where possible to avoid creating invariant resultsets many times. (was: Materialize union subqueries in select list where possible to avoid creating invariant resultsets many times.)
Derby Info: [Existing Application Impact, Release Note Needed] (was: [Release Note Needed, Existing Application Impact])
Removed the word "union" from the summary since the changes affect subqueries in general, not just UNION subqueries (as Satheesh pointed out). I decided to leave the actual description as it is, though, since I think it's useful as background to the follow-up comments which eventually led to the final changes. Also, if we change the description many of the comments will no longer make sense. For the sake of clarity I prefer to leave the description as it is. The more generic "summary" will be what's picked up in release notes, so I think that's good enough...
Of course, people should feel free to speak up if they disagree.
> Materialize subqueries in select list where possible to avoid creating invariant resultsets many times.
> -------------------------------------------------------------------------------------------------------
>
> Key: DERBY-781
> URL: http://issues.apache.org/jira/browse/DERBY-781
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.1.1.0, 10.2.1.0
> Environment: generic
> Reporter: Satheesh Bandaram
> Assigned To: A B
> Attachments: d781_v1.patch, d781_v1.stat, d781_v2.patch, DERBY-781_v1.html
>
>
> Derby's handling of union subqueries in from list can be improved by materializing invariant resultsets once, rather than creating them many times.
> For example:
> create view V1 as select i, j from T1 union select i,j from T2;
> create view V2 as select a,b from T3 union select a,b from T4;
> insert into T1 values (1,1), (2,2), (3,3), (4,4), (5,5);
> For a query like select * from V1, V2 where V1.j = V2.b and V1.i in (1,2,3,4,5), it is possible the resultset for V2 is created 5 times. (assuming V2 is choosen as the the inner table) This can be very costly if the underlying selects can take long time and also may perform union many times.
> Enhance materialization logic in setOperatorNode.java. It currently returns FALSE always.
> public boolean performMaterialization(JBitSet outerTables)
> throws StandardException
> {
> // RESOLVE - just say no to materialization right now - should be a cost based decision
> return false;
> /* Actual materialization, if appropriate, will be placed by our parent PRN.
> * This is because PRN might have a join condition to apply. (Materialization
> * can only occur before that.
> */
> //return true;
> }
--
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