@Brendand Maybe deleting all documents from a given channel on the server is the easier approach. Any idea how to accomplish this?
Am Sonntag, 22. November 2015 11:31:34 UTC+1 schrieb Brendan Duddridge: > > Well that definitely complicates things. Perhaps another way to reset back > to a previous state would be to purge all the documents on the server for a > specific channel? Given that in my case a user can have multiple cblite2 > database files, each belonging to their own channel. And then restore the > cblite2 database file to a previous version? > > Thanks, > > Brendan > > On Saturday, November 21, 2015 at 11:39:51 PM UTC-7, Jens Alfke wrote: >> >> >> On Nov 21, 2015, at 7:19 PM, Brendan Duddridge <[email protected]> wrote: >> >> Are you implying in your response to this question that you can't just >> replace the cblite2 database package and that you must read through the >> backup file, restoring to the current database with the contents of the >> backup file? Does that mean that you would then also have to delete all the >> documents created since the most recent document in the backup database? >> >> >> Yes, *if* your purpose in backing up is to reset the database back to >> the state it was in at some past time (as opposed to just being able to >> restore the database later on in case of data loss.) In resetting back to a >> *past* state, you are fighting against the replicator, whose job it is >> to update to the *latest* state available on the server. That’s why you >> can’t just restore the database file — it contains old revisions that will >> be replaced by newer ones from the server. >> >> —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/e8c6a4cd-2342-4cf8-a99e-46e04fb66428%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
