Configuration option to use triggers

MySQL requires the SUPER privilege in order to create and drop triggers. (Actually, since 5.1 this has only been required when binary logging is enabled.) This privilege violates basic security practices and makes shared hosting difficult, because it means that the db user will be able to affect other users and databases.

I propose that we make the triggers an optional feature, which can be disabled by a configuration variable. Ideally, there would be a way to generate a database migration script to add and update triggers, which can be executed manually.