code:Note that this is not necessary the optimal database design, even for the simplest case, but it is a simple one. In particular, the ways it uses ids and names could be further refined.select column, names, here
from skeletons
inner join region_to_skeleton using (skeleton_id)
inner join region using (region_id)
inner join time_period_to_skeleton using (skeleton_id)
inner join time_period using (time_period_id)
where region_name == "asia" and time_period_name == "modern"
quote:There are at least two ways to do this.
I'm confused about how the region and time period get from the drop down list over to the mysql code.
quote:I don't think the database is going to be that big. Not more than 100 collections, I'm guessing. I'm not really sure how many visitors. Not that many, since it would just be used by people studying or interested in skeletons and only occasionally or rarely when they do use it. Certainly not anything like the number of visitors Hatrack gets.
Originally posted by fugu13:
How much data is going to be on this site, approximately? I assume it won't need to be updated terribly often. Also, how many visitors are you hoping to accommodate?
quote:I'm not sure what you mean by that, unless you mean that I was focusing on the front-end and not the back-end.
Also, you're answering the opposite direction, Tom.