You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am upgrading from Haystack 2.1.0 and commit 37add92 of the xapian-backend. I have switched to Haystack 2.3.1 and the latest version of this backend, which at this time is a3a3a4e.
After doing some manual testing I have noticed some different behavior. I do not know if this is a problem with Haystack, the xapian backend, or what...
I stepped through the code in both my old and new environments and it looks like it is not a Haystack issue. Haystack seems to pass the same parameters in both cases to the backend. However the new backend is building a very different query than before.
The biggest thing I see is that the new code in _query_from_term() does a if field_name == 'content' but then keeps going and falls into the new if/then/else and hits the exact case. The old code only did the content check. So the new code ends up with a 2 element query_list whereas the old code has 1 element. Hope that makes sense.
I'll try to play around with the code some more but I don't quite have the background yet to understand what's going on. Hopefully a dev can take a look at this.
I am upgrading from Haystack 2.1.0 and commit 37add92 of the xapian-backend. I have switched to Haystack 2.3.1 and the latest version of this backend, which at this time is a3a3a4e.
After doing some manual testing I have noticed some different behavior. I do not know if this is a problem with Haystack, the xapian backend, or what...
Under my old environment, both calls to
sqs.count()
would return the same number of results.Do you have any thoughts or advice on how to troubleshoot or debug this further?
Thank you!
The text was updated successfully, but these errors were encountered: