I fixed it. I don't like poking around in MySQL. It's like putting my hands in the wood chipper.
I did mysqldump -u user --database development_database > backup.sql then I dropped the whole database and recreated it's name. I did rake db:schema:load to recreate all of the tables. I saw some cool command go by saying "assume_migration(20090309)" or something like that. So I have a feeling that real Rails weenie would be able to do this with the One Correct Command. I tried rake db:migrate but it choked on the three new migrations, those which were named with the date-time stamp. So I went into those and commented out everything in self.up. I retried rake db:migrate and it happily pulled them in. I held my breath and did rake db:migrate again and it was quiet. Phew. So they had "stuck." I exported the schema_migrations table to migration.sql, uploaded that to my production server. I went into mysql and did drop table schema_migrations then went out to the prompt and did mysql -u user --database production_database < migration.sql and it read it in. I did rake db:migrate and it seemed to stick. I'm sure other people have run into this (or will) and there's probably a bunch of scripts out there which do what I did, but automagically. I wish there were just a rake db:fix_migrations command. --Colin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
