Hey Everyone, Reading up on the CouchDB 2.0 migration guides and getting a bit antsy around the mentions of out of order changes feed and sorts. Is it possible for the changes feed to send older changes before newer changes for the same document ID across multiple calls?
Assuming start at ?since=“” and always pass in the “last_seq” on every additional call could a situation like this occur in a single or multiple HTTP calls: — Changes feed emits Doc A change (seq: 2-XXXX) — Changes feed emits Doc B change (seq: 3-XXXX) — Changes feed emits Doc A change (seq: 1-XXXX) I’m really hoping the case is just that across different doc ids changes can be out of order. Our use case on mobile is a bit particular as we duplicate edits into a separate SQLite table and use the changes feed to keep the local database up to date with winning revs from the server, it just increases the performance of sync by a ton since there is only 1 check and set in SQLite per change that comes in. Cheers, Robert
