RE: triggers within commit cycles

At 14:55 08/21/2001, Joe Pluta wrote:

>What would be nice is a way to set a flag in a job that says "bypass
>triggers"; if I had that level of granularity in my requests, I'd be very
>happy.

Actually, you can do that, sort of. I just finished a job where I needed to
suppress some trigger operations, and I used a status code in the new
record buffer to accomplish that. If I passed a lower case value, the
trigger would skip a section of code and then convert the status code to
upper case so that the expected value ended up in the database. It was a
little messy, but the best I could do within the constraints of the
application, which sometimes required file A's trigger to update file B,
and sometimes required file B's trigger to update file A. The application
code didn't need to know about it - just two trigger programs talking to
each other.


Pete Hall
pbhall@execpc.com
http://www.execpc.com/~pbhall/