From 5916403991e0f3f8f14523827745bae42e2817d1 Mon Sep 17 00:00:00 2001 From: Vijay Dev Date: Sat, 7 Apr 2012 16:47:32 +0530 Subject: Revert "Where migration can get wrong help added" This reverts commit b11113f924d2eb2acbe836954d17a02163f45275. --- guides/source/migrations.textile | 10 ---------- 1 file changed, 10 deletions(-) (limited to 'guides/source') diff --git a/guides/source/migrations.textile b/guides/source/migrations.textile index 0405f45fa8..f663496854 100644 --- a/guides/source/migrations.textile +++ b/guides/source/migrations.textile @@ -927,13 +927,3 @@ features, the +execute+ method can be used to execute arbitrary SQL. You could also use some plugin like "foreigner":https://github.com/matthuhiggins/foreigner which add foreign key support to Active Record (including support for dumping foreign keys in +db/schema.rb+). - -h3. Where you may get into trouble ? - -While running specific migrations with VERSION specified, By mistake if you misspell -command you may get into big trouble. - -Consider scenario where you want to run down migration +db:migrate:down VERSION=324213490000+ -By mistake if you type something like +db:migrate :down VERSION=324213490000+ then it will -change the complete meaning of migration command and it will be migrated like you are -executing +db:migrate VERSION=32421349000+ -- cgit v1.2.3