> Say you've got a COURSE table that represents many courses. New courses will
> always be being added to the table. Each course will have many quizzes and
> questions that need to be stored. You would not want to have a single QUIZ
> table with a composite key of COURSE_ID and QUIZ_ID because potentially this
> table would become prohibitively large, correct?
What is prohibitively large? 10 million? 100 million?
> Also, each quiz will have
> many questions, stored in a QUESTION table. This even more so would become
> prohibitively large if you stored questions for every quiz in every course
> in one table. Sooo, you would want a QUIZ table and QUESTION table for each
> course, correct?
No. Generally speaking, databases scale better in the number of
rows per table as in the number of tables per schema. One course
table, one quiz table, one question table.
Jochem
--
Who needs virtual reality
if you can just dream?
- Loesje
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
