In trying to actually do something nontrivial with Ruby on Rails, I've spnt the evening trying to familiarize myself with the usefulness of migrations. There are several excellent articles on blogs that extol its virtues, but I've mostly used a single migration that builds my whole schema. To make a change this way, you apparently change the migrations, roll back one version, then run the migration again. This feels wrong.
So, I guess it boils down to:
1) If I'm not using source control, what good is an old version of my database schema?
2) If I am using version control, how is this any more useful than something like Hibernate mapping files, which would just be stored with their respective versions of application sources?
Guess I'll have to tinker with it some more...Posted by orteg004 at March 29, 2006 12:20 AM