Hi everybody again!
So, advices here helped! Thanks!
After some research and testing this solutions seem to work OK:
I have only one!! writable sqlite db. (implemented using singleton as
some people suggested here)
Also, I've got some db code to synchronize write operations.
Only one thread can
and just as reliable. If you
don't understand threads then the content provider technique is safer.
On Apr 1, 7:51 am, Evgeny Nacu evgeny.n...@gmail.com wrote:
Thanks to everyone!
I've heard that ContentProviders do not have such problem. May be
I'll try to use them, but I have many
Kostya, how many users do use your app?
Cause my version works ok for me and for most my users. But some of
them keep getting such error.
I think, this problem is related to some devices, not every.
Or, may be some very specific cases.
Also, do your background threads use ContentProvider to
Thanks to everyone!
I've heard that ContentProviders do not have such problem. May be
I'll try to use them, but I have many things to change.
Thanks for the suggestion.
Evgeny
On 1 апр, 05:11, gjs garyjamessi...@gmail.com wrote:
Hi,
I (strongly?) suggest you wrap access to the sqlite3
Hi everybody!
I would like to know better ways to use SQLite in Android.
I've got some UI Activities and background service (Android service
which runs some AsyncTasks to change the data, they also can use
database concurrently )
First I tried to use all this stuff as is, just open cursor in
5 matches
Mail list logo
