Group: I am very confused about the need to wrap a ContentProvider around a sqlite db if the db is to only be used locally. I have no plans to expose the data in my sqlite db to any other app.
The quote on the following page would indicate a cp is not necessary if the data is only to be accessed by the local application: *"You don't need a provider to use an SQLite database if the use is entirely within your own application."* http://developer.android.com/guide/topics/providers/content-provider-creating.html That said, it seems every other piece of documentation on the web espouses the use of ContentProviders since they aid multi-threaded programming via the use of Loaders. Can someone please answer definitively for me the following: 1. Are ContentProviders required to use Loaders w/Sqlite? 2. If ContentProviders are *not* required to use Loaders w/Sqlite, is there any recommended example which shows how to use the two together? 1. I really like the update notification feature of Loaders so this would aid me greatly 3. If Sqlite has a recommended way to achieve functional parity to Loaders with another method, what is that method? Hopefully this all makes sense. I have been reading all day, and that quote in the Google docs worries me. I don't want to waste time creating the ContentProvider layer if it is a waste of time. I don't have any idea why the google doc says ContentProviders are not necessary with a local Sqlite data store--when it seems absolutely required to have a ContentProvider in order to be able to use the cool functionality of Loaders? Thanks in advance. -ncdroid -- 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
