Lines Matching full:provider
20 <a href="{@docRoot}guide/topics/providers/content-provider-basics.html">
21 Content Provider Basics</a>
24 <a href="{@docRoot}guide/topics/providers/contacts-provider.html">
25 Contacts Provider</a>
50 {@link android.provider.ContactsContract.Contacts} row for a contact the user has picked.
57 {@link android.provider.ContactsContract.Data} table for any rows that contain the contact's
58 {@link android.provider.ContactsContract.Data#LOOKUP_KEY}. This column is available in
59 the {@link android.provider.ContactsContract.Data} table, because the Contacts
60 Provider makes an implicit join between the {@link android.provider.ContactsContract.Contacts}
61 table and the {@link android.provider.ContactsContract.Data} table. The
62 {@link android.provider.ContactsContract.Contacts#LOOKUP_KEY} column is described
68 {@link android.provider.ContactsContract.Data} table. Consider the performance impact before
73 To read from the Contacts Provider, your app must have
88 {@link android.provider.ContactsContract.Data#_ID Data._ID} if you're binding the result
90 won't work. Also retrieve {@link android.provider.ContactsContract.Data#MIMETYPE Data.MIMETYPE}
117 {@link android.provider.ContactsContract.Data} table, using the column names defined in
118 the {@link android.provider.ContactsContract.Data} class.
122 {@link android.provider.ContactsContract.Data} class. Notice, however, that the columns
123 {@link android.provider.ContactsContract.DataColumns#SYNC1} through
124 {@link android.provider.ContactsContract.DataColumns#SYNC4} are meant to be used by sync
131 the {@link android.provider.ContactsContract.Contacts#LOOKUP_KEY Contacts.LOOKUP_KEY} column to
156 {@link android.provider.ContactsContract.Data#MIMETYPE Data.MIMETYPE}. This query argument
174 Always do retrievals from the Contacts Provider (and all other content providers) in a
214 the {@link android.provider.ContactsContract.Data} table, use the constant
215 {@link android.provider.ContactsContract.Data#CONTENT_URI Data.CONTENT_URI} as the content URI.
245 when the Contacts Provider returns the results of the query. For example:
294 {@link android.provider.ContactsContract.CommonDataKinds} subclass corresponding to the
302 {@link android.provider.ContactsContract.Data#MIMETYPE MIMETYPE} value that's specific to
310 {@link android.database.Cursor} by {@link android.provider.ContactsContract.Data#MIMETYPE
320 of {@link android.provider.ContactsContract.CommonDataKinds} for the data type.
336 {@link android.provider.ContactsContract.CommonDataKinds.Email}, instead of the column names
337 defined in the class {@link android.provider.ContactsContract.Data}. Using the email-specific
342 {@link android.provider.ContactsContract.CommonDataKinds} subclass.
347 {@link android.provider.ContactsContract.Data#LOOKUP_KEY} and the
348 {@link android.provider.ContactsContract.Data#MIMETYPE Data.MIMETYPE} of the details you
349 want. Enclose the {@link android.provider.ContactsContract.Data#MIMETYPE MIMETYPE} value in
351 of the constant; otherwise, the provider interprets the constant as a variable name rather
371 specific data type, omit the sort on {@link android.provider.ContactsContract.Data#MIMETYPE}.
374 {@link android.provider.ContactsContract.CommonDataKinds.Email#TYPE Email.TYPE}:
