Details
-
New Feature
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.2
-
New Contributors Level (Easy)
Description
As discussed in this thread: http://mail-archives.apache.org/mod_mbox/couchdb-user/201206.mbox/%3CCAAOi-OHB6%3DYu%2Bt%3DWkiFAypQAfnv%3DQd-PL4tELZNL1C1-TQvtWw%40mail.gmail.com%3E
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...
—
Attachments
Issue Links
- is duplicated by
-
COUCHDB-1108 expand options for since argument in _changes
- Closed
- relates to
-
COUCHDB-2256 Implement since=now in _changes
- Resolved