aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorAnnaErshova <anna.ershova@gmail.com>2015-10-15 09:36:57 -0400
committerAnnaErshova <anna.ershova@gmail.com>2015-10-15 09:36:57 -0400
commit0166adcee8a84bb40f92f3a69676178ecedc4e79 (patch)
tree54ff8bd34ddef173750e5d6b1293825f1d75a3e8 /guides
parentb6cf69ebcbf7372c61d38aa33baa7d0f4224679b (diff)
downloadrails-0166adcee8a84bb40f92f3a69676178ecedc4e79.tar.gz
rails-0166adcee8a84bb40f92f3a69676178ecedc4e79.tar.bz2
rails-0166adcee8a84bb40f92f3a69676178ecedc4e79.zip
Clarifies db can be set up from structure.sql also
I added that *structure.sql* file can be used when *db:reset* is run. *db:reset* tasks states *db:reset* loads database from *db/schema.rb* or *db/structure.sql* depending on the configuration (although *db/schema.rb* is the default), hence the change.
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 c5ac70143d..f2143a0e82 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 `schema.rb` or `structure.rb` 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.