SQLite implements its own locking protocol internally. If you want operations to wait rather than fail, you need to wrap operations from both sources with your own synchronization primitives that wait rather than fail.
On Feb 11, 1:34 pm, Julius Spencer <[email protected]> wrote: > Hi, > > I have an IntentService which syncs data from a server and takes a few > minutes. The operation is database intensive locally (SQLite). > > I would like the user to be able to continue to use the application while the > sync operation is going which involves the odd write to the database. > > Currently I'm getting "database is locked" errors. Has anyone come across > this issue before and solved it? > > Regards, > Julius. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
