This question might have been asked a while ago (in fact i asked it
too but still no answer :).
Let's say i'm changing the project build target from Android 1.6 to
Android 2.2 and that the android:minSdkVersion attribute is changed
accordingly. What will
happen to my current users who don't have A
> Let's say i'm changing the project build target from Android 1.6 to
> Android 2.2 and that the android:minSdkVersion attribute is changed
> accordingly. What will
> happen to my current users who don't have Android 2.2? Will they
> receive the update through
No. that's what minSdkVersion is for.
Thanks for the answer! I know the build target doesn't have to match
minSdkVersion, but new features aren't really my problem: I was thinking
about recreating the db structure from scratch. If i were to treat all users
alike i'd have to write some kind of transition from the old db structure to
the
03.08.2010 14:32, Teo пишет:
If i were to treat all users alike i'd have to write some kind of
transition from the old db structure to the new one in the app, and
tying all the loose ends would be a pain
Android supports database versioning.
http://developer.android.com/reference/android/data
I know, i'm already using it. The code remains the same for everyone though
:) What i'll probably do is to simply create a new db and in case it's not a
new user i'll populate it exhaustively from the old db and then later delete
the old db, while trying to keep my sanity in the process :)
On Tue,
5 matches
Mail list logo
