Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of faust451@gmail.com designates
 74.125.78.25 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=rHyqrPfQ8YZq8y+xilXjmVvSjJv6HgUuzeLcIgx91G/xbOWAoQo6Pl4QkJX+4Gq2Np
         uqRRxlA43UJec1mFHg4CIMLC1h9EyZ5THEYA4dzuKDyA7IlcrU1A0zBWNY/j07jS2b7D
         N8j0n4Bo9I7MOljzVQQYTxvhAY4k8FtW6jmos=
MIME-Version: 1.0
In-Reply-To: <46ACF4F3-1F6C-40F6-95C5-4B9286890BBA@gmail.com>
References: <AANLkTimTGIz5oiVC8DgNpVMducMlKrxtpFvCqNGmwCAq@mail.gmail.com>
	<46ACF4F3-1F6C-40F6-95C5-4B9286890BBA@gmail.com>
Date: Fri, 18 Jun 2010 00:37:29 +0400
Message-ID: <AANLkTimwk7jUmaWi-rvnVvIeHA1zlUnnmCW62QjWsVUX@mail.gmail.com>
Subject: Re: Need advice about docs structure design.
From: faust 1111 <faust451@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

If i keep  them in the same database
What about view speed?

Example users add many bookmarks and when try fetch Posts each
bookmark processed by this view but it's unnecessary it's slow down my
views is not it?.


2010/6/18 J Chris Anderson <jchris@gmail.com>:
>
> On Jun 17, 2010, at 1:15 PM, faust 1111 wrote:
>
>> Hy guy's.
>>
>> My model:
>> Users has
>> =A0Bookmarks and Posts
>>
>> have idea keep Bookmarks and Posts in separate DB (for speed views).
>> But in view i want fetch Bookmarks and Posts with user name,
>>
>
> You should keep them in the same database (replication is easier, too) an=
d then use this kind of query:
>
> http://www.cmlenz.net/archives/2007/10/couchdb-joins
>
>> In what way i can do this?
>> keep copy of users in each DB?
>>
>> or may be keep users in separate DB, fetch bookmarks or posts and then
>> fetch users and then merge?
>>
>> Yes i know i can copy user name to doc, but have a trouble when user
>> name is changed (it's force me use stale=3Dok in request view
>> +background process to track changes and run rebuild index).
>>
>> I think it's will be cool crazy stuff if i can update docs(cached
>> fields - not have effect to index) and say Couch you don't need
>> rebuild index relax ;).
>>
>> Any advice?
>
>