That's a great idea. I never would have considered that.
Do you create a full rails project to handle migrations or what? How do you integrate that in with your other code?
Do you create a full rails project to handle migrations or what? How do you integrate that in with your other code?
And then follow the migration syntax to modify your schema. Rails will take care if the timesramping, rollbacks (in most cases),etc. You can manage your indexes, primary,etc everything here. You don't need to write any other rails code.
Check this whole directory as a part of your main source repo.
Another commenter pointed out a standalone gem for migrations. That might be OK, but I'd rather use mainline rails in this case.