MySQL Workbench 6.1 - 导入记录集时出错

Question

I'm going to be getting a new computer soon and I don't want to lose all of the data I have entered in my tables, so I decided to test out the feature that allows you to export and import CSV files. I exported a table successfully (data was transferred to Microsoft Excel in CSV file), but when I opened the file in Microsoft Excel and added a few rows and tried to import it back in to MySQL Workbench, I got the following error:

"Error importing recordset

error calling Python module function
SQLIDEUtils.importRecordsetDataFromFile"

I've searched all over for info on this, but can't find any solutions. Does anyone know what I'm doing wrong?

Answer 1

In Workbench, open a MySQL connection and then navigate to [Server] --> [ Data Export ]. There are several backup options here, including saving the data as an individual file or folder. Choose the databases you want to export, and then click [Start Export].

If you ever prefer using Excel for editing and such, then use the MySQL for Excel plugin to access MySQL databases from within Excel. However, I don't think you need it here.

Answer 2

To export your mySQL data, use mysqldump , which will create all the schema for you.

Excel probably added some stuff to your file and now mySQL can't understand it. The best way to find out is by comparing the files before and after the change.

Answer 3

That error indicates a format problem. If the file is small enough, try opening it in wordpad (or the mac equivalent) and see if there's any difference in the formatting? Could be that the delimiting got a little messed up (this can happen especially with end of row markers in MySQL, I've noticed, it can also happen in mac to pc handoffs). If all else fails you could try exporting using a different format and see if that makes a difference (maybe tsv) when you add new rows.

Answer 4

Another reason can be the line endings used. Depending on the system and editor used to work with the cvs file it the line endings might get changed. For me mysql supported UNIX line endings. And in the editor the line ending had been set to MAC OS 9 since I was using a MAC. Changing it to UNIX line ending worked.

Answer 5

I found that it might be due to a wrong encoding of the input file. Using Notepad++ for example (or another similar editor) you need to change file encoding to UTF-8.