Subject Database level triggers
Author Chris Meelhuysen
I'm new to the workings of Firebird so excuse this if its a repeat of an old

I just saw an article about generic triggers, but I don't think it meant the
same as what I'm asking about.

Would it be possible and is it helpful to have Database level triggers. As
before any insert no matter what table or before any update or any delete.
I just see this useful to reduce triggers that are used in multiple tables.
Such as I want to set up a database after update trigger so that if a user
does an update to no matter which table I can put an entry in a log that
they did an update, rather then having to put that trigger on every after
update for every table.

Also, if such a procedure passed in the table that was actually being worked
on I could further say if table is in (tasks, calls, assignments) then
update activity and show that someone was updating their work load.

Does this idea make sense? Is it a new one? Does it have merit?