4-1

In this question I was more concerned about lookup tables. Of course, for real parent and child we must have triggers in place. I do agree with having them for lookup as well, but want to find out the general practice.


>Nadya,
>
>The database must protect it's integrity via foreign keys. You have no control that your business layer will be the only way those tables are accessed. One accidental slip on an update or delete with no FK constraint in place and you are scrambling to try to recover the table.
>
>
>>We just had a discussion between developers about how do we usually handle lookup codes. E.g.suppose you have a table, which has several coded fields, which could be ever empty (NULL) or valid codes. Do you create a trigger (restrict) for Insert/Update/Delete or do you simply handle this in the application itself. Also I'd like to hear about your experience with different back-ends. I see advantages and disadvantages of both approaches and would really appreciate your input on the matter. So, basically I'm conducting a pool.