Re: How to prevent all failures of database triggers?

Nick Todd (ssl_at_aladdin.co.uk) wrote:
: Any ideas on how to avoid this? I've tried wrapping up the code in a
: stored procedure but his doesn't seem to help. I've a horrible feeling
: that the only way to get around this problem will be to use the
: DBMS_SQL package and parse my DML at run-time.
Have you tried creating stored procedures that perform the initial table updates? These can be compiled and have access to the table as user A, but access to the procedure can be given to user B, who would not normally have write access to the table in question.

I wish you had included more details in your post, but I think that this approach might be something that you can build on. I am presuming that your initial post referred to putting the trigger code into a procedure, rather than the actual write to the table. If it referred to what I have suggested, I am afraid that I cannot help you.

One question that I do have for you is this: Is the trigger actually causing the error, or is the update/insert failing because the user does not have the proper grants on the table? My suspicion, from what you've written, is that the latter is occurring. Again, I don't have enough information to be more concrete.

If there is anything I can do to help out, please send me mail and I will respoind as quickly as possible.

Jonathan Received on Sun Sep 24 1995 - 00:00:00 CEST