[
https://issues.apache.org/jira/browse/COUCHDB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012564#comment-13012564
]
Randall Leeds commented on COUCHDB-1108:
----------------------------------------
I think I wrote this patch and it was rejected a while back.
https://issues.apache.org/jira/browse/COUCHDB-650
It looks like the rationale wasn't so much that it was a bad feature, but that
the original ticket was requesting it for a different purpose that was
fulfilled instead by putting update_seq in the view response.
I'm still for adding this.
> expand options for since argument in _changes
> ---------------------------------------------
>
> Key: COUCHDB-1108
> URL: https://issues.apache.org/jira/browse/COUCHDB-1108
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
> Affects Versions: 1.0.2
> Reporter: Thomas Vander Stichele
> Priority: Minor
>
> It would be useful to get continous _change feed from the current change_id.
> Now, if you only care about new changes, you have to first get the change_seq
> from the db, then ask for the _change feed with since=...
> since=current as an argument could be an option.
> Similarly, it might be useful to start with the last five changes (in all
> notification ways). for example, since=-5
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira