Rails migrations with the same name

Question

How do people cope with this problem elegantly?

I had a migration that created a table, then another to remove that table, now I want to re-introduce it, problem is i cant as they have the same name.

Answer 1

If I understand you correctly, Rails complains only about migration name only. Well, migration name has no affect on its functionality, so you can just use a different one.