Moving all DB management logic from LauncherProvider into a separate class

This would make it easier to move the controller to LauncherModel

Bug: 277345535
Test: Presubmit
Flag: N/A
Change-Id: I4d044cf41361f400968ef65e18de5d3976fcdec7
This commit is contained in:
Sunny Goyal
2023-04-10 15:28:59 -07:00
parent f8e0e7270e
commit 1ae46ca868
6 changed files with 497 additions and 324 deletions
@@ -63,6 +63,7 @@ import com.android.launcher3.model.BgDataModel;
import com.android.launcher3.model.BgDataModel.Callbacks;
import com.android.launcher3.model.DatabaseHelper;
import com.android.launcher3.model.ItemInstallQueue;
import com.android.launcher3.model.ModelDbController;
import com.android.launcher3.model.data.AppInfo;
import com.android.launcher3.model.data.ItemInfo;
import com.android.launcher3.pm.InstallSessionHelper;
@@ -471,16 +472,16 @@ public class LauncherModelHelper {
@Override
public boolean onCreate() {
mModelDbController = new ModelDbController(getContext());
return true;
}
public SQLiteDatabase getDb() {
createDbIfNotExists();
return mOpenHelper.getWritableDatabase();
return mModelDbController.getDatabaseHelper().getWritableDatabase();
}
public DatabaseHelper getHelper() {
return mOpenHelper;
return mModelDbController.getDatabaseHelper();
}
}