couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] Commented: (COUCHDB-290) Include sequence number in update notifications
Date Mon, 16 Mar 2009 13:04:50 GMT


Robert Newson commented on COUCHDB-290:

@Jan no, I do not use endkey. I specify startkey and limit only (I already know startkey and
limit is just to make the couchdb call a constant cost). If the update notification contained
the new update_seq I would not have to find it with a call to http://localhost:5984/<dbname>.
I use the new update_seq as the escape condition for my loop. That is, my code attempts to
catch up from where I left off to where couchdb is at the time of the notification, neither
more nor less. 

Having the new sequence in the update notification would eliminate the http://localhost:5984/<dbname>
call. It's not a big deal for me, couchdb-lucene works fine without it, but I don't see any
downside, and some modest upside, to the suggestion.

> Include sequence number in update notifications
> -----------------------------------------------
>                 Key: COUCHDB-290
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 0.9
>            Reporter: Elliot Murphy
>            Priority: Minor
>             Fix For: 0.9
>         Attachments: couchdb-sequences.patch, couchdb-sequences.patch
> Hi! There's been requests to include the sequence number when sending an update notification.
 Thanks to the guidance from davisp on #couchdb on March 13th, I've been able to put together
a little patch that does just that. In the future I'm interested in doing the same for the
create notification, and perhaps extending create/delete/update notifications to include a
list of affected doc IDs.
> For now though, just this simple patch.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message