Separated database table logic and added SocialProvider.
Created a second ContentProvider to handle social stream data, called
"Activities" here. Designed schema after the data provided by various
online stream sources, including the "Atom Activity Extensions" RFC
Internet-Draft available at http://activitystrea.ms/.
Because social data references Contacts data directly by _ID, we keep
the data behind both ContentProviders in a single database to improve
join query performance.
To make sure that both ContentProviders use the same underlying
database through a single SQLiteDatabase instance, we only allow access
to OpenHelper as a singleton.
6 files changed