[Feature Request] schema:dump --database=db2 --migrations=db1

[helderneves91]

Hello,

Imagine that the main database is db1 and the migrations table in here, on db1.
Imagine that we have another db, called db2, without the migrations table.

At the moment the schema:dump allow the dump of the db1 without any problem. Works as expected!
On the other hand, db2 doesn't have the migrations table, so, laravel will throw an error:

Error Output:
================
mysqldump: [Warning] Using a password on the command line interface can be insecure.
mysqldump: Couldn't find table: "migrations"

At the moment is there any way to achieve this?

Thanks!

[helderneves91]

I don't feel really confortable working in a solution to this...

I have sent a PR #48280 to allow schema:dump to inject CREATE/USE database. We'll need this if we have a solution like this.