Just to mention there is also a update_seq query option, which instructs CouchDB to include a update_seq value in the view response, indicating which sequence id of the database the view reflects. [1] This comes in handy in a situation where you are interested in future changes of a view.
g jo [1] http://wiki.apache.org/couchdb/HTTP_view_API#Querying_Options On 06/20/2012 06:42 PM, Robert Newson wrote: > Do GET /dbname and the return JSON blob should have the current sequence > under the update_seq key. > > B. > > On 20 Jun 2012, at 17:30, Daniel Gonzalez wrote: > >> Hello, >> >> 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? >> >> Thanks and regards, >> Daniel
