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

fromdb/todb: Order of options/arguments shouldn't be as finicky #72

Open
tsibley opened this issue Dec 16, 2015 · 3 comments
Open

fromdb/todb: Order of options/arguments shouldn't be as finicky #72

tsibley opened this issue Dec 16, 2015 · 3 comments
Labels

Comments

@tsibley
Copy link
Collaborator

tsibley commented Dec 16, 2015

These operations are very picky about the order of their arguments, with error messages that seem bogus or are non-sequiturs when the order is wrong. I keep running into this, cursing, and moving on with the task at hand, but I should sit down and make it more liberal in what it accepts!

@tsibley
Copy link
Collaborator Author

tsibley commented Dec 16, 2015

Relatedly: Stop making empty testDb SQLite databases when fromdb/todb errors during option parsing.

@benbernard
Copy link
Owner

ugh, as the author of those, I'm embarrassed it works that way, maybe I can look into it soon

@tsibley
Copy link
Collaborator Author

tsibley commented Dec 16, 2015

Ah no worries, we've all looked back on our own code with embarrassment before, or at least I have. I couldn't care less about blame. :-)

On Dec 16, 2015, at 7:17, Ben Bernard notifications@github.com wrote:

ugh, as the author of those, I'm embarrassed it works that way, maybe I can look into it soon


Reply to this email directly or view it on GitHub.

@tsibley tsibley added the ux label Feb 2, 2017
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

2 participants