[
https://issues.apache.org/jira/browse/JCR-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611675#action_12611675
]
Thomas Mueller commented on JCR-1673:
-------------------------------------
> You need to mark the literal value as a date, otherwise the query will
> default to string comparison
This sounds logical, but... how does the string representation of a date look
like? I would have guessed that the string representation of
xs:dateTime('2008-07-08T15:10:07.125+10:00') is
'2008-07-08T15:10:07.125+10:00'? But if that would be the case, then
'2008-07-08T15:10:07.125+10:00' > '2008-07-09T14:55:29.774+10:00' should not
return true...
Of course you should use the correct data types (because of timezone problems
and so on), but I don't understand the example above.
> Date comparitons are backwards in Queries
> -----------------------------------------
>
> Key: JCR-1673
> URL: https://issues.apache.org/jira/browse/JCR-1673
> Project: Jackrabbit
> Issue Type: Bug
> Components: query
> Affects Versions: core 1.4.1, core 1.4.4
> Reporter: Michael Neale
> Assignee: Jukka Zitting
> Priority: Critical
>
> Imagine there is a node with jcr:created of:
> 2008-07-08T15:10:07.125+10:00
> The following query:
> SELECT ... FROM .... WHERE jcr:created < '2009-07-08T15:10:07.125+10:00'
> should return it, but it doesn't. However, if you put:
> SELECT ... FROM .... WHERE jcr:created > '2009-07-08T15:10:07.125+10:00'
> then it does return it. Whoops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
