Based on this website's blogpost on how to non-destructively upgrade your Android app's database, I've encountered a scenario such as this:
1. I have a database which has a database version 1 which has an existing table being constructed in user's phones.
2. If I were to have a new column in my database table, if I were to deploy the new version of the app into the Google Play Store (what I mean here is an incremental install), of course I would have users bitching about force closes in my app because the database is altered, for instance by adding another column in my database table.
Comments
Post a Comment