On Thu, Mar 4, 2010 at 9:58 AM, Michael Pavling <[email protected]> wrote: >>> Similarly, you can now no longer alter your models, because some >>> migrations rely on the operation of the model at that "point in time"
> Today I decide that I need to have an "expired flag" on my posts, and > it's required, so I create a new migration ... > But now, when I roll back my migrations and try to roll them forward > again, ... Well, sorry, why are you "rolling back" at all? Why not just run the new migration? I can't remember every needing to do a rollback for other than a single most recent migration (due to some obvious d'oh! screwup like a typo). > I can't believe you're making me go through these hoops to show > you how bad a practice it is to put data in your migrations This seems to be a lesson in "at some point old migrations will fail if (when) your models change enough" rather than anything to do with migrations and data. -- Hassan Schroeder ------------------------ [email protected] twitter: @hassan -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
