From c570ba70fe6ed53fd1ac5f30f0c9ba4cb7cd4796 Mon Sep 17 00:00:00 2001 From: John Gallagher Date: Sat, 27 Oct 2012 21:54:44 +0100 Subject: Changed comment section to be more explicit. I had an issue with rolling back a migration and couldn't understand why 'rake db:reset' didn't work. --- guides/source/migrations.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'guides/source') diff --git a/guides/source/migrations.md b/guides/source/migrations.md index 3eeb45f8c6..314ee3f5cd 100644 --- a/guides/source/migrations.md +++ b/guides/source/migrations.md @@ -684,8 +684,9 @@ version to migrate to. 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 -[schema.rb](#schema-dumping-and-you). +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, 'rake db:reset' +may not help you. To find out more about dumping the schema see [schema.rb](#schema-dumping-and-you). ### Running Specific Migrations -- cgit v1.2.3