Marnen Laibow-Koser wrote: > How? You're not normally going to be running old migrations. What > specific problem do you think you will run into if you leave the old > migrations around?
I moved the complete database from my interim server to the permanent one. This database had been modified by the data migrations and in the meantime some data has been changed. So it's not a good idea, to rerun the data migrations on the new server. To prevent this, I locally removed the data migrations on the new server before migrating. On my developmentsystem, they're still present and dont harm, but I guess, they will be pushed up to the server again with my next update and will get run, because there is no corresponding entry in the migration data base. Maybe, the simplest solution will be, to do something to make them null migrations on the development system. -- 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 [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.
