Go to file
Marc Blank 0e1595c177 Handle unexpected deletion of EmailProvider database
* Addresses #2226426
* If the user deletes Email data, or if data corruption causes
  EmailProvider.db to be deleted, we will be in an inconsistent
  state with any existing Exchange accounts, since the AccountManager
  will still know about them, contacts (and eventually calendar) items will
  continue to exist, etc.
* Run an integrity check when the provider is created, deleting any
  orphaned EmailProvider.db or EmailProviderBody.db
* Catch SQLiteException's in the Provider and do an integrity check
  if any is caught

Change-Id: I47d523b90a6b8f71ba8e13fba4b04846b3da1b1d
2009-12-07 21:12:57 -08:00
assets auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00
docs auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00
images auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00
res am 6d69fb7c: Fix 2266119: Simplify account creation strings and remove translation requirement 2009-12-02 19:04:52 -08:00
src Handle unexpected deletion of EmailProvider database 2009-12-07 21:12:57 -08:00
tests Handle unexpected deletion of EmailProvider database 2009-12-07 21:12:57 -08:00
.classpath Initial Contribution 2008-10-21 07:00:00 -07:00
.project Initial Contribution 2008-10-21 07:00:00 -07:00
Android.mk Various EAS related changes related to accounts and services. 2009-07-13 19:10:08 -07:00
AndroidManifest.xml Per spec, allow all attachments to be added via INTENT. 2009-09-27 23:49:10 -07:00
MODULE_LICENSE_APACHE2 auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00
NOTICE auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00