SQLite DB persistence

1

Hi,
Ok, so I’ve noted over the past year or so that when I do updates to Android apps things have changed…
Before then, if you deleted an app and installed with a new apk, then the SQLite tables etc would refresh…
Now, it’s very interesting. If you update an app, keep the bundle identifier the same and just increase the version number, then no matter WHAT you do with the previous app (in terms of Force Stop / Clear Cache / Clear Storage / uninstall app) it appears the SQLite tables are retained. (even after device reboot.)

e.g.
Version 1 _ has a table with 3 fields (e.g. fielda, fieldb, fieldc)
You install version 1 etc (send back the tables via SQLExport to a server)

You then delete / wipe / remove etc etc all traces of that App. Reboot the device.

You then update the app, adding in a new field to the table ( so now it has field1,field2, field3, field4)
You build the app as version 2.
You download the apk, install, open it…Export the tables… Take a look (even in notepad)
The new field is NOT there.
The DB seems to be persisting (even outside the app!)

Now there could be benefits to this… but in editing table structures this is a pain.
Any solutions (other than, maybe renaming the DB, perhaps) ?

Is this the way it’s supposed to work now?
Thanks,
Neil

2

Incidentally, one way of ‘fixing’ this is to have something like :

DBVERSION = Replace(localStorage.appversion,".","")
DB = SqlOpenDatabase("DNAME" & DBVERSION & ".db","1.0","DB Remote Database")

So, everytime you do a version update your DB will update too (albeit losing your data in the old DB…)

3

What happens to abandoned Sqlite DBs within an app space?
Does the Android system wipe them after a while?

4

Apologies… some of this has been previosuly discussed under :

SQLite DB not being installed