You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ActiveRecord natively supports multiple database connections. There's no reason for migrations not to do the same.
Not to mess things up, migrations for default database should still reside in db/migrate, while others should reside in db/migrate/database_config_name_without_environment_name.
Also, db:migrate should support option for specifying which database to run migrations on.
Imported from Lighthouse. Original ticket at: http://rails.lighthouseapp.com/projects/8994/tickets/6391
Created by Arthur Pirogovski - 2011-02-08 22:28:53 UTC
ActiveRecord natively supports multiple database connections. There's no reason for migrations not to do the same.
Not to mess things up, migrations for default database should still reside in db/migrate, while others should reside in db/migrate/database_config_name_without_environment_name.
Also, db:migrate should support option for specifying which database to run migrations on.
Directory layout example:
db/migrate
db/migrate/second
Corresponding db config:
The text was updated successfully, but these errors were encountered: