Resolved Load icecat indexes Column count doesn't match value count at row 1

So i get a patch later?
Thanks Roland

Hello,

If we get the column count, this means the line is even longer than the new length I set. To prevent such issues in the future I will set it to 0. This makes the import a little slower but we won't have a problem with very long lines.

when i do single 500 lines i got: Column count doesn't match value count at row 471

Dear Roland,

First i was glad it was running, but after a while got again error:
Column count doesn't match value count at row 971

Hello,

Ok, this is a surprise. I ran the import with 3 lines and single mode and it runs and runs and after 5 batches I cancelled it assuming all is fine. Running with your setting of 20 lines I can see the issue as well.

Now I also know why. There is 1 line in that CSV of 100,000 lines that is super duper long compared to the rest. Almost 3000 characters long, we only read the first 2048 characters. So that caused an invalid entry. Anyhow, all fixed.

Please follow the same steps as before and you should be OK.

Let me know how it goes.

when i do single and 20 lines then 20 lines are imported but following error:
Column count doesn't match value count at row 4

i installed the patch
verified database
but in maintenance i have now another error: Column count doesn't match value count at row 24

Hello,

I had a look and noticed that ICEcat added 2 new columns and this is causing the error you see. Attached is a patch file that you can load. This patch contains the fixes regarding the ICEcat change.

After you loaded the patch, please take the following steps:

1. Go to CSVI via Extensions -> CSVI Pro
2. Click on About in the left menu
3. Click on Verify Database in the toolbar (this takes a moment to complete)
4. Go to Maintenance
5. Now you can load the ICEcat indexes

This should complete without a problem now.

Please let me know how it goes.

Hello,

The column count error means there is something going wrong with the insert of the data. I am going to check that and get back to you.

As for the Full loadtype, the MySQL function LOAD DATA LOCAL INFILE must be enabled. On most hosting platforms this is disabled by default.