Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
1.1.0
-
None
-
None
-
None
Description
Specifying sessionVariables=characterEncoding=utf8 as part of the connection-string seems to have no effect. Created databases and tables uses latin1 unless the following is set on the server:
skip-character-set-client-handshake
character-set-server=utf8
collation-server=utf8_general_ci