diff options
| -rw-r--r-- | railties/guides/source/migrations.textile | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/railties/guides/source/migrations.textile b/railties/guides/source/migrations.textile index 3a20e84ddb..17d5c5aca2 100644 --- a/railties/guides/source/migrations.textile +++ b/railties/guides/source/migrations.textile @@ -58,7 +58,7 @@ end This migration adds a +receive_newsletter+ column to the +users+ table. We want it to default to +false+ for new users, but existing users are considered to have already opted in, so we use the User model to set the flag to +true+ for existing users. -NOTE: Some "caveats":#using-models-in-your-migrations apply to using models in your migrations. +NOTE: Some "caveats":#using-modelsin-your-migrations apply to using models in your migrations. h4. Migrations are Classes @@ -410,7 +410,7 @@ Neither of these Rake tasks do anything you could not do with +db:migrate+, they Lastly, the +db:reset+ task will drop the database, recreate it and load the current schema into it. -NOTE: This is not the same as running all the migrations - see the section on "schema.rb":#schemadumpingandyou. +NOTE: This is not the same as running all the migrations - see the section on "schema.rb":#schema-dumpingand-you. h4. Being Specific |