db design question
From: t <tomcolumbia_at_hotmail.com>
Date: Fri, 14 Mar 2003 19:42:16 GMT
Message-ID: <sgqca.222883$na.10378076_at_news2.calgary.shaw.ca>
I'm relatively new to db design. So I'm just gonna throw this out to yall:
Date: Fri, 14 Mar 2003 19:42:16 GMT
Message-ID: <sgqca.222883$na.10378076_at_news2.calgary.shaw.ca>
I'm relatively new to db design. So I'm just gonna throw this out to yall:
I have the following database dependencies:
employees->->customers
-a room only has one plan
i am having trouble trying to normalize those relations.
would this be very far off design?
employees(*empID, username, etc)
customers->->plans
plans->->rooms
rooms->->codes
-plan only has one customer
-a code only has one room
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 and plan. Since every plan is unique, rooms and codes can be retrieved as well.