Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAMGvKfu_V+3_BKGREw4GCD3kv=iMEQqi+ub0rQD2G+nUJ5D=nw@mail.gmail.com>
References: 
 <CAMGvKfsVMY1=Nrej4rd7i-ywcArz5s3xaaCCc9u66U_3znVnUg@mail.gmail.com>
	<CAE45B9C.1F16E%dstuebe@asascience.com>
	<CAKGmkL0SOVRnOT4ShLSDkN9AEStfiv8L1qFE7DSWeo4FjeZo1A@mail.gmail.com>
	<CAPTWwjBqQUY=Qrc-ZUnaHgHsTOd2edsD1Kv2wM3xSHjemyq2mQ@mail.gmail.com>
	<CAMGvKfu_V+3_BKGREw4GCD3kv=iMEQqi+ub0rQD2G+nUJ5D=nw@mail.gmail.com>
Date: Sun, 13 Nov 2011 11:41:40 +0000
Message-ID: 
 <CABvT1DEh1RuxUpJF1x4Fv1xRySE9NFsyq_fMudwbN_K=_-3AGg@mail.gmail.com>
Subject: Re: Document design: Logging accesses to an item by a user
From: Robert Newson <rnewson@apache.org>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Update handlers just move logic to the server side, they are not
atomic or transactional, only the document update itself is. In other
words, you *can* get a 409 conflict using an update handler.

B.

On 13 November 2011 09:24, Marian Steinbach <marian.steinbach@gmail.com> wrote:
> Sounds like the relation-document way (having a songaccess doc,
> equivalent to having had a songaccess table) would be the easiest one.
> I'll have to look into update handlers though.
>
> Thanks guys!
>