> I'm wondering why you would keep the questions & answers in separate tables? Seems like an over complication for a simple question/answer scenario.
Quite a few simple reasons: 1)Not all questions will have the same number of answers associated with them: I have true/false questions as well as multiple choice questions. 2)I can reuse the same answers in multiple questions without data redundancy. 3)It could be worse: I could have 1 table containing questions, 1 table linking questions to sets of answers, 1 table linking sets of answers to answers, and 1 table of answers, which would result in a completely optimized and normalized database for holding large number of questions and answers. In that situation, each question could have multiple sets of answers and the same set of answers appear in multiple questions. I've already passed having 100 answers, but at this point I don't have enough questions to make the 4 table idea work [Plus I'm fighting an internal battle to keep it simple.]. But then, all I would have to do is rand() off the combination of question/answer set and I would get no duplicates. Community email addresses: Post message: [email protected] Subscribe: [EMAIL PROTECTED] Unsubscribe: [EMAIL PROTECTED] List owner: [EMAIL PROTECTED] Shortcut URL to this page: http://groups.yahoo.com/group/php-list Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/php-list/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/php-list/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
