ContentProvider doesn't define this (though the API is strongly designed around being backed by SQLite); it is up to the implementation of the content provider to decide how it will manage its storage. Look at the sample code for examples -- the NotePad sample is probably a good place to start.
On Fri, Nov 5, 2010 at 5:22 PM, d1m_bu1b <[email protected]> wrote: > Any pointers? > All I could find is a block diagram of SQL and a streamFile > capability. > There must be some documentation somewhere. > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] 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 [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
