Cascade delete and Triggers

If you are using a database in your android application you are probably going to delete data at some point. When dealing with one to many relationships, the children should also be deleted when the master is deleted.

For example, a table Album contains many songs stored in another table Songs. The table Songs has a foreign key album_id referencing the primary key id in table Album.

Sqlite3 doesn't support cascade delete until version 3.6.19 (available on Android 2.2), so if you want this to work on a device running android prior to version 2.2 it can be solved using Triggers:

In your database helper class, create a String containg the trigger command:
private static final String CREATE_TRIGGER_DELETE_ALBUM =
     "CREATE TRIGGER fkd_songs_album_id "
       +"BEFORE DELETE ON Album "
       +"DELETE FROM Songs WHERE album_id = OLD._id; " 
and add this after you have created the tables:
  public void onCreate(SQLiteDatabase db) {
       //Create tables
Now, when deleting an Album all of it's songs will also be deleted.


Optimizing code

Since mobile devices are pretty limited when it comes to hardware specs, there are a few things you should think of as a developer to optimize the code. This will make the app run faster and smoother, and the user will more likely keep using your app.

1. One thing I noticed when debugging my app, was a lot of lines in Logcat that looked like: "Gc freed x objects / y bytes in z ms". This is the garbage collector doing it's work and it's of course impossible to write an app that has no GC at some point. But if you start seeing these lines frequently and when the app is idle, you should be able to optimize the code.

The most probable cause for this is that you create too many objects. Look for code like:
public void onClick(View view) {
  String aString = object.getString();
  Integer anInteger = object.getInteger();
Change this by declaring the variables as class member variables instead, then you will create only one object instead of one object/onclick action. Note that you shouldn't use this as a general rule though. A member (global) variable's life cycle is longer compared to local variables, so it will allocate memory for a longer time.

In a GPS listener method executing once every second you should use member variables.

In a method that will be executed a few times only, local variables are preferred.

2. Analyze the layout. If you start nesting several LinearLayout you should consider switching to RelativeLayout instead. The deeper the layout tree becomes, the more expensive it is. One way to analyze this is to use the tool Hierarchy Viewer (included in the SDK). Run your application and click on <Focused Window> and then hit Ctrl + L to load the current activity. You should aim for a wide layout instead of deep layout with many levels.

3. Avoid boxing and Un-boxing of objects:
public void stupid() {
  Integer anInteger = Integer.valueOf(new Float(String.valueOf(1.1f)).toString());
This will create many objects. Use the primitives (i.e. float, int) instead of their wrapper classes (i.e. Float, Integer) when possible.

4. Access the member variables directly instead of using a getter method. It will always be faster.

5. Reuse views. For example, instead of creating a new TextView object for each TextView in a layout, you should consider reusing only one TextView.

6. This is more of a power consumption optimization, but a good one. If you are using GPS listener for example, you should consider turning it off when the phone is idle or when the user exits the activity where GPS is used, by implementing the onResume and onPause methods:
protected void onResume() {
  // Acquire a reference to the system Location Manager
  locationManager = (LocationManager) this.getSystemService(Context.LOCATION_SERVICE);
  // Define a listener that responds to location updates
  locationListener = new LocationListener() {
   public void onLocationChanged(Location location) {
 // Register the listener with the Location Manager to receive location
 locationManager.requestLocationUpdates(LocationManager.GPS_PROVIDER, 0, 0, locationListener);
 protected void onPause() {
  locationManager = null;



The first problem I ran into was of course how to include code snippets in my blog posts. So I stumbled upon SyntaxHighlighter and it works perfectly.

To use it on your own blog page, simply follow these steps.

1. On your blogger page, go to "Design/Template" -> "Edit HTML" and add these lines above the </head> tag:
<link href='http://alexgorbatchev.com/pub/sh/current/styles/shCore.css' rel='stylesheet' type='text/css'/>
<link href='http://alexgorbatchev.com/pub/sh/current/styles/shThemeDefault.css' rel='stylesheet' type='text/css'/>
<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shCore.js' type='text/javascript'/>

2. Add support for the languages needed, a full list of supported languages can be found here. For example continue to add these lines:
<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushCss.js' type='text/javascript'/>
<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushJava.js' type='text/javascript'/>
<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushJScript.js' type='text/javascript'/>
<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushSql.js' type='text/javascript'/>
<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushXml.js' type='text/javascript'/>

3. Lastly add this line
<script language='javascript'> SyntaxHighlighter.config.bloggerMode = true;
 SyntaxHighlighter.config.clipboardSwf =
 SyntaxHighlighter.all(); </script>

Click on Save to complete the implementation. Try it out by creating a new post and in the HTML section type:

<pre class="brush: java">
private void test() {
System.out.println("Testing code snippets");


In this blog I will keep you updated throughout my first android project. I will share the knowledge gathered, as we all know that it can be frustrating at times when a simple task seems completely impossible. I have myself spent several hours digging through information on the internet, and a lot of times on other peoples blogs.