MySQL Bugs: #110705: Import of CSV only partially completed, with report of invalid character in file

Bug #110705	Import of CSV only partially completed, with report of invalid character in file
Submitted:	17 Apr 2023 0:15	Modified:	17 Apr 2023 16:04
Reporter:	Jack Eisenberg	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Migration	Severity:	S2 (Serious)
Version:	8.0.32	OS:	Windows (Microsoft Windows 10 Home)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\Owner\AppData\Roaming\MySQL\Workbench\log\wb.log]

I've been using MySQL Workbench for a very long time.  Today, I tried to import a CSV file (something I do twice monthly) and the import failed after successfully importing 30 records.  The log file indicates there is a character that cannot be mapped, but I cannot see any indication of an error when visually inspecting the CSV file.  I tried the import multiple times, and even made sure the Workbench software was up-to-date before trying the last import.

This is my first time reporting to Oracle, so I will need to find how to upload the log file, SQL table definition and CSV file for your engineers.

How to repeat:
Since I am attempting to import into an existing file, I cannot give you exact instructions.  However, in an attempt to recreate the issue, I copied the structure of my REAL table into a SECOND table and tried to import the CSV into the second table.  The same problem occurred.

Other pertinent information...  I work with several businesses, and even after encountering the error with the submitted CSV file, I tried doing an import for a DIFFERENT business (the data is imported to the same table for all businesses), and that import succeeded.  So, whatever happened with this failed import did not seem to affect the operation of the program.

On a hunch, I tried to import a PRIOR PERIOD file into the table, so I could see whether this new issue would prevent imports of CSV files that had previously been acceptable.  I was able to successfully import the prior period data into my TEST table.  The second file upload contained the prior period CSV file.

Hello Jack Eisenberg,

Thank you for the bug report.
Imho this is duplicate of Bug #95700, please see Bug #95700.

Regards,
Ashwini Patil