couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens Alfke <>
Subject Re: Best practice for storing large dynamic tree in CouchDB?
Date Thu, 05 Jan 2012 01:42:56 GMT

On Jan 4, 2012, at 1:23 AM, CGS wrote:

> a) deleting a node requires deletion of the whole tree branch;

In any tree, if you delete a node you have to do something with its children, whether deleting
them or moving them elsewhere. Same here. You wouldn’t have to delete the whole branch;
the former children could just have their ‘parent’ reference updated to point to some
other node.

> b) renaming a node requires update for all the documents within that 
> tree branch.

You can’t change the _id of a document in CouchDB anyway. If tree nodes need to be renameable,
you have to store the name separately from the ID. It would be best to make the ID something
intrinsically immutable, like a file’s inode number.

View raw message