/**@class android.provider.ContactsContract.RawContacts.Entity
 implements android.provider.BaseColumns

 implements android.provider.ContactsContract.DataColumns

@extends java.lang.Object

 <p>
 A sub-directory of a single raw contact that contains all of its
 {@link android.provider.ContactsContract.Data} rows. To access this directory append
 {@link android.provider.ContactsContract.RawContacts.Entity#CONTENT_DIRECTORY} to the raw contact URI. See
 {@link android.provider.ContactsContract.RawContactsEntity} for a stand-alone table containing the same
 data.
 </p>
 <p>
 Entity has two ID fields: {@link #_ID} for the raw contact
 and {@link #DATA_ID} for the data rows.
 Entity always contains at least one row, even if there are no
 actual data rows. In this case the {@link #DATA_ID} field will be
 null.
 </p>
 <p>
 Using Entity should be preferred to using two separate queries:
 RawContacts followed by Data. The reason is that Entity reads all
 data for a raw contact in one transaction, so there is no possibility
 of the data changing between the two queries.
*/
var Entity = {

/** The directory twig for this sub-table
*/
CONTENT_DIRECTORY : "entity",
/** The ID of the data row. The value will be null if this raw contact has no
 data rows.
 <P>Type: INTEGER</P>
*/
DATA_ID : "data_id",

};