jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Parvulescu <alex.parvule...@gmail.com>
Subject Re: Multi-value properties and order
Date Tue, 25 Mar 2014 14:00:08 GMT
Hi,

> While chatting with a colleague he raised a doubt abut if the order is
> kept or it could change over the time.

guilty as charged :)

Sorry about the confusion, I was thinking about the fact that the child
nodes don't have a guaranteed order, and applied the same line of thinking
for the properties too.

Thanks Jukka for clarifying!

Out of curiosity, do we have any tests that verify this behavior?


best,
alex


On Tue, Mar 25, 2014 at 2:51 PM, Jukka Zitting <jukka.zitting@gmail.com>wrote:

> Hi,
>
> On Tue, Mar 25, 2014 at 9:43 AM, Davide Giannella
> <giannella.davide@gmail.com> wrote:
> > While chatting with a colleague he raised a doubt abut if the order is
> > kept or it could change over the time. So if I have { ":next" : [ "a",
> > "b", "c" ] } is it guaranteed that it will always be "abc" and not "cba"
> > or something else other times?
>
> The value list of a multi-valued property always keeps its order.
>
> For example, we use a multi-valued property to store the order of the
> children of an orderable node.
>
> BR,
>
> Jukka Zitting
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message