Hey guys - this isn't strictly java related, but....
As part of our project, we're releasing 'live' systems for the client at
short 2 week iterations or so (or trying to). However, as the project
grows, the db structure is slightly changing (adding new tables, adding
reference fields from existing tables to new ones etc. etc. etc.
I was wondering what 'best practises' there were out there managing
db-schema versioning, for updating one db schema to another, without loss
of data.
We're using an inhosue modelling tool (well, its more a sourceforge project
of mine) that generates our sql schema, DAO objects, and generic backend
stuff, and am looking to extend it to create "diffs" between two models,
and generic the requred alter table/create table stuff, and provide for
custom user processing of data (i.e., field x needs be 1/2'd, field y needs
to be split into field y1 and y2, before deing dropped) etc. etc.
I was wondering how other people have handled this in the past, weather
anyone knows of any existing projects/products to handle it etc. etc...
(target db is postgres, and running under linux if it matters).
Mark
-- \m/ --
[EMAIL PROTECTED] - ICQ: 1934853 JID: [EMAIL PROTECTED]
____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm
Be respectful! Clean up your posts before replying
____________________________________________________
- [jdjlist] Re: SQL Schema version/maintenance Mark Derricutt
- [jdjlist] Re: SQL Schema version/maintenance Tomm Carr
- [jdjlist] Re: SQL Schema version/maintenance M.Francis
- [jdjlist] Re: SQL Schema version/maintenance Tomm Carr
- [jdjlist] Re: SQL Schema version/maintenan... M.Francis
- [jdjlist] Re: SQL Schema version/main... Tomm Carr
- [jdjlist] Re: SQL Schema version/... Jason Bell
