We use content providers because of the nice integration that is provided to support our applications. Content Providers allow us to use ContentResolver and AsyncQueryHandler and all the other tools. ContentProvider helps us manage our database more easily than trying to do it on our own.
The only reason not to use a ContentProvider is if you are concerned about other applications reading your data via your ContentProvider. So, you use permissions to protect the data and if the user decides to let another application access those permissions, that is their choice. ContentProvider makes the whole business of using a database in your application much easier and robust. There is really no reason to ever not use a ContentProvider, if you are using a database in your application. On Aug 9, 5:36 am, Sohan badaya <[email protected]> wrote: > Hi All, > > I have a doubt about content provider. Why we use content provider? > can't we use database of a application? > If we talk about other application also. can't we use database of that > application directly wihout > content provider? > > Thanks, > Sohan -- 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
