Thank you, this was helpful - we also observed the +14 hours issue and
worked around it by adding time zone to the constants generated SPARQL
queries.
Thanks again
Holger
On 4/10/2014 22:18, Rob Walpole wrote:
We hit this exact problem a while ago...
Basically if no timezone is specified
We hit this exact problem a while ago...
Basically if no timezone is specified then it takes the max and min
possible timezone difference, i.e. +14 hours and -14 hours, and for
anything that falls within this block of time no comparison can be made.
The best solution is just to add the timezone