>From the interface methods on SQLiteDatabase, it seems very much like it is intended for one instance of SQLiteDatabase per open database, and that you share it between threads.
You can apparently even set locking enabled. ================= public void setLockingEnabled (boolean lockingEnabled) Since: API Level 1 Control whether or not the SQLiteDatabase is made thread-safe by using locks around critical sections. This is pretty expensive, so if you know that your DB will only be used by a single thread then you should set this to false. The default is true. ================= I think I will have to set/leave this to true and take the performance hit - I hope it is not too huge. To find out all the dynamic behavior with multiple readers and writers, I will probably have to experiment. I'm pretty sure that someone has figured this all out, but it wouldn't hurt to know how it all fits my application. Nathan
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
