kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

Re-word confusing section

Browse source
This commit is contained in:
Jason Noble 2011-12-03 19:10:49 -07:00
parent c8f8ecfd38
commit 1f765a2f72
1 changed files with 3 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
railties/guides/source/migrations.textile
View file

@ -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 For example Alice adds migrations +20080906120000+ and +20080906123000+ and Bob
adds +20080906124500+ and runs it. Alice finishes her changes and checks in her 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 migrations and Bob pulls down the latest changes. When Bob runs +rake
run Alice's two migrations so +rake db:migrate+ would run them (even though db:migrate+, Rails knows that it has not run Alice's two migrations so it
Bob's migration with a later timestamp has been run), and similarly migrating executes the +up+ method for each migration.
down would not run their +down+ methods.
Of course this is no substitution for communication within the team. For 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 example, if Alice's migration removed a table that Bob's migration assumed to