Views Arguments+Content Taxonomy: Allow multiple terms per argument (1,2,3) AND not working

(fixed version)

OK, I've been digging into this one for hours today, and it's far too easy to get caught in the web of code that is views and cck. Here's what I've managed to figure out:

I believe what's happening is that Content Taxonomy's attempt to set the handler to content_taxonomy_handler_filter_many_to_one isn't sticking. When I look at $this->argument with dpm in the build function of view.inc, it claims that the content handler is content_handler_argument_numeric. However if I do a similar test with a view based on numbers instead of content taxonomy (allowing multiple values), it claims the content handler is content_handler_argument_many_to_one.

I notice that the module makes reference to content_taxonomy_handler_filter_many_to_one but not to content_taxonomy_handler_argument_many_to_one... could this be the missing element? I've tried hacking it in alongside the filter and unfortunately it doesn't appear to be doing anything. :(

I feel quite close on this one, any guidance or assistance would be much appreciated!

The SQL for AND and OR are both identical.. both look like the OR clause.

Here is the SQL for an AND argument in the Content Taxonomy View: 129,131

SELECT DISTINCT(node.nid) AS nid,
   node.title AS node_title,
   node.type AS node_type,
   node.vid AS node_vid
 FROM qcskunkworks_node node 
 LEFT JOIN qcskunkworks_content_field_tax_one node_data_field_tax_one ON node.vid = node_data_field_tax_one.vid
 WHERE (node.type in ('tax_test')) AND (node_data_field_tax_one.field_tax_one_value IN (129, 131))
 GROUP BY nid

And here is the SQL for an OR argument in the Content Taxonomy View: 129+131:

SELECT DISTINCT(node.nid) AS nid,
   node.title AS node_title,
   node.type AS node_type,
   node.vid AS node_vid
 FROM qcskunkworks_node node 
 LEFT JOIN qcskunkworks_content_field_tax_one node_data_field_tax_one ON node.vid = node_data_field_tax_one.vid
 WHERE (node.type in ('tax_test')) AND (node_data_field_tax_one.field_tax_one_value IN (129, 131))
 GROUP BY nid

By my eye that's identical.

However, if I create another view, this time restricting by a CCK numeric field, the SQL is obviously different.

Here is the SQL for an AND argument in the CCK Numeric View: 10,20

SELECT node.nid AS nid,
   node.title AS node_title,
   node.type AS node_type,
   node.vid AS node_vid
 FROM qcskunkworks_node node 
 INNER JOIN qcskunkworks_content_field_tax_num node_data_field_tax_num_value_0 ON node.vid = node_data_field_tax_num_value_0.vid AND node_data_field_tax_num_value_0.field_tax_num_value = 10
 INNER JOIN qcskunkworks_content_field_tax_num node_data_field_tax_num_value_1 ON node.vid = node_data_field_tax_num_value_1.vid AND node_data_field_tax_num_value_1.field_tax_num_value = 20
 WHERE (node.type in ('tax_test')) AND (node_data_field_tax_num_value_0.field_tax_num_value = 10 AND node_data_field_tax_num_value_1.field_tax_num_value = 20)

And here is the SQL for the OR argument in the CCK numeric view: 10+20:

SELECT node.nid AS nid,
   node.title AS node_title,
   node.type AS node_type,
   node.vid AS node_vid
 FROM qcskunkworks_node node 
 INNER JOIN qcskunkworks_content_field_tax_num node_data_field_tax_num ON node.vid = node_data_field_tax_num.vid
 WHERE (node.type in ('tax_test')) AND (node_data_field_tax_num.field_tax_num_value IN (10, 20))

As you can see, for content taxonomy everything behaves like an OR (10+20) rather than an and (10,20)... although it uses LEFT JOINs instead of INNER JOINs.. I can't seem to pin down where this is happening.

Somehow this clause in the SQL:

 LEFT JOIN qcskunkworks_content_field_tax_one node_data_field_tax_one ON node.vid = node_data_field_tax_one.vid
 WHERE (node.type in ('tax_test')) AND (node_data_field_tax_one.field_tax_one_value IN (129, 131))

Needs to become:

 INNER JOIN qcskunkworks_content_field_tax_one node_data_field_tax_one_value_0 ON node.vid = node_data_field_tax_one_value_0.vid AND node_data_field_tax_one_value_0.field_tax_one_value = 129
 INNER JOIN qcskunkworks_content_field_tax_one node_data_field_tax_one_value_1 ON node.vid = node_data_field_tax_one_value_1.vid AND node_data_field_tax_one_value_1.field_tax_one_value = 131

... and I can verify this does in fact only return the correct results.

Are there good examples for overwriting the where condition in the SQL query? I'm about ready to do this and give up on doing it properly... It just feels like I'm so damned close to figuring it out and breaking through to a new undestanding of views.

EDIT: code tags, clarification on where each of the four queries are generated.

Another is to just write your own queries (take the url, turn it to what you need, db_query ("SELECT..."), etc) and stuff into something like PHP field, if it works.

Just to verify, you're actually advocating bypassing views all together and just creating a standard PHP page that renders data? I feel a bit sad that views might not be up for the task, but I will have to resort to that if it doesn't work.

I've been working with dereine on IRC for about an hour on this one, and can confirm it does in fact work. Thank you so much dereine!

I feel good that I was about 80% of the way there to understanding this problem. Hopefully I'll be able to tackle tough ones like this in the future on my own.

I think I understand Geir19's frustration/confusion. We're actually talking about two different things:

http://drupal.org/node/924648#comment-3912034

Just for the record, I am *not* attempting to use "Taxonomy: Term ID" or "Taxonomy: Term ID (with depth)" as an argument. Rather I am using a content_taxonomy CCK field "Content: Field name (field_xyz)". There is an option under Content Types > Manage Fields that allow you to tie changes in the CCK field to the taxonomy of the node. I am not using this, and have it turned off.