As guessed, the problem was with the client_encoding on the database. crd_production=# show client_encoding; client_encoding —————– LATIN1 (1 row) To change the client encoding to UTF-8, you need to do this crd_production=# SET client_encoding = ‘UTF8’; SET Check again crd_production=# show client_encoding; client_encoding —————– UTF8 (1 row) Things work fine now.
I think OP was asking about charset that Workbench uses in its editor and how to setup Workbench to use UTF-8 in GUI – not how to setup default charset used for database table in Workbench. At the moment in Workbench one can set database table charset but regardless of it Workbench will in it’s … Read more
UTF-8 is prepared for world domination, Latin1 isn’t. If you’re trying to store non-Latin characters like Chinese, Japanese, Hebrew, Russian, etc using Latin1 encoding, then they will end up as mojibake. You may find the introductory text of this article useful (and even more if you know a bit Java). Note that full 4-byte UTF-8 … Read more