4 ms·
Generally you would use an expand/contract migration pattern. You deploy a schema expansion so that both the new and old code will run, deploy the new code, an
by the_fury 12y ago
Generally you would use an expand/contract migration pattern.
You deploy a schema expansion so that both the new and old code will run, deploy the new code, and once the new code has been validated you deploy a schema contraction.
http://exortech.com/blog/2009/02/01/weekly-release-blog-11-zero-downtime-database-deployment/ http://exortech.com/blog/2009/02/01/weekly-release-blog-11-z...
- mcguire 12y agoThat's what I came up with, too. But it's still coupled: you can't "go back to a previous version of an app without having to also figure out what schema changes need to be made", post-validation, anyway.