Ian Bicking: the old part of his blog

Re: using native triggers

If you're writing an in-house app, or one targeted at only one DB, then putting the triggers in the DB can make sense (because you don't change databases often, as you pointed out). But if you're writing an app on top of SQLObject which you then want others to use with many different databases, it's nice to write the triggers once, rather than once for each potential target DB.
Comment on Re: Another plan: SQLObject 0.7
by Robert Brewer