couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randall Leeds <>
Subject Re: Preserving seq order through replication
Date Tue, 09 Mar 2010 00:26:22 GMT
On Mon, Mar 8, 2010 at 15:43, Mark Hammond <> wrote:
> I'm not really up on this in any detail, but isn't there the possibility
> that 'y' will have had the same edit performed on 2 different nodes, while
> 'x' was only edited on one of them.  The change to 'y' will not be
> replicated at all between the 2 nodes with identical edits, whereas 'x' will
> - meaning 'x' will be seen to arrive later than 'y' on one of the nodes?

Depending on any particular seq order is probably a bad idea.
I don't think it's appropriate to assume seq is at all meaningful
except for sending back in the ?since parameter to _changes.
seq for one server should never be assumed to be meaningful on another.

View raw message