RE: Privileges on Triggers
- From: "Koppelaars, Toon" <T.Koppelaars@xxxxxxxxxxxxxxxxxxxx>
- To: <wjwagman@xxxxxxxxxxx>, "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 1 Nov 2007 21:40:31 +0100
Bill,
Triggers are not directly executed by users.
Triggers are indirectly executed when the user executes a DML-statement (an
insert, update or delete statement).
So, there is no concept of 'granting someone execute on a trigger'.
Instead you grant someone to perform DML on a table (that has triggers attached
to it).
I don't see how creating a public synonym for a trigger could 'fix' a problem,
you were experiencing with regards to triggers executing or not.
Toon
-----Oorspronkelijk bericht-----
Van: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]Namens William Wagman
Verzonden: donderdag 1 november 2007 21:13
Aan: oracle-l
Onderwerp: Privileges on Triggers
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@xxxxxxxxxxx
(530) 754-6208
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
