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.

Sign up for GitHub

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

Jump to bottom

Correct handling for SQL exceptions #32

Open
supertri opened this issue Mar 21, 2011 · 0 comments
Open

Correct handling for SQL exceptions #32

supertri opened this issue Mar 21, 2011 · 0 comments

Comments

@supertri
Copy link
Member

Right now, most SQL exceptions are caught and then a stack trace is printed. And then execution moves on. Should the program instead initiate a shutdown sequence in these cases? What is a good way to consistently handle these exceptions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@supertri