Would you suggest that search in selection type functionality use filters or
redo the search with an AND clause?
--Peter
On 7/26/02 10:18 AM, "Doug Cutting" <[EMAIL PROTECTED]> wrote:
> Also, a Filter implementation can cache bit vectors for common queries.
> When this is appropriate, Filters
Peter,
I did something like this. It's based on a numeric data type we support. The
only difficulty is that you must specify the size and precision of the
number in order for it to be normalized and collate properly. The
alternative is to set a maximum size and normalize all your numeric data to
What would be the criteria for Numeric support?
Currently we are looking to add the ability to hack around adding numeric
support by creating a NumberField (exactly analogous to DateField).
The idea right now is that it would pad the numbers to some level, and only
handle integers at the beginni
Armbrust, Daniel C. wrote:
> I don't know what a "good" numbers implementation is, but the way that I do it now,
>with filters on the bit set after they come back just feels like a hack. Even if bit
>sets are very fast, it doesn't seem right to iterate over nearly the entire set of
>terms to f
