Hi,
I've been currently working on a couple of issues which demand changes in
the database.
As I worked to get these issues resolved, I've found that I had to go
through a lot of hoops when updating the database.
Here's the list of files that I'm referring to:
src/org/mifos/framework/persistence/DatabaseVersionPersistence.java
sql/latest-data.sql
sql/latest-schema.sql
sql/mifosdroptables.sql
sql/mifosmasterdata.sql
sql/upgrade_to_<database version>.sql
sql/downgrade_from_<database version>.sql
Is there not a better way of allowing for database changes?
As far as I understand it, the upgrade, downgrade, database versioning
notions are almost futile as they only consider schema changes and
wouldn't help on data migration.
I can't imagine they could be used effectively in a production
environment. So my question is, what is the point of having them around at
all?
Cheers
Chico
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
