Skip to content

Correct handling for SQL exceptions #32

@supertri

Description

@supertri

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