aboutsummaryrefslogtreecommitdiffstats
path: root/railties/guides/source/migrations.textile
diff options
context:
space:
mode:
Diffstat (limited to 'railties/guides/source/migrations.textile')
-rw-r--r--railties/guides/source/migrations.textile4
1 files changed, 3 insertions, 1 deletions
diff --git a/railties/guides/source/migrations.textile b/railties/guides/source/migrations.textile
index 5e4d948b24..8df721782c 100644
--- a/railties/guides/source/migrations.textile
+++ b/railties/guides/source/migrations.textile
@@ -586,7 +586,9 @@ Neither of these Rake tasks do anything you could not do with +db:migrate+. They
are simply more convenient, since you do not need to explicitly specify the
version to migrate to.
-Lastly, the +db:reset+ task will drop the database, recreate it and load the
+h4. Resetting the database
+
+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