For those of you keeping score at home, I’m happy to announce that I will be giving a talk at RailsConf on Rails Migrations.
If you have specific topics or questions you’d like to have addressed besides the ones mentioned in the talk proposal, please leave a comment. Thanks!
Looking forward to meeting you in Chicago!
4 comments ↓
* Is there a better way to develop a new migration other than run, fail, comment some lines, re-run, then migrate back and forth to verify? * Can transactions help when writing migrations? * How can migrations be tested? * Changes to models can make earlier migrations fail. How can one write migrations that are bulletproof?
Thanks, Geoffrey! Those are good ideas.
* Show how to prevent/allow migrations in different environments. ex. selectively preventing migration to production environment. * When migrating a latency DB, show a way to indicate table metadata that did not properly translate to rails migration schema.
MikeR, Thanks for stopping by. I’m not sure I understand your second one. I am assuming you meant “legacy db”. Do you have a solution for detection of errors in schema translation?
Leave a Comment