Re: Work Around for Mutating Trigger Error

Try this more advanced technique (its a design vision thing, but way more elegant than brute force triggers):

1. create a view layer onto of your schema
2. do all access via the view layer
3. use instead of triggers to do your work. These can't cause mutating/constraining table errors.

Obviously, this is not just a simple coding thing, it requires you to think about design and access of your database. But hey, that's what we get paid for ain't it. Thinking usually results in better stuff anyway should you do this or not.

Good luck Received on Thu Aug 02 2001 - 17:34:21 CEST