aboutsummaryrefslogtreecommitdiffstats
path: root/railties
diff options
context:
space:
mode:
authorJason Noble <perlwizard@gmail.com>2011-12-03 19:21:08 -0700
committerJason Noble <perlwizard@gmail.com>2011-12-03 19:31:44 -0700
commit82ba3a79bf19d1d6d0a596914bbbcfaefa251874 (patch)
treeaabb8f4b16d5402b7ee5386add93843064794996 /railties
parentd8c8bf5f05f50ef5e4709941bcb7a7ab97e44cee (diff)
downloadrails-82ba3a79bf19d1d6d0a596914bbbcfaefa251874.tar.gz
rails-82ba3a79bf19d1d6d0a596914bbbcfaefa251874.tar.bz2
rails-82ba3a79bf19d1d6d0a596914bbbcfaefa251874.zip
Move this into a section so that "Resetting the database" will show up in TOC
Diffstat (limited to 'railties')
-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