| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Switch com.android.internal.util.Objects to com.google.common.base.Objects.
Technically this change is not necessary for the provider but it nice to
use the same code everywhere. And since the provider already has a
dependency on guava anyways, this doesn't hurt.
Bug: 6948882
Change-Id: I565d65f00b1f25c4ae1bf3c8086c10ab2f31dfd5
|
|
|
|
| |
Change-Id: If3afb134ea36bd93859efcd114885526e1592b91
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Check if there's really a new or removed account in
updateAccountsInBackground() before doing everything else.
If there's none, we'll skip re-scanning directories too.
- Preheat the account cache when the provider starts.
- Use account_id for the account filter query parameters. The contacts URI
now supports the parameters too.
Change-Id: I12e1116890df4c20b354618acfaee9dc009dc68e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove the account columns (type, name, data_set) from the
raw_contacts/groups tables and add account_id instead.
- Re-create the accounts table. The new table now has the _ID column. Rows
in this table now has a different lifecyle than before:
-- New row is created as the provider detects a new account during a write
operation to the raw_contacts and groups table.
-- Stale rows are removed upon account removal.
- Removed account consistency check for steam items/photos. We don't do this
kind of check for other tables.
Change-Id: I1ce01590aef70f417fa89426dae762a41d25d656
|
|
The intent of the data set field is to provide a way for multiple
sync adapters from the same account name + type to manage separate
sets of data in the raw_contacts and groups table.
For example, this would allow for Focus groups to be synced in from
Focus via the Google Contacts sync adapter, and for Google+ Circles
to be synced in from the Google+ app, even though both are tied to
the same account name + type.
Bug 5077096
Change-Id: I641c5d233d8d4d70988d209179c4e79bdb9c7ea1
|