I can't really answer your question directly, but I will say that I have one design doc for every type (or OO class) of document I have. It makes sense when mating CouchDB with a object oriented language (Ruby in my case), but YMMV.
On Sat, Jul 9, 2011 at 6:59 PM, Mark Hahn <[email protected]> wrote: > In that case, if you say that by definition all docs in one app are > related, then there should be one database, but different design docs > for performance. > > What is the utility of having multiple views in one design doc, other > than being able to edit them in one place? Or another way to phrase > the same question: why do design docs exist? -- Keith Gable A+ Certified Professional Network+ Certified Professional Web Developer
