> I'm attempting to organize a sport report site into working order. > > We've got approximately 100 tables, and I'm unsure whether to break the > info > up by sport (i.e. baseball, basketball, hockey, etc.) or to lump all the > tables in one db and prefix tables by their sport name (e.g. bk_scoring = > basketball scoring table).
How about just a "scoring" table that has a column on whether it's Basketball, Hockey, Basket-Weaving, etc? How similar are the scoring tables between sports? If the tables for each sport are the same, then keep them in one database and just have identifiers in the table that say what sport it's for. Do you normally run queries that combine sports? Or is it something like if a user is in the "basketball" area, then all of the queries will pull basketball related data? > On the surface, it would seem easier to use multiple dbs, but then again, > common tables, such as schools and coach_info would have to be duplicated > in > each db. That's not a good idea... ---John W. Holmes... PHP Architect - A monthly magazine for PHP Professionals. Get your copy today. http://www.phparch.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
