Imagine a rails app that has two versions that developers need to support: 1.0 and 2.0. There are 2 database schemas: app-1, app-2.
After fixing a bunch of very important bugs in production (1.0), some junior developer named Bob switches the branch to 2.0 to implement a few features but somehow gets his app connected to the schema app-1 and does rake db:migrate As I understand, in that case the app-1 schema will be migrated to 2.0. Considering a fact that migrations are not always reversible, Bob is in trouble and instead doing useful work, has to restore the db schema. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/UzjmeqoPdcwJ. For more options, visit https://groups.google.com/groups/opt_out.
