 | | | Subject: Re: Privileges on Triggers | Subject: Re: Privileges on Triggers 2007-11-01 - By Andrew Kerber
Back
Why would you need to grant execute or any other privilege on a trigger? It
is executed automatically when the corresponding dml is run on the table or
action is taken within the database. No privilege is needed outside those
granted on the table. I suppose you might need to put an alter privilege on
it to allow a non-privileged user the ability to change the trigger if you
really wanted to, but I cant think of anything else...
On 11/1/07, William Wagman <wjwagman@(protected)> wrote:
>
> Greetings,
>
> I have been playing around trying to grant execute on a trigger to a
> particular user. After playing with this for a while and reading docs I
> have come to the conclusion that execute on a trigger is not an allowed
> grant. Instead the access is given via a public synonym. For example,
> give the particular trigger, usera.trigger. If usera wants to allow
> userb to use the trigger it is sufficient merely to create a public
> synonym, create public synonym trigger on usera.trigger and user b will
> then be able to use the trigger. Seems to simplistic for me, is that
> correct or am I missing something?
>
> Thanks.
>
> Bill Wagman
> Univ. of California at Davis
> IET Campus Data Center
> wjwagman@(protected)
> (530) 754-6208
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
Why would you need to grant execute or any other privilege on a trigger?
It is executed automatically when the corresponding dml is run on the table or
action is taken within the database. No privilege is needed outside those
granted on the table. I suppose you might need to put an alter privilege
on it to allow a non-privileged user the ability to change the trigger if you
really wanted to, but I cant think of anything else...
<br><br><div><span class="gmail_quote">On 11/1/07, <b class="gmail_sendername"
>William Wagman</b> <<a href="mailto:wjwagman@(protected)">wjwagman@(protected)
.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left:
1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Greetings,<br><br>I have been playing around trying to grant execute on a
trigger to a<br>particular user. After playing with this for a while and
reading docs I<br>have come to the conclusion that execute on a trigger is not
an allowed
<br>grant. Instead the access is given via a public synonym. For example,<br
>give the particular trigger, usera.trigger. If usera wants to allow<br>userb to
use the trigger it is sufficient merely to create a public<br>synonym, create
public synonym trigger on
usera.trigger and user b will<br>then be able to use the trigger. Seems to
simplistic for me, is that<br>correct or am I missing something?<br><br>Thanks.
<br><br>Bill Wagman<br>Univ. of California at Davis<br>IET Campus Data Center
<br><a href="mailto:wjwagman@(protected)">wjwagman@(protected)</a><br>(530) 754
-6208<br>--<br><a href="http://www.freelists.org/webpage/oracle-l">http://www
.freelists.org/webpage/oracle-l</a><br><br><br></blockquote></div>
<br><br clear="all"><br>-- <br>Andrew W. Kerber<br><br>'If at first you
dont succeed, dont take up skydiving.'
|
|
|