RE: Restricting procedure calls to a package
- From: "Mercadante, Thomas F (LABOR)" <Thomas.Mercadante@xxxxxxxxxxxxxxxxx>
- To: <asahoshi@xxxxxxxxxxxxxx>, <Oracle-L@xxxxxxxxxxxxx>
- Date: Thu, 6 Apr 2006 08:00:14 -0400
John,
I agree with Jared. Write some wrapper procedures that calls the
procedures within the package as separate units and grant these procs to
the users.
For example:
If the original package has three procs in it (one for insert, update
and delete), write three additional procedures that call each of the
other procs directly. Grant these procs to the users.
Good Luck!
Tom
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of John P Weatherman
Sent: Wednesday, April 05, 2006 6:30 PM
To: Oracle-L@xxxxxxxxxxxxx
Subject: Restricting procedure calls to a package
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
very. I know I could control it with table level grants, but as PL/SQL
ignores roles, that means I have to maintain very large permissions
lists on every user. There has to be a better way (shy of my writing a
bunch of additional code to handle user adds and mods).
Thanks,
John
--
John P Weatherman
Oracle DBA
Madison River Communications
jweatherman91@xxxxxxxxxxxxxx
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
