I think flat is OK, its once you get up to the "millions" of documents it may hurt, so you have to put that in perspective ;)
A heirarchy may be for classification in folders. Remember in JCR its easy to move a resource around when you want to re-arrange it later on. On 11/17/06, David Moss <[EMAIL PROTECTED]> wrote:
This might sound like a simple question, but what advantage is there in building a tree structure to store my data? If I'm storing a single type of data 'documents' that is distributed to 'recipients' (be it groups or users). What advantage is there in building a user / group / role hierarchy and retrieing documents through that as opposed to simply storing documents with an attribute indicating the recipient? I realise this would result in a flatter tree structure, which I've read elsewhere is not handled so well by jackrabbit. What's the reason for this? Are attribute values indexed at all? Many thanks, David. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
