Re: Multiple parent design

The downside to this approach is that extensibility is difficult. In other words, every time I need to add a parent entity that can have a phone I would need to add two tables and adjust any database writes to save to two tables. This is similar to the solution whereby I create a "Parents" table that contains a combined list of Company id's and Person id's.

Thomas

<snip>

> Create two tables Companyphone and Personphone. Add check constraint
> "phone not in {the other table}". Create obvious foreign keys. Create
> view Allphone as Companyphone UNION Personphone.
Received on Fri Apr 16 2004 - 10:00:22 CDT