Filtering with a given set of arguments fails when both filters are set to "force single" [#261152]

I set the priority of this bug report to minor in the event that this is somehow obviously my fault. The issue I have come across is as follows:

I have a content type (say, fruit) to which two vocabularies apply (colour and shape). I have set up a view such that I have three fields:
node: title
taxonomy: all terms (colour)
taxonomy: all terms (shape)

with filters:

node: type
taxonomy: term id (colour)
taxonomy: term id (shape)

of the above, the filters of colour and shape are both exposed. If I set one filter to 'Force single' (resulting in a drop down box) and the other with 'Force single' unchecked (resulting in a multiple-select list thingo), then any arguments I enter produce the expected result. However, when both filters are set to 'Force single' - resulting in two drop down boxes - then regardless of what arguments I enter, the view produces no result.

So, essentially, *leaving all other settings unchanged*, it works fine when one is 'Force single' and the other is not. But if I change it so that both filters force single, then no combination of arguments will produce any results. I have tested with not only with the content type and taxonomy that I'm actually working with but also with a new content type, vocabulary and term list specifically to test the error with.

The error occurs using every combination of reduce duplicates possible.

Comments

Comment #1

merlinofchaos CreditAttribution: merlinofchaos commented 21 May 2008 at 16:56

Assigned:	edmunsta	» Unassigned
Priority:	Minor	» Normal

Ok, that sounds like it is not obviously your fault, and is likely a bug.

Can you paste the query it produces in the live preview? That might give me something to go on before I reproduce the situation.

Comment #2

edmunsta CreditAttribution: edmunsta commented 22 May 2008 at 04:41

Ok here's the query when one if 'force single' and the other is not (ie. query works):

SELECT node.nid AS nid,
   node.vid AS node_vid,
   node.title AS node_title,
   users.name AS users_name,
   node_comment_statistics.comment_count AS node_comment_statistics_comment_count,
   node_comment_statistics.last_comment_timestamp AS node_comment_statistics_last_comment_timestamp
 FROM node node 
 INNER JOIN term_node term_node ON node.vid = term_node.vid
 LEFT JOIN term_node term_node_59 ON node.vid = term_node_59.vid AND term_node_59.tid = 59
 LEFT JOIN users users ON node.uid = users.uid
 LEFT JOIN node_comment_statistics node_comment_statistics ON node.nid = node_comment_statistics.nid
 WHERE (node.type in ('helprequest')) AND (term_node.tid = 7) AND (term_node_59.tid = 59)
   ORDER BY node_title ASC

And here is the query when both are set to force single:

SELECT node.nid AS nid,
   node.vid AS node_vid,
   node.title AS node_title,
   users.name AS users_name,
   node_comment_statistics.comment_count AS node_comment_statistics_comment_count,
   node_comment_statistics.last_comment_timestamp AS node_comment_statistics_last_comment_timestamp
 FROM node node 
 INNER JOIN term_node term_node ON node.vid = term_node.vid
 LEFT JOIN users users ON node.uid = users.uid
 LEFT JOIN node_comment_statistics node_comment_statistics ON node.nid = node_comment_statistics.nid
 WHERE (node.type in ('helprequest')) AND (term_node.tid = 7) AND ()
   ORDER BY node_title ASC

So it appears as though it just completely skips the filter or something.