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 lewcid@gmail.com designates
 209.85.160.52 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=v0mD1ay1vlRBOxUXHhjBhnc6sjpiXo/uEuCdud4AHAff89Ru2Ht/F9S0zUgeqSyHGa
         s8+8iAXhvinVn7dFNUqE2pGJ22wGcrEfWdw32B9I8Q5Spe4YK97Ugc+bYFnVLj0jIzcd
         zWwno4egL253URtaJhbE2JO927AjqZtwiQVRE=
MIME-Version: 1.0
In-Reply-To: <594289661003021356k1dd980d6gb507c50bc6eb707c@mail.gmail.com>
References: <e24817d11003021016m5b748b4fscc8078d5f943a84e@mail.gmail.com>
	 <21a5a18d1003021103m466b3363p9c549e25792f72af@mail.gmail.com>
	 <e24817d11003021111n59d1fef1qd200e85926b70271@mail.gmail.com>
	 <3A7E9A0D-0535-4B36-831E-6AB88A526F2A@gmail.com>
	 <e24817d11003021135y2a3f2856uf1d75c26ed33e0a4@mail.gmail.com>
	 <594289661003021356k1dd980d6gb507c50bc6eb707c@mail.gmail.com>
Date: Tue, 2 Mar 2010 23:28:30 +0100
Message-ID: <e24817d11003021428t5cf1ac17kc17fc30024877feb@mail.gmail.com>
Subject: Re: Implementing next and previous links
From: Saq Imtiaz <lewcid@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=000e0cd13ac29db4910480d8e2b5

--000e0cd13ac29db4910480d8e2b5
Content-Type: text/plain; charset=ISO-8859-1

Hi Dave,

Its an interesting idea and one that I had considered briefly. The issue
here would be that if a post was updated, added or deleted in the middle of
a sequence the next and previous attributes for all affected documents would
need to be updated. This should be an infrequent enough operation that
performance should not be an issue... and it could be handled by the
clientside code responsible for allowing creation of new docs. OK I must
confess I'm a little unsure as to whether I rejected this approach so
quickly before. Thinking of a doubly-linked list had left a bad taste in my
mouth at first but it might be more convenient than the other approaches
I've discussed... using include_docs we could even get access to the next
and previous docs if necessary. Late here now so will sleep on it but
there's a good chance I'll try going down this road.
Cheers,
Saq

On Tue, Mar 2, 2010 at 22:56, David Goodlad <david@goodlad.ca> wrote:

>
> >  What I haven't found a way to do is end up with a /date/docid/ type of
> URL
> > for the previous post where the date and docid are both attributes of
> that
> > previous post. Unless I've missed something significant the _rewrite
> handler
> > can't do this as it provides simple mapping between different URL paths
> and
> > can't perform any queries to the database to determine the appropriate
> > document id for instance.
>
> Why not reference the next and previous docids within the doc itself
> (ie: a doubly-linked list)?
>
> Dave
>

--000e0cd13ac29db4910480d8e2b5--