I have an app with 2 Activities and an IntentService all which need to access the same SQLite Database table. What's an appropriate pattern to use?
Should I create a ContentProvider that manages access to the database, ie opening/closing, querying, updating etc. And have the 3 clients all access the DB via the ContentProvider? Or is it OK for each client to access the DB directly? This is the approach I have now and it seems to be working, but I need to close my cursor and the DB after executing every statement or I start generating stacktraces in the log about unclosed DB resources. But closing the DB after each statement seems wasteful and I suspect that this approach will always be susceptible to the stacktraces because there is always the potential for collisions between either of the Activities and the IntentService. I haven't been able to find any good resources that show DB usage in full. It always snippets that miss out the *obvious* piece such as when should the resources be closed etc. Can someone set me straight? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
