Comments on: Storing Hierarchical Data in CouchDB

By: Michael

Michael — Thu, 04 Mar 2010 13:05:27 +0000

Thanks for the good example. I tried to figure it out on my own before and the missing bit was the endkey syntax of ["foo", {}]. What exactly does it mean? Where can I get more information about how startkey and endkey are compared to the actual keys?

Thanks, Michael

By: pib

pib — Sun, 27 Dec 2009 09:32:57 +0000

I’d say write up a quick script that loads as many ducuments as possinble into memory (within reason), and then does bulk inserts to put them in CouchDB. Since it will be your initial import, I’d suggesting using batch mode, too, since you don’t need data safety until you’ve actually got something up and running.

Check out the sections here on bulk inserts and batch mode: http://books.couchdb.org/relax/reference/high-performance

By: HariKrishnan

HariKrishnan — Sun, 27 Dec 2009 08:06:38 +0000

Hey,

Nice article. I really would like to apply this, but the trouble is how would we get this data into couch db in the first place. Lets say we have a lot of data in a self-referential table of a legacy system. I was wondering what would be the most efficient way to pull this information into couchDb.

Thanks, HariKrishnan

By: Nicholas Orr

Nicholas Orr — Wed, 09 Dec 2009 00:35:05 +0000

It took me a little bit to apply the information in this post – however having played a bit it all makes sense and has saved me a bit of time.

The issue with using the doc uuid’s is they are too long for the reduce functions offered above. I’ve managed to do everything I need from the map functions so that is good.

Thanks a lot for the information

Nick

By: Helder Ribeiro — Second steps with CouchDB: Playing with hierarchical data

Helder Ribeiro — Second steps with CouchDB: Playing with hierarchical data — Tue, 19 May 2009 19:29:45 +0000

[...] had seen this blog post about how to store hierarchical data in CouchDB and decided to play with the example data and views the guy provided (big thanks to Paul Bonser!). [...]

By: Helder

Helder — Thu, 29 Jan 2009 09:06:39 +0000

Hey, thanks for the great example! The part about selecting descendants was kinda tricky and I didn't really figure out what it was doing until I ran it myself on Futon (I was thinking the start/end keys would select the doc before passing it to the map function). I ended up noticing that what you get indeed is the sub-tree, including the sub-tree root. So if you really only want to get the descendants then you have to exclude the self, like this (forgive my poor, unoptimized js):

function(doc) { for (var i in doc.path) { if (i < doc.path.length -1) { emit([doc.path[i], doc.path], doc) } } }

By: Daily Digest for 2008-11-21 | Pedro Trindade

Daily Digest for 2008-11-21 | Pedro Trindade — Sat, 22 Nov 2008 08:09:18 +0000

[...] PIBlog » Blog Archive » Storing Hierarchical Data in CouchDB [...]

By: CouchDB resources | Tech Mix

CouchDB resources | Tech Mix — Fri, 03 Oct 2008 10:53:30 +0000

[...] General Discussion:CouchDB – Use caseCouchdb Joins by Paul Joseph DavisCouchDB Joins by Christopher LenzStoring hierachical data in CouchDB [...]

By: Jay

Jay — Wed, 09 Jul 2008 19:48:58 +0000

Ok, I kinda “embelished” (w/o knowing it). It did work but then I browsed away and came back and it throws the error again… Close though!

By: Jay

Jay — Wed, 09 Jul 2008 19:45:33 +0000

Sorry to anyone else learning from examples as I am, that last line of code should have “GOOG” as being quoted.