I am trying to figure out the exact content of continuous _changes feed and am confused with the result rows with seq like “1999::2999”. Would someone know to explain why at times we have this :: notation instead of just single integer, like “1999”? My understanding this far is that in the example …

Please don’t parse or modify the sequence IDs! As I said, you must treat them as opaque. The format or the interpretation could change at any time, which could break your code. In some edge cases we might end up re-sending existing changes. I’m not involved in Sync Gateway development anymore, but …

It’s an obscure implementation detail; nothing a client should need to care about. As a client, just treat sequence IDs as opaque JSON objects and don’t interpret their contents. (For example, Cloudant and BigCouch sequence IDs are long strings of base64.)

Hi! Thanks for reply! I am trying to keep up with the changes feed in custom listener and it is now unclear how to store the latest seen seq. Normally I store the seq from each changefeed item as latest seq and use it in _changes POST since-parameter. EDIT –> This part was not correct… it was du…

Ok, good to know, I will recheck how I am utilizing those seq-ids! I also found some detailed info here: [image] couchbase/sync_gateway sync_gateway - Connects Couchbase Lite to Couchbase Server … and also here some hints what the two :: separated values might b…

Investigating more on this: If our changefeed listener has last seq “11112::12345” for example, and then the SG is restarted, the since=“11112::12345” does not work anymore. I have to test more, but I assume that since=“12345” would give the right starting point work after the SG restart. If we don…

Ended up modifying our code so that it does not assume anything about seq format. Now the whole program works fine! : )

@MLModel Thanks for pointing that out - the docs need to be corrected.

But the v. Mobile 1.3 REST documentation of _changes2 explicitly states that they are integers. Those docs are for Couchbase Lite, which uses integers as sequence IDs. Sync Gateway does not.

Why _changes feed seq has format "integer::integer" sometimes?

Mobile Sync Gateway

MLModel November 5, 2016, 10:51pm 8

But the v. Mobile 1.3 REST documentation of _changes explicitly states that they are integers.

Topic		Replies	Views
Sync Gateway _changes returns "seq":"6647722::6647727" Sync Gateway	4	1103	October 23, 2019
String "seq" breaks CouchDB compatibility Sync Gateway	4	2456	May 20, 2015
Strange sync gateway sequence values Mobile	2	1252	October 30, 2018
Strange sequence number and changes-feed issue Sync Gateway	4	1595	October 29, 2020
More documentation on _changes feed message formats? Sync Gateway	4	1116	July 21, 2017

Why _changes feed seq has format "integer::integer" sometimes?

Related topics