Android: access SQLite database via Content Provider or implement DAO?

android database sqlite android-contentprovider dao
user1135437 picture user1135437 · Nov 24, 2012 · Viewed 15.3k times · Source

I'm wondering which is the best approach to access my application database: use a Content Provider, or implement my DAO by hand? From my latest investigations, seems that Content Provider, even for app internal use, is preferable, but I don't know exactly what are the drawbacks of each approach. Can you give some feedback about this?

Answer

Labeeb Panampullan picture Labeeb Panampullan · Nov 24, 2012

I prefer to use ContentProvider if you have concerns of closing or locking of db. Check Simple Content Provider for db operations

Related questions

IllegalArgumentException: the bind value at index 1 is null

Does anybody know what this means? 12-31 20:55:45.861: ERROR/AndroidRuntime(12478): Caused by: java.lang.IllegalArgumentException: the bind value at index 1 is null 12-31 20:55:45.861: ERROR/AndroidRuntime(12478): at android.database.sqlite.SQLiteProgram.bindString(SQLiteProgram.java:234) 12-31 20:55:45.861: ERROR/AndroidRuntime(12478): at android.database.sqlite.SQLiteQuery.…

Read More
How do I view the SQLite database on an Android device?

I have a set of data in an SQLite database. I need to view the database on a device. How do I do that? I have checked in ddms mode. The data in file explorer is empty.

Read More
What are the best practices for SQLite on Android?

What would be considered the best practices when executing queries on an SQLite database within an Android app? Is it safe to run inserts, deletes and select queries from an AsyncTask's doInBackground? Or should I use the UI Thread? I …

Read More