Remember once MySQL storage, text garbled problem

recently, a tool has been developed using ADO to parse a log merge library (MYSQL) as follows

All-xx:panax notoginseng: [INFO ] rolename=♣, Innova, orderid=  1408190037102121039, price=10.0, point=

found in the rolename in the storage after the ♣ display as-garbled, the first thought is the table coding problem, after the confirmation is Utf-8 coding wood problem, and later ruled out the file encoding and the code string are not garbled problem, with empirical analysis, may be the problem of the connection string it, The Utf-8 encoded parameter option was added to the MySQL connection string and the test was OK.

server=10.10. 10.10; convertzerodatetime=true;characterset=utf8;checkparameters=false;allowuservariables=true;user ID =xxxx;password=xxx;port=3316; Integrated security=false

The Characterset=utf8 in the above connection string is the processing option for character encoding.