diff options
author | Vijay Dev <vijaydev.cse@gmail.com> | 2013-08-31 00:49:27 +0530 |
---|---|---|
committer | Vijay Dev <vijaydev.cse@gmail.com> | 2013-08-31 00:49:27 +0530 |
commit | ab0cbff07ebb5df8c9354fa2b3fd9984e039d2c6 (patch) | |
tree | ead7b55d9f8025b5608338278ad03ee809244535 /guides/source/migrations.md | |
parent | 15455d76c8d33b3767a61e0cdd2de0ff592098ef (diff) | |
parent | 3bcecf8258d6b63ded2714672f92ad767423e41f (diff) | |
download | rails-ab0cbff07ebb5df8c9354fa2b3fd9984e039d2c6.tar.gz rails-ab0cbff07ebb5df8c9354fa2b3fd9984e039d2c6.tar.bz2 rails-ab0cbff07ebb5df8c9354fa2b3fd9984e039d2c6.zip |
Merge branch 'master' of github.com:rails/docrails
Diffstat (limited to 'guides/source/migrations.md')
-rw-r--r-- | guides/source/migrations.md | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/guides/source/migrations.md b/guides/source/migrations.md index 6100fc89c8..414ce46a4e 100644 --- a/guides/source/migrations.md +++ b/guides/source/migrations.md @@ -692,10 +692,15 @@ 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. +### Setup the Database + +The `rake db:setup` task will create the database, load the schema and initialize +it with the seed data. + ### Resetting the Database -The `rake db:reset` task will drop the database, recreate it and load the -current schema into it. +The `rake db:reset` task will drop the database and set it up again. This is +functionally equivalent to `rake db:drop db:setup`. 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, |