> >PLAYER_PARENTS
> >--
> >PlayerID (link to PLAYER.PlayerID)
> >ParentID (link to PARENTS.ParentID)
>
> This table is necessary if player can have more than two parents.
> Otherwise, I would add two fields to table PLAYER referring to
> CONTACTS.

Ah, could be true.

But ... in case of only 1 parent known: this will lead to a NULL
in table PLAYER. This could mean two things: no parent, or
parent unknown. Given that NULL means two things these days,
I tried to avoid them.

Alternatively, we could use this table to add not only parents
but also - dang, gotta to find the English word for it - people
who take care of the kid but aren't the real parents.
Obviously, a column "relation_type" would be in order then
(if we don't want to have other tables instead, like "PLAYER_CARETAKER")
(isn't a caretaker someone who does funerals? ah well, you get the idea)

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com