Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4B1C2F6A.1070506@rogerbinns.com>
Date: Sun, 06 Dec 2009 14:25:46 -0800
From: Roger Binns <rogerb@rogerbinns.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: Design Question
References: <741a4d620912061401s172d43d2pf2a84ae2d3589150@mail.gmail.com>
In-Reply-To: <741a4d620912061401s172d43d2pf2a84ae2d3589150@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthew Gamble wrote:
> I'm sorry if a question like this has been asked
> before, but I couldn't find anything in the archives that was quite the same
> as what I'm trying to do.

There indeed was a similar discussion.  One of the final conclusions was
that it would be best to have each user plus their data stored in a separate
DB.  The reason for this is that it makes the security rules easier to
define and also makes more sense for replication.  (Presumably you want to
eventually allow the users to run a personal CouchDB with the same database.)

> attachment but that made it very hard to search the data as it required the

May be helpful http://wiki.apache.org/couchdb/Full_text_search

> Or is it best to put each user as their own database and store the address
> books / VCards as documents?

That would be most natural.  In theory you can write an update handler that
parses the vCard into fields and makes them keys of the doc.  If you do this
then the full text search should work really easily.

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkscL2oACgkQmOOfHg372QSAwACdGdOXBMw9W7a5jLAeXPHGGz27
Za4An3KylQT6Z788a09Nr1MOH2jiXeFU
=AJpY
-----END PGP SIGNATURE-----