In the context of I/O 2017, Google released the Room Persistence Library, an intermediate layer between application logic and Android’s SQLite database. Using Room, you no longer have to handle stuff like network connection errors or caching yourself. Today’s article will help you get started with the library and teach you all the skills you need to implement Room in your own applications.
Background of my sample application
The following code snippets are part of one of my side projects. This application manages shopping lists, which in itself can have entries. Actually, this is a very simple application, but it illustrates the functionality of Room very well.
The structure of Room is based on three elements, which I will explain in detail below. These elements are the entities, data access objects and the database itself. While the purpose of the database should be clear, I would like to comment briefly on that of the other two.
Entities in general represent real things. Almost anything can be an entity. Think of a car, a house, yourself.
I wanted to keep the application very minimalistic, which is why each shopping list only has a title and a timestamp. This allows the user to sort the list chronologically. The class for displaying entries has the same attributes, supplemented by a reference to a shopping list. This is already a bit strange, because this setup corresponds to that of a relational database. When working with object relational mappers, however, you would rather give each shopping list a list of entry elements directly. Room separates itself from this approach: Room doesn’t allow object references. Google covers this extensively in a dedicated article. Instead, you have to explicitly tell Room what parts you need.
For this reason I will build my pojos according to a relational database schema. This results in the following schema:
In Android, this schema can be translated to regular POJO classes. Using Java annotations, you can tell your class what elements should be treated in which way. The class which represents a shopping list looks like this:
As you can see, there are already multiple annotations. The first one is the @Entity annotation. It tells room that this class needs to be persisted to a database and what the name of the matching table will be. The next annotation is @PrimaryKey. You need to assign a primary key to each entity. Doing so, you specify a unique identifier to each of the tables entries. I added autoGenerate = true, so Room will be handling this matter for me.
In general, I don’t recommend to use simple integers as primary keys, but that’s another topic. Also, for the sake of simplicity, I set the scope of all properties to public. When using private, Room requires appropriate accessor methods to these properties.
Per default, room will use class and property names to specify the respective elements in the database. By using the @ColumnInfo annotation, you can customize these. The last annotation in this example is @Ignore, which tells room to ignore the property when loading or saving data.
You can see another annotation when checking out the class representing an item inside a shopping list:
As mentioned earlier, I’ve added a reference to the shopping list to each item. Since the id we specified for these is an automatically generate integer, we can simply access it here and store it as integer as well. By adding a @ForeignKey annotation, you’ll firstly need to specify the referenced class, followed by the referenced row. Complete the statement by specifying the column of the current class with which the join is to be done. In my case, this is the id column of the ShoppingList class and the list_id column of the ShoppingListItem class. Note that the names must match those of the table and you may have overwritten them with @ColumnInfo annotation.
You can also customize the OnDelete action. If CASCADE is specified as an OnDelete action, all items in a list are deleted if the list itself is deleted.
Data Access Objects
The next part we will cover are the DAOs. Data Access Objects allow you to interact between the database and the entity. And here’s the best part: they are very easy to implement. I have created two DAOs, one for the lists and one for the entries. In order to keep the whole thing a little bit short here, I’m just going to go into the DAO of my list.
A DAO is basically an interface that describes the interaction possibilities with the database. How exactly these look depends of course on your specific application. By specifying a Java annotation you can control the type of operation. In addition to the regular operations for creating, updating, or deleting objects, Room offers you the option of implementing your own queries using the query statement.
Of course, you can also use parameters in your custom queries. To do this, simply enter the name of the parameter with a preceding colon in the query.
In my final section, the database itself, I will show you how to combine the components and how to persist your objects.
To interact with the SQLite database, you need to create a separate class that inherits from RoomDatabase and passes the connection details via @Database annotation. Google recommends using a singleton pattern, which I have implemented in my application.
As you may have noticed, I explicitly allowed Room to perform database operations in the UI thread. Please note you should not release something like this in a production-ready application. Otherwise, longer running operations may block the user interface and have negative effects on the UX.
The following example shows you how to retrieve data from the database.
You can now perform all other operations in the same way. All information as well as advanced topics can be found directly on Google in the corresponding documentation.
Subscribe via RSS