With complex queries, SearchQuerySet.exclude() filters instead of excludes about xapian-haystack HOT 4 CLOSED

Well, I guess actually it needs to be an AND_NOT with an extra set of () around the subqueries. After a week of working on nothing but this, my head is spinning. :-)

from xapian-haystack.

Sorry it took me so long to respond to this.

I think I see what's going wrong here. The problem is the result of using SQ with exclude. I'm not sure if the issue is with Haystack itself yet, or if it's the Xapian backend. I'll need to speak with Daniel before I can be sure.

In the meantime, I'd recommend building an query that combines exclusion filters and SQ by doing something like:

 sqs.filter(~SQ(
     SQ(contenttype='events.event) & SQ(date__lte=(today - SITE_SEARCH_EVENTS_FROM) & SQ(date__gte=(today + SITE_SEARCH_EVENTS_TO))
 ))

from xapian-haystack.

Confirmed that the problem is the exclude(SQ(...)) bit. It's definitely canceling itself out. i.e., what's happening is:

sq.exclude(*args) actually, internally, calls sq.filter(~SQ(*args)), so when you pass in a SQ as the arg, you're getting:

sq.filter(~SQ(SQ(foo))

The result; the opposite of what you want.

I think you're best bet is to use filter directly with a ~SQ. This should give you the behaviour you're expecting.

I'm going to keep this ticket open until I get feedback from Daniel, just to be absolutely certain I'm understanding this is working as designed.

from xapian-haystack.

Resolved on IRC and git messages.

from xapian-haystack.