Okay, okay... "disable" is too strong a word. The trigger still fires, but it just doesn't do anything. Via the USER built-in PL/SQL function, you can easily bypass trigger activity for a user. This example shows how.
File List:
disable_a_trigger_for_a_specific_user.sql
2Kb
Similar code
Dynamic trigger
(Popularity: ) : Write business rules using conditions (T-SQL), message texts (plain text) and actions (T-SQL) and store them in a database table. These rules will be automatically called by a general purpose trigger generated dynamically by the Software. Build "selective firing" into your database triggers
(Popularity: ) : PL/SQL example with narrative that illustrates how to build "selective firing" into database triggers via an outermost, enclosing conditional that evaluates user ID.
Code Library
) : Write business rules using conditions (T-SQL), message texts (plain text) and actions (T-SQL) and store them in a database table. These rules will be automatically called by a general purpose trigger generated dynamically by the Software.