[
https://issues.apache.org/jira/browse/OAK-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979482#comment-13979482
]
Michael Dürig commented on OAK-1763:
------------------------------------
bq. Probably the best solution is to pass down to the
IndexStoreStrategy.update() the PropertyValue itself and leave it decide what
to do with it.
Something along these lines might work best here... right.
bq. About the heuristic approach...
Not sure whether this works correctly e.g for cases like \["goofy", "42",
"Arthur"]. How would you ensure that numbers are compared as strings here?
bq. Maybe filing a different bug for that?
Might make sense yes.
> OrderedIndex does not comply with JCR's compareTo semantics
> -----------------------------------------------------------
>
> Key: OAK-1763
> URL: https://issues.apache.org/jira/browse/OAK-1763
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Michael Dürig
>
> The ordered index currently uses the lexicographical order of the string
> representation of the values. This does not comply with [JCR's compareTo
> sementics |
> http://www.day.com/specs/jcr/2.0/3_Repository_Model.html#3.6.5.1%20CompareTo%20Semantics]
> for e.g. double values.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
