Problem

Currently, when SQL queries fail on the server side (e.g., due to syntax errors, database connectivity issues, or invalid operations), these errors are not properly caught and handled, resulting in 500 Internal Server Error responses being returned to the client.

Background

This issue was identified during the investigation of PR #1136, which fixed invalid SQL CAST operations causing MySQL compatibility issues in the WebUI. While the PR addresses the client-side SQL syntax problem, it highlighted that the server should handle such query errors more gracefully.

Current Behavior

• SQL query errors cause unhandled exceptions on the server
• 500 Internal Server Error responses are returned to the client
• Limited debugging information available for troubleshooting
• Poor user experience when database issues occur

Expected Behavior

The server should:

1. Catch and handle SQL query errors appropriately
2. Return meaningful HTTP status codes and error messages to the client
3. Log detailed error information for debugging purposes
4. Provide graceful degradation when possible
5. Prevent internal server errors from reaching the client unnecessarily

Impact

• Better user experience with more informative error messages
• Easier debugging and troubleshooting of database-related issues
• More robust error handling architecture
• Improved system reliability

References

• Related PR: fix(webui): Cast BIGINT values as UNSIGNED to fix MySQL-specific type errors in dashboard stats queries (fixes #1137). #1136 (MySQL compatibility fix)
• Comment: fix(webui): Cast BIGINT values as UNSIGNED to fix MySQL-specific type errors in dashboard stats queries (fixes #1137). #1136 (comment)

Acceptance Criteria

• Implement proper SQL query error handling on the server side
• Return appropriate HTTP status codes for different types of errors
• Provide meaningful error messages to the client
• Add comprehensive logging for debugging purposes
• Test error handling with various database error scenarios