I'm using the query path processor and when I try to run an import I get this error:

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 'name2', 'name3', 'name4', 'name5', 'name6' at line 1

Nothing shows up in my log.

Comments

Jooblay.net’s picture

Jooblay.net commented

Do your have feeds tamper and your mapping set correctly... :) Double check to make sure you mapping is correct and you have 1 unique value ticked in you feed import.

revanshu’s picture

revanshu commented
Component: Feeds Import » Code
Issue summary: View changes

hello I am getting the same error
I am using feeds_tamper for importing taxonomy terms with multiple terms associated.
I have mapped it to the term name. Still i am getting the same error and no data is imported.
have you solve this problem @jmickela

Mizpah’s picture

Mizpah commented

Unsure if this is the same issue ? https://drupal.org/node/2271393 (currently in the XPath queue)

This is an XML import, using XPath XML Parser. The title field is marked as unique (incidentally I would prefer to mark the ITEM ID as unique, but that option is not available (field is a text field).

How can I see the entirety of the SQL query ?

AROOJ.SHAH’s picture

AROOJ.SHAH commented
Title: I get "Syntax error or access violation: 1064 You have an error in your SQL syntax" when I try to run a user import. » You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '4)' at line 1
bluegeek9’s picture

bluegeek9 commented
Status: Active » Closed (outdated)

Drupal 7 reached end of life and the D7 version of Feeds is no longer being developed. To keep the issue queue focused on supported versions, we’re closing older D7 issues.

If you still have questions about using Feeds on Drupal 7, feel free to ask. While we won’t fix D7 bugs anymore, we’re happy to offer guidance to help you move forward. You can do so by opening (or reopening) a D7 issue, or by reaching out in the #feeds channel on Drupal Slack.

If this issue is still relevant for Drupal 10+, please open a follow-up issue or merge request with proposed changes. Contributions are always welcome!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.