SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'last_comment_uid' at row 1

I'm getting a similar error. Looks like it's caused by a custom element. Any fix/config for feeds to ignore custom fields?

SQLSTATE[HY000]: General error: 1366 Incorrect integer value: 'Matt' for column 'last_comment_uid' at row 1

Edit: using dev version of feeds, generic import form, HTTP Fetcher, Simple Synd. Parser, Node Processor

I was also receiving these errors but - I figured it out!

The reason this was happening is because the original importer that I cloned had a uid element left in it. So when it's attempting to import content with a column that is missing for UID it basically fails. Ooops.

I am getting this error message as well, and Feeds report 0 imports, yet the content is imported!

I have just a single column text file with titles. The content type has some fields (none required), and the import fails on those.

Any tips?

Very simple dear your CSV file is not utf 8 encoded that is required when inserting a database record of a node

Thanks I tried the following in Notepad++
-convert to uft8 the encoding
-convert line endings to Unix

The error still exists unfortunately.

This is an encoding problem with the text. Not a bug.

You might try html entity decode in feeds_tamper.

Even in utf8 encoded data, I always have problems with entities being in text they don't belong in. Below is a sample set from a recent project. The text going into drupal should not have the entities such as & in most fields (title, body, etc.).

    $from[] = '&';    $to[] = '&';
    $from[] = ' ';   $to[] = ' ';
    $from[] = '‘';  $to[] = "‘";
    $from[] = '’';  $to[] = "’";
    $from[] = '“';  $to[] = "“";
    $from[] = '”';  $to[] = "”";
    $from[] = '–';  $to[] = "–";
    $from[] = '—';  $to[] = "—";
    $from[] = '•';   $to[] = '•';
    $from[] = '™';  $to[] = '™';
    $from[] = '®';    $to[] = '®';
    $from[] = '©';   $to[] = '©';
    $from[] = 'é'; $to[] = 'é';
    $from[] = 'í'; $to[] = 'Í';
    $from[] = 'ñ'; $to[] = 'ñ';
    $from[] = 'í';   $to[] = 'í';
    $from[] = 'ñ';   $to[] = 'ñ';
    $from[] = ' ';   $to[] = ' '; 

    $from[] = '\x26';     $to[] = '&';
    $from[] = '\xA0';     $to[] = ' ';
    $from[] = '\x2018';   $to[] = "‘";
    $from[] = '\x2019';   $to[] = "’";
    $from[] = '\x201C';   $to[] = "“";
    $from[] = '\x201D;';  $to[] = "”";
    $from[] = '\x2013';   $to[] = "–";
    $from[] = '\x2014';   $to[] = "—";
    $from[] = '\x97';     $to[] = '—';
    $from[] = '\x2022';   $to[] = '•';
    $from[] = '\x2122';   $to[] = '™';
    $from[] = '\xA9';     $to[] = '©';
    $from[] = '\xAE';     $to[] = 'R'; 
    $from[] = '\xE9';     $to[] = 'é';
    $from[] = '\xED';     $to[] = 'í';  
    $from[] = '\x92';     $to[] = '"'; 
    $from[] = '\x93';     $to[] = '"';
    $from[] = '\xF1';     $to[] = 'ñ';
    $from[] = '\xED';     $to[] = 'í';

Hello,

Wanted to share my solution:

I did not have default values set for required fields. After setting those my problem went away. For me encoding was not the issue.

Can you please explain what fields and where i.e. which module etc. I have the same error and can find out what causes it..

For this particular error referencing last_comment_uid, I turned off the core Comment module during my feeds import and the error disappeared.

I am also experiencing this error when using a 7.x-2.x-dev Feed importer with FeedsNodeProcessor.

SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'last_comment_uid' at row 1

I can confirm that disabling the comment module allows me to import. Although that is not an acceptable solution.

I looked into the database to found this error is happening on this table: node_comment_statistics

I discovered in my case that the error is being caused when a new nodes is being created and the function comment_node_insert() is passed a $node parameter that does not have the $node->uid set. That function is called from entity_save() in FeedsNodeProcessor.inc.

So, I proposed a patch that is a quick fix solution (at least in my case). I am not sure if this problem needs to be fixed elsewhere in the code, but my patch will ensure $entity->uid is set.

updated patch to utilize entityValidate function.

can you provide an import file to test this fix with. I like the change, but don't have any way to verify the change actually works before I commit this patch.

Thanks.

I got the problem with multiple imports as well when using the FeedsHTTPFetcher. I tried to apply the path from #11 and #13 to the FeedsHTTPFetcher, but it doesn't work for me.

I like to help out with this, but I am still quite new to Drupal coding, so I am not sure where to start (with debugging or whatever).

@vogelsang, when you say "it doesn't work for me" did you mean the patch didn't apply or the patch did apply but you still experienced errors? Are you using the latest 7.x-2.x-dev? Can you provide any example of what you are try to do?

Even better title. I am still getting this. Is it just us that face this issue?

Thanks, #13 patch still applies clean and works :)

I re-rolled the patch, should apply to latest 7.x-2.x-dev.

http://drupalcode.org/project/feeds.git/commit/3b51292