Permalink
Browse files

Where migration can get wrong help added

  • Loading branch information...
1 parent e59b669 commit b11113f924d2eb2acbe836954d17a02163f45275 Sandip Ransing committed Apr 5, 2012
Showing with 10 additions and 0 deletions.
  1. +10 −0 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+

0 comments on commit b11113f

Please sign in to comment.