couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1501) Add flag to the changes API to return only new changes
Date Fri, 22 Jun 2012 13:53:42 GMT


Robert Newson commented on COUCHDB-1501:

You can record the update sequence value while reading the changes feed, it's the value you
then pass back to the since parameter. This feature would mean you would miss updates.

You can already get the current update sequence, as I told you on the mailing lists and as
you show above, with GET /dbname.

What's the motivating use case here? If we do this, and I don't think we should, the option
would need to be very clear that you are potentially missing changes (to ensure no one tries
using it for replication).
> Add flag to the changes API to return only new changes
> ------------------------------------------------------
>                 Key: COUCHDB-1501
>                 URL:
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: JavaScript View Server
>    Affects Versions: 1.2
>            Reporter: Daniel Gonzalez
>            Priority: Minor
> As discussed in this thread:
> I copy paste part of the conversation.
> ---
> I am subscribing to the _changes API. My database is quite big, and each time I restart
my client, I get all old notifications. I only need the new notifications, since the moment
that I subscribe to the feed.
> I have seen that there is a "since" parameter, but this is not helping me further, because
I do not know what is the last document sequence number. So I would need one of the following:
> - a method to get the last sequence number to use as value for "since"
> - a flag to tell the _changes API to just give me the changed *from now on*. This would
be the most clean solution, since it saves me a request to get the since parameter (which
can be outdated anyway very fast). Is there something like this?
> ---
> I ended up going the GET /dbname route
> I guess there is no specific flag for the _changes API to request future changes...
> ---

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message