> There is prefix compression used on term values. So you could pad > numbers with lots of leading zeros and not incur much additional > size... 000000000001, for example.
Interesting... One annoyance I have run across is the impedance mismatch between range queries and sorting. If your terms are indexed as standard numbers, then integer sorting is fast, but range queries don't work (for negative values). If you format the terms such that range queries work for any integer, then you have to use the slower string (or custom) sorting. Is there a way around this besides writing my own custom sorting hit collector? -Yonik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
