MySQL Bugs: #120898: MySQL Workbench Table Data Import Wizard imports 0 records although CSV preview displays data

Bug #120898	MySQL Workbench Table Data Import Wizard imports 0 records although CSV preview displays data
Submitted:	11 Jul 20:40
Reporter:	Aastha Singh	Email Updates:
Status:	Won't Fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	MySQL Workbench 8.0.47	OS:	Windows (11)
Assigned to:		CPU Architecture:	Any
Tags:	csv import, Import Wizard, table data import wizard, workbench

Description:
I am using MySQL Workbench 8.0.47 on Windows 11.

I created a schema named "pizza_sales" and imported a CSV file using the Table Data Import Wizard.

The wizard correctly detects the CSV file, displays the column names, and shows a preview of the data. The table is created successfully, but after the import completes, the Import Results page reports "0 records imported".

The CSV file is not empty and opens correctly in Microsoft Excel with thousands of rows. UTF-8 encoding is detected automatically. Running SELECT COUNT(*) FROM pizza_sales; returns 0, confirming that no rows were inserted. SHOW WARNINGS; returns no warnings.

Expected behavior:
The data shown in the preview should be imported into the table.

Actual behavior:
The table is created, but zero records are inserted without any error or warning.

How to repeat:
1. Open MySQL Workbench 8.0.47 on Windows 11.
2. Connect to a local MySQL server.
3. Create a new schema named "pizza_sales".
4. Right-click the schema's Tables folder and select "Table Data Import Wizard".
5. Select a valid CSV file containing data.
6. Choose "Create a new table" and continue with the default import settings (UTF-8 encoding).
7. Verify that the preview displays the CSV data correctly.
8. Click Next and then Finish to complete the import.
9. The table is created successfully, but the Import Results page reports "0 records imported".
10. Running `SELECT COUNT(*) FROM pizza_sales;` returns 0 rows.

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.