Fixed
Status Update
No update yet.
Comments
ga...@gmail.com
yb...@google.com
yb...@google.com
hi,
what do you think about moving the error handler's method into the callback class?
android.arch.persistence.db.SupportSQLiteOpenHelper.Callback#onCorruption(SQLiteDatabase db)
what do you think about moving the error handler's method into the callback class?
android.arch.persistence.db.SupportSQLiteOpenHelper.Callback#onCorruption(SQLiteDatabase db)
ga...@gmail.com
SupportSQLiteDatabase as arg for the callback method right? Works for me.
yb...@google.com
not an arg but method.
So the Callback class gets a new method like this:
android.arch.persistence.db.SupportSQLiteOpenHelper.Callback#onCorruption(SupportSQLiteDatabase db)
So the Callback class gets a new method like this:
android.arch.persistence.db.SupportSQLiteOpenHelper.Callback#onCorruption(SupportSQLiteDatabase db)
Description
Version used: 1.0.0-alpha9
The errorHandler field of SupportSQLiteOpenHelper.Configuration[0] uses android.database.DatabaseErrorHandler[1]. The problem is that the onCorrupted method of DatabaseErrorHandler has android.database.SQLiteDatabase as parameter, which custom implementations won't have an instance of because they write their own implementation of android.arch.persistence.db.SupportSQLiteDatabase[2]. My proposal would be to add a SupportDatabaseErrorHandler which uses SupportSQLiteDatabase instead of the platform one.
[0]:
[1]:
[2]: