[integrityfirstauto]

Hi all;

I am getting to the stage with my project where preserving my data in my
database is becoming critical yet my model isn't entirely stable.

I need to be able to preserve data - what I would call metadata - like
Cities, States, etc. I'd also like to be ship datafiles to customers with
this kind of data in it. What are you guys doing to manage this kind of
problem?

I'm guessing I should have two EcoSpaces with two models. One 'stable'
model that I keep the meta data in and the main product's 'production' model
that can change. Then write code to move data from one to the other as I
need to backup/restore data.

Do I have the right idea? Any other ideas? Any easy/dirty tricks??!

Thanks!

Damian

[Peter Morris]

At the moment I am in the fortunate position to be able to apply migrations
myself as I write apps for a single customer. When this was not the case
(when I developed in Win32 using Bold) I would do this

01: After release backup the DB
02: Do all of my development
03: When ready to release I would restore the DB
04: Get the SQL script for migration
05: Apply this script to the DB in a "ServerInstall.exe" application.



Pete