Hi,
We have been using couchbase lite in IOS for analytics, where the device
pushes data to the server (one way only).
There is a lot of data that gets logged that is not going to be useful once
it is replicated on the server.
So once in a while, we wan't to get rid of the local data.
Some approaches that are being tried;
1. Delete the local database and re-create it and all connected
replications.
Concerns: Will the switch be clean ?
- a) If recreating the replication objects after re-creation of db would
be sufficient. Or are there more cached data to clean up ?
- b) How to handle incoming updates ? Should I keep a temporary db to
write to and then copy it back when the db is being set up ?
- c) Will the operation be time consuming ? Can/Should it be moved to a
different thread ?
2. Purge the documents, once replication is stopped.
Concerns: Time consumption.
- a) Since, it blocks the database, it can be moved to a different
thread, while app runs on.
- b) The incoming data need to be managed with either session memory
or a temporary db while purge operation happens
- c) Also, is the compact operation recommended here after purge ?
- d) How to check if the purge is going on ?
What is the recommended course of action in this case ?
Is it easier to delete the database or purge it ? The key point is that,
if the database is replicated on server, we don't care about it being on
the device anymore.
--
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/b901271e-5deb-41ae-8b41-772cad5b337f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
