--- In php_mysql@yahoogroups.com, John Magee <jema...@...> wrote: > > > > > On 5/21/10 9:52 AM, "pirate_lenny" <piratele...@...> wrote: > > > Hi Shahu - > > > > See? I didn't want to bore you with the overall scope of my project and it > > turns out I'm giving too little info! > > > > I think what you suggest is what I'm looking for. And then I would create > > another table for all information about the play (such as synopsis, etc) > > that > > would relate to mainproperty in your example? > > > > Jeremy > > > > > Searching problems are almost always solved by normalizing the database > better...normalization SUCKS (in my opinion, it's the part of database > design I hate) but if you don't do it properly you most likely will run into > problems. > > It took me 2 years to solve a normalization issue I was working on to be > able to build databases like the 'standings / stats' type stuff available on > ESPN...and it just came to me one night while I was aobut to fall asleep. > > Gotta normalize before you build :) >
*sarcastically, although knowing you're right* Fine time you choose to tell me that!!! After the site is up and running and I'm cleaning up someone else's mess!!!!! That brings up an interesting question. How do you make changes to the structure and the way data is looked up without interrupting usage of the site? Do you write a script that updates the records when someone lands on a page with "un-updated" records? Or do you shut down the site for a couple of hours and update?
