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: domain of kerr.rainey@gmail.com
 designates 72.14.220.156 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=W6CWtWtmG18EwDlyzKd8d8HvuCJuRrqp+e7KeLYgIxzlM3/1dvcBh3sNhiu8MuIj8D
         y6IcVB3MfmOqF68faP5Jzop07QDfcNEvzF45R/4AxCGBGVGMsOeFR1Kuv2E5FSk76TGr
         J77t4alAPGJHKfP8XQlLwcL6FqQxBLkHTCots=
MIME-Version: 1.0
In-Reply-To: <64a10fff0902120746j187aff2bpc1e5585b32007497@mail.gmail.com>
References: <4b307fd10902120242v3bbbc93fs92c88503eb632fe9@mail.gmail.com>
	 <64a10fff0902120746j187aff2bpc1e5585b32007497@mail.gmail.com>
Date: Thu, 12 Feb 2009 15:59:40 +0000
Message-ID: <5e6458d0902120759r24d7010evef257a4674d94187@mail.gmail.com>
Subject: Re: playing with tags
From: Kerr Rainey <kerr.rainey@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

2009/2/12 Dean Landolt <dean@deanlandolt.com>:
> This is an issue that has been nagging at me lately. Storing tags in the doc
> seems like a recipe for disaster (that is, if you consider view contention
> disaster). I would argue that tags (and other readily changeable
> user-specific state information like read/unread, favorite, blah blah)
> should be kept in separate docs and bridged together in views.

Erm... why do think tags for a blog post would be rapidly changing?
They would be set by the owner of a post and that's it.  The
likelihood of a tag changing in this scenario is no greater than the
post being edited.  It's meta info, but clearly part of the post.  You
won't have many people try to update the same post, or at least the
contention on that is very low.

--
Kerr