Hello, I have written MultiThreadSQLiteOpenHelper which is an enhanced SQLiteOpenHelper for Android applications where several threads might open and close the same sqlite database.
Instead of calling close method, threads ask for closing the database, thus preventing a thread from performing a query on a closed database. If each thread asked for closing, then a close is actually performed. Each activity or thread (ui-thread and user-threads) performs an open call on database when resuming, and asks for closing the database when pausing or finishing. Source code and samples available here: https://github.com/d4rxh4wx/MultiThreadSQLiteOpenHelper ref: http://stackoverflow.com/questions/8888530/ok-to-have-one-instance-of-sqliteopenhelper-shared-by-all-activities-in-an-andro I would be glad to have your feedbacks. d4rxh4wx -- 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