Lists Home |
Date Index |
If the question is schema the right place to capture constraints I think u nailed it in your post - however - given that constraints have validity periods I don't see database constraints supporting such a mechanism - whether that validity period is driven by a start date , end date or locale based or some other policies, etc is question for an individual application to anwser.
I was trying to address the part of being "wary of constraints" - to me constraints need to be enforced - would i opt for database constraints or declarative constraints based system or procedural constraints or processes - the anwser is it depends on the scenario - each come with tradeoffs.
for example consider the constraint the expiry date should be after effective date - in most scenarios that constraint holds true!
Michael Kay <firstname.lastname@example.org> wrote:
> The constraints are driven by the organizational policies. If the organizational policies require that employees must be over 16, then they need to be enforced.
That's precisely the assumption I was complaining about. If the MD of your subsidiary in Egypt tells you that he has just hired a 14-year-old tea-boy, then in most organizations that I know of it's not the job of the IT department to tell him he shouldn't have done that: IT is the servant, not the master. When the crunch comes, the tea-boy won't be fired (and even if he is, the IT system will have to record the fact).
The way to enforce an organizational policy on recruitment is by having a process for approving all hiring of employees, not by restricting the capabilities of the employee database.
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!