Sure, but in almost all cases it is backed by SQLite - so intentionally gimping the API that's supposed to be used for exchanging data across applications is monumentally stupid - since JDBC is not an alternative on Android.
Designing for the lowest common denominator != good. > ContentProvider is not a database abstraction -- it's a content store > abstraction. Not all ContentProviders will be backed up by a SQLite > database or anything else that interprets SQL. Hence, it is not surprising > to me that ContentProvider does not support arbitrary SQL statements. > > Since a ContentProvider -- particularly one needing your proposed UPDATE > statement -- is only needed for inter-process content sharing, you might > consider switching to a remote service (using AIDL) instead. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > Android App Developer Books:http://commonsware.com/books.html -- 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
