Closed whatyouhide closed 1 year ago
On the off chance someone is relying on this, I don’t think this is worth changing, given how minimal it is. :)
How can they be relying on returning bad errors and catching the error that DBConnection raises?
Isn't this propagated upstream to run/3
as per the previous PR?
Yes, but I mean, you think they're relying on possibly returning bad values (like in Postgrex or something)? I think that would be considered a bug, so they should probably not be catching it?
I don’t think they are or should be, but this is minor to justify potentially breaking something. That’s all :)
As mentioned in #281. cc @wojtekmach, I went with
RuntimeError
, which I think makes more sense here thanArgumentError
.