But the transaction could be implicit. Or involving other tables that don't need the Transact row. Sounds like what you are really asking, is for statement-level triggers IMHO, rather than Transaction-level triggers, which can thus be table-specific, and insert the row if needed (although how to know if the row is needed? Implies having a built-in for the *current* transaction somehow). I've long wished for statement-level triggers in SQLite, as opposed to `FOR EACH ROW` ones. Been using the former in Oracle and PostgreSQL, and miss them in SQLite.