I have a conventional rails app that is happily running on top of a single database managing it's migrations. The name of default database is abc
and all the migration files reside in db/migrate
directory.
I now need to manage migrations on another database named xyz
. While putting all the relevant migration files in db/migrate/xyz
and running the command rake db:multi:migrate DATABASE=xyz
works like charm, I am unable to run the migration on the database abc
.
What I don't want to do is to move all the files from db/migrate
to db/migrate/abc
and duplicate the database configurations in config/database.yml
by creating abc_#{abc}
.
In my opinion, there should be a default behavior to pick files from db/migrate
and run migration on default database using the command rake db:multi:migrate
.
Please let me know if there are any issues with this. If all of us agree, I can take this up. Or, am I missing something?