Re: Restricting procedure calls to a package

If you make it private then no one will be able to execute the code.

The only way to execute it would be from other calls within the package body.

You can create wrappers to individual functions and procedures, and grant permissions on those.

There's a lot of new features in PL/SQL, so perhaps there is some other way to approach this. Might require some manual perusal. (pun intended)

Jared

On 4/5/06, David Sharples <davidsharples_at_gmail.com> wrote:
>
> if all there code is all self evneloped inone package then make everything
> private apart from some functions which you can delcare in the spec which
> the users can access
>
>
> On 05/04/06, John P Weatherman <asahoshi_at_infionline.net> wrote:
> >
> > All,
> >
> > I may well have been reading the Wrong FM, but I haven't seen this
> > explicitly ruled out anywhere either. Is it possible to grant execute
> > on only selected procedures within a package or is it an all or nothing
> > deal. My developers have managed to code functional units so that all
> > the select/insert/update/delete code is in the same package and they
> > won't break it out...but the end users who can perform these functions
>
>
>

--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

--
http://www.freelists.org/webpage/oracle-l