Migrations running errantly

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!

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs