> On Apr 1, 2016, at 3:45 PM, Brendan Duddridge <[email protected]> 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/1A6530FC-4E45-49AD-8D60-DB53D642A0FA%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
