: nice not to have to think about this on the client side. Perhaps I am just
: missing something. In other words, do we support Lucene's DateTools
: Resolution capabilities?
currently the only way to do something like this with DateField is for the
client to specify a rounding operation when in
On Aug 15, 2009, at 10:11 AM, Yonik Seeley wrote:
Now that we have date fields that internally store milliseconds (and
can currently be used in function queries) we have the basis for a
good replacement for using things like ord(date)... which is now a bad
idea since it causes the FieldCache to
: Yeah, I've had the same idea... typing of the functions. I think
: we'll get to that sooner or later, but I'm not sure it's something we
: can do for 1.4, and it would seem to cause a proliferation of classes
: (or switch statements at every level?).
i don't see why it would cause either ... a
On Sat, Aug 15, 2009 at 11:16 AM, Chris
Hostetter wrote:
>
> : We could either:
> : - change function queries to use doubles internally - probably a good
> : idea for the future in general - seems like geo might need more
> : precision too.
> : - come up with a new date scale function that uses dou
: We could either:
: - change function queries to use doubles internally - probably a good
: idea for the future in general - seems like geo might need more
: precision too.
: - come up with a new date scale function that uses doubles internally?
off the cuff idea i remember thinking of a long ti
