Return-Path: Delivered-To: apmail-incubator-couchdb-user-archive@locus.apache.org Received: (qmail 97221 invoked from network); 3 Sep 2008 16:25:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Sep 2008 16:25:20 -0000 Received: (qmail 7833 invoked by uid 500); 3 Sep 2008 16:25:17 -0000 Delivered-To: apmail-incubator-couchdb-user-archive@incubator.apache.org Received: (qmail 7797 invoked by uid 500); 3 Sep 2008 16:25:17 -0000 Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: couchdb-user@incubator.apache.org Delivered-To: mailing list couchdb-user@incubator.apache.org Received: (qmail 7785 invoked by uid 99); 3 Sep 2008 16:25:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Sep 2008 09:25:16 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.68.5.17] (HELO relay03.pair.com) (209.68.5.17) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 03 Sep 2008 16:24:18 +0000 Received: (qmail 41682 invoked from network); 3 Sep 2008 16:24:48 -0000 Received: from unknown (HELO ?192.168.1.149?) (unknown) by unknown with SMTP; 3 Sep 2008 16:24:48 -0000 X-pair-Authenticated: 96.33.90.152 Message-Id: <088E6FD0-F769-40E4-9C25-FEB2C4102748@apache.org> From: Damien Katz To: couchdb-user@incubator.apache.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v926) Subject: Re: extra information in design documents Date: Wed, 3 Sep 2008 12:24:48 -0400 References: <8E4BBF90-56DF-4E58-8FFB-DAF5EF334028@oxdi.eu> <5e6458d0809030735h77c47d58r5f712f55f87269b2@mail.gmail.com> X-Mailer: Apple Mail (2.926) X-Virus-Checked: Checked by ClamAV on apache.org 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. -Damien 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