aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRafael Mendonça França <rafaelmfranca@gmail.com>2015-10-15 18:37:19 -0300
committerRafael Mendonça França <rafaelmfranca@gmail.com>2015-10-15 18:37:19 -0300
commit3b61027092517ac9fd2736d38673c27fedd08c1b (patch)
tree5c507c7d8bfa2288e94a762158f9bf2eaa089fbd
parent3253185b363da4e98a63f3f82b94e8e5e33154c9 (diff)
parent5cde56e173f80068845c605f70925af5326152f5 (diff)
downloadrails-3b61027092517ac9fd2736d38673c27fedd08c1b.tar.gz
rails-3b61027092517ac9fd2736d38673c27fedd08c1b.tar.bz2
rails-3b61027092517ac9fd2736d38673c27fedd08c1b.zip
Merge pull request #21966 from AnnaErshova/dbreset-edit
Clarifies db can be set up from structure.sql as well as from schema.rb
-rw-r--r--guides/source/active_record_migrations.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/active_record_migrations.md b/guides/source/active_record_migrations.md
index c5ac70143d..67881e6087 100644
--- a/guides/source/active_record_migrations.md
+++ b/guides/source/active_record_migrations.md
@@ -789,7 +789,7 @@ 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,
+contents of the current `db/schema.rb` or `db/structure.sql` 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 Dumping and You](#schema-dumping-and-you) section.