[
https://issues.apache.org/jira/browse/OAK-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407987#comment-13407987
]
Thomas Mueller commented on OAK-169:
------------------------------------
Carstens use case for "log entries" seems quite common. More generally, a
sequence of nodes, with a incremental name or timestamp name (2012-01-12
12:03:45.0, 2012-01-12 12:03:46.3,...). This matches OAK-129 (Add support for
auto creating node names). Having to use queries seems complicated. Of course
the known workaround (use a multi-level structure to avoid flat nodes) is
possible but then I think we agreed we want to support "many child nodes".
I believe most uses cases could be solved if child node lists are automatically
ordered by name. That means, if node are not manually ordered, they are sorted
by name. This matches what many file systems do, is easy to understand and use,
and easy to implement (including support for huge number of child nodes).
> 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
