Error message
"in not implemented" - when I try to filter by node type this error throws
Even no data has been fetched

Comments

jiivonen’s picture

Do you have MongoDB as field storage? Or do you get this with MySQL?
I get this with MongoDB but can't decide where to fix it.

cpc’s picture

I was able to fix this problem by updating the mongodb module in "mongodb_field_storage.module" down in the _mongodb_field_storage_query_value function.

The problem is a case comparison where lowercase 'in' is being compared against uppercase 'IN'.

I changed:
switch ($operator) {

to:
switch (strtoupper($operator)) {

...and that worked for me.

Someone should commit this update...

roynilanjan’s picture

@CPC is it a hack or you should give a patch?

jiivonen’s picture

I provided that patch already in february in http://drupal.org/node/1459116 But it was not included. Probably you could go there and give more feed back why it's needed?

chx’s picture

Status: Active » Closed (duplicate)

I will fix it over there.

chx’s picture

Status: Closed (duplicate) » Active

Hrm, I was wrong :) the documentation clearly says IN and so I will fix it here.

firebird’s picture

Status: Active » Needs review
StatusFileSize
new1.06 KB

Here's a quick and dirty patch that fixes the problem for me.

chx’s picture

Status: Needs review » Needs work

Thanks for the patch but this IMO should be fixed in the IN handlers themselves (handlers/efq_views_handler_filter_entity_in_operator.inc, handlers/efq_views_handler_filter_field_in_operator.inc, handlers/efq_views_handler_filter_property_in_operator.inc)

jiivonen’s picture

How about ALL, STARTS_WITH, CONTAINS and BETWEEN, should we open separate issues about them and their case or include in this one?

chx’s picture

Status: Needs work » Fixed

Check the alpha. ALL is not supported by EntityFieldQuery, STARTS_WITH, CONTAINS and BETWEEN is implemented.

Status: Fixed » Closed (fixed)

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