Home
last modified time | relevance | path

Searched refs:ACCOUNT_TYPE (Results 1 – 25 of 38) sorted by relevance

12

/frameworks/base/core/java/android/provider/
DSyncStateContract.java45 public static final String ACCOUNT_TYPE = "account_type"; field
61 Columns.ACCOUNT_NAME + "=? AND " + Columns.ACCOUNT_TYPE + "=?";
108 values.put(Columns.ACCOUNT_TYPE, account.type); in set()
117 values.put(Columns.ACCOUNT_TYPE, account.type); in insert()
165 .withValue(Columns.ACCOUNT_TYPE, account.type) in newSetOperation()
DBrowserContract.java125 public static final String ACCOUNT_TYPE = "account_type"; field
425 public static final String ACCOUNT_TYPE = "account_type"; field in BrowserContract.Accounts
DContactsContract.java505 public static final String ACCOUNT_TYPE = "accountType"; field in ContactsContract.Directory
804 public static final String ACCOUNT_TYPE = "account_type"; field
3050 DatabaseUtils.cursorStringToContentValuesIfPresent(cursor, cv, ACCOUNT_TYPE); in getEntityAndIncrementCursor()
3589 public static final String ACCOUNT_TYPE = "account_type"; field
7821 DatabaseUtils.cursorStringToContentValuesIfPresent(cursor, values, ACCOUNT_TYPE); in getEntityAndIncrementCursor()
7956 public static final String ACCOUNT_TYPE = "account_type"; field
9294 public static final String ACCOUNT_TYPE = "account_type"; field
9430 public static final String ACCOUNT_TYPE = "account_type"; field
DCalendarContract.java288 public static final String ACCOUNT_TYPE = "account_type"; field
528 DatabaseUtils.cursorStringToContentValuesIfPresent(cursor, cv, ACCOUNT_TYPE); in getEntityAndIncrementCursor()
722 ACCOUNT_TYPE,
1669 ACCOUNT_TYPE,
/frameworks/base/services/tests/servicestests/src/com/android/server/accounts/
DPreNTestDatabaseHelper.java29 public static final String ACCOUNT_TYPE = "type1"; field in PreNTestDatabaseHelper
30 public static final String ACCOUNT_NAME = "account@" + ACCOUNT_TYPE;
47 + "('" + ACCOUNT_NAME + "', '" + ACCOUNT_TYPE + "', '" + ACCOUNT_PASSWORD + "')"); in onCreate()
/frameworks/ex/common/java/com/android/common/content/
DSyncStateContentProviderHelper.java35 + SyncStateContract.Columns.ACCOUNT_TYPE + "=?";
45 SyncStateContract.Columns.ACCOUNT_TYPE};
59 + SyncStateContract.Columns.ACCOUNT_TYPE + " TEXT NOT NULL," in createDatabase()
62 + SyncStateContract.Columns.ACCOUNT_TYPE + "));"); in createDatabase()
/frameworks/base/docs/html-intl/intl/ja/guide/topics/providers/
Dcalendar-provider.jd279 <div class="sidebox-wrapper"> <div class="sidebox"> <h3>ACCOUNT_TYPE を含める必要がある理由
280 …のセクションに {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE} も含…
284 これは、指定されたアカウントは <code>ACCOUNT_NAME</code> とその <code>ACCOUNT_TYPE</code> がどちらも与えられることで一意とみなされるからです。
286 <code>ACCOUNT_TYPE</code> は、そのアカウントが {@link android.accounts.AccountManager} で登録されたときに使用されたアカウント認証シ…
296 この例のクエリは、<code>ACCOUNT_NAME</code> が「sampleuser@google.com」で、<code>ACCOUNT_TYPE</code> が「com.google…
313 + Calendars.ACCOUNT_TYPE + " = ?) AND ("
373 アプリケーションがローカル カレンダーを作成する必要がある場合は、{@link android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE}…
1163 …#ACCOUNT_NAME} と {@link android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} をクエリ パラメータとして …
1170 …イムゾーン、アクセスレベル、場所など、数多くにアクセスできます。ただし、<code>ACCOUNT_NAME</code> と <code>ACCOUNT_TYPE</code> で指定されるもの…
1180 .appendQueryParameter(Calendars.ACCOUNT_TYPE, accountType).build();
Dcontacts-provider.jd197 詳しくは、次の {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE} の項目をご覧ください。
208 {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE}
1079 .withValue(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType())
1507 rawContactRow.put(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType());
1843 {@code android.provider.ContactsContract.StreamItemsColumns#ACCOUNT_TYPE}
/frameworks/base/docs/html-intl/intl/ru/guide/topics/providers/
Dcalendar-provider.jd280 ACCOUNT_TYPE?</h3> <p>При создании запроса {@link
284 {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}. Это необхо…
286 <code>ACCOUNT_TYPE</code>. Параметр <code>ACCOUNT_TYPE</code> в строке обозначает
298 — sampleuser@google.com, <code>ACCOUNT_TYPE</code>
313 + Calendars.ACCOUNT_TYPE + " = ?) AND ("
376 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} типа {@link
1165 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} в качестве параметров запроса в URI. </…
1173 <code>ACCOUNT_TYPE</code>.</li> </ul>
1180 .appendQueryParameter(Calendars.ACCOUNT_TYPE, accountType).build();
Dcontacts-provider.jd199 {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE}.
208 {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE}
1079 .withValue(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType())
1507 rawContactRow.put(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType());
1843 {@code android.provider.ContactsContract.StreamItemsColumns#ACCOUNT_TYPE}
/frameworks/base/docs/html-intl/intl/ko/guide/topics/providers/
Dcalendar-provider.jd280 ACCOUNT_TYPE을 반드시 포함시켜야 하는 이유는 무엇일까요?</h3> <p>{@link
283 {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}
286 <code>ACCOUNT_TYPE</code>이 모두 있을 때뿐이기 때문입니다. <code>ACCOUNT_TYPE</code>은 계정이
298 "sampleuser@google.com", <code>ACCOUNT_TYPE</code>
313 + Calendars.ACCOUNT_TYPE + " = ?) AND ("
377 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE}을 사용합니다.
1165 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE}을 제공해야 합니다. </li>
1173 <code>ACCOUNT_TYPE</code>에 한정됩니다.</li> </ul>
1180 .appendQueryParameter(Calendars.ACCOUNT_TYPE, accountType).build();
Dcontacts-provider.jd198 {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE}의
208 {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE}
1079 .withValue(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType())
1507 rawContactRow.put(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType());
1843 {@code android.provider.ContactsContract.StreamItemsColumns#ACCOUNT_TYPE}
/frameworks/base/docs/html-intl/intl/zh-tw/guide/topics/providers/
Dcalendar-provider.jd279 <div class="sidebox-wrapper"> <div class="sidebox"> <h3>為什麼一定要包含 ACCOUNT_TYPE？
283 {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}。
285 <code>ACCOUNT_TYPE</code> 情況下，此帳戶才會視為唯一的。
286 <code>ACCOUNT_TYPE</code> 是對應至帳戶驗證器的字串。帳戶使用
296 在此範例中，查詢會尋找日曆中有 <code>ACCOUNT_NAME</code> "sampleuser@google.com"、<code>ACCOUNT_TYPE</code> "com.go…
313 + Calendars.ACCOUNT_TYPE + " = ?) AND ("
373 …rContract#ACCOUNT_TYPE_LOCAL} 的 {@link android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE}。
1165 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} 作為查詢參數。 </li>
1171 <code>ACCOUNT_TYPE</code>。
1180 .appendQueryParameter(Calendars.ACCOUNT_TYPE, accountType).build();
Dcontacts-provider.jd198 {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE}。
208 {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE}
1079 .withValue(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType())
1507 rawContactRow.put(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType());
1843 {@code android.provider.ContactsContract.StreamItemsColumns#ACCOUNT_TYPE}
/frameworks/base/docs/html-intl/intl/zh-cn/guide/topics/providers/
Dcalendar-provider.jd280 ACCOUNT_TYPE？</h3> <p>如果您查询 {@link
283 {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}
285 <code>ACCOUNT_NAME</code> 及其 <code>ACCOUNT_TYPE</code>
286 的情况下，才能将其视为唯一帐户。<code>ACCOUNT_TYPE</code>
298 为“sampleuser@google.com”、<code>ACCOUNT_TYPE</code>
313 + Calendars.ACCOUNT_TYPE + " = ?) AND ("
378 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE}，通过以同步适配器形式执行日历插入来实现目的。{@link android.pr…
1165 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} 作为 URI 中的查询参数。 </li>
1173 <code>ACCOUNT_TYPE</code>。</li> </ul>
1180 .appendQueryParameter(Calendars.ACCOUNT_TYPE, accountType).build();
Dcontacts-provider.jd198 {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE} 的下一条目。
208 {@link android.provider.ContactsContract.SyncColumns#ACCOUNT_TYPE}
1079 .withValue(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType())
1507 rawContactRow.put(ContactsContract.RawContacts.ACCOUNT_TYPE, mSelectedAccount.getType());
1843 {@code android.provider.ContactsContract.StreamItemsColumns#ACCOUNT_TYPE}
/frameworks/base/docs/html-intl/intl/in/guide/topics/providers/
Dcalendar-provider.jd280 ACCOUNT_TYPE?</h3> <p>Jika Anda membuat query pada {@link
283 {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}
286 <code>ACCOUNT_TYPE</code>-nya. <code>ACCOUNT_TYPE</code> adalah string yang sesuai dengan
298 "sampleuser@google.com", <code>ACCOUNT_TYPE</code>
313 + Calendars.ACCOUNT_TYPE + " = ?) AND ("
376 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} dari {@link
1165 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} sebagai parameter query dalam URI. </li>
1173 <code>ACCOUNT_TYPE</code> yang ditetapkannya.</li> </ul>
1180 .appendQueryParameter(Calendars.ACCOUNT_TYPE, accountType).build();
/frameworks/opt/chips/src/com/android/ex/chips/
DBaseRecipientAdapter.java124 Directory.ACCOUNT_TYPE, // 2
132 public static final int ACCOUNT_TYPE = 2; field in BaseRecipientAdapter.DirectoryListQuery
730 params.accountType = directoryCursor.getString(DirectoryListQuery.ACCOUNT_TYPE); in setupOtherDirectories()
/frameworks/ex/common/java/com/android/common/contacts/
DBaseEmailAddressAdapter.java147 public static final int ACCOUNT_TYPE = 2; field in BaseEmailAddressAdapter.DirectoryListQuery
385 partition.accountType = directoryCursor.getString(DirectoryListQuery.ACCOUNT_TYPE); in onDirectoryLoadFinished()
/frameworks/base/docs/html/guide/topics/providers/
Dcalendar-provider.jd280 ACCOUNT_TYPE?</h3> <p>If you query on a {@link
283 {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}
286 <code>ACCOUNT_TYPE</code>. The <code>ACCOUNT_TYPE</code> is the string corresponding to the
298 "sampleuser@google.com", the <code>ACCOUNT_TYPE</code>
313 + Calendars.ACCOUNT_TYPE + " = ?) AND ("
376 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} of {@link
1173 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} as query parameters in the URI. </li>
1181 <code>ACCOUNT_TYPE</code> it specified.</li> </ul>
1188 .appendQueryParameter(Calendars.ACCOUNT_TYPE, accountType).build();
/frameworks/opt/vcard/tests/src/com/android/vcard/tests/testutils/
DImportTestProvider.java84 TestCase.assertNull(actualContentValues.get(RawContacts.ACCOUNT_TYPE)); in applyBatch()
/frameworks/base/docs/html-intl/intl/pt-br/guide/topics/providers/
Dcalendar-provider.jd280 ACCOUNT_TYPE?</h3> <p>Ao consultar um {@link
283 {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}
286 e <code>ACCOUNT_TYPE</code>. <code>ACCOUNT_TYPE</code> é a string correspondente
298 "sampleuser@google.com", o <code>ACCOUNT_TYPE</code>
313 + Calendars.ACCOUNT_TYPE + " = ?) AND ("
376 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} de {@link
1165 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} como parâmetros da consulta na URI. </l…
1173 e ao <code>ACCOUNT_TYPE</code> que especificou.</li> </ul>
1180 .appendQueryParameter(Calendars.ACCOUNT_TYPE, accountType).build();
/frameworks/base/keystore/java/android/security/
DKeyChain.java97 public static final String ACCOUNT_TYPE = "com.android.keychain"; field in KeyChain
/frameworks/base/docs/html-intl/intl/vi/guide/topics/providers/
Dcalendar-provider.jd280 ACCOUNT_TYPE?</h3> <p>Nếu bạn truy vấn trên một {@link
283 {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}
286 <code>ACCOUNT_TYPE</code> của nó. <code>ACCOUNT_TYPE</code> là xâu tương ứng với
298 "sampleuser@google.com", <code>ACCOUNT_TYPE</code>
313 + Calendars.ACCOUNT_TYPE + " = ?) AND ("
376 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} của {@link
1165 android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE} làm tham số truy vấn trong URI. </li>
1173 <code>ACCOUNT_TYPE</code> mà nó quy định.</li> </ul>
1180 .appendQueryParameter(Calendars.ACCOUNT_TYPE, accountType).build();
/frameworks/base/docs/html/training/sync-adapters/
Dcreating-sync-adapter.jd387 public static final String ACCOUNT_TYPE = "example.com";
410 ACCOUNT, ACCOUNT_TYPE);
477 constant {@code ACCOUNT_TYPE} in the code snippet in the section

12