Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E6B059F53 for ; Sat, 15 Oct 2011 13:15:56 +0000 (UTC) Received: (qmail 45383 invoked by uid 500); 15 Oct 2011 13:15:55 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 45318 invoked by uid 500); 15 Oct 2011 13:15:54 -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 45310 invoked by uid 99); 15 Oct 2011 13:15:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Oct 2011 13:15:54 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a78.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Oct 2011 13:15:47 +0000 Received: from homiemail-a78.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a78.g.dreamhost.com (Postfix) with ESMTP id 0708815C059 for ; Sat, 15 Oct 2011 06:15:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=ecstatic.com; h=content-type :mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; q=dns; s= ecstatic.com; b=xa2cl17FbMACxkdQR9sLqs8Ei5e496PF5BJlkV9iyfapTdIJ 1VsBAJodlly5OX3yNMV/j5b1kLZuvVMaxG2MjhLnisJKSLyNYf65l0EfJ1mEDp8q VaMd5kvGoNCPLUGsddQUaQgW7ywBFaOpkH5rFMcoQepppmtg+mUPezRsyyE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ecstatic.com; h= content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; s= ecstatic.com; bh=RX+s1YhXtWFb34tEoHlNOKkFnwU=; b=rW2JUzTJeYUWT8+ u8J3oR4w7xXZtFqkNdbMU9PAxVpcXqEVLwy+9z9YlQ/6hiUgqOjVE6BcsCrVUPqz d0nXEBE8+adH7M0UFxYbI7JR+CFwfzPmDD22HDiIvlzdouP9CAnC65p+tN0L2iaS kPEctrf3o11mwdynaCazm6mVWxB8= Received: from [192.168.0.1] (men75-1-81-57-191-45.fbx.proxad.net [81.57.191.45]) (Authenticated sender: roger@ecstatic.com) by homiemail-a78.g.dreamhost.com (Postfix) with ESMTPA id 9E49715C058 for ; Sat, 15 Oct 2011 06:15:22 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: When to normalize data From: Roger Rohrbach In-Reply-To: <4E9902C3.80807@davidjfox.com> Date: Sat, 15 Oct 2011 15:15:19 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <8F8D8A3F-2531-42DF-BFDF-EA3AABE65F7A@ecstatic.com> References: <4E9902C3.80807@davidjfox.com> To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org Without answering your question directly, I'd encourage you to read the = article (w/suggested best practices) in schema design over at = mongodb.org: http://www.mongodb.org/display/DOCS/Schema+Design On Oct 15, 2011, at 5:49 AM, David Fox wrote: > Are there any general guidelines determining when it makes sense to = normalize?