[
https://issues.apache.org/jira/browse/JCR-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611941#action_12611941
]
Marcel Reutegger commented on JCR-1673:
---------------------------------------
Jackrabbit translates a JCR date into a string representation that has a
lexicographical order equivalent to the JCR date order. When you use a string
literal in your query then Jackrabbit will match that literal with the string
representation of the date, which gives you a somewhat surprising result.
> 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.
