I'm using the latest dev version of cnr with PostgresQL 9.0 as a database. When trying to update existing nodes I get the following error:

PDOException: SQLSTATE[22P02]: Invalid text representation: 7 ERROR: invalid input syntax for integer: "werkproces_per_kerntaak" LINE 4: AND nid > 'werkproces_per_ker... ^: SELECT nid FROM {node} WHERE type IN (:types_0) AND nid > :args ORDER BY nid LIMIT 50 OFFSET 0; Array ( [:args] => werkproces_per_kerntaak [:types_0] => werkproces_per_kerntaak ) in corresponding_node_references_batch_update_existing_nodes() (line 324 of /Users/eric/Sites/drupal7-unstable/sites/all/modules/cnr/corresponding_node_references.module).

The to be updated content type has an "unlimited" kind of relation. Maybe PostgresQL is more "picky" in checking some constraints? Can anybody confirm if there is an issue with updating existing nodes with PostgresQL? If not so, I'll have to look in some other direction.

Kind regards,

CommentFileSizeAuthor
#5 add_field_attach_presave-1153786-5.patch503 bytesacrollet
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sneyerst’s picture

Subscribing... (same issue on SQL Server).

ivevangenechten’s picture

Same here...

czigor’s picture

Status: Active » Fixed

This might be solved by #1250024: "Update existing nodes" only updates certain nodes, please reopen if problem still exists.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

acrollet’s picture

Status: Closed (fixed) » Needs review
FileSize
503 bytes

I had a similar problem when updating a node with a cck link field, see related issue #1290904: Link > node_load() > field_attach_update() =PDOException: SQLSTATE[42000] INSERT INTO {field_data_field_link}. Adding a call to field_attach_presave before the field_attach_update in the _corresponding_node_references_update function worked for me. patch attached.

acrollet’s picture

Status: Needs review » Closed (fixed)

On second thought, these issues are not closely related enough to warrant re-opening this issue. Closing, and will open a new ticket.