Solved

Problem with Database design. As is needs to use explode function etc, too much array processing:

Posted on 2006-07-09
7
226 Views
Last Modified: 2012-08-13
I need some design help for my database to manage a special kind of messaging system. its structured by sessions. Each session has 5 questions. So user one might initiate a session with user 2, with 5 simple questions simplified:

Whats your fav color? why?
where were you born?
etc..

user one sends the questions, with his answer already noted. Then user two puts his answers to each question and it is sent back, which user one can reply if he/she desires. Basically like a message thread of each question, but each one group by 5. I need each thread or session to be visible to under each user's account. I need help on an efficent structure for the database to keep track of all this data.
Can anyone offer any suggestions?


Each question has to be saved individually and asked to the responder. Then a message thread can initiate..


Table Sessions
_______________
I've gotten this far but I need something to organize the responses individually based on the question. The site asks the questions manually and individually rather than just pasting them up there and being an actual message board. Here is what I've come up with, please let me know if you can make it more efficent: (assume all answers are colors)
A Column:
Session ID: Primary key
userone e-mail: example@dot.com
usertwo e-mail: example2@dot.com
Questions asked: 12, 15, 19, 22, 10   (question numbers from another table)
Userone Answers: red10901blue10901green10901purple10901orange10901  (answers seperated by 10901, will be split into an array with PHP)
Usertwo Answers: green10901pink10901purple10901indigo10901lavender10901
Conversation timestamps userone: 11/27/05, 12/30/05  
Conversation responses userone: Thats interesting, I agree (answers seperated by comma, will be matched up with data)
Conversation timestampes usertwo: 11/28/05, 12/31/06
Conversation responses usertwo: blah blah, blah

Somehow it seems inefficent.. Like all the seperators and array processing that must occur.. Any suggestions to avoid the need for array seperators would help a lot..
0
Comment
Question by:stormist
  • 3
7 Comments
 
LVL 10

Expert Comment

by:ThaSmartUno
ID: 17070220
Table 1: (User)
UserID (PK, autoincrement)
SessionID

Table 2: (Email)
EmailID (PK, autoincrement)
UserID (FK)
Email

Table 3: (Questions)
QuestionID (PK, autoincrement)
Question

Table 4: (Question_Answers)
AnswerID (PK, autoincrement)
QuestionID (FK)
UserID (FK)

Table 5: (Converstation)
ConversationID (PK, autoincrement)
UserID (FK)
TimeStamp
Response

This is my suggestion
0
 
LVL 10

Expert Comment

by:ThaSmartUno
ID: 17070221
in Question_Answers ... you would also want an 'Answer'
0
 
LVL 10

Author Comment

by:stormist
ID: 17077037
If each conversation has several responses, wouldn't the conversationID have to stay static? Autoincrementing would change the conversation ID for each response, thereby having no means to track which responses are from which conversation?
0
 
LVL 10

Accepted Solution

by:
ThaSmartUno earned 500 total points
ID: 17077539
I guess you could have:

-- Conversation --
ConversationID (PK, auto)
StartUserID (FK)   ( these two would be optional )
StartTime

-- Conversation_Response --
ResponseID (PK, auto)
UserID (FK)
TimeStamp
Response
0
 
LVL 9

Expert Comment

by:cristi_2112
ID: 17114811
Hello,

I don't know why you should use Table 2 (Email). Could a user have several email addresses ?
If not, you could make :

Table 1: (User)
UserID (PK, autoincrement)
SessionID
Email (Indexed eventually)

Instead of your EmailID, you could use UserID...
Good luck.
0

Featured Post

Master Your Team's Linux and Cloud Stack

Come see why top tech companies like Mailchimp and Media Temple use Linux Academy to build their employee training programs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Build an array called $myWeek which will hold the array elements Today, Yesterday and then builds up the rest of the week by the name of the day going back 1 week.   (CODE) (CODE) Then you just need to pass your date to the function. If i…
Password hashing is better than message digests or encryption, and you should be using it instead of message digests or encryption.  Find out why and how in this article, which supplements the original article on PHP Client Registration, Login, Logo…
Learn how to match and substitute tagged data using PHP regular expressions. Demonstrated on Windows 7, but also applies to other operating systems. Demonstrated technique applies to PHP (all versions) and Firefox, but very similar techniques will w…
The viewer will learn how to dynamically set the form action using jQuery.

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question