Hi all,
we noticed a change in behavior between the recent Jena versions.
SELECT *
WHERE {
BIND("2014-04-08T00:00:00"^^xsd:dateTime AS ?time0) .
BIND("2014-04-08T00:00:00+10:00"^^xsd:dateTime AS ?time1) .
BIND(xsd:date(?time0) AS ?date0) .
BIND(xsd:date(?time1) AS ?date1) .
BIND(?date0 > ?date1 AS ?compare)
With Jena 2.11 ?compare is unbound, indicating that it is impossible to
compare times or dates that have a different time zone.
Is this the expected behavior? Shouldn't it in theory figure out the
time zones itself (e.g. by aligning all to a universal time zone)
instead of failing?
What would be a work-around to do this "manually" for data that is
stored in mixed time zones?
Thanks
Holger
we noticed a change in behavior between the recent Jena versions.
SELECT *
WHERE {
BIND("2014-04-08T00:00:00"^^xsd:dateTime AS ?time0) .
BIND("2014-04-08T00:00:00+10:00"^^xsd:dateTime AS ?time1) .
BIND(xsd:date(?time0) AS ?date0) .
BIND(xsd:date(?time1) AS ?date1) .
BIND(?date0 > ?date1 AS ?compare)
With Jena 2.11 ?compare is unbound, indicating that it is impossible to
compare times or dates that have a different time zone.
Is this the expected behavior? Shouldn't it in theory figure out the
time zones itself (e.g. by aligning all to a universal time zone)
instead of failing?
What would be a work-around to do this "manually" for data that is
stored in mixed time zones?
Thanks
Holger