3 ms·
I don't see any problem with evolving invariants over time as business requirements change. The point is to be clear about your invariants for any given release
by anonymousDan 4y ago
I don't see any problem with evolving invariants over time as business requirements change. The point is to be clear about your invariants for any given release.
- tabtab 4y agoWe usually put most "constraints" in the database. It's often a D.R.Y. violation to echo them in code.
- anonymousDan 4y agoAh, I think I understand your previous comment a bit better now. Yes it's a fair point about the best place to enforce the invariants.