This has now been fixed in upstream [1],
and will be in the next release
(which will be the one after 5.13.0).

[1] https://github.com/jeremyevans/sequel/commit/0e9e0a

Reply via email to