Re: Views inside views, execution plan & external WHERE clause

From: Mikito Harakiri <mikharakiri_at_ywho.com>
Date: Tue, 1 Jul 2003 09:15:38 -0700
Message-ID: <IziMa.6$jL4.34@news.oracle.com>

"Jan" <janik_at_pobox.sk> wrote in message
news:81511301.0307010432.6bf03a85_at_posting.google.com...
> ...
> WHERE employe_id=(SELECT My_Package.Get_Employee_ID FROM DUAL)
>
> Before you execute the query you just set employee id via
>
> Set_Employee_ID
>
> so it does what you want:
>
> 1) Filter complex data
> 2) Join single results

Except that:
1. Potential SQL<-->PLSQL context switch per each tuple execution. 2. Optimizer not being able to combine 2 executions together and produce a good plan.
3. People looking into the code and asking: who designed this mess? Received on Tue Jul 01 2003 - 11:15:38 CDT