Design question

  • Hi Everyone,

    I'm working on a database design and had a couple questions.  First, let me say that I am not an architect or DBA I'm just pretending to be both right now.

    I have a table called Resume that I need to link up to contact information for a user.  So I have a FK in the Resume table to the ContactInfo table.  In the ContactInfo table I have a FK to the Address table.  Next I have a AddressPhone table that has a FK to the Address table and to a PhoneType table.

    The purpose of this is to allow users to enter as many different types of phone numbers as they wish.  I don't want to limit them to something like home, work and cell.

    Is there a better way to set this up?

    Thanks,

    Wes

  • Sounds good to me so far, but why are you relating phones to addresses rather than phones to people? Mobile phones aren't address-based, and when people move they can often move their phone numbers with them. So there's no reason to logically link them to an address.

    --
    Adam Machanic
    whoisactive

  • Yup I agree with you.  Since I posted this question this morning I have changed it to hang off of the contact info.  It can't hand off people because I want each person to be able to create multiple contact info entities (stand alone) and then just associate one with their resume.  This gives them the most flexibility.

    Thanks,

    Wes

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply