Re: Help with Stored Procedure [Basic]

On Mar 05, 1996 15:56:45 in article <Re: Help with Stored Procedure [Basic]>, 'bfntd_at_aimnet.com (Tony Damon)' wrote:    

>There has been some discussion here lately that if your access
>permissions for the table were enabled thru a role then they will
>not be enabled in a stored procedure. The permissions will have
>to be explicitly granted for them to work in a stored procedure.
>
>If this is true, does anyone have an explaination for this behavior?
>
>Tony Damon
 

This is a security feature of Oracle. Say you have a user, Joe User, and you don't want him to have select, update, etc on all the tables, but you do want him to be able to run a program that updates the tables. In other words, you don't want him personally going into SQL*plus and screwing with the tables. Then what you do is implement the program using PL/SQL. Compile the PL/SQL under an account that has select, update, delete, insert on the tables. Then give Joe User a separate account which has execute permissions on the PL/SQL procedures. Now the only way Joe can update is by using the PL/SQL. Pretty nifty, huh?  

Amy Received on Wed Mar 06 1996 - 00:00:00 CET