Does “is_any” has a bug in searchlogic? “is_any” used to work fine
for me. All of a sudden now, for unknown reasons, when I write for
example :attribute_is_any =>  , the sql output is “where
attribute != 1” which is the opposite of what I want of course.
Curiously, the problem only occurs when running with a web server
(mongrel). I see the problem in the log. But when I go to the
console, it works fine, the correct sql output is shown : “where
attribute == 1”. Basically, the same searchlogic object returns
opposite results in the console vs. through the web server.
I had to switch to “equals_any” The problem goes away. Is this a bug?