--- In php_mysql@yahoogroups.com, John Magee <jema...@...> wrote:
>
>
>
>
> On 5/21/10 10:26 AM, "pirate_lenny" <piratele...@...> wrote:
>
> >
> > *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?
> It dpeends on how much you have to change...develop the code and database
> changes on a test server and then upload them when you are sure they're
> fixed.
>
> All depends on how much database is broken and needs fixing and how old the
> site is - maybe the entire site re-design occurs and you just incorporate it
> into the relaunch.
>
> Bad relationships are 'workable' but usually they make sites work much
> slower
>
Where my problem lies is that there are content editors working on the site
daily. So, I'm trying to figure out a way to fix the site while not
interrupting their work. And some of the changes that I need to make in the way
updates are made and data is displayed are fairly extensive.
