[lelanthran]

Yes, and isn't it wonderful that you get an error message when you try to change a business rule, forcing you to properly encode the new rule instead?

A lot of these types of scenarios are missing the fact that, without these enforcements in the database, sooner or later a developer is going to make a change that violates an existing business rule without realising that they just broke a rule!

Rules change. We know this. What is valuable is being told that some new rule conflicts with an existing rule.

If you don't enforce the business rules in the database, how do you know when a new rule conflicts with some existing rule?