[erlang-questions] [HEADS UP] Emysql driver

Garrett Smith g@REDACTED
Fri Jul 5 16:27:14 CEST 2013

On Fri, Jun 21, 2013 at 4:38 AM, Jesper Louis Andersen
<jesper.louis.andersen@REDACTED> wrote:
> Hi Erlangers,
> Henning Diedrich and I have been working a bit on the Emysql driver,
>   https://github.com/Eonblast/Emysql
> cleaning it up and removing old cruft from it. Over the last month or so we
> have reached a point where 3-4 emysql branches were merged back into the
> above path. It has been running in production at a customer site, Issuu, for
> about 1 month without any problems to report and we believe it is fairly
> stable.
> NOTE: There is a backwards-incompatible change in `master`. We removed the
> encoding support of automatic conversion of binaries into utf-8. This means
> that client *users* are now responsible for encoding data properly. On the
> other hand, this means that the driver won't try to encode binary BLOB data
> as utf-8 anymore :)
> Branches of interest: `master`. Try it out. It contains the merger.
> Tags of interest: `0.2.16`. This tag is just *before* the merge, so if you
> need time to adapt to the new setup, you can lock to this tag and obtain the
> old behaviour.

Sorry for the delay in looking at this.

At first glance, it looks like I'd be losing the connect timeout
enhancements from here:


I noticed there's a connect test change however -- is that a
functional equivalent to handling connection timeouts?

It's less important, but that repo also has a much saner app_pool/2
function that uses Options rather than the 8 - 9 [sick] arguments of
the other two variants.


More information about the erlang-questions mailing list