![]() If there were a large number of schema changes or conversion scripts to manipulate the data, this can get really hairy. Since we can't overwrite the live data with test data, this involves manually re-creating all the schema changes. Where everything breaks down is the deployment to production. ![]() You end up with whatever test data the last developer to commit had on his sandbox server. Also, the data on the test server is inconsistent. ![]() We have a test (virtual) server that runs "release candidates." Deploying to the test server is currently a very manual process, and usually involves me loading the latest SQL from SVN and tweaking it. If we do that now, it will reload the database from SVN for each build. We're wanting to deploy a continuous integration development server that will always be running the latest committed code. Currently, developers will make a change to the SQL schema and do a dump of the database to a text file that they commit into SVN. It is their personal sandbox to do whatever they want. Each developer has a virtual machine running our app and the MySQL database. ![]() I've had a hard time trying to find good examples of how to manage database schemas and data between development, test, and production servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |