Missing diacritics when exporting to database

Hi there,

I have a issue with missing diacritics when exporting to database.
Using MySQL connector
My database have UTF8 collation

In EasyMorph I have “Tričko” but after export I can see in my database just “Tricko”.
Some other words works fine, for example “Náramek”

There is copy of SQL Insert from my server:
INSERT+INTO+%60reporting%60.%60rg_product%60+%28%60reference%60%2
C+%60name%60%2C+%60type%60%2C+%60youtuber%60%2C+%60price%60%2C+%60commission%60%2C+%60supplier%60%2C+%60description%60%2C+%60delivery_date%60%2C+%60service_factor%60%2C+%60combination_id%60%2C+%60purchase_price%60%29+VALUES+%28%27N299%27%2C+%27N%C3%A1ramek+Porty+Future+Kong%27%2C+%27N%C3%A1ramek%27%2C+%27Porty%27%2C+89%2C+30%2C+%27HK+SKYEE%27%2C+%27N%C3%A1ramek%27%2C+25%2C+1%2C+NULL%2C+3.65%29%2C+%28%27T678XS%27%2C+%27Tricko+Moon+Fire+Blue+%5BXS%5D%27%2C+%27Tricko%27%2C+%27Moon%27%2C+375%2C+125%2C+%27JimiPrint%27%2C…

You can see difference between “N%C3%A1ramek” and “Tricko”.

How can I fix this?

Hi David, and welcome to the Community!

Which MySQL version, EasyMorph version, and connector type (native or ODBC) are you using?

If it’s an ODBC connector, which ODBC driver version are you using?

I tried to replicate this issue on our test MySQL server, but it worked correctly with a table with the utf8mb3 charset and the utf8_general_ci collation.

Hi Andrew,

MySQL 5.7.36
EasyMorph 4.7.2.3
connector type is native

I did some more tests and I can see this:
EasyMorph connects with latin1 encoding and there is bad diacritics in SQL

2023-03-13T10:43:07.924086Z 11492061 Query SET NAMES latin1

2023-03-13T10:43:13.173979Z 11492061 Query INSERT INTO reporting.rg_product (reference, name, type, youtuber, price, commission, supplier, description, delivery_date, service_factor, combination_id, purchase_price) VALUES (‘T00281XL’, ‘Detsk� mikina SirYakari UHC [XL]’, ‘Tricko’, ‘SirYakari’, 100, 200, ‘JimiPrint’, ‘Mikina’, NULL, 1, 4, 1.00)

You can try to set the encoding of the connection in the connector’s custom properties:

I was able to replicate the issue by setting the CharSet property to latin1. Also, I made sure that it works correctly with the utf8 charset.

You are my hero! :slight_smile: Works perfect, thank you

You are welcome!