Re: Single vs. Multiple DBs || Which way to go?

Hey John. Thanks for the candid reply -- basket weaving ;--) Re: scoring, yes, you're right, queries are sport dependent; i.e. if you're in the basketball section, basketball queries are run........... At this point in my development experience, creating an all sport scoring table is stretching it a bit. Based on a hockey report I created a few months ago, I understand how to create functional, albeit crude, single sport interfaces. Given the limited time frame I'm working with, using the single sport model is preferred -- because I've yet to learn the alternatives! In any case, the multi-db model is out of the picture for now. I'll just have to alias the table names and do the best I can to organize the table structure in a sensible manner. If you have any brainstorms about how to work with a multi-sport interface in a single db, let me know. I'm not looking forward to sifting through a 100 tables.......... Thanks, --Noah ----- Original Message ----- From: "John W. Holmes" <holmes072000@charter.net> To: "'CF High'" <noah@newminddesign.com>; <php-general@lists.php.net> Sent: Saturday, February 08, 2003 7:32 AM Subject: RE: [PHP] Single vs. Multiple DBs || Which way to go? > > 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/ > >