Android SQLite Database: Creating db at runtime or using prepopulated db?

Question

I'm writing an app which will rely heavily on the use of a database. This database will have two "bigger" tables (50rows*70columns and 200rows*20columns) and 5 or 6 smaller tables. The app will need to access, read and edit the database.

Now, I'm having doubts about whether I should create the database programatically at runtime or using a prepopulated one on the assets folder. Considering the size of the database described in the first paragraph, which method do you think brings more advantages?

Thank you.

score 3 · Accepted Answer · answered Feb 03 '12 at 17:07

3

I am a fan of shipping my apps with a pre-populated database if the data is not dynamic. Why parse a text file and do a bunch of inserts if you can just copy the database from your assets folder?

Here is a guide to do it yourself
Here is a nice helper class if you would rather use proven code

answered Feb 03 '12 at 17:07

JustinMorris

7,259
3
30
36

The app will need to add some rows to the tables. Can I edit a prepopulated database? – tyb Feb 03 '12 at 17:10
absolutely, once you copy it over its the exact same as if you just created it programmically – JustinMorris Feb 03 '12 at 17:24

score 1 · Answer 2 · edited May 23 '17 at 11:53

1

Prepopulated is the best practice in such conditions. How to use the prepopulated database? see this.

edited May 23 '17 at 11:53

Community

1
1

answered Feb 03 '12 at 17:21

Yaqub Ahmad

27,569
23
102
149

The app will need to add some rows to the tables. Is it possible when using a prepopulated db? thanks – tyb Feb 03 '12 at 17:23
1

yes why not, see the link & you will find how to use the prepopulated database. – Yaqub Ahmad Feb 03 '12 at 17:25

Android SQLite Database: Creating db at runtime or using prepopulated db?

2 Answers2