User Name Password Register
DaniWeb IT Discussion Community
All
What is DaniWeb IT Discussion Community?
You're currently browsing the Database Design section within the Web Development category of DaniWeb, a massive community of 402,022 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,442 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Views: 992 | Replies: 1
Reply
Join Date: Jan 2007
Posts: 1
Reputation: whatnow is an unknown quantity at this point 
Rep Power: 0
Solved Threads: 0
whatnow whatnow is offline Offline
Newbie Poster

noob design help please

  #1  
Apr 12th, 2007
I am in the pen and paper stage of designing a database that I'd like to to turn into a web form and I'm kind of stuck by my lack of knowledge.

Aside from the typical contact info, the form will also collect whether the user wants to register with the site as a distributor, athletic director, player or fan (I work for a sports apparel mfg).

Would it be wise to have a contact table with minimal info (name and email(pk) only) with separate tables for dealer, director, player or fan and have the mailing info for each inside each table or should I have a contact table with all general contact info and then create a separate role table. I figured the role table could have an auto-incrementID(pk) and then role name so that additional roles can be added down the line. Or am I way out in left field not making any sense?

TIA for your thoughts and efforts.
AddThis Social Bookmark Button
Reply With Quote  
Join Date: Feb 2007
Location: London
Posts: 114
Reputation: davidcairns is an unknown quantity at this point 
Rep Power: 2
Solved Threads: 8
davidcairns davidcairns is offline Offline
Junior Poster

Re: noob design help please

  #2  
Apr 12th, 2007
I would not have separate tables at all (except in exceptional circumstances) and use a contact type field to define the kind of user involved. Having said that it depends on how different the info you need is on each type and how likely it is that types would be added/deleted/changed
Reply With Quote  
Reply

Only community members can participate in forum threads. You must register or log in to contribute.

DaniWeb Database Design Marketplace
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

 

Thread Tools Display Modes

Similar Threads
Other Threads in the Database Design Forum

All times are GMT -4. The time now is 10:08 pm.
Forum system based on vBulletin Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
©2003 - 2008 DaniWeb® LLC