T
TheMadDBA
Guest
A better way would be for the trigger to decide based on the data what to do (or make a business object and get rid of the triggers completely). Really this is easy enough for you to test... but it only disabled during the scope of that internal procedure. /*--- Triggers active here ---*/ RUN SomeIP. /*--- triggers disabled in SomeIP ---*/ /*---- Triggers active again ---*/ assign table.field = "ABC". PROCEDURE SomeIP: disable triggers for load of table. END.
Continue reading...
Continue reading...