Re: Inlist Iterator and NULLs *SOLVED*

Thanks to Wolfgang for spotting the problem. It was not the inlist iterator at all but an outer join! The NOT NULL predicate invalidated the outer join, so the optimizer was smart enough to make a different decision. I am still perplexed as to why the table access information was so radically different, but in light of the new finding, an explanation can be found.

The lesson learned here is to not to focus on a 'problem' until you fully understand the whole situation.

Daniel

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Daniel Fink
  INET: daniel.fink_at_sun.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).



text/x-vcard attachment: Card for Daniel Fink