Skip to content

Catch another error message related to lost connection

Created by: muffato

Seeing I need to add the message in two places, I'm wondering if I should introduce a new method, say in DBConnection, that tells whether an error message is due to lost connection, and call it from these two places. I could then add two other methods to tell whether an error message is (1) due to deadlock, (2) due to the unavailability of the server. Both are currently implemented the same way: if $@ =~ /.../ or ...

Merge request reports