Re: Views inside views, execution plan & external WHERE clause
Date: 2 Jul 2003 00:37:25 -0700
Message-ID: <81511301.0307012337.7ab61684_at_posting.google.com>
-
[Quoted]
- Just ONE. because there is: SELECT func FROM DUAL
[Quoted] see that your understanding is wrong e.g. on: http://asktom.oracle.com/pls/ask/f?p=4950:8:380014022855969596::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:9808349898392,
[Quoted] You can also use SYS_CONTEXT instead of Your_Function.
[Quoted] 2. Why? This I didn`t test, please show us. BTW, if that is true It will be still better since my approach is doing:
Filter comlex data - the first,
Joins of single result - the second
3. They can say the same about Analytic functions, about Bulk Collect etc. if they don`t understand it.
Jan
>
> 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 Wed Jul 02 2003 - 09:37:25 CEST