數(shù)據(jù)庫版本如何單獨(dú)升級(jí),并且將原有數(shù)據(jù)遷移過去
在我們開發(fā)的應(yīng)用中,一般都會(huì)涉及到數(shù)據(jù)庫,使用數(shù)據(jù)的時(shí)候會(huì)涉及到數(shù)據(jù)庫的升級(jí)、數(shù)據(jù)的遷移、增加行的字段等。比如,用戶定制數(shù)據(jù)的保存,文件的端點(diǎn)續(xù)傳信息的保存等都會(huì)涉及到數(shù)據(jù)庫。
我們應(yīng)用***個(gè)版本是V1.0,在迭代版本V1.1 時(shí),我們?cè)跀?shù)據(jù)庫中增加了一個(gè)字段。因此V1.0的數(shù)據(jù)庫在V1.1版本需要升級(jí),V1.0版本升級(jí)到V1.1時(shí)原來數(shù)據(jù)庫中的數(shù)據(jù)不能丟失,
那么在V1.1中就要有地方能夠檢測(cè)出來版本的差異,并且把V1.0軟件的數(shù)據(jù)庫升級(jí)到V1.1軟件能夠使用的數(shù)據(jù)庫。也就是說,要在V1.0軟件的數(shù)據(jù)庫的那個(gè)表中增加那個(gè)字段,并賦予這個(gè)字段默認(rèn)值。 應(yīng)用中怎么檢測(cè)數(shù)據(jù)庫需要升級(jí)呢? SQLiteOpenHelper 類中有一個(gè)方法:
- public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {}
當(dāng)我們創(chuàng)建對(duì)象的時(shí)候如果傳入的版本號(hào)大于之前的版本號(hào),該方法就會(huì)被調(diào)用,通過判斷oldVersion 和 newVersion 就可以決定如何升級(jí)數(shù)據(jù)庫。在這個(gè)函數(shù)中把老版本數(shù)據(jù)庫的相應(yīng)表中增加字段,并給每條記錄增加默認(rèn)值即可。新版本號(hào)和老版本號(hào)都會(huì)作為onUpgrade函數(shù)的參數(shù)傳進(jìn)來,便于開發(fā)者知道數(shù)據(jù)庫應(yīng)該從哪個(gè)版本升級(jí)到哪個(gè)版本。升級(jí)完成后,數(shù)據(jù)庫會(huì)自動(dòng)存儲(chǔ)***的版本號(hào)為當(dāng)前數(shù)據(jù)庫版本號(hào)。
數(shù)據(jù)庫升級(jí)
SQLite提供了ALTER TABLE命令,允許用戶重命名或添加新的字段到已有表中,但是不能從表中刪除字段。并且只能在表的末尾添加字段,比如,為Orders 表中添加一個(gè)字段:”ALTER TABLE Order ADDCOLUMN Country”
代碼如下:
- public class OrderDBHelper extends SQLiteOpenHelper {
- private static final int DB_VERSION = 1;
- private static final String DB_NAME = "Test.db";
- public static final String TABLE_NAME = "Orders";
- public OrderDBHelper(Context context, int version) {
- super(context, DB_NAME, null, version);
- }
- @Override
- public void onCreate(SQLiteDatabase db) {
- String sql = "create table if not exists " + TABLE_NAME + " (Id integer primary key, " +
- "CustomName text, OrderPrice integer)";
- db.execSQL(sql);
- }
- @Override
- public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {
- Log.e("owen", "DB onUpgrade");
- if (newVersion == 2) {
- db.execSQL("ALTER TABLE " + TABLE_NAME + " ADD COLUMN Country");
- Cursor cr = db.rawQuery("select * from " + TABLE_NAME, null);
- while (cr.moveToNext()) {
- String name = cr.getString(cr.getColumnIndex("CustomName"));
- ContentValues values = new ContentValues();
- values.put("CustomName", name);
- values.put("Country", "China");
- db.update(TABLE_NAME, values, "CustomName=?", new String[] {name});
- }
- cr.close();
- }
- }
- OrderDBHelper orderDBHelper = new OrderDBHelper(this, 2);
- SQLiteDatabase db = orderDBHelper.getWritableDatabase();
- ContentValues contentValues = new ContentValues();
- contentValues.put("OrderPrice", 100);
- contentValues.put("CustomName", "OwenChan");
- db.insert(OrderDBHelper.TABLE_NAME, null, contentValues);
- Log.e("owen", "create finish");
- Cursor cr = db.rawQuery("select * from " + OrderDBHelper.TABLE_NAME , null);
- while (cr.moveToNext()) {
- String name = cr.getString(cr.getColumnIndex("CustomName"));
- Log.e("owen", "name:" + name);
- String country = cr.getString(cr.getColumnIndex("Country"));
- Log.e("owen", "country:" + country);
- }
- cr.close();
- db.close();
數(shù)據(jù)庫的遷移
可以分一下幾個(gè)步驟遷移數(shù)據(jù)庫。
1、 將表名改成臨時(shí)表
ALTER TABLE Order RENAME TO _Order;
2、創(chuàng)建新表
- CREATETABLE Test(Id VARCHAR(32) PRIMARY KEY ,CustomName VARCHAR(32) NOTNULL , Country VARCHAR(16) NOTNULL);
3、導(dǎo)入數(shù)據(jù)
- INSERTINTO Order SELECT id, “”, Age FROM _Order;
4、刪除臨時(shí)表
DROPTABLE _Order;
通過以上四個(gè)步驟,就可以完成舊數(shù)據(jù)庫結(jié)構(gòu)向新數(shù)據(jù)庫結(jié)構(gòu)的遷移,并且其中還可以保證數(shù)據(jù)不會(huì)因?yàn)樯?jí)而流失。 當(dāng)然,如果遇到減少字段的情況,也可以通過創(chuàng)建臨時(shí)表的方式來實(shí)現(xiàn)。
實(shí)現(xiàn)代碼如下:
- @Override
- public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {
- if (newVersion == 2) {
- char str = '"';
- db.beginTransaction();
- db.execSQL("ALTER TABLE Order RENAME TO _Order");
- db.execSQL("CREATE TABLE Order(Id integer primary key autoincrement , CustomName VARCHAR(20) NOT NULL,"
- + " Country VARCHAR(32) NOT NULL , OrderPrice VARCHAR(16) NOT NULL)");
- db.execSQL("INSERT INTO Order SELECT Id, " + str + str
- + ", CustomName, OrderPrice FROM _Order");
- db.setTransactionSuccessful();
- db.endTransaction();
- }
- }
多個(gè)數(shù)據(jù)庫版本的升級(jí)
假如我們開發(fā)的程序已經(jīng)發(fā)布了兩個(gè)版本:V1.0,V2.0,我們正在開發(fā)V3.0。版本號(hào)分別是1,2,3。對(duì)于這種情況,我們應(yīng)該如何實(shí)現(xiàn)升級(jí)? 用戶的選擇有:
- V1.0 -> V3.0 DB 1 -> 2
- V2.0 -> V3.0 DB 2 -> 3
數(shù)據(jù)庫的每一個(gè)版本所代表的數(shù)據(jù)庫必須是定義好的,比如說V1.0的數(shù)據(jù)庫,它可能只有兩張表TableA和TableB,如果V2.0要添加一張表TableC,如果V3.0要修改TableC,數(shù)據(jù)庫結(jié)構(gòu)如下:
- V1.0 —> TableA, TableB V1.2 —> TableA, TableB, TableC V1.3 —> TableA, TableB, TableC (Modify)
代碼如下:
- @Override
- public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {
- if (1 == oldVersion) {
- String sql = "Create table C....";
- db.execSQL(sql);
- oldVersion = 2;
- }
- if (2 == oldVersion) {
- //modify C
- oldVersion = 3;
- }
- }
導(dǎo)入已有數(shù)據(jù)庫:
- /**
- * Created by Owen Chan
- * On 2017-09-26.
- */
- public class DbManager {
- public static final String PACKAGE_NAME = "com.example.sql";
- public static final String DB_NAME = "table.db";
- public static final String DB_PATH = "/data/data/" + PACKAGE_NAME;
- private Context mContext;
- public DbManager(Context mContext) {
- this.mContext = mContext;
- }
- public SQLiteDatabase openDataBase() {
- return SQLiteDatabase.openOrCreateDatabase(DB_PATH + "/" + DB_NAME, null);
- }
- public void importDB() {
- File file = new File(DB_PATH + "/" + DB_NAME);
- if (!file.exists()) {
- try {
- FileOutputStream out = new FileOutputStream(file);
- int buffer = 1024;
- InputStream in = mContext.getResources().openRawResource(R.raw.xxxx);
- byte[] bts = new byte[buffer];
- int lenght;
- while ((lenght = in.read(bts)) > 0) {
- out.write(bts, 0, bts.length);
- }
- out.close();
- in.close();
- } catch (Exception e) {
- e.printStackTrace();
- }
- }
- }
- }
調(diào)用方式:
- @Override
- protected void onResume() {
- super.onResume();
- DbManager dbManager = new DbManager(this);
- dbManager.importDB();
- SQLiteDatabase db = dbManager.openDataBase();
- db.execSQL("do what you want");
- }