Should there be one SQLiteOpenHelper for each table in the database?

android database android-sqlite
Matteo Bononi 'peorthyr' picture Matteo Bononi 'peorthyr' · Dec 14, 2012 · Viewed 7.5k times · Source

Is it better to have a single big SQLiteOpenHelper subclass that defines onCreate and onUpgrade methods for every table in the database, or is better to have many SQLiteOpenHelper subclasses, one for each table?

Is there a best practice? Or are both acceptable, but with different good and bad side effects?

Answer

MysticMagicϡ picture MysticMagicϡ · Dec 14, 2012

You should have a single SQLiteOpenHelper class for all the tables. Check this link.

Related questions

Set default value of an integer column SQLite

I am creating an SQLite database in android. db.execSQL("CREATE TABLE " + DATABASE_TABLE + " (" + KEY_ROWID + " INTEGER PRIMARY KEY AUTOINCREMENT, " + KEY_NAME + " TEXT NOT NULL, " + KEY_WORKED + " INTEGER, " + KEY_NOTE + " INTEGER);"); Is it possible to set the default value of …

Read More
Retrieve database or any other file from the Internal Storage using run-as

On a non-rooted android device, I can navigate to the data folder containing the database using the run-as command with my package name. Most files types I am content with just viewing, but with the database I would like to …

Read More
SQLite returned an error code of 14

I am trying to copy an existing database from my assets folder and execute some operations on it. Everything is working fine but I've gotten the following error in the log files of my emulator: sqlite returned: error code = 14, msg = …

Read More