Op zaterdag 23 augustus 2014 20:08:48 UTC+2 schreef Jens Alfke: > > > On Aug 23, 2014, at 10:06 AM, [email protected] <javascript:> wrote: > > I have an iOS app running on devices A and B, both configured with a > continuous push replication to the other. The databases on the devices are > in sync with 300 documents that won't be modified. When 100 docs are purged > from A (in a 'backgroundTellDatabaseNamed' block) they are replicated back > in from B. > Is that to be expected ? > > > Yes, this is actually correct behavior. Purge is sort of weird — it > completely forgets about the document and its history, so the next time the > replicator hears about the document it will think it's new and will > download it. This has a couple of unexpected side effects: >
But the replicator won't hear about the document because it never changes. And its not the first replication: the 300 documents were created on A and replicated to B. This is the background: the documents are restaurant orders. Once they are paid they become irrelevant for our application and to keep the db clean we periodically purge old paid orders - but they returned back from peers. I've solved the problem by adding a replication filter that skips old/paid orders but I don't understand why that should be necessary. -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/8fbdd7f0-fe30-4ffd-97a5-9eb4d0cd7788%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
