Class::DBI provides triggers in a database transparent way.

Although transaction support doesn't really fit the way it works, it does function and you can use it.

As a bonus, instead of using triggers to sold the original posters problem, you _could_ subclass it and override the class methods for creating, deleting and updating objects.