[
https://issues.apache.org/jira/browse/COUCHDB-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682216#action_12682216
]
Paul Joseph Davis commented on COUCHDB-290:
-------------------------------------------
Patch looks simple enough. I'd rename seq to update_seq to maintain
consistency. I'm uncertain about adding the list of affected document ids. I'd
have to go back and look at the code paths again to see what's what. If adding
the list included making a hit all the way down to the update sequence btree
I'd force the overhead to the client instead of including it in every update
notification. Minus the s/seq/update_seq/ I'd be good applying this as is.
> Include sequence number in update notifications
> -----------------------------------------------
>
> Key: COUCHDB-290
> URL: https://issues.apache.org/jira/browse/COUCHDB-290
> Project: CouchDB
> Issue Type: Improvement
> Affects Versions: 0.9
> Reporter: Elliot Murphy
> Priority: Minor
> Fix For: 0.9
>
> Attachments: 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.
