Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Almost every table in my DB has triggers that fire on INSERT, UPDATE, DELETE and write the changes to a separate read only DB. This makes it possible to track changes and undo things well after the...
#2: Post edited
- Almost every table in my DB has triggers that fire on INSERT, UPDATE, DELETE and write the changes to a separate read only DB. This makes it possible to track changes and undo things well after the fact, but also makes operations slower.
For changes that don't need an audit trail, **would it be possible to disable the triggers for only that query or that specific DB user?**
- Almost every table in my DB has triggers that fire on INSERT, UPDATE, DELETE and write the changes to a separate read only DB. This makes it possible to track changes and undo things well after the fact, but also makes operations slower.
- For changes that don't need an audit trail, **would it be possible to disable the triggers for only specific queries or specific database users?**
#1: Initial revision
In MySQL, is it possible to disable triggers for only certain queries or users?
Almost every table in my DB has triggers that fire on INSERT, UPDATE, DELETE and write the changes to a separate read only DB. This makes it possible to track changes and undo things well after the fact, but also makes operations slower. For changes that don't need an audit trail, **would it be possible to disable the triggers for only that query or that specific DB user?**