mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
adding Migration#change to the CHANGELOG
This commit is contained in:
parent
87124457e5
commit
db32b545da
1 changed files with 18 additions and 0 deletions
|
@ -1,5 +1,23 @@
|
||||||
*Rails 3.1.0 (unreleased)*
|
*Rails 3.1.0 (unreleased)*
|
||||||
|
|
||||||
|
* Migrations can be defined as reversible, meaning that the migration system
|
||||||
|
will figure out how to reverse your migration. To use reversible migrations,
|
||||||
|
just define the "change" method. For example:
|
||||||
|
|
||||||
|
class MyMigration < ActiveRecord::Migration
|
||||||
|
def change
|
||||||
|
create_table(:horses) do
|
||||||
|
t.column :content, :text
|
||||||
|
t.column :remind_at, :datetime
|
||||||
|
end
|
||||||
|
end
|
||||||
|
end
|
||||||
|
|
||||||
|
Some things cannot be automatically reversed for you. If you know how to
|
||||||
|
reverse those things, you should define 'up' and 'down' in your migration. If
|
||||||
|
you define something in `change` that cannot be reversed, an
|
||||||
|
IrreversibleMigration exception will be raised when going down.
|
||||||
|
|
||||||
* Migrations should use instance methods rather than class methods:
|
* Migrations should use instance methods rather than class methods:
|
||||||
class FooMigration < ActiveRecord::Migration
|
class FooMigration < ActiveRecord::Migration
|
||||||
def up
|
def up
|
||||||
|
|
Loading…
Reference in a new issue