If you do it this way you will have to redesign your table every time you
make some small change and
it will be difficult to query the results (e.g. how many questions did
people answer ). What happens when you add a 16th question.
At a bare minimum I would make the following:
1. user table:
> userid
> userpass
> nickname
> lastname
> firstname
> email
> phone
> address1
> address2
> city
> state
> zip
2. Question table
QID PK
Question
3. Person_Question_XREF
userid
QID
Answer
(PK is combo userid and QID)
I don't know exactly what you are doing with payment but I would break that
out also.
Also I would break contact information out so person could have more than
one phone number, email etc.
In general if you take the time to make your design adaptable to change you
will simplify the maintenance of the application.
<shameless_plug_here>
Just as an example I recently launched a roommate matching service and wound
up with over 60 tables before I was done. Nothing is ever as simple as it
first appears
www.cyberroomies.com
</shameless_plug_here>
Don
Don Vawter
[EMAIL PROTECTED]
www.cyberroomies.com
----- Original Message -----
From: "Adrian Cesana" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Tuesday, August 28, 2001 12:34 PM
Subject: OT: DB design suggestion
> I need to build a "singles" database...After pondering a while it seems a
> single (no pun intended) table would be simplest to deal with, or would it
> be better to split the user information from the user details, looking for
> suggestions. The basic info I need would be (im sure I missed a few
> fields):
>
>
> userid
> userpass
> nickname
> lastname
> firstname
> email
> phone
> address1
> address2
> city
> state
> zip
> payment1
> payment2
> payment3
> question1
> question2
> question3
> question4
> question5
> question6
> question7
> question8
> question9
> question10
> question11
> question12
> question13
> question14
> question15
> text1
> text2
> text3
> text4
> text5
> image1
> image2
> image3
> image4
> sound1
> sound2
> video1
> video2
>
> Thanks! Adrian
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
