Hi,
I wonder how people would handle this design:
family --- property/ address [1/many to 1]
family head of family [1 to 1]
family 2nd contact [1 to 0/1]
family ---other members [1 to 0/many]
family ---other stuff [1 to 0/many]
Note: property --- family [1 to 0/many] i.e
Consultant answer: Depends
OK, now that we have that out of the way, what do you mean by
family? These days, family has lots of permutations: dad's family,
mom's family, other mom's family...
I prefer this:
family - fam_link - persons
fam_link includes properties such as:
role
Maybe the design is wrong... g
In the sort of world we live in these days, a person maybe the head of
many families, ala dirty old man/village bike g
Sorry, I couldn't resist
Tristan
-Original Message-
family head of family [1 to 1]
Heya Andy.
I would have at least a people table - with a few extra columns -
family head specifier - 0 if head of family, 1 if not
family id - contains 0 if a head of family
- contains the primary key of the family head record .
If you don't want to add columns in a table, then you could
make
4 matches
Mail list logo