Re: Some weird behavior with a collection in a subquery.

Sorry for the repost. Thought it didn't come trough as I was posting for the 1st time.

Lex, thanks for sharing this info.=20

Here is clarification since the term in-list could really confuse. Some time ago we've switched from using huge in-list clauses to really neat looking, tiny queries that employs collections. Once cast to tables they are really semantically no different from any other tables and joined to the results same way as any other types of tables would.

What is different and causing all the trouble that they considered as potential semi-join candidates. Unlike the normal tables.

Thanks again.

• Vlad

On 6/10/05, Lex de Haan <lex.de.haan_at_naturaljoin.nl> wrote:
> I have no experience at all with collections in in-lists,
> but in general, in-lists can be resolved in three ways by Oracle:
>=20
> - using the INLIST ITERATOR (most of the time the most efficient path)
> - in-list expansion, so it becomes sort of a repeated UNION ALL
> - apply the in-list afterwards as a filter
>=20
> the first two approaches can be prevented, and the third one can be force=
d.
> hope this helps,
>=20
> kind regards,
>=20
> Lex.
>

--
http://www.freelists.org/webpage/oracle-l