Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Subject: Re: planning out a database
From: Dan Himes <dhimes@vlesolutions.com>
To: user@couchdb.apache.org
In-Reply-To: <0FAA378F-C9F1-4520-BFCD-0ED440FF6F9A@vpro.nl>
References: <AANLkTik8qdRJW3F8xWMQo0C8Lf=Essogkpt_E7_XjsWY@mail.gmail.com>
	 <0FAA378F-C9F1-4520-BFCD-0ED440FF6F9A@vpro.nl>
Content-Type: multipart/alternative; boundary="=-3N9lMNdcK0vxJvlAD7ls"
Organization: Virtual Learning Environment Solutions, Inc.
Date: Sat, 30 Oct 2010 12:47:39 -0400
Message-ID: <1288457259.24561.0.camel@dirac.home>
Mime-Version: 1.0

--=-3N9lMNdcK0vxJvlAD7ls
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Thu, 2010-10-28 at 10:29 +0200, Nils Breunese wrote:

> Jeffrey M. Barber wrote:
> 
> > Is it a good idea to have a single application work inside of a single
> > CouchDB database?
> >
> > Right now, I'm making sure each document I put into the CouchDB has a 'ns'
> > field (for namespace) so I can pull it out for indexing, but I'm thinking
> > that as this grows this may be a bad idea. Is it worth pulling out each ns
> > into a database? or is this just going to be a pre-optimization in the long
> > term.
> 
> Using an ns-like property is a commonly used pattern in CouchDB databases. I don't think it's worth it to start splitting up your database. You lose some flexibility as functions exist on a database-level and cannot work across different databases and I don't see any real advantage in doing it.
> 
> Nils.
> ------------------------------------------------------------------------
>  VPRO
>  phone:  +31(0)356712911
>  e-mail: info@vpro.nl
>  web:    www.vpro.nl
> ------------------------------------------------------------------------


I'm very glad to hear this, as it is the pattern I opted for also.

Dan

--=-3N9lMNdcK0vxJvlAD7ls--