So then what is the point of the IrreversibleMigration exception? If you are going to force people to create a rollback then that exception should not exist.
On 9/22/07, DHH <[EMAIL PROTECTED]> wrote: > > > Posted here as it's a somewhat opinionated patch. > > This doesn't match my usage pattern. Usually my migrations that just > go up are about fixing data or something else, like populating a > counter cache. I still want to be able to go 3 versions back, but if > there's an irreversible mixed in there it'll halt. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
