On Thu, Apr 9, 2015 at 1:21 PM, Jan Korte <[email protected]> wrote: > I execute an application on two computers, each with a CouchDB model. Now > when the model changes, the view on the other computer get's updated, too. > But when the order of changes is wrong, there will be errors (e.g. edit an > item before it was added).
Well, changes feed emits only one event per changed document. In case of continuous feeds, it also follows the upcoming updates as well. These events are ordered by the way they'd happened in database (thanks to update_seq). This behaviour also known as eventual consistency, when event B cannot happen after A if IRL it actually happened before A. So does the changes feed. For CouchDB 2.0 you shouldn't relay on such order even more. What you really need, imho, is model migration or well handled it upgrade by the fact of receiving outdated one. -- ,,,^..^,,,
