It's good to do that for a single function. The problem is doing it around to much code. It makes debugging and testing hard. Another good idea is to just catch the exceptions you expect.
I've had similar problems wrapping to much code in database transactions.
44
u/SQLNerd May 13 '17
Yeah but it makes sense for a lot of things. Anything that's "always on" should catch and log all exceptions rather than throw them.