eDir2eDir: Structured Attribute Problem

[geoffc]

EricVeysey wrote:
> Thanks for the replies!
>
> I've done a query of our tree and found indeed it was a unique number.
>
> I saw some examples of people sticking 0 for the namespace. I've added
> 10 accounts with the 0 as namespace and it works.
>
> I read up about definition of namespace:
>
> name space
> Controls the syntax of naming, such as which characters are legal in
> filenames and path separators, how long the name can be, and whether
> case is significant and/or preserved.

Alas the context is incorrect for this one...

You are referring to nameSpace in general, most specifically in the case
of an actual Path attribute.

Here we are overloading the syntax, such that we are using nameSpace for
something else. What that something else is? No clue.



> Every volume must have one or more name spaces associated with it. If a
> volume has more than one name space associated with it, valid filenames
> will be maintained on that volume for all of its name spaces. If a file
> name is legal in more than one name space, it is stored only once and
> shared by the name spaces.
>
> I've come to the conclusion that 0 would mean no restriction on the
> value, and since I'm inputting a static value there should be no problem
> with it.
>
> Any thoughts?
>
>