AegisSailor
05-02-2006, 09:39 AM
Greetings friends and neighbors!
Knowing very little about proper database design, I thought I would ask you experts in the crowd.
Suppose - just suppose - I were running a fan fiction site where hundreds of authors were to post their stories, anywhere from 3000 to 150,000 words in length, broken up into however many chapters the author decides.
In terms of efficient database operation, what is the best way to store these chapters, given that there could be hundreds of different stories of varying lenght?
The obvious solution is to create a table for all stories that has, say, 75 chapter fields. This seems wasteful because what if a certain story has only 20 chapters? Or One? And how does a table with that many LARGE fields effect the database?
The only other option I can think of is to have a table for all chapter 1's, all chapter 2's, all chapter 3's, and so on. This seems counter-intuitive to me, but perhaps that is easier on the database engine?
It's important to note that I would like the site to support many simultaneous users.
I appreciate your help! My database experiance is limited to MS Access, so you can see why I'm worried about a poorly performing database!
Thanks again,
Roger
Knowing very little about proper database design, I thought I would ask you experts in the crowd.
Suppose - just suppose - I were running a fan fiction site where hundreds of authors were to post their stories, anywhere from 3000 to 150,000 words in length, broken up into however many chapters the author decides.
In terms of efficient database operation, what is the best way to store these chapters, given that there could be hundreds of different stories of varying lenght?
The obvious solution is to create a table for all stories that has, say, 75 chapter fields. This seems wasteful because what if a certain story has only 20 chapters? Or One? And how does a table with that many LARGE fields effect the database?
The only other option I can think of is to have a table for all chapter 1's, all chapter 2's, all chapter 3's, and so on. This seems counter-intuitive to me, but perhaps that is easier on the database engine?
It's important to note that I would like the site to support many simultaneous users.
I appreciate your help! My database experiance is limited to MS Access, so you can see why I'm worried about a poorly performing database!
Thanks again,
Roger