The behavior of rake db:migrate:down is a little bit unexpected (to me at least).
If I do this: $ rake db:version Current version: 20080930121212 $ rake db:migrate:down VERSION=20080930121212 what happens is the schema in that migration is rolled back, but the migration version is NOT removed from schema_migrations table. So now rails *thinks* the db is at version X (according to schema_migrations), when it fact its schema is *really* at version X-1. Am I missing something obvious here? I would have expected db:migrate:down to also remove that version from schema_migrations. Thanks dwh --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
