blob query with InexactContentUti about schematic HOT 11 CLOSED

So if you query the database yourself it doesn't work either?

from schematic.

It works in the classic way when I query the dB with contentresolver. But
InexactContentUri is cool to use.

On Tue, Oct 6, 2015, 7:09 PM Simon Vig Therkildsen [email protected]
wrote:

So if you query the database yourself it doesn't work either?

—
Reply to this email directly or view it on GitHub
#37 (comment).

from schematic.

I just wanted to see your opinion.

On Tue, Oct 6, 2015, 9:06 PM Said Tahsin Dane [email protected] wrote:

It works in the classic way when I query the dB with contentresolver. But
InexactContentUri is cool to use.

On Tue, Oct 6, 2015, 7:09 PM Simon Vig Therkildsen <
[email protected]> wrote:

So if you query the database yourself it doesn't work either?

—
Reply to this email directly or view it on GitHub
#37 (comment).

from schematic.

Well, for your example I wouldn't use @InexactContentUri, I'd just use @ContentUri and define the where parameter.

from schematic.

Oh I thought there can be only a single @ContentUri in a class. I couldn't
annotate a method with it. And your sample project as well has only one.

Can I just add another @ContentUri?

On Tue, Oct 6, 2015, 9:17 PM Simon Vig Therkildsen [email protected]
wrote:

Well, for your example I wouldn't use @InexactContentUri, I'd just use
@ContentUri and define the where parameter.

—
Reply to this email directly or view it on GitHub
#37 (comment).

from schematic.

Sure, you can have all the @ContentUri annotated fields you want :)

from schematic.

Do they have to be fields? Not methods?

On Tue, Oct 6, 2015, 10:45 PM Simon Vig Therkildsen <
[email protected]> wrote:

Sure, you can have all the @ContentUri annotated fields you want :)

—
Reply to this email directly or view it on GitHub
#37 (comment).

from schematic.

Yes, the @ContentUri Uri never changes, so that's just for static fields. @InexactContentUri is used when the Uri is created based on some value (e.g. an id).

from schematic.

It seems that I can do what I need using @ContentUri.
@IntexactContentUri with blobs do not work. If it is ok, we can close this issue.

from schematic.

@InexactContentUri works fine with blobs, your @InexactContentUri and @ContentUri just aren't querying the same thing. If you care you can attach a debugger and find out what is being passed to SQLiteDatabase#query in the two cases, to see what the difference it.

from schematic.

Yes it did. Thank you very much.

Little bit documentation on @InexactContentUri and @ContentUri would be really helpfull. I want to help. Sending a PR now. If you don't like it, you can add your own.

Thank you for the great lib.

from schematic.