CODEWITHSUNDEEP
androiddatabasedesign-patternsandroid-contentprovider
Soumya Simanta
Soumya Simanta

Reputation: 11741

Android Content Provider inside the same application

I've more than one activity (inside the same Application) that needs to have access to the database. What's the best pattern to implement this ? Do I need a content provider even if all activities belong to the same application?

Which activity should have the responsibility for opening and closing the database ?

Upvotes: 3

Views: 1273

Answers (3)

MH16
MH16

Reputation: 2356

Content providers offer a structured storage mechanism that can be limited to your own application or exported to allow access by other applications. If you do not intend to provide other applications with access to your ContentProvider, mark them as android:exported=false in the application manifest. Otherwise, set the android:exported attribute to true to allow other apps to access the stored data.

https://developer.android.com/training/articles/security-tips

Upvotes: 0

Eno
Eno

Reputation: 10850

Your two options are Content Provider or just using your own database abstraction layer. The content provider is a better way to go as pointed out, if you need other apps to share your data or if you need to hook into some other part of Android (like the Quick Search framework). It should not be tied into an Activity - should just be a separate class that you import and use.

The OReilly Android programming book has a chapter which illustrates both approaches, its a good read.

Upvotes: 3

Cristian
Cristian

Reputation: 200080

Not necessary. You just have to create a Content Provider if you want some external application to access your data.

Upvotes: 0

Related Questions