Am 23.12.11 00:06, schrieb lbendlin:
it's not a bug, that's how SQLite works. You can't have concurrent
writes. Not sure how the content provider buffers this but if you do
plain SQLite you are basically blocking the database with each write,
and you need to use semaphores to manage that.
I
To OP:
Do your threads use separate instances of SQLiteDatabase object pointing
to the same database one- or one SQLiteDatabase instance, shared?
23.12.2011 18:03, Ralph Bergmann | the4thFloor.eu пишет:
Am 23.12.11 00:06, schrieb lbendlin:
it's not a bug, that's how SQLite works. You can't
The threads use the content provider. The content provider's insert()
method gets a database from the SQLiteOpenHelper each time.
I'll add that the content provider we're using is a modified version of
Google's telephony content provider. We've been able to duplicate this
behavior with the
it's not a bug, that's how SQLite works. You can't have concurrent writes.
Not sure how the content provider buffers this but if you do plain SQLite
you are basically blocking the database with each write, and you need to
use semaphores to manage that.
--
You received this message because you
4 matches
Mail list logo
