No, that would expose the implementation behind the content provider more than we want. For your own content provider you can fairly easily define your own URI schemes that allow arbitrary joins or such across tables or other things, but we don't plan on this becoming a general facility that all content providers must allow.
On Thu, Jan 15, 2009 at 7:07 AM, A T <somecs...@gmail.com> wrote: > I have one quick question and one maybe not-as-quick question: > > 1. Will we be able to employ more robust SQL(ite) queries on content > providers with future releases? For instance: joins, distinct, count, > max, etc? > > 2. Why isn't this possible now? I understand the concept of DB table > abstraction and the reasoning behind it, but why not still provide > some roundabout way of doing these operations (without storing the > content in a local SQLite table, of course)? > > > > Thanks AT > > > > -- 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. 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 -~----------~----~----~----~------~----~------~--~---
