Better handling of bad/non-existent dbs #16

Closed
opened 6 years ago by abrax · 0 comments
abrax commented 6 years ago
Owner

Before running each command, lizard.py should do the relevant sanity checks (does the db exist? is the schema correct?) and print an easy to understand error message instead of a stack trace.

Before running each command, `lizard.py` should do the relevant sanity checks (does the db exist? is the schema correct?) and print an easy to understand error message instead of a stack trace.
abrax referenced this issue from a commit 6 years ago
abrax closed this issue 6 years ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.