The number of companies I've worked out where I said, "We can do that in the database with a view or a trigger" to be followed up by "Sounds Hacky" or "How do you saved that to Version Control" is staggering though. Modern programmers seem to be afraid of SQL.
I see that objection a lot and it is just weird to me. You save it to version control like you do any other program source code. SQL is just text.
I'm conservative with triggers. They have their place, but can definitely be abused. The problem arises when someone doesn't realize they are there, and updates start having unexpected (to them) side effects. I'll tend to prefer a stored procedure that is explicit about doing the main update and any needed side-effects.
