My first thoughts after reviewing your structure is that items like
"payment1, payment2, payment3" or "question1, question2, etc.. " should be
split up into separate tables. It depends upon how you are planning on
using the resultant data.
Can you guarantee that every user will have 15 Questions? Will their be
any duplication of Questions for multiple users, or are you positive that
every user will have 15 unique questions?
The same thought process goes for payment, text, image, sound, and video.
At 11:34 AM 08/28/2001 -0700, you wrote:
>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
