Hi Dianne, i get ur point that Content provider is built on top of SQlite but i wanna know is what additional features does a provider support. Say if a make my own Database Store class and provide methods in it to insert/update/delete into a database.
And if i create a Provider for the same purpose, ...in what way will a Provider prove to be more beneficial over the DatabaseStore class other than the fact that provider will allow me to share data ovet different applications On Sep 10, 11:01 am, Dianne Hackborn <hack...@android.com> wrote: > Content provider is (generally) built on top of SQLite. You don't pick one > or the other. > > On Wed, Sep 9, 2009 at 9:24 PM, Chris <narendrasingh.bi...@gmail.com> wrote: > > > I would like to know the exact difference between Content provider and > > SQLiteDatabase. If we have to share our data among applications then > > we use Content provider, otherwise SQLiteDatabase. Is this is the ONLY > > difference, OR using Content Provider has something to do with > > performence??? > > Any input will be highly appreciated. > > > Thanks > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
