Return-Path: Delivered-To: apmail-incubator-couchdb-user-archive@locus.apache.org Received: (qmail 69854 invoked from network); 3 Nov 2008 09:35:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Nov 2008 09:35:46 -0000 Received: (qmail 33995 invoked by uid 500); 3 Nov 2008 09:35:51 -0000 Delivered-To: apmail-incubator-couchdb-user-archive@incubator.apache.org Received: (qmail 33955 invoked by uid 500); 3 Nov 2008 09:35:51 -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 33944 invoked by uid 99); 3 Nov 2008 09:35:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2008 01:35:51 -0800 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 [216.52.237.208] (HELO x8.develooper.com) (216.52.237.208) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2008 09:34:33 +0000 Received: (qmail 28183 invoked from network); 3 Nov 2008 09:35:13 -0000 Received: from gw.develooper.com (HELO embla.bn.dev) (ask@mail.dev@64.81.84.140) by smtp.develooper.com with (AES128-SHA encrypted) SMTP; 3 Nov 2008 09:35:13 -0000 Message-Id: From: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= 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 v929.2) Subject: Re: How to organize views Date: Mon, 3 Nov 2008 01:35:12 -0800 References: <913EB1B8-AC34-4406-93A2-73F90CCEC7D8@apache.org> X-Mailer: Apple Mail (2.929.2) X-Virus-Checked: Checked by ClamAV on apache.org On Nov 2, 2008, at 14:28, Paul Davis wrote: > There are two main thoughts at the moment. Group views like you have > by data that is indexed, or group everything required for a given > application in a single design doc. Interesting - thanks! Another thought I had was that index updates on big databases really need to be transactional in a way. I was thinking of having my application do some indirection to find the design document / view name; so rather than just doing GET /foo/ _view/foo/bar then do GET /foo/view_foo which would return something like { "current": "foo234", "next": "foo235" } The process that updates the design document would force indexing on foo235 to happen and when it's done then update the view_foo document to have "current" point to "foo235". It seems like something that could be better handled inside CouchDB though. Any thoughts? - ask -- http://develooper.com/ - http://askask.com/