[android-developers] Re: Sqlite3 concurrency

2009-10-27 Thread mirko
Hi Mariano, I use close only once. The DB object is held in an Android service. When the service stops the DB object is closed. I think you should not have two opened DB objects at the same time. Mirko On 23 Okt., 22:09, Mariano Kamp mariano.k...@gmail.com wrote: Hey Mirko,   thank you very

[android-developers] Re: Sqlite3 concurrency

2009-10-27 Thread Mariano Kamp
Thanks. You're right. I tried close on the readOnlyDB and it closed both database object ;-( Still not sure how to deal with the readlock then? ;-( 2009/10/27 mirko mirkocze...@googlemail.com Hi Mariano, I use close only once. The DB object is held in an Android service. When the service

[android-developers] Re: Sqlite3 concurrency

2009-10-23 Thread mirko
Hi Mariano, I had the same problems with my app. After reading a little bit on the SQLite Website my understanding was that locking is done with process (thread) locks. So there are many reader treads possible, but only one writer thread. For this reason your SQLiteDatabase object needs to be a

[android-developers] Re: Sqlite3 concurrency

2009-10-23 Thread Mariano Kamp
Hey Mirko, thank you very much for taking the time to give me such a detailed and easy to understand answer. I think that I already have implemented my code the way you describe as I originally started out with the Notepad