Well, that could possibly happen if someone exported from Database A, then imported into a copy of Database A (say on another device), then tried to sync them together after. I know they shouldn't really do this and just setting up sync between the two databases in the first place is the right thing to do, but if there's a path to an issue like this, someone will find it :-)
The fewer support requests I get from people trying to do this the better. On Monday, April 4, 2016 at 11:18:28 AM UTC-6, Jens Alfke wrote: > > > > On Apr 1, 2016, at 3:45 PM, Brendan Duddridge <[email protected] > <javascript:>> wrote: > > > > Is there any downside to the way I've done it above? I actually have > that technique working, but I think it does mean I get an additional > revision for each document. > > The downside is just that you end up with a different revision history > than in the original database you created the JSON file from. This won’t be > a problem unless you later try to replicate between the new and original > database, in which case there will suddenly be conflicts because the docs > have two different rev histories. > > (On the other hand, if you use this technique to copy docs into two > destination databases, those should be consistent with each other and > replication will work.) > > So if you know you won’t be replicating between the source and destination > database, this approach is fine. > > —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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/4357860e-8d82-48e0-bec4-104780721d30%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
