currently the referencing is not optimized at all. your results are expected. using UUIDs or paths as references is a valid alternative, although the Node.getReferences() is more expensive since you need to use the query.
regards, toby On 9/11/06, Christoph Kiehl <[EMAIL PROTECTED]> wrote:
Hi, I'm experiencing an extreme performance/storage problem with references. In my case I got node(document) that reference another node(state) by reference. This state node is referenced by about 100.000 document nodes (still growing to about 1.000.000). As NodeReferences get persisted on every change, there is a lot of data written to the database on each added reference. What is the best way to handle this number of references? Is there a better way than saving the state uuid as string property an hence give up referencial integrity? Cheers, Christoph
-- -----------------------------------------< [EMAIL PROTECTED] >--- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---
