If dev db has new migration they may become invalid

[alex-ross]

Using postgres.

If my development database has more tables in it then the one I trying to pull using cap db:pull my migrations will fail afterwards. When the capistrano task calls rake db:restore it changes the schema_migrations data but will not drop or reset the tables.

To solve this i can manually recreate the database before using rake db:restore.

Is this as designed or is this a bug?

How to recreate:

1. create an migration in any rails app using PostgreSQL (haven't tried MySQL).
2. run migration, only on your development machine.
3. run cap db:pull
4. run your migrations again and it will fail because the database it tries to create already exists.