On 2.9.14 8:12 , Tobias Bocanegra wrote:
I would allow the "*[n]" suffix format for names and paths but not
being smart about it. eg:
session.getNode("/foo/bar[5]");
-> works if such a node exists
"/foo".addNode("bar")
-> works, if "bar" does not exist, otherwise fails
"/foo".addNode("
On 2.9.14 8:12 , Tobias Bocanegra wrote:
"/foo".addNode("bar[3]")
-> works, if "bar[3]" does not exist, otherwise fails
This violates the contract though: "The relPath provided must not have
an index on its final element." I think we should restrict ourselves to
the read methods and not
hi,
On Tue, Sep 2, 2014 at 8:11 AM, Michael Dürig wrote:
>
> Hi,
>
> There was a discussion on the user list re. this [1]: When upgrading a
> repository that contains SNSs, those are treated according to Oak's basic
> same name sibling support. That is, the names of such nodes are suffixed
> with
Hi,
There was a discussion on the user list re. this [1]: When upgrading a
repository that contains SNSs, those are treated according to Oak's
basic same name sibling support. That is, the names of such nodes are
suffixed with their indexes in square brackets (see OAK-203 [2]). This
is probl
