search -compare "{!= key value}" produces bogus results for indexed columns about speedtables HOT 4 CLOSED

The problem was that the optimizer was prematurely setting the walk-type to a HASH walk rather than an INDEX walk when evaluating a possible HASH walk, after setting up for an INDEX walk, but before discarding the HASH. So it was performing a HASH walk with a search structure set up for an INDEX walk.

Let me know if this latest update fixes it.

from speedtables.

Yup, seems to work for my example! Though it's hard for me to say if it regresses anything else, since this type of problem wasn't caught by the current test cases.

You left the debug printing enabled in your commit, so another commit is needed to disable or remove it.

So the problem wasn't specifically due to the != operator, but the types of two indexes being used to optimize the search. This could have a lot of unexpected and wide-impacting behavior.

from speedtables.

You got into that quickly. I did another commit to remove the debug print shortly afterwards.

I'm pretty sure there's no regression, I know what decision I made that caused this one to happen, it was a switch to using indexes rather than hashes for some searches.

from speedtables.

Closing, since your commit seems to fix it.

from speedtables.