Re: db design question

From: Peter Johal <>
Date: Sun, 16 Mar 2003 22:56:02 +0100
Message-ID: <b52rpm$oaj$>


Using this model, you can only link a customer to an employee if there is a plan. You could introduce an Account entity, which links customers to employees, and base plans on that entity.

Also, don't you want to model types of plans, rooms and codes? And then make the plans, rooms and codes themselves into intersection entities.


t <> schreef in berichtnieuws sgqca.222883$
> I'm relatively new to db design. So I'm just gonna throw this out to
> I have the following database dependencies:
> employees->->customers
> customers->->plans
> plans->->rooms
> rooms->->codes
> -a room only has one plan
> -plan only has one customer
> -a code only has one room
> i am having trouble trying to normalize those relations.
> would this be very far off design?
> employees(*empID, username, etc)
> customers(*custID, customerName, etc)
> plans(*planID,custID,empID, planName, etc)
> rooms(*roomID,planID, roomName, etc)
> codes(*codeID,roomID, codeName)
> this design allows me to keep track of which employee has what customer
> plan. Since every plan is unique, rooms and codes can be retrieved as
> if you need more information, don't hesitate to ask. i really appreciate
> the help.
Received on Sun Mar 16 2003 - 22:56:02 CET

Original text of this message