What would make migrations run unexpectedly? We ran cap deploy:migrations and did not expect any migrations to run since none had been changed. The schema_migrations table was there and contained the appropriate value for the last valid migration. But for some reason, the migrations started executing anyway.
Our application was recently upgraded from Rails 1.x to 2.x. Our migrations use the old one-up numbering scheme. The configuration was not updated to indicate that the new timestamp naming scheme should not be used. But it still seemed to work fine in our dev and test environments. It only ran errantly on production. What exactly happens to determine if migrations are needed? Has anyone ever seen this happen, perhaps if something is wrong with the database table or something else? Thanks! -- 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 -~----------~----~----~----~------~----~------~--~---
