It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
Database triggers are good. There are legitimate concerns about visibility and how they're used, but the most common complaint -- "you're putting business logic in the database!" -- ignores that the database already encapsulates and structures business logic to begin with.
Database triggers are good. There are legitimate concerns about visibility and how they're used, but the most common complaint -- "you're putting business logic in the database!" -- ignores that the database already encapsulates and structures business logic to begin with.
If all the triggers are nicely documented in your migration files and your test suite uses a real DB, why not really?