Download & Extend
Views Calc » Issues

Wrong join added to query when node translation enabled

Posted by floretan on May 30, 2009 at 2:07am
Project:Views Calc
Version:6.x-1.3
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

Here's how to reproduce the problem:

Create a views_calc field with %node.nid as its value.
Create a node view with the views_calc field that you created.
The following query is generated:

SELECT node.nid AS nid,
   (node.nid) AS cid2
FROM node node

Now enable the core "content translation" module. The generated query is now:

SELECT node.nid AS nid,
   (node.nid) AS cid2
FROM node node
LEFT JOIN node node2 ON node.tnid = node2.tnid

What happens is that when the content translation module is enabled, the join data from translation.views.inc is used and you end up with a gazillion rows because of the extra join.

This is most likely a bug in views and would appear in any module that tries to do a $query->add_table('node') twice with the content translation module enabled, but I'm posting it here since it really appears in a views_calc context.

Login or register to post comments

Comments

#1

Posted by hansrossel on October 28, 2009 at 8:02am

I can confirm this. Also the SUM is multiplied by the number of languages, so 3 languages gives a sum that is 3 times the expected value.

#2

Posted by hd on September 22, 2010 at 2:24am

Before I came across this post I created http://drupal.org/node/904038 which pretty much confirms what is being described here.

#3

Posted by miro_dietiker on January 19, 2011 at 12:16am
Title:Wrong join added to the query when i18n is enabled» Wrong join added to query when node translation enabled
Category:bug report» feature request

This might depend the translation mode.

Possibly translation cases currently simply are not supported. I even think, we should call this feature request.