On Apr 4, 2016, at 11:13 AM, Brendan Duddridge
<[email protected]<mailto:[email protected]>> wrote:
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 :-)
I can imagine situations where database A contains terabytes* of data, and you
want to copy its data into an existing database B at some other location. In
this case the fastest way to replicate [depending on distance] is probably to
export A to a hard drive and carry the hard drive over to where database B is,
then import it from the save file. ("Never underestimate the bandwidth of a
station wagon full of tapes hurtling down the highway.” –Andrew Tanenbaum,
1981. See also What If?<https://what-if.xkcd.com/31/>)
—Jens
* don’t laugh, this isn’t unusual for CouchDB or Couchbase, and CBL’s SQLite
and ForestDB storage can scale to this size.
--
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/68961E57-090E-4B0C-BFFE-EA9CE8364F6D%40couchbase.com.
For more options, visit https://groups.google.com/d/optout.
