Android SQLiteAssetHelper Can't upgrade read-only database from version 1 to 2:

Question

I want to create an offline dictionary app, that need sometimes to get update and old database will be replaced by new one. It's what I want to do, and I did something like this with SQLiteAssetHelper Library:

Note: SQLiteAssetHelper will copy database from assets folder into app data folder

public class MyDb extends SQLiteAssetHelper {
  private static final String DATABASE_NAME    = "db.sqlite";
  private static final int    DATABASE_VERSION = 1;
  public MyDb(Context context) {
    super(context, DATABASE_NAME, null, DATABASE_VERSION);
  }
}

now i want to update database, after puting new db.sqlite file into assets folder, I have manipulate my codes like this:

public class MyDb extends SQLiteAssetHelper {
  private static final String DATABASE_NAME    = "db.sqlite";
  private static final int    DATABASE_VERSION = 2;
  public MyDb(Context context) {
    super(context, DATABASE_NAME, null, DATABASE_VERSION);
  }
}

but when i compiled and run, it says: Can't upgrade read-only database from version 1 to 2

what is the solution?

by clearing app data, it will works fine...

SORRY FOR MY BAD ENGLISH...

it's here https://github.com/jgilfelt/android-sqlite-asset-helper — Pejman, Nov 02 '14 at 19:16
try this link http://stackoverflow.com/questions/14287191/android-cant-upgrade-read-only-database-from-version-0-to-1 — Jickson, Nov 02 '14 at 19:16
Also this http://stackoverflow.com/questions/7313029/sqliteexception-cant-upgrade-read-only-database-from-version-1-to-2 — Jickson, Nov 02 '14 at 19:16
it's not working with db.execSQL("DROP TABLE IF EXISTS " + TABLE); — Pejman, Nov 02 '14 at 19:21
Have you used the file naming convention? ```assets/databases/_upgrade_-.sql``` — Kiril Aleksandrov, Nov 02 '14 at 19:26

score 7 · Accepted Answer · edited Jun 20 '20 at 09:12

7

Quoting the documentation:

If you have a read-only database or do not care about user data loss, you can force users onto the latest version of the SQLite database each time the version number is incremented (overwriting the local database with the one in the assets) by calling the setForcedUpgrade() method in your SQLiteAsstHelper subclass constructor.

You can additionally pass an argument that is the version number below which the upgrade will be forced.

Note that this will overwrite an existing local database and all data within it.

You are not calling setForcedUpgrade() from your constructor.

edited Jun 20 '20 at 09:12

Community

1
1

answered Nov 02 '14 at 19:37

CommonsWare

986,068
189
2,389
2,491

@Omid: Start over with a fresh install of your database version 1 app and try again, in case your past attempts corrupted your files. Beyond that, consider posting the entire stack trace in your question. – CommonsWare Nov 02 '14 at 19:46
1

Not sure why Omid is having issues, this worked fine for me. Overwrote the old database, imported the new one, just like I wanted. – JustSomeQuickGuy Dec 21 '14 at 20:59

score 6 · Answer 2 · answered Mar 16 '15 at 05:33

You should call setForcedUpgrade(); after your Constructor :

public class MyDb extends SQLiteAssetHelper {

  private static final int    DATABASE_VERSION = 2;//+1
  public MyDb(Context context) {
    super(context, DATABASE_NAME, null, DATABASE_VERSION);
    setForcedUpgrade(); 
  }
}

Pejman · Answer 3 · 2016-05-31T14:14:43.500

2

It's solved by this:

  @Override public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {
    if (oldVersion != newVersion) {
      context.deleteDatabase(DATABASE_NAME);
      new MyDb(context);
    }else
      super.onUpgrade(db, oldVersion, newVersion);
  }

It's very useful for some database that we don't need old data when getting update.

edited May 31 '16 at 14:14

answered Nov 03 '14 at 00:29

Pejman

2,442
4
34
62

This is the correct answer, as setForcedUpgrade(); is simply not working, i would suggest to put context.deleteDatabase(DATABASE_NAME); in the constructor of the SQLiteAssetHelper class instead of setForcedUpgrade(); – ueen May 24 '19 at 21:01

score 2 · Answer 4 · answered Nov 03 '14 at 12:14

Please note that deleting the old db and creating new one in onUpgrade is not the right solution. Older data has to be migrated. Incase you are not interested in maintaining older data ov version 1, it is alright.

Right way is to use onUpgrade to modify the schema. Most of the time altering the schema required recreating table. In such cases follow below approach

rename existing table (say table_xyz) to be altered to some temp name (say temp_table_xyz)
create the table (table_xyz) with new schema
copy the contents from temp table temp_table_xyz to the new table_xyz

my data are not important to stay, this is a dictionary, sometimes we change misspells in db. so old db must delete i think — Pejman, Nov 03 '14 at 15:06

Android SQLiteAssetHelper Can't upgrade read-only database from version 1 to 2:

4 Answers4