Re: Some database discussions...

How did the parent know to chain out to the child on which column to
ensure that there was no match and therefore it would be safe to remove
this parent row?

My problem with DB defined RI constraints is with the generic
non-descriptive error messages, and that the error handling doesn't provide
for cursor positioning and highlighting on relevant columns.

I may be missing something. For shops that implement DB defined RI
constraints, how do they handle user interface requirements (i.e. friendly,
meaningful error messages, cursor positioning on relevant columns, and
highlighting)?