Re:Fork Your Application's Data (Not Just Your Code)
by atomical on Thursday November 08, 2012 @05:04PM
(#4760132)
This isn't a setup issue. Don't work on more than one branch/feature at a time. It's a bad idea and not conducive to getting shit done.
Re:Fork Your Application's Data (Not Just Your Code)
by samspot on Thursday November 08, 2012 @06:49PM
(#4760539)
You act like we have a choice in the matter.
"Sorry, I can't look into your emergency production problem, I'm adding features to a blog."
Re:Fork Your Application's Data (Not Just Your Code)
by eggbrain on Thursday November 08, 2012 @05:53PM
(#4760328)
Git checkout -b "feature-1"
Git commit -am "Added feature 1, which included a migration"
Git checkout -b "feature-2-that-builds-off-feature-1"
Git commit -am "Added feature 2, which includes another migration"
Git checkout master
Broken (and with multiple migration files, even though I branched off for each new feature.)
Yes, but they happen. This seems like replying to someone drowning "well, you should have avoided swimming!"
You also make the assumption that we are using Rails (or some framework with migration support) -- many people won't have that luxury.
Finally, while the setup might be challenging (as in, figuring out a way to implement db tracking in git), I find it very curious that it would be much easier in anyones mind to do two tasks, doing all the rollbacks and switching branches, vs just switching the branch.