Fixed
Status Update
Comments
se...@google.com <se...@google.com> #2
mm...@commonsware.com <mm...@commonsware.com> #3
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)
yb...@google.com <yb...@google.com> #4
SupportSQLiteDatabase as arg for the callback method right? Works for me.
yb...@google.com <yb...@google.com> #5
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)
yb...@google.com <yb...@google.com> #6
this is fixed for the next version.
note that, you still need a version upgrade to get the new behavior since we didn't want to change the existing schema files.
note that, you still need a version upgrade to get the new behavior since we didn't want to change the existing schema files.
Description
Version used: 1.0.0-alpha8
If I change the order of the member variables within an @Entity Class, I am forced to provide a migration.
Before:
@Entity(tableName = "contacts")
public class ContactEntity {
@PrimaryKey(autoGenerate = true)
private Long id;
@ColumnInfo(name = "phone")
private String phone;
@ColumnInfo(name = "name")
private String name;
@ColumnInfo(name = "mail")
private String mail;
}
After:
@Entity(tableName = "contacts")
public class ContactEntity {
@PrimaryKey(autoGenerate = true)
private Long id;
@ColumnInfo(name = "name")
private String name;
@ColumnInfo(name = "phone")
private String phone;
@ColumnInfo(name = "mail")
private String mail;
}
Is this intended behaviour?
If yes, how would such a migration look like?