Oops. I thought I read somewhere that multi-value properties don't necessarily maintain their order. I can't seem to find the place where I read that, though, so it looks like I just had the wrong idea :(
Thanks for the correction, though. -Brian On 2/26/07, Stefan Guggisberg <[EMAIL PROTECTED]> wrote:
On 2/26/07, Brian Thompson <[EMAIL PROTECTED]> wrote: > On 2/26/07, avim <[EMAIL PROTECTED]> wrote: > > > > > > What is the score in this case? > > Anyway I don't think it will give me the desired order, and there is a > > need > > for kind of predicates/relations with extra data/connection objects > > anyway. > > Any advice/best practices? > > > > > In my application, I had one instance where I needed to keep track of an > ordered list of references to other nodes in the repository. At first > glance, using a multi-valued property on my tracker node seemed like the > best idea. Since that doesn't guarantee any sort of order, I resorted to > orderable child nodes, each one of which has a property that refers to the > desired node. It's a little less elegant, but until Jackrabbit supports > orderable multi-valued properties, it will have to do. for the sake of correctness: jackrabbit *does* support orderable multi-valued properties. in fact all multi-valued properties do persist the order of their values. cheers stefan > > -Brian >
