Create/Drop database set on config

[dmmartins]

It doesn't make sense to specify database name on db:create when you have database set on config file and migrations depend on that config.
Somehow related to #468.

[wzrdtales]

@dmmartins I think your suggested change would be confusing and the current implementation speaks like what it does.

What I could think of instead would be an init command, as db:create says: I create a db, but to imply that the config is interpreted here and it takes the db name, would be an unexpected behaviour. So I would rather do the thing mentioned before instead of altering the command in this way you suggested.

[dmmartins]

It should be consistent. Currently you need to pass the database name on db create but you can't do that for migrations.
So if you have database name set in config file you can't create the database because it tries to connect to the database that doesn't exist. If you remove database name from config, you can't run migrations.

Do you think (optionally) passing database name on migrations would be better?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Ajaxy]

Any update on this?

[aprakash-sovrn]

+1