G
gdickson
Guest
The internal procedure (where the DISABLE TRIGGERS FOR LOAD) is used, is being passed the table in question as a parameter. Currently the trigger only updates three fields, a date, time, and code. The thinking is that under certain conditions, those three fields need to be set differently than how the trigger would set them. This is the same table that is being updated by the calling procedure. Maybe that is obvious, but just to be sure... So are the triggers only disabled for the subset of time that the internal procedure is executing (it calls no other procedures), or are the triggers disabled from the point in execution of the statement, through the end of the internal procedure AND the end of the calling procedure? We are having discussions about better ways to implement what the business requested, but we are in a "if it ain't broke, don't fix it" kind of state. I am just trying to be sure it ain't broke, before we push it into production.
Continue reading...
Continue reading...