On Mon, Nov 16, 2009 at 05:14:19AM +0200, Andreas Pavlogiannis wrote:
* Each file is represented by a single document that has a path
attribute that indicates the directory that is being stored to. This
gives the advantage of avoiding conventional pathname translation and
On 16 Nov 2009, at 05:28, Adam Wolff wrote:
There isn't a great way to store hierarchical data in couch. If you want to
actually move stuff around, the full pathname is a no-go, since there are no
bulk updates. The only other trick here, if you have meaningful roots or
branch points, is to
Ok, for some apps it's a no-go. If this is a
highly concurrent server app, you'll orphan data if you start two
rename updates at the same time,
a
On Monday, November 16, 2009, Jan Lehnardt j...@apache.org wrote:
On 16 Nov 2009, at 05:28, Adam Wolff wrote:
There isn't a great way to store
Greetings,
I recently started exploring the capabilities of couchdb and although I
find it really interesting and flexible, I am experiencing some
difficulties:
Is there any recommended way to store hierarchical data? Consider for
example the case of a file system with multiple directories.
On 16/11/2009 2:14 PM, Andreas Pavlogiannis wrote:
* Each file is represented by a single document that has a path
attribute that indicates the directory that is being stored to. This
gives the advantage of avoiding conventional pathname translation and
retrieving the correct document
There isn't a great way to store hierarchical data in couch. If you want to
actually move stuff around, the full pathname is a no-go, since there are no
bulk updates. The only other trick here, if you have meaningful roots or
branch points, is to store a reference to those in addition to the
I actually am using CouchDB for storing hierarchical filesystem-like
data. A good way of thinking about it is the same as amazon s3. It's
really a key/value store, but hierarchy is inferred by key names.
One food for thought is, if say you create keys to contain the full
name and then infer the
