> I should add that there is also a set of database design wisdom that suggests you should never use database constraints such as foreign keys, only app/api con

> I should add that there is also a set of database design wisdom that suggests you should never use database constraints such as foreign keys, only app/api constraints, but that's a whole different tangent. That’s less a DB design thought and more of a “devs with little formal training in RDBMS who only want to use it as a dumb store” thought. Use the DB to its strengths. CHECK constraints add an infinitesimal amount of overhead for writes, and guarantee that there will never be invalid data written. A bad code change could allow, however briefly, for that to occur.