Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add init optionality #339

Open
wzrdtales opened this issue Jan 17, 2016 · 0 comments
Open

Add init optionality #339

wzrdtales opened this issue Jan 17, 2016 · 0 comments
Labels

Comments

@wzrdtales
Copy link
Member

wzrdtales commented Jan 17, 2016

Current behavior

If db-migrate tries to connect to a database that does not yet exists it is going to throw an error. The user needs to create the database with fitting permissions first.

Proposed solution

Add a command line option --init which tells db-migrate to first check if the database exists and then tries to execute a database execution. This tasks has items listed below.

Affected drivers

All: New method showDatabases is needed

Items:

API extensions

  • New command line option


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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant