How using SQLiteOpenHelper with database on sd-card?

后端 未结 6 812
渐次进展
渐次进展 2021-02-08 00:50

According to various answers here and in the web extending Application and it\'s inherited method getDatabasePath() would allow to set the database storage path from the standar

6条回答
  •  误落风尘
    2021-02-08 01:09

    Rewriting SQLOpenHelper to use the SD card directory rather than the context and then extending that seems to work for me.

    import android.database.sqlite.SQLiteDatabase;
    import android.database.sqlite.SQLiteDatabase.CursorFactory;
    import android.database.sqlite.SQLiteException;
    import android.util.Log;
    
    /**
     * SDCardSQLiteOpenhelper is a class that is based on SQLiteOpenHelper except
     * that it does not use the context to get the database. It was written owing to
     * a bug in Android 4.0.3 so that using a ContextWrapper to override
     * openOrCreateDatabase, as was done with Android 2.3.3, no longer worked. 
    *
    * The mContext field has been replaced by mDir. It does not use lock on the * database as that method is package private to * android.database.sqlite.SQLiteDatabase. Otherwise the implementation is * similar.
    *
    * * @see android.database.sqlite.SQLiteOpenHelper */ public abstract class SDCardSQLiteOpenHelper { private static final String TAG = SDCardSQLiteOpenHelper.class .getSimpleName(); // private final Context mContext; private final String mName; private final String mDir; private final CursorFactory mFactory; private final int mNewVersion; private SQLiteDatabase mDatabase = null; private boolean mIsInitializing = false; /** * Create a helper object to create, open, and/or manage a database. This * method always returns very quickly. The database is not actually created * or opened until one of {@link #getWritableDatabase} or * {@link #getReadableDatabase} is called. * * @param dir * the directory on the SD card. It must exist and the SD card * must be available. The caller should check this. * @param name * of the database file, or null for an in-memory database * @param factory * to use for creating cursor objects, or null for the default * @param version * number of the database (starting at 1); if the database is * older, {@link #onUpgrade} will be used to upgrade the * database; if the database is newer, {@link #onDowngrade} will * be used to downgrade the database */ public SDCardSQLiteOpenHelper(String dir, String name, CursorFactory factory, int version) { if (version < 1) throw new IllegalArgumentException("Version must be >= 1, was " + version); // mContext = context; mDir = dir; mName = name; mFactory = factory; mNewVersion = version; } /** * Return the name of the SQLite database being opened, as given to the * constructor. */ public String getDatabaseName() { return mName; } /** * Create and/or open a database that will be used for reading and writing. * The first time this is called, the database will be opened and * {@link #onCreate}, {@link #onUpgrade} and/or {@link #onOpen} will be * called. * *

    * Once opened successfully, the database is cached, so you can call this * method every time you need to write to the database. (Make sure to call * {@link #close} when you no longer need the database.) Errors such as bad * permissions or a full disk may cause this method to fail, but future * attempts may succeed if the problem is fixed. *

    * *

    * Database upgrade may take a long time, you should not call this method * from the application main thread, including from * {@link android.content.ContentProvider#onCreate * ContentProvider.onCreate()}. * * @throws SQLiteException * if the database cannot be opened for writing * @return a read/write database object valid until {@link #close} is called */ public synchronized SQLiteDatabase getWritableDatabase() { if (mDatabase != null) { if (!mDatabase.isOpen()) { // darn! the user closed the database by calling // mDatabase.close() mDatabase = null; } else if (!mDatabase.isReadOnly()) { return mDatabase; // The database is already open for business } } if (mIsInitializing) { throw new IllegalStateException( "getWritableDatabase called recursively"); } // If we have a read-only database open, someone could be using it // (though they shouldn't), which would cause a lock to be held on // the file, and our attempts to open the database read-write would // fail waiting for the file lock. To prevent that, we acquire the // lock on the read-only database, which shuts out other users. boolean success = false; SQLiteDatabase db = null; // NOT AVAILABLE // if (mDatabase != null) { // mDatabase.lock(); // } try { mIsInitializing = true; if (mName == null) { db = SQLiteDatabase.create(null); } else { String path = mDir + "/" + mName; // db = mContext.openOrCreateDatabase(mName, 0, mFactory, // mErrorHandler); db = SQLiteDatabase.openDatabase(path, null, SQLiteDatabase.CREATE_IF_NECESSARY); } int version = db.getVersion(); if (version != mNewVersion) { db.beginTransaction(); try { if (version == 0) { onCreate(db); } else { if (version > mNewVersion) { onDowngrade(db, version, mNewVersion); } else { onUpgrade(db, version, mNewVersion); } } db.setVersion(mNewVersion); db.setTransactionSuccessful(); } finally { db.endTransaction(); } } onOpen(db); success = true; return db; } finally { mIsInitializing = false; if (success) { if (mDatabase != null) { try { mDatabase.close(); } catch (Exception e) { // Do nothing } // NOT AVAILABLE // mDatabase.unlock(); } mDatabase = db; } else { // NOT AVAILABLE // if (mDatabase != null) { // mDatabase.unlock(); // } if (db != null) db.close(); } } } /** * Create and/or open a database. This will be the same object returned by * {@link #getWritableDatabase} unless some problem, such as a full disk, * requires the database to be opened read-only. In that case, a read-only * database object will be returned. If the problem is fixed, a future call * to {@link #getWritableDatabase} may succeed, in which case the read-only * database object will be closed and the read/write object will be returned * in the future. * *

    * Like {@link #getWritableDatabase}, this method may take a long time to * return, so you should not call it from the application main thread, * including from {@link android.content.ContentProvider#onCreate * ContentProvider.onCreate()}. * * @throws SQLiteException * if the database cannot be opened * @return a database object valid until {@link #getWritableDatabase} or * {@link #close} is called. */ public synchronized SQLiteDatabase getReadableDatabase() { if (mDatabase != null) { if (!mDatabase.isOpen()) { // darn! the user closed the database by calling // mDatabase.close() mDatabase = null; } else { return mDatabase; // The database is already open for business } } if (mIsInitializing) { throw new IllegalStateException( "getReadableDatabase called recursively"); } try { return getWritableDatabase(); } catch (SQLiteException e) { if (mName == null) throw e; // Can't open a temp database read-only! Log.e(TAG, "Couldn't open " + mName + " for writing (will try read-only):", e); } SQLiteDatabase db = null; try { mIsInitializing = true; // String path = mContext.getDatabasePath(mName).getPath(); String path = mDir + "/" + mName; db = SQLiteDatabase.openDatabase(path, mFactory, SQLiteDatabase.OPEN_READONLY); if (db.getVersion() != mNewVersion) { throw new SQLiteException( "Can't upgrade read-only database from version " + db.getVersion() + " to " + mNewVersion + ": " + path); } onOpen(db); Log.w(TAG, "Opened " + mName + " in read-only mode"); mDatabase = db; return mDatabase; } finally { mIsInitializing = false; if (db != null && db != mDatabase) db.close(); } } /** * Close any open database object. */ public synchronized void close() { if (mIsInitializing) throw new IllegalStateException("Closed during initialization"); if (mDatabase != null && mDatabase.isOpen()) { mDatabase.close(); mDatabase = null; } } /** * Called when the database is created for the first time. This is where the * creation of tables and the initial population of the tables should * happen. * * @param db * The database. */ public abstract void onCreate(SQLiteDatabase db); /** * Called when the database needs to be upgraded. The implementation should * use this method to drop tables, add tables, or do anything else it needs * to upgrade to the new schema version. * *

    * The SQLite ALTER TABLE documentation can be found here. If you add new * columns you can use ALTER TABLE to insert them into a live table. If you * rename or remove columns you can use ALTER TABLE to rename the old table, * then create the new table and then populate the new table with the * contents of the old table. * * @param db * The database. * @param oldVersion * The old database version. * @param newVersion * The new database version. */ public abstract void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion); /** * Called when the database needs to be downgraded. This is stricly similar * to onUpgrade() method, but is called whenever current version is newer * than requested one. However, this method is not abstract, so it is not * mandatory for a customer to implement it. If not overridden, default * implementation will reject downgrade and throws SQLiteException * * @param db * The database. * @param oldVersion * The old database version. * @param newVersion * The new database version. */ public void onDowngrade(SQLiteDatabase db, int oldVersion, int newVersion) { throw new SQLiteException("Can't downgrade database from version " + oldVersion + " to " + newVersion); } /** * Called when the database has been opened. The implementation should check * {@link SQLiteDatabase#isReadOnly} before updating the database. * * @param db * The database. */ public void onOpen(SQLiteDatabase db) { } }

    This was done when the method described above by Roger Keays stopped working on Android 4.0.3.

提交回复
热议问题