From 1f765a2f720c63b8b0e937a100837d27731719aa Mon Sep 17 00:00:00 2001 From: Jason Noble Date: Sat, 3 Dec 2011 19:10:49 -0700 Subject: Re-word confusing section --- railties/guides/source/migrations.textile | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'railties/guides') diff --git a/railties/guides/source/migrations.textile b/railties/guides/source/migrations.textile index ee0aa1d0f1..2654b43cad 100644 --- a/railties/guides/source/migrations.textile +++ b/railties/guides/source/migrations.textile @@ -163,10 +163,9 @@ allows Rails to handle common situations that occur with multiple developers. For example Alice adds migrations +20080906120000+ and +20080906123000+ and Bob adds +20080906124500+ and runs it. Alice finishes her changes and checks in her -migrations and Bob pulls down the latest changes. Rails knows that it has not -run Alice's two migrations so +rake db:migrate+ would run them (even though -Bob's migration with a later timestamp has been run), and similarly migrating -down would not run their +down+ methods. +migrations and Bob pulls down the latest changes. When Bob runs +rake +db:migrate+, Rails knows that it has not run Alice's two migrations so it +executes the +up+ method for each migration. Of course this is no substitution for communication within the team. For example, if Alice's migration removed a table that Bob's migration assumed to -- cgit v1.2.3