On 2 Mar 2012, at 5:58pm, Roger Binns <rog...@rogerbinns.com> wrote:
> On 02/03/12 09:40, Simon Slavin wrote: >> What ContentProvider is, as far as I can work out, is a way of >> accessing a SQLite database file in a form convenient for Android >> apps. > > No, it is a way for Android app components to expose and manipulate data > with those components being in the same or different apps. How the data > is actually stored (in a database, in SQLite, on a server, rot13 encoded > steganographically in gif files) is immaterial. > > All Android apps are made up of multiple components, and the APIs for > components decouples them as much as possible so they can be mixed and > matched with an app or across apps. ContentProvider is one of those > decoupling APIs for data. > > http://developer.android.com/guide/topics/fundamentals.html I see. And I read your previous post too (it just appeared after I'd posted). Okay so even if you were using ContentProvider you'd still be using another thing to read the SQLite database. No problem. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
