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 randall.leeds@gmail.com
 designates 209.85.219.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAL+Y1nvsOsPpeH5XH-MnqCHqadYdKJ_UmiWptoOK6o-K=TgQFw@mail.gmail.com>
References: <20130516144732.0dda4bbf@svilendobrev.com>
	<CAL+Y1nvsOsPpeH5XH-MnqCHqadYdKJ_UmiWptoOK6o-K=TgQFw@mail.gmail.com>
Date: Thu, 16 May 2013 16:32:10 -0700
Message-ID: 
 <CAAL6JQh6wnLuvs8GFSO88z3CGBVw5DTVSST5wNcX33YjG-QZSQ@mail.gmail.com>
Subject: Re: tracking changes - how to check what was deleted?
From: Randall Leeds <randall.leeds@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=089e013a0ada86262d04dcde4686

--089e013a0ada86262d04dcde4686
Content-Type: text/plain; charset=UTF-8

Actually, it's even easier than this. It is acceptable to put a body in the
DELETE. You can store whatever fields you want accessible in your deletion
stubs.
On May 16, 2013 9:00 AM, "Dave Cottlehuber" <dch@jsonified.com> wrote:

> On 16 May 2013 13:47, svilen <az@svilendobrev.com> wrote:
> > g'day
> > so i have multiple (3) kinds of documents (say with fields .type=..) in
> > same database. And i listen to changes feed, and according to type,
> > show the different kinds of docs in 3 different windows.
> >
> > if some doc was deleted, how can i guess what .type it had ?
> > changes return only _id and _rev of the new deleted stub..
> > is looking up the doc.id in those 3 caches the only option?
> >
> > ciao
> > svilen
>
> Hey Svilen,
>
> Some things:
>
> Changes only returns the "last known good" change (~handwavey~) if
> that makes sense - e.g. if doc a -> a' -> a'' -> a''' are processed in
> between you checking changes, you will not receive a', a'' at all.
>
> Document deletion inside couch is simply taking doc._id,_rev only and
> storing a new doc._id, doc._deleted, and _rev + 1. There is nothing
> stopping you re-implementing DELETE yourself (e.g. update handler
> server side, or client side as you like), and storing doc._id _rev AND
> _type as well.
>
> Alternatively, use a byte of the id to store the type if you can achieve
> that.
>
> That should see you right.
>
> A+
> Dave
>

--089e013a0ada86262d04dcde4686--