Torgeir Veimo wrote:
>
>
> On 24 Aug 2006, at 00:30, JavaJ wrote:
>
>>
>> Is there some kind of tool available that will allow you to inspect
>> and
>> traverse your repository through a UI, like inspect nodes,
>> properties, node
>> types?
>
> Are you looking for desktop or HTML based?
no, only if you alter the references pointing to NodeX.
On 9/12/06, Michael Neale <[EMAIL PROTECTED]> wrote:
right, so saving a document, which itself has only one reference, causes ALL
the references of NodeX to be updated/saved?
On 9/12/06, Christoph Kiehl <[EMAIL PROTECTED]> wrote:
>
> Mic
right, so saving a document, which itself has only one reference, causes ALL
the references of NodeX to be updated/saved?
On 9/12/06, Christoph Kiehl <[EMAIL PROTECTED]> wrote:
Michael Neale wrote:
> I gather you are referring to saving the node that has all the
> references as
> attributes?
Michael Neale wrote:
I gather you are referring to saving the node that has all the
references as
attributes?
ie:
NodeA ---> NodeX *
Where there are 100 000 NodeX instances. NodeX.getReferences() would then
return just one NodeA (in this case).
No, my scenario is the following:
NodeA * --
I gather you are referring to saving the node that has all the references as
attributes?
ie:
NodeA ---> NodeX *
Where there are 100 000 NodeX instances. NodeX.getReferences() would then
return just one NodeA (in this case).
So when you save NodeA - you are saving all the references - and I woul
currently the referencing is not optimized at all. your results are expected.
using UUIDs or paths as references is a valid alternative, although
the Node.getReferences() is more expensive since you need to use the
query.
regards, toby
On 9/11/06, Christoph Kiehl <[EMAIL PROTECTED]> wrote:
Hi,
