Description:
Title
MySQL Workbench 8.0.45 on macOS fails to import UTF-8 CSV with ASCII decoding error for large files
Product:
MySQL Workbench
Version:
8.0.45 (Community Edition)
Operating System:
macOS (Apple Silicon / M2)
Description:
When importing a UTF-8 encoded CSV file using the Table Data Import Wizard in MySQL Workbench 8.0.45 on macOS, the import fails with an ASCII decoding error.
Steps to Reproduce:
1. Open MySQL Workbench 8.0.45 on macOS (Apple Silicon)
2. Connect to a local MySQL server
3. Use Table Data Import Wizard
4. Select a UTF-8 encoded CSV file (~10,000 rows)
5. Encoding is detected or manually set to UTF-8
6. Start the import process
Expected Result:
The CSV file should be imported successfully.
Actual Result:
The import fails with the following error:
Unhandled exception: 'ascii' codec can't decode byte 0xc2 in position 874: ordinal not in range(128)
Additional Observations:
- Smaller CSV files (~100 rows) import successfully
- The same CSV file imports correctly on another machine
- LOAD DATA LOCAL INFILE is disabled by default
- There is no option in MySQL Workbench Preferences to enable local_infile on macOS
- Import only works via terminal using mysql --local-infile=1
Workaround:
Using the MySQL command-line client with --local-infile=1 and importing via LOAD DATA LOCAL INFILE.
How to repeat:
1. Install MySQL Workbench 8.0.45 on macOS (Apple Silicon).
2. Open MySQL Workbench and connect to a local MySQL server.
3. Open Table Data Import Wizard.
4. Select a UTF-8 encoded CSV file with approximately 10,000 rows.
5. Ensure encoding is set to UTF-8.
6. Start the import process.
7. Import fails with an ASCII decoding error.
Suggested fix:
-Ensure MySQL Workbench consistently uses UTF-8 decoding for CSV imports on macOS and does not fall back to ASCII.
-Additionally, expose a visible option in Workbench Preferences to enable LOAD DATA LOCAL INFILE on macOS.
