| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ifbf422a2eb177858813d118f03ceddcd807e73b4
|
|
|
|
|
| |
This will dump out the contents of the operation in some error cases
to make debugging easier.
|
|
|
|
| |
Fixes http://b/2226007
|
|
|
|
|
|
|
| |
passed in array.
Bug: 2221947
Change-Id: I3b7d5cbef61777d76ca7fc0d7c91c44553e609a9
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When performing a set of batch operations, some callers need
to enforce that a query has specific values. For example,
when persisting edited Contact values, we need to assert
that the RawContacts.VERSION matches the version we read out
through queryEntities().
This change adds a new TYPE_ASSERT that uses withValues()
and withSelection(), and checks all values when applying the
batch operation, bailing if any values don't match.
|
|
|
|
| |
- change the ContentProviderOperation selection backref store the backref as a long instead of as a string
|
|
|
|
|
|
|
|
|
|
| |
Internally, ContentProviderOperation maintains a "type",
which correspond to builder methods, such as "newInsert()".
Unit tests often need to assert which operations are
being built, so this change adds a getType() accessor and
esposes the internal constants used. They are marked with
@hide so they are not exposed in the public API.
|
| |
|
|
|
|
| |
- add the group membership common kind as well as some IM utilities to the ContactsContract
|
|
|
|
|
|
| |
- change the applyBatch to take an ArrayList rather than an []
- change Entity to be a final flass that contains ContentValues
- remove the ability to update/insert Entities by a ContentProviderOperation
|
| |
|
|
|