On 8/29/07, Jay Levitt <[EMAIL PROTECTED]> wrote: > > > Interesting... I didn't expect such a negative reaction! > > When the problem happens to me, it's usually because (a) I've written > a migration that aborted, or (b) I tried to merge and renumber two > migrations but forgot to roll back first, thus often yielding problem > (a). When that happens, I've got, say, a schema_info of 34, but half > of the fields from migration 35. So I can't migrate down, because > there are fields that shouldn't be there in 34, but neither can I > repeat the migration. This doesn't happen to you folks? >
It doesn't happen to me for a few reasons: 1. I am very careful that my migration down matches my migration up. Using TextMate and mistyping in the up, will also mistype in the down, so when I find and fix the up I am always careful to fix the down too. 2. I don't often merge migrations, and I never renumber. 3. If the schema number did get updated, but the migration failed, I go and change the schema number. I do this until the migration is working. -- Thank you, Steven A Bristol [EMAIL PROTECTED] Home page: http://lesseverything.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
