| Bug #95415 | Table Data Import Wizard fails on UTF-8 encoded file with BOM | ||
|---|---|---|---|
| Submitted: | 19 May 2019 8:05 | Modified: | 7 Feb 2022 10:47 |
| Reporter: | Georgi Sotirov | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 8.0.16, 8.0.18 | OS: | Windows (Windows 10 Home) |
| Assigned to: | CPU Architecture: | x86 | |
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
[19 May 2019 8:06]
Georgi Sotirov
[19 May 2019 8:07]
Georgi Sotirov
UTF-8 encoded CSV without BOM
Attachment: cities.csv (application/octet-stream, text), 548 bytes.
[19 May 2019 8:08]
Georgi Sotirov
Wizard error
Attachment: wb_8016_data_import_error-utf8-bom.png (image/png, text), 23.65 KiB.
