When you trigger migration up or down programmatically, you cannot specify migration table in options

When you trigger migration up or down programmatically, you cannot specify migration table in options. Its needed to specify migration table something like:

DBMigrate.getInstance(true, {
config: {
database: ...,
user: ...,
table: 'migration_tabe_name'
}
}

for now you can only specify migration table as an argument:

db-migrate up --table migration_tabe_name

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[wzrdtales]

@georgearrowwood Good catch!
Definitely needs to be added.

[denneralex]

Hey all, I was having the same issue and going through the code I've noticed you expose an _internals attribute that would not solve it the best way but could help temporarily.

But when I was trying to use that I noticed the binding doesn't work, the property is null cause its not binding to the internals property. Could be just a matter of using a getter to bind it to the class like this:

get _internals () { return this.internals }

Does it make sense or the way it is today is an expected behaviour? Am I missing anything?

If this works for you I can send a PR for that.