Unable to set path for migrations on a gateway about rom-sql HOT 3 CLOSED

I ran into this issue myself - even with a single gateway there seems to be no way to specify a migration path.

from rom-sql.

Apologies for not responding to this for so long. Migrations are handled by a migrator object, which is configured and injected to a gateway as one of the options, so it's a matter of tweaking this line to also pass gateway.options[:migrator]. Then we could have a convention that when you configure a gateway by doing [:sql, 'sqlite3://my_db', migrator: { path: 'my_migrations' }] it'll just pass these migrator options to the migrator object for your gateway.

How does that sound?

from rom-sql.

Now this should be possible in this way

conn1 = Sequel.connect(uri1)
conn2 = Sequel.connect(uri2)
migrator1 = ROM::SQL::Migration::Migrator.new(conn1, path: migration1_dir)
migrator2 = ROM::SQL::Migration::Migrator.new(conn2, path: migration2_dir)
rom = ROM.container(
  default: [:sql, conn1, migrator: migrator1],
  non_default: [:sql, conn2, migrator: migrator2]
)

rom.gateways[:default].run_migrations # run migrations from migration1_dir
rom.gateways[:non_default].run_migrations # run migrations from migration2_dir

I haven't tested it, so lemme know if something doesn't work as expected. It's rather verbose but I believe we'll make it more concise during the work on migrations for rom-sql 2.0.

from rom-sql.