Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 32261 invoked from network); 6 Aug 2009 22:48:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Aug 2009 22:48:00 -0000 Received: (qmail 36573 invoked by uid 500); 6 Aug 2009 22:48:06 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 36487 invoked by uid 500); 6 Aug 2009 22:48:06 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 36477 invoked by uid 500); 6 Aug 2009 22:48:06 -0000 Delivered-To: apmail-incubator-couchdb-user@incubator.apache.org Received: (qmail 36474 invoked by uid 99); 6 Aug 2009 22:48:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 22:48:06 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jwalgran@gmail.com designates 209.85.219.212 as permitted sender) Received: from [209.85.219.212] (HELO mail-ew0-f212.google.com) (209.85.219.212) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 22:47:57 +0000 Received: by ewy8 with SMTP id 8so707285ewy.12 for ; Thu, 06 Aug 2009 15:47:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=yIIfBmqab/+NGvaku1U5c/7CtEbSlbQ4NYOKSWwnqhA=; b=ZJN4WKDC4019qpFLl/HIYrHpQsPYmL9amY0ZvpP0qVE8Y4obxqgooi2kMJDH30Bb51 rpaCx9x3m9fJpEXI7FTxmhHfNVuRKsaW6lkxLC+h0z2UMsk4J6taAGDivF91GNzg9vxR Mqoq7nqv1ThCxnK44a5MOlgIR+LXMintdYbNg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=TbqxnCMsvhbVsZ5xqEJgsRG1k8vgt+XbWyANAakUn2Nbe+w7rbItuQg5YY4HnUGg+5 EPMeWMs30llsb6juhCd5pQnF9k52ltC15NJV/MSu0IclnIWUzwLzEJG/yFzcC6MFXKT5 UPH57z/QBbt8sRjRGneCVB1Ma2Yc3w9+HypnU= MIME-Version: 1.0 Received: by 10.216.87.68 with SMTP id x46mr93084wee.2.1249598856754; Thu, 06 Aug 2009 15:47:36 -0700 (PDT) Reply-To: jwalgran@gmail.com Date: Thu, 6 Aug 2009 18:47:36 -0400 Message-ID: Subject: Best practice: adding an app specific chunk to a document From: Justin Walgran To: couchdb-user@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I'm building a couch app that works with it's own database of documents or as an add-in to any existing database of documents. In the case where the app is added to an existing database, I would like to scan the documents and add a little "meta" section to each one for storing information relevant to the app. I am very excited by the idea of "mix in" applications, but this raises a few questions: Is it wrong to "pollute" the existing documents with my extra meta section? Are there any thoughts on the best value to use as a key for my data section to minimize collisions? Is a single master GUID my only choice? Thanks for the feedback. -Justin