|
From: Andy T. <an...@gm...> - 2004-11-18 04:07:07
|
On Wed, 17 Nov 2004 04:23:31 -0500, Leif K-Brooks <eu...@ec...> wrote: > I'm developing a web web application project which uses SQLObject for > the database connection. Everything's working great on my test system; > however, looking into the future, I can see that my project will have > updates released at some point, some of which will probably involve > changes to the database schema. > > If everyone upgraded straight from version A to version B, it would be > very simple: release a script that alters the database along with every > version and have the users run it. Unfortunately, some people will end > up going from version A straight to version D, which would end up giving > them a messed up database schema. > > How do other people handle upgrades to database schemas gracefully? > > With each release include a script which migrates the database from the previous version to the current version. If people need/want to skip a few intermediate releases they will still have to run all of the update scripts. That saves you writing several different upgrade scripts for each release. Regards, Andy -- From the desk of Andrew J Todd esq |
