All my views are broken after the update.
Also, views coming from the workbench moderation module are affected.

the error message on all views:

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 'id, field_revision_field_ausgabe_livein_entity id) subquery' at line 7

please help. I don't think this is a misconfiguration in the views since they are very different in queries but getting all the similar error like above.

since i don't know which more information i can deliver, i suggest people who experiencing same issue follow this. if i am the only one here with this issue, feel free to close it.

Thanks for feedback.

Comments

kcathebat’s picture

I am having a similar issue. the view that I had in place are all fine, but when I try to create a new view they all come up as page cannot be displayed. Tried on multiple sites now and still failing even with the simplest of views.

Here is the results on a simple view I created
http://www.oregonsoccerclubs.com/?q=board#overlay-context=node%3Fq%3Dnode

Alex_eav’s picture

Hello,
I have the same problem after update to 7.x-3.3

tim.plunkett’s picture

Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

Can you please provide steps to reproduce?
Ideally, an exported view that someone can test. Don't paste it directly to the issue, use something like http://paste.pocoo.org

Alex_eav’s picture

Hello,
Here is error message:
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 'id, field_data_field_goods_groups_field_goods_groups_tid ORDER BY field_data_fie' at line 6

And here is the link to exported view http://paste.pocoo.org/show/565909/
You should look on 'Water goods' or 'Master' Display

mxh’s picture

unfortunately, i have no time at the moment to provide you more information. I will post my exported view next free time. I'm sorry for the lag. Hope the view from Alex_eav (thank you!) will help you more.

ficklecat’s picture

I also had this error on upgrading to Views 3.3. It my case it was a view using aggregation. Views was not outputing the GROUP BY correctly, the field alias was not removing a space from the grouping column "Entity ID" :

SELECT node.nid AS nid, field_data_field_company_image.entityid AS field_data_field_company_image_entityid, node.title AS node_title, MIN(node.nid) AS nid_1, 'node' AS field_data_field_company_image_node_entity_type, COUNT(field_company_ref_node.nid) AS field_company_ref_node_nid
FROM
{node} node
LEFT JOIN {field_data_field_company_ref} field_data_field_company_ref ON node.nid = field_data_field_company_ref.field_company_ref_nid
LEFT JOIN {node} field_company_ref_node ON field_data_field_company_ref.entity_id = field_company_ref_node.nid
INNER JOIN {field_data_field_company_type} field_data_field_company_type ON node.nid = field_data_field_company_type.entity_id AND (field_data_field_company_type.entity_type = 'node' AND field_data_field_company_type.deleted = '0')
LEFT JOIN {field_data_field_company_image} field_data_field_company_image ON node.nid = field_data_field_company_image.entity_id AND (field_data_field_company_image.entity_type = 'node' AND field_data_field_company_image.deleted = '0')
WHERE (( (node.status = '1') AND (node.type IN ('company')) AND (field_data_field_company_type.field_company_type_tid = '7') ))
GROUP BY nid, field_data_field_company_image_entity id, node_title
HAVING (( (COUNT(field_company_ref_node.nid) > '0') ))

Changing the grouping column to FID and then switching it back to Entity ID saves the view correctly however,

Hope this helps someone.

dawehner’s picture

@ficklecat

If you update to 7.x-3.x-dev this would be fixed as far as i remember.

Alex_eav’s picture

Yes, I've tested and can confirm, it's fixed in 7.x-3.x-dev.

tim.plunkett’s picture

Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

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