With Android Architecture Components getting a stable 1.0 version, there are now no excuses of not using it 🙂 Along with handling lifecycle events, realtime data updates in UI (ViewModel with LiveData) and pagination of loaded data (Paging), comes Room – small, yet powerful SQLite ORM. In this post I’m gonna demonstrate its core capabilities on an example Android application.
Remember those times implementing SQLiteOpenHelper and checking SQL queries in run-time? Good news is that you don’t have to do it anymore! Room performs compile-time checks on your SQL queries and you don’t have to write any SQLite code which is not in a direct relation with your data queries. Great, lets use it!
First of all, Room is a part of Architecture Components, which means it works really well with ViewModel, LiveData and Paging (but does not depend on them!). Also, RxJava and Kotlin are perfectly fine too. In order to add Room to the project, I’m adding the following lines in app’s build.gradle file:
Check for the latest library version here.
Additionally, provide a location of DB’s schema in defaultConfig scope. This way you can always check how it looks, maybe decide to modify your tables once you notice something in scheme.
arguments = ["room.schemaLocation":
Continue reading Database example app with Room ORM
Today’s tutorial will be about SQLCipher and its integration in Android (with the means of Android Studio). Just to give some introduction, SQLCipher is used for a full database encryption. What full means is that the DB file is entirely encrypted, not only separate rows or tables. Zetetic, the company behind SQLCipher, provides Community and Commercial edition. You can use the former for commercial projects, though, just have to provide license doc in your app. Also, SQLCipher is not for Android only, it can be used on various platforms.
Regarding security features, SQLCipher uses 256-bit AES in CBC mode by default, with 1kB page size, and it derives the key data using PBKDF2 function. The difference in API that you instantly notice is the passphrase argument in
getWritableDatabase() methods. Now, this passphrase should never be stored in the application, otherwise the whole point of encryption is wasted. One thing to keep in mind, is that the passphrase is not a key! Yes, the DB is encrypted using the key, but it is generated based on the passphrase (~ password) and also can be re-set using PRAGMA rekey command.
Continue reading Tutorial: Add SQLCipher to your Android app
This tutorial demonstrates greenDAO 2.x integration. Since greenDAO 3.x was released, its integration differs from 2.x. Now, you can either have a generation project or everything in one app’s project. There is a build-in encryption (SQLCipher underneath) which you can use if you want. There are now annotations and the package name has been changed to
org.greenrobot.greendao. Here is a good article if you want to migrate to greenDAO 3.x – Updating to greenDAO 3 and annotations and here are some Code examples.
Today I want to present you my new tutorial about greenDAO integration. For those who haven’t heard, this is a great open source Android ORM solution which enables you to forget about SQLite low-level stuff and concentrate on the database’s overall lifecycle, models and how do they relate. You don’t actually need to bother how to populate the database and how the relations work, because greenDAO handles it for you. All you need to know is what you want to keep in your DB.
Sounds great, huh? But what about performance? Continue reading Tutorial: How to easily integrate greenDAO into your Android project