I was actually talking about updating an existing production database. In such a case, the migrations which would be run would be just the ones between the previous release and the current one.
I have not tried your suggestion of rake db:schema:load but, judging by the contents of schema.rb, this would drop all of the tables and recreate them. We would lose both our application data and our user data. Perhaps I misunderstood how you were thinking to use that? On Jun 12, 2:28 pm, Marnen Laibow-Koser <rails-mailing-l...@andreas- s.net> wrote: > 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-Koserhttp://www.marnen.org > [email protected] > -- > Posted viahttp://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 [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 -~----------~----~----~----~------~----~------~--~---
