Re: Trigger blocking

Peter,

I think you have answered your own question about why it strikes me as unlikely it would ever be implemented at the system level:

A perfect block would be better and faster although the ability to block a trigger may have serious audit implications.

I have only used a read trigger when I needed to log access to sensitive data. As such, it seems like it could defeat the entire purpose if it was easy to temporarily disable the read trigger for a specific job. Not only would you need to lock down access to the method, but you'd also need very robust logging of each time it was disabled. And the log file would need to inhibit record updates and deletions too.

If you are already using a pointer you've resolved to a job user space, I suspect you are already as efficient as you are going to be able to reasonably make it. Trying to do more may be, as Barbara Morris has said about some performance enhancement techniques, like standing on a chair to get closer to the moon. (I've always loved that saying -- thanks again Barbara!)

Doug