It seems that MySQL client library translates connections to localhost to a local UNIX socket, instead of making a TCP connection to localhost address - which is 127.0.0.1.
Such behavior was initially reported to MySQL team on 2007, and it seems that they claim it's not a bug, regardless if I use the mysql CLI tool, mysql2 gem, but trilogy is handling that case in the correct way.
I need to borrow your wisdom on this topic:
how did you solve this issue?
is it possible to point me in the code where did you solve it?
Hey trilogy team,
It seems that MySQL client library translates connections to
localhost
to a local UNIX socket, instead of making a TCP connection tolocalhost
address - which is127.0.0.1
.Such behavior was initially reported to MySQL team on 2007, and it seems that they claim it's not a bug, regardless if I use the
mysql
CLI tool, mysql2 gem, buttrilogy
is handling that case in the correct way.I need to borrow your wisdom on this topic: