Duplicated 'migrations' table when using schemas

When using a `schema: 'mySchema'` configuration in the `database.json, I can run db-migrate and it will create a migrations table on the `public` schema.
Running the migration again leads to a second `migrations` table inside the `mySchema` schema.

I would guess that this might require a better configuration possibility for the migrations schema which is currently only possible via the `--table my_migrations` command line argument. I would like to configure a like like `myOtherSchema.my_migrations`, because I don't want to mix real/customer data with technical data (migrations).

Sidenote: is it possible to configure the migration table via the database.json? I tried, but failed.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/42531816-duplicated-migrations-table-when-using-schemas?utm_campaign=plugin&utm_content=tracker%2F14258523&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F14258523&utm_medium=issues&utm_source=github).