Re: Materialized View

From: joel garry <>
Date: Fri, 18 May 2012 09:11:43 -0700 (PDT)
Message-ID: <>

On May 18, 5:14 am, "Gerard H. Pille" <> wrote:
> ddf wrote:
> > On May 17, 10:52 am, Mladen Gogala<>  wrote:
> >> On Thu, 17 May 2012 09:35:42 -0700, ExecMan wrote:
> >>> This is all done in a PL/SQL procedure.  Sorry if I did not indicate
> >>> that before........
> >> You're creating a materialized view in a PL/SQL procedure?
> >> --
> > Using EXECUTE IMMEDATE.  The PL/SQL variable you are trying to pass in
> > the execute immediate text does not exist in the SQL context you
> > create with the execute immediate call -- thus it's out of scope for
> > SQL as it has no idea what you are referring to.  It's basically the
> > same talking on the telephone to someone across town and saying 'Did
> > you see that?' while looking at an event outside of your window; the
> > person across town doesn't have your viewpoint and can't relate to the
> > question or the subject of it.
> > David Fitzjarrell
> You're wasting your precious breath, David, if the man doesn't realize he's switching from
> PL/SQL to SQL when calling "execute immediate" ...

It really isn't obvious what is PL and what is SQL, everyone has to be edakated about it. The grammar isn't always explicit about what is procedural and what is not. For example, AVG is a PL/SQL keyword, can be used as an aggregate, and can be used in analytics. But not always, like in ADRCI. There's something new I learned today.


-- is bogus.
When all is going to fail, blame your predecessor:
Received on Fri May 18 2012 - 11:11:43 CDT

Original text of this message