From b11113f924d2eb2acbe836954d17a02163f45275 Mon Sep 17 00:00:00 2001
From: Sandip Ransing <sandip@joshsoftware.com>
Date: Fri, 6 Apr 2012 01:11:42 +0530
Subject: Where migration can get wrong help added

---
 guides/source/migrations.textile | 10 ++++++++++
 1 file changed, 10 insertions(+)

(limited to 'guides/source/migrations.textile')

diff --git a/guides/source/migrations.textile b/guides/source/migrations.textile
index 1d8c1e03f3..a565974227 100644
--- a/guides/source/migrations.textile
+++ b/guides/source/migrations.textile
@@ -928,3 +928,13 @@ 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

