couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damien Katz <>
Subject Re: extra information in design documents
Date Wed, 03 Sep 2008 16:24:48 GMT
Indeed, a single design document is meant to be able to hold  
everything necessary for a application. That way the application  
design replicates around as single unit, and you can have multiple  
application designs for the same database (maybe for different  
clients, web vs mobile vs desktop).

The only thing to worry about is collisions with your custom fields  
and CouchDB reserved fields. As new design fields are added in later  
versions of CouchDB, they might take the name of some custom field  
already used by your application, which can cause problems. This is  
the reserved keyword problem you see over and over again in languages  
and tools. There really isn't much you can do as the user except name  
your symbols something unlikely to be later reserved.


On Sep 3, 2008, at 11:56 AM, Chris Farmiloe wrote:

>> Design docs are nothing more than regular documents with a
>> special name and specified views attribute.
> This is what I suspected.
> I am able to treat them as so, I guess I was also asking if this is  
> something that will be frowned upon. It seems extremely logical from  
> my point of view (even their name design-documents is perfect), but  
> also feels a little like I'm writing into some sacred area of the  
> DB's setup.
> Chris

View raw message