> Jeff Wolfe-3 wrote: >> >> As a related note, since we now have a fielded product, does Sculptor have >> a >> philosophy on how to do a database upgrade? We can't actually rerun run >> the >> DDL directly because it would whack a lot of customer data. We've kicked >> around ideas ranging from hand writing alter scripts to exporting and >> reimporting the DB every time. >> >> Thanks, >> Jeff >> >> > > Database migration is an interesting topic. I would love to support it in > sculptor in some way in the future, but it is not easy. Any ideas of how to > do it are welcome.
>From DSL you don't know "semantic" meaning of change. For example you rename column in DSL. Is it renamed column? Is it new column. Old column have to be removed? Answer is unclear if you look into DSL. And we don't speak about more comples cases like, you move columns to other entity with 1->N relation. Another problem is that in dev env you can do more iterations till you release final version. Applying N scripts to upgrade production database is usually very bad idea. This are reasons, why I guess, that creating such incremental script is impossible to implement. Only one reliable way exist: write and tune it by hand. Pavel ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
