thanks for detailed explanation.
John Haxby wrote:
Volodymyr Bychkoviak wrote:
User has an input (javaScript calendar) on page where he can choose
some date to include in search. Search resolution is day resolution.
If user will enter same date in different time of date he will get
different
Volodymyr Bychkoviak wrote:
User has an input (javaScript calendar) on page where he can choose
some date to include in search. Search resolution is day resolution.
If user will enter same date in different time of date he will get
different results (because calendar will also set current hour
Ok, I'll try to explain a bit.
User has an input (javaScript calendar) on page where he can choose some
date to include in search. Search resolution is day resolution.
If user will enter same date in different time of date he will get
different results (because calendar will also set current
John Haxby wrote:
I ran across the problem with DateTools not using UTC when I tried to
use an index created in California from the UK: I was looking for
documents with a particular date stamp but I found documents with a
date stamp from the wrong day. Even more interesting and bizarre
things
Volodymyr Bychkoviak wrote:
I'm using DateTools with Resolution.DAY.
I know that dates internally are converted to GMT.
Converting dates "2006-10-01 00:00" and "2006-10-01 15:00" from
"Etc/GMT-2" timezone will give us
"20060930" and "20061001" respectively.
But these dates are identical with
I'm using DateTools with Resolution.DAY.
I know that dates internally are converted to GMT.
Converting dates "2006-10-01 00:00" and "2006-10-01 15:00" from
"Etc/GMT-2" timezone will give us
"20060930" and "20061001" respectively.
But these dates are identical with day resolution.
Is this bug
