jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting" <jukka.zitt...@gmail.com>
Subject Re: Enforcing constraints; Sessions and Threading
Date Mon, 05 Nov 2007 21:51:11 GMT

On 11/5/07, Dan Diephouse <dan.diephouse@mulesource.com> wrote:
> Jukka Zitting wrote:
> > There's nothing like a UNIQUE constraint in JCR or Jackrabbit (though
> > it might be good to have at least a Jackrabbit feature request in Jira
> > for that), so the closest you can get probably to make the "resource
> > name" be the name of the entry node and have all the entries stored as
> > children of a parent node that doesn't allow same-name-siblings.
>  OK that could work!

There's an added benefit if you plan to use the "resource name" as a
primary identifier for the entries, as you'll then be able to use
normal path resolution instead of a more expensive query to retrieve
an entry.


Jukka Zitting

View raw message