I don't disagree, but another reason for using triggers and whatnot for audit trails is that if someone were to get direct access to the database (say, even a D

I don't disagree, but another reason for using triggers and whatnot for audit trails is that if someone were to get direct access to the database (say, even a DBA), application level audit trails are useless. Of course, the other side of the coin is that if someone has access to the DB, what's to stop them from just disabling the triggers themselves, right? In my case, triggers and constraints are a Good Thing(TM) because our DBs are touched by different applications running on different platforms (and hardware). Maintenance is actually easier with the database triggers and constraints in place, since shared data access libraries aren't feasible.