Having a bunch of grouped optional values in other tables adds a ton of maintenance and query complexity.
The "clear constraints" belong in business logic, whether in triggers at the database level or before queries get executed at the application level.
Now, splitting up tables can produce performance optimizations. I'm not saying to never do it. But it's a tradeoff that increases complexity.
Having a bunch of grouped optional values in other tables adds a ton of maintenance and query complexity.
The "clear constraints" belong in business logic, whether in triggers at the database level or before queries get executed at the application level.
Now, splitting up tables can produce performance optimizations. I'm not saying to never do it. But it's a tradeoff that increases complexity.