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 patrick.antivackis@gmail.com
 designates 209.85.218.163 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;
        b=DRCLcAaK85/32yUxS1pJFs+8xsePwxvrKcKsMYoBVqTmlr3wkmielqw23cKxmmDgMi
         WgBrcvWOLBFCaZsQSJDKXZJFaY5cCF2tr8MVZ1mYC623iUq/xg6kJwN127oTPpyqjGIA
         VViUT9NE1rC2f3F46i/D18RVOOv6ROR+JBdzM=
MIME-Version: 1.0
In-Reply-To: <5e6458d0902120759r24d7010evef257a4674d94187@mail.gmail.com>
References: <4b307fd10902120242v3bbbc93fs92c88503eb632fe9@mail.gmail.com>
	 <64a10fff0902120746j187aff2bpc1e5585b32007497@mail.gmail.com>
	 <5e6458d0902120759r24d7010evef257a4674d94187@mail.gmail.com>
Date: Thu, 12 Feb 2009 17:07:33 +0100
Message-ID: <7060483c0902120807r47420629j705905910f2c8f4@mail.gmail.com>
Subject: Re: playing with tags
From: Patrick Antivackis <patrick.antivackis@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001636c5a8e603d5920462baeb8e

--001636c5a8e603d5920462baeb8e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

> but now, I want all articles wich are tagged with "couchdb" *and* "python"
> (I want the article1). Is there a method to do it directly with CouchDB
views ?
> Something like that :

The only way to do that is to emit all the possible tags combinations for an
article.
In order to decrease the number of combinations, you first order them by
alphabetical order, then you emit them.

For the query, you will order alphabetically the tags you are looking for
and then use a starkey/endkey view retrieval.


2009/2/12 Kerr Rainey <kerr.rainey@gmail.com>

> 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
>

--001636c5a8e603d5920462baeb8e--