> On Nov 1, 2014, at 9:05 AM, Nithin Haridas <nit...@odinix.com> wrote: > > 3) Add all incoming data to a temporary db while the above process is going > on. > 4) Copy the data from temporary db to the recreated db.
I think that's going to cause problems. Copying documents from one database to another without using the replicator won't preserve the replication history (and might even alter the revision ID), and that has the potential to confuse the replicator. In the worst case those copied documents could get replicated back up to the server as false conflicts, then pulled by other clients, causing a big mess. It would be best to keep the incoming docs in a separate database locally. They can live in the same database on the server; just point both local databases at the same server database, but in the pull replication add a local filter that only brings in the docs that you want (i.e. not the docs that your other db is pushing.) —Jens -- 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 mobile-couchbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/DF6522D5-F255-4A67-B444-929CDB00409F%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
