above are entirely my own and not
those of my employer or clients **
> -Original Message-
> From: Kimberly Smith [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 11, 2001 6:40 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: DB Design and Views
>
>
> I
I would avoid views based on view. As well, I would avoid using views
where you will later turn around and throw a distinct or a group by
or anything else on it (especially if you are dealing with a lot of data).
Basically, You cannot be assured that the optimizer will pick the proper
path once t
Forget the optimizer, what about the developer?
This just doesn't seem like a good idea, or in
the words of Wayne Brady 'That is just wrong on
so many levels'.
Jared
On Tuesday 11 December 2001 04:30, Stefan Jahnke wrote:
> Hi,
>
> as I remember, it was always recommended to avoid the use of
Uh Oh ...
I have a forms application that is built on views that are built on views
that are built on views ... up to 5 levels deep. The fun part is we have to
go to CBO now ... and the tables underlying the views range from 10 rows
to 20M rows.
Talk about fun ...
Raj
__
