I think what you're getting at is that you're trying to consider both
'contactInfo' and 'entity' to be superclasses, with subclasses like
'phoneContactInfo', 'addressContactInfo', etc. and you'd like other tables
to have fields which reference the superclass. Inheritance relationships are
a common
Here's a design question similar to the current threads on normalization
issues.
Suppose I have three types of contact information I want to keep track of:
Postal address, phone, and email. The design is that any given entity
that has contacts info associated may have zero or more of each.
I al
