I've got an experimental solution to the problem of database-busy errors/warnings in Couchbase Lite on iOS/Mac. It uses an in-memory lock to coordinate access to the database between threads, instead of SQLite's default behavior of using file locking. It works for me in unit tests, but I'd like for some people to try it out in real apps that have had database-busy problems.
It's currently checked in on the feature/sqlite_locking branch. There are no API changes nor anything you need to do differently. There should just be less contention between multiple threads accessing the database (including the replicator and LiveQueries.) Please let me know whether it helps, or if you run into any problems. —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/AB8FBC8A-E766-4457-B648-42581DECE460%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
