If you define defaults in your database, you should specify the defaults in your Enterprise Objects Framework application as well. As a result, the Framework may prevent subsequent updates to the object. A rule can verify that a value is in a proper format or is within an acceptable range. Whenever a value is inserted or updated, the database server verifies that the value conforms to the rule before it performs the operation. You should implement data validation in your Enterprise Objects Framework application whether or not you use database rules.
Many databases provide mechanisms to enforce relational integrity rules.
Enterprise Objects Framework also provides mechanisms for enforcing these types of rules. For example, you can specify delete rules for relationships in EOModeler. If you use database triggers and constraints, you will have to duplicate the logic in your Enterprise Objects Framework application. In some cases, the duplication won't hurt anything, but in other cases you have to provide special handling to avoid run-time errors. For example, suppose you have a constraint specifying that you can't delete a department if it still has employees.