This is not one of the functions of EOModeler. Its focus is modeling
the mapping between enterprise objects and external data stores. There
is a schema syncrhronizaiton function that works for some databases.
I've never trusted it for the sort of thing you are describing. Best
keep to the old ways for schema migration.
Chuck
On Apr 30, 2004, at 6:48 PM, Bob McCormick wrote:
In pre-EOM days, I would simply add my changes to a SQL script and
when it was time to move to the next revision, we'd just apply that
script to the production database. I could maintain the script
manually, or I also had a tool that would perform a diff against the
two structures' meta data and write the script for me. Was really
simple to work in a test environment and then keep scripts with
version numbers to bring a database up to the latest 'shipping'
version.
Have not a clue how to do this in EOM, so wondering if anyone could
clue me in on the best way to do something like this.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
