What does happen if I need a different propery to be unique among nodes of the same type? (let's say, no two nodes with the same 'name' property).
I have the same problem that Brice_ has, and the solution I came up with was to query the repository for another node with the same property before adding a new one. Is there any practical problem with this approach I am not aware of? Thanks, Rodrigo. On Thu, Aug 20, 2009 at 9:06 AM, Brice_ <[email protected]> wrote: > > Thank you > > > Jukka Zitting wrote: > > > > Hi, > > > > On Thu, Aug 20, 2009 at 2:54 PM, Brice_<[email protected]> wrote: > >> Is it possible to set a property to be unique in the context as the > >> primary > >> key of relational DB? > > > > No, but here's what you can do: > > > > * The UUID of a mix:referenceable node is guaranteed to be unique > > within a workspace. In fact the generated UUIDs are pretty strongly > > guaranteed to be truly unique unless you explicitly create another > > node (via versioning or import) with the same UUID in a separate > > workspace. > > > > * The name of a node is unique among the child nodes of the same > > parent unless the same-name-siblings option is been enabled in the > > relevant node type. > > > > BR, > > > > Jukka Zitting > > > > > > -- > View this message in context: > http://www.nabble.com/Primary-property-tp25061460p25061672.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > >
