How we use migration scripts in V4: We have a shared database that we develop on. When new features are implemented the changes are checked in. We might make a number of changes relating to a number of different features. When it comes to testing these changes we use a migration script to update a test copy of the production environment. This migration script is generated by picking the committed changes we want to include. Assuming the changes pass testing then the same script is used to update the production database. Out test and production databases aren't linked to source control but I guess they could be.
Anonymous
supported this idea
·
How we use migration scripts in V4: We have a shared database that we develop on. When new features are implemented the changes are checked in. We might make a number of changes relating to a number of different features. When it comes to testing these changes we use a migration script to update a test copy of the production environment. This migration script is generated by picking the committed changes we want to include. Assuming the changes pass testing then the same script is used to update the production database. Out test and production databases aren't linked to source control but I guess they could be.