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

improved error messages - missing psql/mysql binaries #37

Open
JohnMurray opened this issue Mar 1, 2015 · 0 comments
Open

improved error messages - missing psql/mysql binaries #37

JohnMurray opened this issue Mar 1, 2015 · 0 comments

Comments

@JohnMurray
Copy link
Contributor

See issue #36 for context.

Rather than throwing an exception all the way up the stack we should

  1. Catch the issue earlier and provide a better output message (possibly depending on the -v option how much of it we show vs a normal failure)
  2. Provide a specific error message / check when the binary cannot be found (either psql or mysql)

It might also make sense to provide a configuration option that allows you to provide a path to the specific pgsql or mysql binary that you would like to use, with the default value (if no config value provided) being whatever the script can locate on the current path.

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

No branches or pull requests

1 participant