Re: Searching OO Associations with RDBMS Persistence Models

Robert Martin wrote:
There are some structural issues that can be interpreted as business
rules, but care should be taken. The fact that an Employee always has
an employer is a business rule. The fact that the Employer field of
the Employee table cannot be null is an integrity rule. The two
correspond, but are not identical.

Formally, both business rules and integrity rules are constraints.
Constraints are symbolic formulas with equality or inequality symbols.

.

Relevant Pages

  • Re: Searching OO Associations with RDBMS Persistence Models
    ... the Employee table cannot be null is an integrity rule. ... Constraints are symbolic formulas with equality or inequality ... Not every business rule can be expressed in ... traditional programming language to rule based system any day. ...
    (comp.object)
  • Re: Which database design is better
    ... > Ambigous DRI actions are possible. ... It would amount to a business rule that: ... -You must add an employee to a store before assigning a key employee. ...
    (microsoft.public.sqlserver.programming)
  • Re: circular relationships ok?
    ... (employee_id INTEGER PRIMARY KEY, ... The business rule is that each employee has a manager who is also an ... Cycles do not have unambiguous semantics. ...
    (comp.databases.theory)
  • Re: Searching OO Associations with RDBMS Persistence Models
    ... the Employee table cannot be null is an integrity rule. ... both business rules and integrity rules are constraints. ... Constraints are symbolic formulas with equality or inequality ... Not every business rule can be expressed in ...
    (comp.object)
  • Re: Searching OO Associations with RDBMS Persistence Models
    ... Constraints are symbolic formulas with equality or ... Not every business rule can be expressed in ... program business rules. ...
    (comp.object)