aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorAnna Ershova <anna.ershova@gmail.com>2015-10-15 16:37:11 -0400
committerAnna Ershova <anna.ershova@gmail.com>2015-10-15 16:37:11 -0400
commit5cde56e173f80068845c605f70925af5326152f5 (patch)
tree804dcf99e37dc18a44d93ff74a5724d64ac79ad4 /guides
parent0166adcee8a84bb40f92f3a69676178ecedc4e79 (diff)
downloadrails-5cde56e173f80068845c605f70925af5326152f5.tar.gz
rails-5cde56e173f80068845c605f70925af5326152f5.tar.bz2
rails-5cde56e173f80068845c605f70925af5326152f5.zip
Update active_record_migrations.md
Add 'db/'; corrects structure.rb to structure.sql
Diffstat (limited to 'guides')
-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 f2143a0e82..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` or `structure.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.