Paul Lynch wrote: [...] > Migrations have a problem, though. After a while, the code changes to > a point where earlier migrations stop working. [...] > Usually this is only a problem if a > few weeks have elapsed since the last update. > > Have other people run into this issue? How are you working around it > (or avoiding it)?
You shouldn't be running lots of old migrations. In general, new installations should be done with rake db:schema:load, not by running every migration since the beginning. Use migrations properly and this problem will go away. > > Thanks, > --Paul Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
