Question

Sqlite on android lets you access the database from multiple procs for reads, but if you’re currently writing from one process, reads and writes from other procs will throw an exception because the first write has a lock on the db.

By “procs” I mean other threads in the same app.

Is there a standard way to have the other threads simply wait until the database is available again, possibly with a specified timeout, rather than throwing an exception?

Anticipating the “why are you doing it that way?” answers, its just the way we’re doing it, and that’s it. We’re also not going to use a content provider. Just want a way to synchronize db access.

Assuming there’s no standard way to do it, we’ll probably wind up writing a wrapper around the db calls to do some thread synchronization.

Answer 1

So long as you’re using the same SQLiteDatabase object, the synchronisation is done for you.

So if you access the object via a singleton, there should be no problem. Though you may want to add some further logic if you want to implement a timeout, e.g. wait/notify or something similar.