Re: Materialized View
From: ddf <oratune_at_msn.com>
Date: Thu, 17 May 2012 12:48:52 -0700 (PDT)
Message-ID: <2d8a8537-0e14-4ba3-970b-1e1b6fd4b279_at_to5g2000pbc.googlegroups.com>
On May 17, 10:52 am, Mladen Gogala <gogala.mla..._at_gmail.com> 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?
>
> --http://mgogala.byethost5.com
Date: Thu, 17 May 2012 12:48:52 -0700 (PDT)
Message-ID: <2d8a8537-0e14-4ba3-970b-1e1b6fd4b279_at_to5g2000pbc.googlegroups.com>
On May 17, 10:52 am, Mladen Gogala <gogala.mla..._at_gmail.com> 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?
>
> --http://mgogala.byethost5.com
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 Received on Thu May 17 2012 - 14:48:52 CDT