Re: changing db schema's after application deployment
- From: Thomas Hawtin <usenet@xxxxxxxxxxxxxxxxx>
- Date: Wed, 31 Aug 2005 19:00:13 +0100
Dave Brown wrote:
Anyway I started to think about what happens in the future when hopefully I have a user base and make changes to my application which require changes to the database. Say for example I add a new column to one of my tables, well I suppose in the startup code I can check for the existance of that particular column and create it if it isnt there already. Which led me to think rather than ship a already existing database, why dont I have a routine at startup that checks for the existance of a database, and creates it and then checks for the existance of each table/column.
Is this a common approach ?
It's usual to provide some kind of utility to create/upgrade databases.
After the first version, you might find it useful to have the code that creates the database create the version 1 schema and then upgrade that. You will have to go back and write the upgrade code anyway, so you might as well not duplicate the effort.
Tom Hawtin -- Unemployed English Java programmer http://jroller.com/page/tackline/ .
- Follow-Ups:
- Re: changing db schema's after application deployment
- From: Dave Brown
- Re: changing db schema's after application deployment
- Next by Date: Re: changing db schema's after application deployment
- Next by thread: Re: changing db schema's after application deployment
- Index(es):
Relevant Pages
|
|
