Re:PostgreSQL anti-patterns: read-modify-write cycles (2014)
by dexwiz on Wednesday December 21, 2016 @08:46AM
(#13228997)
You can check triggers, or any db changes, into version control. Usually is more a migration script like Active Record. And sometimes its more like a log of changes than a total current state, but its definitely doable.
[ Parent
| on HN ]
Re:PostgreSQL anti-patterns: read-modify-write cycles (2014)
by gerhardi on Wednesday December 21, 2016 @09:13AM
(#13229193)
Yes, I just see this kind of arguments coming from quite senior level engineers every now and then. I see the reasoning that application/system level logic should be kept separate from the database, but aggregations are a good example in my opinion of things that database engines are good at, and also as the aggregated data does not insert any new operative data/transactions this should be mostly fine.