On 9/27/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> The simple workarround: if you know all of your data is indexed with
> perfect 0.000second precision, then put "-1MILLI" at the end of your start
> and end date faceting params.
It fixed my problem. Thanks.
--
Guillaume
On 9/27/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> a better option (assuming a query parser change) would be a new option
> thta says wether each computed range should be enclusive of the low poin,t
> the high point, both end points, neither end points, or be "smart" (where
> smart is the sam
: I'm now using date facetting to browse events. It works really fine
: and is really useful. The only problem so far is that if I have an
: event which is exactly on the boundary of two ranges, it is referenced
: 2 times.
yeah, this is one of the big caveats with date faceting right now ... i
st
Hi all,
I'm now using date facetting to browse events. It works really fine
and is really useful. The only problem so far is that if I have an
event which is exactly on the boundary of two ranges, it is referenced
2 times.
If we admit that we have a gap of 6 hours starting from 2007-09-27
12:00,
