There is already an object named 'schema_migrations' in the

Hi Ben,

I think there should be a table generated with name as schema_info in
your database.

this table will have version as the column that contain the number of
the latest migration file you executed.

next time when you run migrations it will run all migration files
having number above the version number mentioned in schema_info table.

try to trace the schema_info table as above behavior.


try to trace it and

Thanks for the response Piyush,

Actually the schema_info table was replace by the schema_migrations
table in later versions of rails (2.0+ I think?). When looking at the
schema_migrations table, I do see all the migrations to date listed.
Rails seems to be making the decision that this is the first time the
migrations have run from some local setting.