Thanks Jukka, Depending on the data layout different solutions are possible.
If there's a finite depth of the tree than one or more final levels could be encoded in a single row. There's virtually an infinite number of columns you could have on a single row (by default limited to 250MB) If more than one row needs update an optimistic locking mechanism could be employed. Again, it depends on the constraints (tree depth, nodes per level number, etc.) Cosmin On 8/17/11 2:51 PM, "Jukka Zitting" <[email protected]> wrote: >Hi, > >On Wed, Aug 17, 2011 at 1:37 PM, Cosmin Lehene <[email protected]> wrote: >> First I'll have to better understand what a bundle is :) (JCR newbie >> here:)). I'll try to read about it. > >A bundle is the unit of data stored by a bundle persistence manager. >It contains the properties and the list of child nodes of a single JCR >node. > >A bundle persistence manager is expected to be able to atomically >update not just a single bundle at a time, but an arbitrarily large >ChangeLog of created, updated and deleted bundles. This has so far >been a big problem for NoSQL-style persistence managers that only >support locking at the level of individual rows. > >BR, > >Jukka Zitting
