Follow-up from "Fix Sentry tracking of SQL queries"
The following discussion from !50413 (merged) should be addressed:
-
@engwan started a discussion: (+1 comment) I just made the "checking the cause" logic more generic here since this exception could also be wrapped.
I'm not sure if we need to keep this though since the linked issue has been closed due to inactivity
🤔