[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407997#comment-13407997
]
Thomas Mueller commented on OAK-169:
------------------------------------
> ordering as a linked list
That's possible, and would scale (no limit on the number of child nodes). It
would be a bit more complicated to implement than simply storing the order as a
multi-valued property: to support efficient move and remove operations, a
doubly linked list (or a skip list) would be needed. Also, the parent node
would need a pointer to the first and last node. When using a multi-valued
property for chaining, it would still only need one property. I have tried to
implement such a feature in the MicroKernel prototype some time ago, but didn't
continue as it turned out a bit complicated to get right (but it's far less
complicated than implementing a b-tree).
> Support orderable nodes
> -----------------------
>
> Key: OAK-169
> URL: https://issues.apache.org/jira/browse/OAK-169
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
> Reporter: Jukka Zitting
>
> There are JCR clients that depend on the ability to explicitly specify the
> order of child nodes. That functionality is not included in the MicroKernel
> tree model, so we need to implement it either in oak-core or oak-jcr using
> something like an extra (hidden) {{oak:childOrder}} property that records the
> specified ordering of child nodes. A multi-valued string property is probably
> good enough for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
