In Rails 2 in migrations there were only 2 methods:
down. They are
called on running migrations up and down respectively with rake tasks
rake db:rollback. In
up method of migration definition you had to write
code which is called only on running migration forward and in down - the code
which is called only on rolling migration back. For example, if you create table
on up you had to drop it manually on rolling back. Rails 3 produced us great method
change which allowed us to write there code which creates a table and drops the
table automatically on rolling migration back. This really great step forward
and thankfully it’s exist in Rails 4 still. But unfortunately there was a problem - you didn’t
have opportunity to say “don’t run this peace of code on down but run this
only on up”. So the solution was just to use old syntax. Since Rails 4 has released
there is a feature to fix this situation.
How would you write migration which should add new column on up and fill all records in table only on up, and only delete this column on down? I bet that in Rails 3 you would write it like this:
You had to avoid using
change method which allows to save some time.
For example, if you didn’t need to update column value immediately
after it’s adding you would cut this code down to like this:
And that’s it. On up it will add column to table and remove it on down. Much less code and it’s a profit.
Rails 4 provides us one more useful way to write what we need in one place:
Check out the original documentation.