Software Dev Geek

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. The blogpost is helpful as he highlighted how database table alteration can be done by incrementing the database version and onUpgrade method is triggered in your SqliteOpenHelper class.

I'm sure that everyone has been starting to use JDK1.7 for Android development. As you upgrade from JDK1.6 to JDK1.7, there is a slight change in terms of generating an MD5 fingerprint of your debug keystore or production keystore using the keytool in the command line. Normally you would do this is JDK6: keytool -list -alias alias_name -keystore my-release-key.keystore This directly gives you the MD5 fingerprint of your keystore. But in JDK1.7 that's not the case, because this command gives you the SHA1 fingerprint instead. To solve this problem, be sure to add a -v: keytool -list -v -alias alias_name -keystore my-release-key.keystore This gives you three types of fingerprints. 

Considering that I haven't really done blog posts about software development, and I don't wanna mix tech stock reviews and software development contents that involve code examples and demos, I have decided that I'm gonna do some entries about the works I've done so far. This includes mostly on Android development, Java based web development, and Grails web development, etc (anything that involves coding).