I really like the migrations that Rails offers. However, I am
wondering if I am missing an easier way to manage them. I have tried
both of the methods suggested in AWDWR…
I have employed the method of keeping all changes to a specific model
in a single migration file, but end up constantly rolling back the
version and then reloading every time I want to make changes to that
To me it seems that migrations should never be rolled back for any
reason. I guess it’s nice to have the “down” method, but I don’t see
a lot of use for it unless you only want to step back from the most
recent migration. Stepping back more than one version removes changes
that I almost always still want to keep.
So that leads me to the method of adding migration after migration
without regard for organizing the models. However, that soon becomes
a bit of a mess.
I think I’m looking for the best of both worlds. Would it not be
easier and more natural for the migrations for each model to be
separated into folders, much like the folder structure of the views?
Within each folder the numbering would start from 000 and the overall
schema and schema table would track the schema version per model. I’m
sure that this would cause another host of problems. Or can this
already be done and I’m missing it?