Sunday 24 June 2012

Android SQLite Database Design Pattern - Extensible, Blocking and Simple

This post is in response to my need to have an Android Database that will:

A) Never ever get into an illegal state, i.e. errors occur if you create/write/read tables at the same time.
B) Split up management of Database tables by creating classes for each one, but still using one single Database.
C) Reuse common Database functionality by creating helper methods.
D) Works at least in Android 2.1+.