Confused about CursorLoaders and using them with special SQLiteOpenHelper

Question

I am writing an application that allows people to set alarms for various tasks that they need to do. My current plan is to store all relevant data in a SQLite database. To this end, I created a class that extends SQLiteOpenHelper and populates it with processing methods for all CRUDs that I expected to accept. Knowing that it was generally a bad idea to do all the processing in a single thread, I looked at ways to split the work between threads and found CursorLoader and LoaderManager that seemed ideal because they were available in the Android Compatibility Library. However, the LoaderManager seems to require the ContentProvider to go through the tutorial in the documentation , and I really did not see the need to do anything with ContentProviders, since I did not plan to allow other applications to access the data. Without ContentProvider, I don’t know how I should get Uri for my databases to submit to CursorLoader. Is there a way for me to continue using my class that extends SQLiteOpenHelper and still implements LoaderManager so that I can save all populating ListFragments with my cursor from the UI thread?

Answer 1

Is there a way to use my class that extends SQLiteOpenHelper and still implements LoaderManager so that I can save all populating ListFragments with my cursor from the UI thread?

You just need another Loader implementation that does not include ContentProvider . It so happened that I wrote one of them .