WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Correct handling for SQL exceptions #32

New issue
New issue
Open
Open
Correct handling for SQL exceptions#32
@supertri

Description

@supertri
supertri
opened on Mar 21, 2011

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions