aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/migrations.md
diff options
context:
space:
mode:
authorJohn Gallagher <john@synapticmishap.co.uk>2012-10-27 21:54:44 +0100
committerJohn Gallagher <john@synapticmishap.co.uk>2012-10-27 21:54:44 +0100
commitc570ba70fe6ed53fd1ac5f30f0c9ba4cb7cd4796 (patch)
treee1c2f333d7b7d6f7d74a44b8627018e6a481ea6a /guides/source/migrations.md
parentcc81af2fe438fd3e2c8f95dae8f757de0bab1b53 (diff)
downloadrails-c570ba70fe6ed53fd1ac5f30f0c9ba4cb7cd4796.tar.gz
rails-c570ba70fe6ed53fd1ac5f30f0c9ba4cb7cd4796.tar.bz2
rails-c570ba70fe6ed53fd1ac5f30f0c9ba4cb7cd4796.zip
Changed comment section to be more explicit. I had an issue with rolling back a migration and couldn't understand why 'rake db:reset' didn't work.
Diffstat (limited to 'guides/source/migrations.md')
-rw-r--r--guides/source/migrations.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/guides/source/migrations.md b/guides/source/migrations.md
index 3eeb45f8c6..314ee3f5cd 100644
--- a/guides/source/migrations.md
+++ b/guides/source/migrations.md
@@ -684,8 +684,9 @@ version to migrate to.
The `rake 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](#schema-dumping-and-you).
+NOTE: This is not the same as running all the migrations. It will only use the contents
+of the current schema.rb file. If a migration can't be rolled back, 'rake db:reset'
+may not help you. To find out more about dumping the schema see [schema.rb](#schema-dumping-and-you).
### Running Specific Migrations