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
c
Thanks for your response. I really don't mean to push the issue, I'm just
afraid that you misunderstood my question. In terms of existing providers,
if I need to do, say, a DISTINCT query, I would have to either load the
table into my own provider/SQLite DB and do it there by executing an
arbitrary
> In terms of existing providers,
> if I need to do, say, a DISTINCT query, I would have to either load the
> table into my own provider/SQLite DB and do it there by executing an
> arbitrary SQLite query, or use a content provider query and operate on the
> cursor manually.
Generally speaking, th
Ok, I did not realize that. I had made the assumption that they were all
DB-based.
My real goal here was to just figure out the best (i.e. quickest) way to do
some operations that are not possible with the given content provider
methods, but at the same time avoid localizing them and then re-uploa
> Ok, I did not realize that. I had made the assumption that they were all
> DB-based.
Some will be, but I'm under the impression that ContentProvider was
specifically designed not to force it. For example, some people are using
ContentProvider to serve static Web content to a WebView, which IMHO
You are right about that :)
Yeah, so, in other words, it doesn't sound like a problem I'm going to be
able to solve here and now, for the project I'm working on.
Ok, no worries. I'm sure I'll figure something out. Thanks again for your
help!
On Thu, Jan 15, 2009 at 4:18 PM, Mark Murphy wrote:
So, I'm working on an app that is accessing an existing content provider
which holds a significant amount of data. I will be querying and updating
this content provider frequently, and it has proven to cause noticeable
delays due to the constraints that are required for these queries. I am
wonderin
It would be hard to say, it depends very much on what exactly you are
doing. In general direct queries on a database are quite fast, but it would
be hard to say how fast it will be to retrieve all data from an existing
provider and write it into your own database.
On Thu, Jan 22, 2009 at 8:52 AM,
Oh, that's not the problem. That will only have to be done once -- the first
time the app is run on a device. The rest of the queries and updates will be
to and from my own database. The updates to the content provider will be
done in the background, and it's ok if the data isn't up to date immedia
9 matches
Mail list logo
