Yes, but if the database can't be opened at sqlite level, it would only
help the app know that, not recover the data... And there are other ways to
detect that. Back to square one: why do they get corrupted in the first place?
Nathan <[email protected]> 20 сентября 2013 г. 4:05:53 написал:
On Thursday, September 19, 2013 4:31:23 PM UTC-7, Kostya Vasilyev wrote:
>
>
http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/2.1_r2/android/database/sqlite/SQLiteDatabase.java
>
> Look for a method called onCorruption.
>
It looks like we could, in 4.0+, define a custom DatabaseErrorHandler that
could do something different.
I have not done so.
Nathan
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
