Managing development databases
Today I asked this question
My development team of four people has been facing this issue for some time now:
Sometimes we need to be working off the same set of data. So while we develop on our local computers, the dev database is connected to remotely.
However, sometimes we need to run operations on the db that will step on other developers' data, ie we break associations. For this a local db would be nice.
Is there a best practice for getting around this dilemma? Is there something like an "SCM for data" tool?
In a weird way, keeping a text file of SQL insert/delete/update queries in the git repo would be useful, but I think this could get very slow very quickly.
How do you guys deal with this?
I got many responses very quickly. When the dust settles, I'm going to write an update with my favorite answers. Until then, feel free to check out the page for yourself--or if you're up to it, post an answer.
Update: Rob Shedd posted the question on Hacker News
. Give that link a shot if you prefer HN over StackOverflow.
28 June 2010