Re: Understanding EXECUTE IMMEDIATE

From: Jim Kennedy <kennedy-downwithspammersfamily_at_attbi.net>
Date: Tue, 27 Sep 2005 18:47:12 -0700
Message-ID: <VcCdnYOnd6xRaKTeRVn-tg@comcast.com>

"pbewig_at_swbell.net" <pbewig_at_gmail.com> wrote in message news:1127824608.996908.199810_at_g47g2000cwa.googlegroups.com...
> Again, I'm not executing insecure code entered bya user during the run
> of the program. I'm executing trusted code written by a programmer as
> part of a PL/SQL client.
>
> To my lispish eyes, EXECUTE IMMEDIATE looks a lot like eval. But I am
> learning that it's not. The only environment that EXECUTE IMMEDIATE
> can see is the database; it can see nothing in the enclosing PL/SQL
> program.
>
> That means my client code will have to store the called-back procedure
> in a known place in the database, so that the package can call it when
> needed.
>
> Phil
>

Phil,
Stop fixating on the solution. State what the problem is that you are trying to solve and I am sure we can give you a reasonable solution. Jim Received on Tue Sep 27 2005 - 20:47:12 CDT