Bug #106423 | importing UTF-8 files does not work | ||
---|---|---|---|
Submitted: | 9 Feb 2022 17:07 | Modified: | 10 Feb 2022 22:15 |
Reporter: | Valerio Messina | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | OS: | Windows | |
Assigned to: | CPU Architecture: | Any |
[9 Feb 2022 17:07]
Valerio Messina
[9 Feb 2022 17:08]
Valerio Messina
tested on Windows only
[9 Feb 2022 17:09]
Valerio Messina
table definition as UTF-8
Attachment: MySQL_Workbench_8.0.28_tableDef.png (image/png, text), 157.43 KiB.
[9 Feb 2022 17:09]
Valerio Messina
Encodinig import settings does not matter
Attachment: MySQL_Workbench_8.0.28_import.png (image/png, text), 16.03 KiB.
[9 Feb 2022 17:13]
Valerio Messina
a csv file saved as UTF-8 containing non ASCII chars
Attachment: DB_PSA_UTF-8_lite.csv.7z (application/octet-stream, text), 551 bytes.
[9 Feb 2022 17:17]
Valerio Messina
here the table def, field "remarks" is a VARCHAR
Attachment: MySQL_Workbench_8.0.28_tableDef2.png (image/png, text), 94.85 KiB.
[9 Feb 2022 17:17]
Valerio Messina
all the "°" chars in the "remarks" field will be garbaged
[10 Feb 2022 13:49]
MySQL Verification Team
Hello Valerio Messina, Thank you for the bug report. Imho this is duplicate of Bug #95700, please see Bug #95700. Regards, Ashwini Patil
[10 Feb 2022 17:23]
Valerio Messina
I'm happy the bug https://bugs.mysql.com/bug.php?id=95700 was already opened only two year ago. Take care that UTF-8 is around from about 2010, Windows support it from WinXP
[10 Feb 2022 22:15]
Valerio Messina
yes, UTF-8 is around from about 2001 (not 2010), about 20 year ago