"Branching the database along with the code" (a classic worth resharing).

Branching the database along with the code

"Branching the database along with the code" (a classic worth resharing).

Note: this article and supporting code have been heavily simplified since their initial publication. If you’re doing all your development on the “master” branch, you’re not using git. It’s fine to stick to master if you’re only learning git, but soon you’ll have to dive into non-linear development. However, although git makes it very easy to quickly switch between branches while hacking on your Rails app, your app still connects to the same database in development no matter what branch you’re on . Why is this a problem? Well, suppose you’re developing a feature that required you to change the database schema. You’re doing this in a separate branch which we’ll call “feature”. Of course, on this branch you’ve written a migration and changed the model code to compensate for the schema change. So far so good. But, if you for whatever reason quickly switch to master to check ou...

Full article: http://mislav.uniqpath.com/rails/branching-the-database-a...

Tweets

@pat_shaughnessy » 09 Nov '12, 4pm
RT @thibaut_barrere: "Branching the database along with the code" [link] (a classic worth resharing).
@thibaut_barrere » 09 Nov '12, 3pm
"Branching the database along with the code" [link] (a classic worth resharing).
@hnfirehose » 08 Nov '12, 10pm
Branching the database along with the code: [link]
@usrjim » 09 Nov '12, 3am
Branching the database along with the code [link]
@PursueMobile » 08 Nov '12, 10pm
Branching the database along with the code [link]