I suspect this is because it is a 1.x application which was upgraded,
but my migrations don’t “stick.” If I
Coder-iMac:patton colin$ rake db:migrate
(in /Users/colin/Desktop/patton)
== 20090217193953 AddLastYearToTarget: migrating
== 20090217193953 AddLastYearToTarget: migrated (0.0001s)
== 20090222192059 AddEditorToUser: migrating
== 20090222192059 AddEditorToUser: migrated (0.0000s)
== 20090222224734 AddSometTimestamps: migrating
== 20090222224734 AddSometTimestamps: migrated (0.0000s)
== 20090301004033 AddCommentRangeToUser: migrating
== 20090301004033 AddCommentRangeToUser: migrated (0.0000s)
If I do the same command again it does EXACTLY the same three
migrations. (Of course, they were all throwing errors, since they had
already done the migration once, so now the lines that do anything are
commented out.)
The table schema_migrations has 147 rows, with the last three being
20090301004033
20090222224734
20090217193953
over and over. It’s like it gets lost and can’t find what one it did
last.
Is there some way to say, “Dump all that migration data, assume
everything has been migrated in to the latest migration?”
Thanks,
–Colin