Bug #95700 | SQL worbench is unable to import UTF8 csv file | ||
---|---|---|---|
Submitted: | 9 Jun 2019 17:08 | Modified: | 10 Jun 2019 6:11 |
Reporter: | Jirka Stejskal | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S2 (Serious) |
Version: | 8.0.16, 8.0.26, 8.0.31, 8.0.32 | OS: | MacOS (macOS 10.14.x Mojave x86_64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix>
- On windows use WinZip or a similar utility to split the large file
[9 Jun 2019 17:12]
Jirka Stejskal
[1 Jul 2022 16:00]
Valerio Messina
table definition as UTF-8
Attachment: MySQL_Workbench_8.0.28_tableDef.png (image/png, text), 157.43 KiB.
[1 Jul 2022 16:01]
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.
[1 Jul 2022 16:01]
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.
[1 Jul 2022 16:01]
Valerio Messina
Encodinig import settings does not matter
Attachment: MySQL_Workbench_8.0.28_import.png (image/png, text), 16.03 KiB.