You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 24, 2022. It is now read-only.
Right now, dbManager is throwing exceptions of basic type "Exception" to handle empty result sets and every context calling one of these functions is catching all exceptions as well.
This results in also catching actually fatal errors such as MySQL syntax errors and alike. This results in Codeface silently ignoring fatal runtime errors.
dbManager should use a custom exception type for empty result sets instead. All locations expecting exceptions must be changed as well.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, dbManager is throwing exceptions of basic type "Exception" to handle empty result sets and every context calling one of these functions is catching all exceptions as well.
This results in also catching actually fatal errors such as MySQL syntax errors and alike. This results in Codeface silently ignoring fatal runtime errors.
dbManager should use a custom exception type for empty result sets instead. All locations expecting exceptions must be changed as well.
The text was updated successfully, but these errors were encountered: