|
TODO: Add Test for the following
If we use a composite condition in join (i.e. join condition which involves "and"
or "or" function rather than single comparison function) then index information is not
used to carry out join. We should find out comparison functions which involves column
from both left and right join table and still should find the index iterator and use it
if available.
If ansi join uses a composite condition then the comparison function which
involves only one table column is applied at table level.
If we do not use new ansi join syntax and join condition is composite join
condition, then Comparison function involving only one table column in that join
condition are being applied twice. Once at each table level and once after creation of
join iterator.
column literal functions are applied at indexed level when possible.
Test in two table right outer join, if only left table of join has an index then
IndexedNestedLoopJoinedRowIterator should be used.
Test three table join (two table have index)results in two indexed joined iterator
nesting.
Test in two table inner join, use of composite condition (condition using and
function) in ansi join on clause still results in use of
IndexedNestedLoopJoinedRowIterator, if only one table is indexed.
Test in non ansi join syntax (where join is specified in where clause), if implied
column literal conditions are applied at table level.
Add Test for dynamic index.
Test dynamic Index : if created then, should use
IndexedNestedLoopJoinedRowIterator if there is no Index available on the join columns
version:
$Revision: 1.12 $ $Date: 2005/12/20 23:52:09 $
author:
Ahimanikya Satapathy |
