> One can also index all of these (or even more) and hide them from the > user: > > YYY > YYYMM > YYYMMDD > YYYMMDDHH > YYYMMDDHHMM > YYYMMDDHHMMSS > > With this, searching ranges would require subclassing the QueryParser > with classes that implement the range search using as few terms as > possible. > That should bring down the number of terms used to a some logarithm > of the total range size.
Yep, that's what we do for large date ranges and it works fine. Just a little logic to determine the way to expand the user input to the least possible terms. Sincerely, James
