Currently, num_col:true and num_col:false are equivalent to num_col:!=0 and num_col:=0. This was done because ratings (which are really integer columns) require that behavior. However, that behavior is wrong for non-ratings numeric columns.
I have changed search to implement the following:
- ratings columns: zero is indistinguishable from not set. Searching for false will find books without a non-zero rating. Searching for true will find all books with a non-zero rating. Searching for =0 is the same as searching for false. Searching for !=0 is the same as searching for true.
- non-ratings columns: zero is distinguished from not set. Searching for false will find books with no value. Searching for true will find books with a value, including the value of zero. Searching for =anything will find books that exactly match "anything". Searching for !=anything will find books with no value or a value not equal to "anything". Searching for <anything (>anything) will find books that have a value less than (greater than) anything, but will not find books that have no value.
These changes will be in the next release.
As regards the saved search issue: I cannot duplicate it. I have a custom column named #myfloat. I entered the search
Code:
#myfloat:"<10.1" and not #myfloat:"=0"
It works. I then created a saved search named "A.Foo Bar" and turned on hierarchies in searches. Expanding "A" and clicking on "Foo Bar" resulted in the same answer as I got when I entered the search. To further test, I used the green arrow button to copy the saved search text to the search box, got what I expected to see, and got the same answer.