When I am writing rails migrations, quite often I make mistake in them
causes the migration tasks to stop halfway with error.
This causes lots of problem, because it results in half of the things in
migrations changed and other half not. Also, as the schema number is
so things cannot be rolled back.
Is there any way to make the entire migration action atomic, i.e.,
or none at all?
Also, while dropping tables how can I determine whether a particular
exists in the database?
Read my blog at: http://cuttingtheredtape.blogspot.com/
| “War is Peace! Freedom is Slavery! Ignorance is Strength!”
| – Orwell, 1984, 1948