[chmod775]

I like the idea and project goals.

There are however gems like this in the source:

https://github.com/gajus/slonik/blob/master/src/routines/exe...

You can spend an hour trying to reason about the control flow of that triple try/catch alone. Bonus points if that function can recursively call itself (not sure what retryTransaction can get up to).

There may be an explanation for this horrifying code, but it should probably be right above in the form of:

     /* 
      * The following code is not for the weak minded.
      *
      * Great care needs to be taken with it, for even the smallest mistake
      * risks summoning the gods of old to end all life on earth
      * in the most terrible way imaginable.
      * 
      * There is however no other way because a, b, and c.
      */

To untangle that mess you'd probably have to rewrite it once just to understand it, rewrite it again to get it right, then spend a month getting the edge-cases right.

But at least afterwards a newcomer can fix a bug without endangering the multiverse.

[zaptheimpaler]

Its really not that complicated.. each except either handles an error or rethrows it for the outer except to handle it.

Maybe a one liner comment would help, but exaggerating as if the code is some horrifying monstrosity is not helpful IMO. It just smells of elitism and makes the code seem more unapproachable than it really is.

[faizshah]

It's not really that complicated it's just error bubbling with a lack of comments. Definitely worth a refactor into an exception map or something instead of this nested mess though. I've seen worse pass lazy code review honestly (working with scientists you really see some crazy code).