On Thu, 17 Aug 2006, Eric Stadtherr wrote:
Martin,
We're talking about the same structure, and I completely agree with you
about the contact_info->contact foreign key. I wouldn't include the
cascading delete on the second FK, though (the contact_info->types
reference), since the types contents should be relatively static and you
want the database to prevent you from deleting types if there are
referring contact_info rows.
Thoughts?
I agree with the fact that types should be a INSERT only table, but it a
type is deleted, what do you do with the contact_info? If you are saying
that if a type has been used in the contact_info table, you can't delete
it, then you are right: there shouldn't be a cascade.
--
21:50:04 up 2 days, 9:07, 0 users, load average: 0.92, 0.37, 0.18
---------------------------------------------------------
Lic. Martín Marqués | SELECT 'mmarques' ||
Centro de Telemática | '@' || 'unl.edu.ar';
Universidad Nacional | DBA, Programador,
del Litoral | Administrador
---------------------------------------------------------
