Re: character set encoding bug in connector 5.1.36/5.1.37?
adding characterEncoding=utf8 to the JDBC url is a workaround to the problem.
I assume the character encoding auto-detection got broken somewhere between 5.1.35 and 5.1.36.
Bug report filed.
http://bugs.mysql.com/bug.php?id=78902
Subject
Written By
Posted
Re: character set encoding bug in connector 5.1.36/5.1.37?
October 21, 2015 10:48AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.