Android API之android.provider.ContactsContract.Data
android.provider.ContactsContract.Data
Constants for the data table, which contains data points tied to a raw contact. Each row of the data table is typically used to store a single piece of contact information (such as a phone number) and its associated metadata (such as whether it is a work or home number).
Data kinds
Data is a generic table that can hold any kind of contact data. The kind of data stored in a given row is specified by the row's MIMETYPE
value, which determines the meaning of the generic columns DATA1
through DATA15
. For example, if the data kind is Phone.CONTENT_ITEM_TYPE
, then the column DATA1
stores the phone number, but if the data kind is Email.CONTENT_ITEM_TYPE
, then DATA1
stores the email address. Sync adapters and applications can introduce their own data kinds.
ContactsContract defines a small number of pre-defined data kinds, e.g. CommonDataKinds.Phone
, CommonDataKinds.Email
etc. As a convenience, these classes define data kind specific aliases for DATA1 etc. For example, Phone.NUMBER
is the same as Data.DATA1
.
DATA1
is an indexed column and should be used for the data element that is expected to be most frequently used in query selections. For example, in the case of a row representing email addresses DATA1
should probably be used for the email address itself, while DATA2
etc can be used for auxiliary information like type of email address.
By convention, DATA15
is used for storing BLOBs (binary data).
The sync adapter for a given account type must correctly handle every data type used in the corresponding raw contacts. Otherwise it could result in lost or corrupted data.
Similarly, you should refrain from introducing new kinds of data for an other party's account types. For example, if you add a data row for "favorite song" to a raw contact owned by a Google account, it will not get synced to the server, because the Google sync adapter does not know how to handle this data kind. Thus new data kinds are typically introduced along with new account types, i.e. new sync adapters.
Batch operations
Data rows can be inserted/updated/deleted using the traditional ContentResolver.insert
, ContentResolver.update
and ContentResolver.delete
methods, however the newer mechanism based on a batch of ContentProviderOperation
will prove to be a better choice in almost all cases. All operations in a batch are executed in a single transaction, which ensures that the phone-side and server-side state of a raw contact are always consistent. Also, the batch-based approach is far more efficient: not only are the database operations faster when executed in a single transaction, but also sending a batch of commands to the content provider saves a lot of time on context switching between your process and the process in which the content provider runs.
The flip side of using batched operations is that a large batch may lock up the database for a long time preventing other applications from accessing data and potentially causing ANRs ("Application Not Responding" dialogs.)
To avoid such lockups of the database, make sure to insert "yield points" in the batch. A yield point indicates to the content provider that before executing the next operation it can commit the changes that have already been made, yield to other requests, open another transaction and continue processing operations. A yield point will not automatically commit the transaction, but only if there is another request waiting on the database. Normally a sync adapter should insert a yield point at the beginning of each raw contact operation sequence in the batch. See ContentProviderOperation.Builder.withYieldAllowed(boolean)
.
Operations
- Insert
-
An individual data row can be inserted using the traditional
ContentResolver.insert(Uri, ContentValues)
method. Multiple rows should always be inserted as a batch.An example of a traditional insert:
ContentValues values = new ContentValues();
values.put(Data.RAW_CONTACT_ID, rawContactId);
values.put(Data.MIMETYPE, Phone.CONTENT_ITEM_TYPE);
values.put(Phone.NUMBER, "1-800-GOOG-411");
values.put(Phone.TYPE, Phone.TYPE_CUSTOM);
values.put(Phone.LABEL, "free directory assistance");
Uri dataUri = getContentResolver().insert(Data.CONTENT_URI, values);The same done using ContentProviderOperations:
ArrayList<ContentProviderOperation> ops = Lists.newArrayList();
ops.add(ContentProviderOperation.newInsert(Data.CONTENT_URI)
.withValue(Data.RAW_CONTACT_ID, rawContactId)
.withValue(Data.MIMETYPE, Phone.CONTENT_ITEM_TYPE)
.withValue(Phone.NUMBER, "1-800-GOOG-411")
.withValue(Phone.TYPE, Phone.TYPE_CUSTOM)
.withValue(Phone.LABEL, "free directory assistance")
.build());
getContentResolver().applyBatch(ContactsContract.AUTHORITY, ops); - Update
-
Just as with insert, update can be done incrementally or as a batch, the batch mode being the preferred method:
ArrayList<ContentProviderOperation> ops = Lists.newArrayList();
ops.add(ContentProviderOperation.newUpdate(Data.CONTENT_URI)
.withSelection(Data._ID + "=?", new String[]{String.valueOf(dataId)})
.withValue(Email.DATA, "somebody@android.com")
.build());
getContentResolver().applyBatch(ContactsContract.AUTHORITY, ops); - Delete
-
Just as with insert and update, deletion can be done either using the
ContentResolver.delete
method or using a ContentProviderOperation:ArrayList<ContentProviderOperation> ops = Lists.newArrayList();
ops.add(ContentProviderOperation.newDelete(Data.CONTENT_URI)
.withSelection(Data._ID + "=?", new String[]{String.valueOf(dataId)})
.build());
getContentResolver().applyBatch(ContactsContract.AUTHORITY, ops); - Query
-
- Finding all Data of a given type for a given contact
-
Cursor c = getContentResolver().query(Data.CONTENT_URI,
new String[] {Data._ID, Phone.NUMBER, Phone.TYPE, Phone.LABEL},
Data.CONTACT_ID + "=?" + " AND "
+ Data.MIMETYPE + "='" + Phone.CONTENT_ITEM_TYPE + "'",
new String[] {String.valueOf(contactId)}, null); - Finding all Data of a given type for a given raw contact
-
Cursor c = getContentResolver().query(Data.CONTENT_URI,
new String[] {Data._ID, Phone.NUMBER, Phone.TYPE, Phone.LABEL},
Data.RAW_CONTACT_ID + "=?" + " AND "
+ Data.MIMETYPE + "='" + Phone.CONTENT_ITEM_TYPE + "'",
new String[] {String.valueOf(rawContactId)}, null); - Finding all Data for a given raw contact
- Most sync adapters will want to read all data rows for a raw contact along with the raw contact itself. For that you should use the
RawContactsEntity
. See alsoRawContacts
.
Columns
Many columns are available via a Data.CONTENT_URI
query. For best performance you should explicitly specify a projection to only those columns that you need.
Data
类型 |
字段名称 |
读写权限 |
备注 |
long |
_ID |
只读 |
Row ID. Sync adapter should try to preserve row IDs during updates. In other words, it would be a bad idea to delete and reinsert a data row. A sync adapter should always do an update instead. |
String |
MIMETYPE |
可读/只写一次 |
The MIME type of the item represented by this row. Examples of common MIME types are:
|
long |
RAW_CONTACT_ID |
可读/可写一次 |
The id of the row in the |
int |
IS_PRIMARY |
可读/可写 |
Whether this is the primary entry of its kind for the raw contact it belongs to. "1" if true, "0" if false. |
int |
IS_SUPER_PRIMARY |
可读/可写 |
Whether this is the primary entry of its kind for the aggregate contact it belongs to. Any data record that is "super primary" must also be "primary". For example, the super-primary entry may be interpreted as the default contact value of its kind (for example, the default phone number to use for the contact). |
int |
DATA_VERSION |
只读 |
The version of this data record. Whenever the data row changes the version goes up. This value is monotonically increasing. |
Any type |
可读/可写 |
Generic data columns. The meaning of each column is determined by the Data columns whose meaning is not explicitly defined for a given MIMETYPE should not be used. There is no guarantee that any sync adapter will preserve them. Sync adapters themselves should not use such columns either, but should instead use |
|
Any type |
可读/可写 |
Generic columns for use by sync adapters. For example, a Photo row may store the image URL in SYNC1, a status (not loaded, loading, loaded, error) in SYNC2, server-side version number in SYNC3 and error code in SYNC4. Some columns from the most recent associated status update are also available through an implicit join. Join with |
|
int |
PRESENCE |
只读 |
IM presence status linked to this data row. Compare with CONTACT_PRESENCE , which contains the contact's presence across all IM rows. See StatusUpdates for individual status definitions. The provider may choose not to store this value in persistent storage. The expectation is that presence status will be updated on a regular basic. |
String |
STATUS |
只读 |
Latest status update linked with this data row. |
long |
STATUS_TIMESTAMP |
只读 |
The absolute time in milliseconds when the latest status was inserted/updated for this data row. |
String |
STATUS_RES_PACKAGE |
只读 |
The package containing resources for this status: label and icon. |
long |
STATUS_LABLE |
只读 |
The resource ID of the label describing the source of status update linked to this data row. This resource is scoped by the STATUS_RES_PACKAGE . |
long |
STATUS_ICON |
只读 |
The resource ID of the icon for the source of the status update linked to this data row. This resource is scoped by the Some columns from the associated raw contact are also available through an implicit join. The other columns are excluded as uninteresting in this context. Join with |
long |
CONTACT_ID |
只读 |
The id of the row in the Contacts table that this data belongs to. |
int |
AGGREGATION_MODE |
只读 |
See RawContacts . |
int |
DELETED |
只读 |
See The ID column for the associated aggregated contact table Join with |
String |
LOOKUP_KEY |
只读 |
See ContactsContract.Contacts |
String |
DISPLAY_NAME |
只读 |
See ContactsContract.Contacts |
long |
PHOTO_ID |
只读 |
See ContactsContract.Contacts |
int |
IN_VISIBLE_GROUP |
只读 |
See ContactsContract.Contacts |
int |
HAS_PHONE_NUMBER |
只读 |
See ContactsContract.Contacts |
int |
TIMES_CONTACTED |
只读 |
See ContactsContract.Contacts |
long |
LAST_TIME_CONTACTED |
只读 |
See ContactsContract.Contacts |
int |
STARRED |
只读 |
See ContactsContract.Contacts |
String |
CUSTOM_RINGTONE |
只读 |
See ContactsContract.Contacts |
int |
SEND_TO_VOICEMAIL |
只读 |
See ContactsContract.Contacts |
int |
CONTACT_PRESENCE |
只读 |
See ContactsContract.Contacts |
String |
CONTACT_STATUS |
只读 |
See ContactsContract.Contacts |
long |
CONTACT_STATUS_TIMESTAMP |
只读 |
See ContactsContract.Contacts |
String |
CONTACT_STATUS_RES_PACKAGE |
只读 |
See ContactsContract.Contacts |
long |
CONTACT_STATUS_LABEL |
只读 |
See ContactsContract.Contacts |
long |
CONTACT_STATUS_ICON |
只读 |
See ContactsContract.Contacts |
Android API之android.provider.ContactsContract.Data的更多相关文章
- Android API之android.provider.ContactsContract.RawContacts
android.provider.ContactsContract.RawContacts Constants for the raw contacts table, which contains o ...
- Android API之android.provider.ContactsContract
android.provider.ContactsContract ContactsContract是联系人provider和app的contract.定义了已支持的URL和column.取代了之前的 ...
- Android API之android.provider.ContactsContract.Contacts
android.provider.ContactsContract.Contacts 对应contacts数据表.RawContacts的一个聚合(aggregate)代表同一个人.每个人在数据表co ...
- 【Android API】Android 4.1 API官方文档详解
原文:http://android.eoe.cn/topic/summary 翻译:[eoeAndroid原创团队]kris.流风而逝.贼寇在何方.snowxwyo.lsy4833406 更新日期:2 ...
- Android API之android.os.Parcelable
android.os.Parcelable Interface for classes whose instances can be written to and restored from a Pa ...
- Android API之android.content.BroadcastReceiver
android.content.BroadcastReceiver Base class for code that will receive intents sent by sendBroadcas ...
- Android API之android.content.AsyncQueryHandler
android.content.AsyncQueryHandler A helper class to help make handling asynchronous ContentResolver ...
- Android API之android.widget.Filterable
android.widget.Filterable 定义了一种可过滤的行为.Filterable接口通常有android.widget.Adapter来实现.接口Filterable中有个抽象方法 ...
- Android API之android.view.View.MeasureSpec
android.view.View.MeasureSpec MeasureSpec是View的内部类 public static class MeasureSpec MeasureSpec封装从par ...
随机推荐
- 【docker】centOS7上部署的mysql和spring boot服务,要求,mysql的时间、java程序服务的时间和宿主机的时间完全保持一致【修改mysql时区,临时和永久】【修改spring boot配置文件时区】【修改docker启动spring boot实例程序时区】
要求:centOS7上部署的mysql和spring boot服务,要求,mysql的时间.java程序服务的时间和宿主机的时间完全保持一致: ============================ ...
- .NET:CLR via C# Compute-Bound Asynchronous Operations
线程槽 使用线程池了以后就不要使用线程槽了,当线程池执行完调度任务后,线程槽的数据还在. 测试代码 using System; using System.Collections.Generic; us ...
- 文件内容操作篇clearerr fclose fdopen feof fflush fgetc fgets fileno fopen fputc fputs fread freopen fseek ftell fwrite getc getchar gets
clearerr(清除文件流的错误旗标) 相关函数 feof 表头文件 #include<stdio.h> 定义函数 void clearerr(FILE * stream); 函数说明 ...
- Linux进程调度的运行队列
当Linux内核要寻找一个新的进程在CPU上运行时,必须只考虑处于可运行状态的进程,(即在TASK_RUNNING状态的进程),因为扫描整个进程链表是相当低效的,所以引入了可运行状态进程的双向循环链表 ...
- SoundPool 音频播放 API 详解【示例】
demo地址:https://github.com/baiqiantao/PermissionTest.git 一个大坑:SoundPool最多只能播放时长10s左右.大小70kb左右(这些值是我多次 ...
- 添加sqljdbc4的maven依赖
sqljdbc是微软sql server的jdbc驱动 使用sqljdbc需要从微软的官方网站下载jar包: http://www.microsoft.com/en-us/download/detai ...
- 把表单转成json,并且name为key,value为值
http://jsfiddle.net/sxGtM/3/http://stackoverflow.com/questions/1184624/convert-form-data-to-js-objec ...
- JQuery模仿淘宝天猫魔盒抢购页面倒计时效果
1.效果及功能说明 通过对时间的控制来告诉用户一个活动还剩多少时间,精确到秒.2.实现原理 首先定义活动的截至的时间,要重年份精确到毫秒,在获得当前的年份到秒钟,在用截至时间,减去现在的时间,剩下的还 ...
- IOS UITableView索引排序功能
UITbableView分组展示信息时,有时在右侧会带索引,右侧的索引一般为分组的首字母,比如城市列表的展示.当点击右侧索引的字母,列表会快速跳到索引对应的分组,方便我们快速查找.下面,就介绍一下索引 ...
- Ubuntu16.04下Neo4j图数据库官网安装部署步骤(图文详解)(博主推荐)
不多说,直接上干货! 说在前面的话 首先,查看下你的操作系统的版本. root@zhouls-virtual-machine:~# cat /etc/issue Ubuntu LTS \n \l r ...