Is It Good Practice To Use Contentprovider To Handle Database Operations?
First let you know I am new in Android. Is it good practice to use ContentProvider to handle database table operations only for one application? Trying to create multiple classes
Solution 1:
Is it good practice to use ContentProvider to handle database table operations only for one application?
If your data is exclusive only for your application and other application cannot use it I don't see any reason to use ContentProviders. ContentProvider is used as an interface for sharing your application's data to other application. If your data can be shared or other application is dependent on it then you have to use ContentProvider.
Also you can create set of permissions to your content providers to restrict some operations in the provider.
Post a Comment for "Is It Good Practice To Use Contentprovider To Handle Database Operations?"