Forum Moderators: mack
Tools: MySQL & PHP
Problem: The DB needs to hold 40 song samples every month. At the beginning of a new month, another 40 samples should replace the existing samples.
1. First off, the database should just reference the file locations right?
2. What would be the best way to build this database? Should I build one massive table with entries for each month? A seperate table for each month? Some other way?
3. Once created, would it be hard to use that database as the source for an online store? What types of considerations will I need to make before building it? Would it be worthwhile to just wait and purchase store front software?
Thanks for any help!
1. First off, the database should just reference the file locations right?
Right. Common practice, faster table lookups.
2. What would be the best way to build this database? Should I build one massive table with entries for each month? A seperate table for each month? Some other way?
One table would be fine. Are you really certain you want to replace your historical data every month? I'd leave it. Besides, the table won't be very massive. 12 months a year, 40 songs a month, 20 years = 9600 rows of data. That's nothing.
3. Once created, would it be hard to use that database as the source for an online store? What types of considerations will I need to make before building it? Would it be worthwhile to just wait and purchase store front software?
I don't think it would be hard to use that data at all. If you did need to populate a different table it would be quite easy to SELECT this existing data INTO the other tables.
