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