Room is a Database Object Mapping library that makes it easy to access database on Android applications.

Rather than hiding the details of SQLite, Room tries to embrace them by providing convenient APIs to query the database and also verify such queries at compile time. This allows you to access the full power of SQLite while having the type safety provided by Java SQL query builders.

There are 3 major components in Room.

  • Database: This annotation marks a class as a database. It should be an abstract class that extends RoomDatabase. At runtime, you can acquire an instance of it via Room.databaseBuilder or Room.inMemoryDatabaseBuilder.

    The database class defines the list of entities and data access objects in the database. It is also the main access point for the underlying connection.

  • Entity: This annotation marks a class as a database row. For each Entity, a database table is created to hold the items. The Entity class must be referenced in the Database#entities array. Each field of the Entity (and its super class) is persisted in the database unless it is denoted otherwise (see Entity docs for details).
  • Dao: This annotation marks a class or interface as a Data Access Object. Data access objects are the main components of Room that are responsible for defining the methods that access the database. The class that is annotated with Database must have an abstract method that has 0 arguments and returns the class that is annotated with Dao. While generating the code at compile time, Room will generate an implementation of this class.

    Using Dao classes for database access rather than query builders or direct queries allows you to keep a separation between different components and easily mock the database access while testing your application.

Below is a sample of a simple database.
 // File:
 public class Song {
   private int id;
   private String name;
   @ColumnInfo(name = "release_year")
   private int releaseYear;
   // getters and setters are ignored for brevity but they are required for Room to work.
 // File:
 public interface SongDao {
   @Query("SELECT * FROM song")
   List<Song> loadAll();
   @Query("SELECT * FROM song WHERE id IN (:songIds)")
   List<Song> loadAllBySongId(int... songIds);
   @Query("SELECT * FROM song WHERE name LIKE :name AND release_year = :year LIMIT 1")
   Song loadOneByNameAndReleaseYear(String first, int year);
   void insertAll(Song... songs);
   void delete(Song song);
 // File:
 @Database(entities = {Song.class})
 public abstract class MusicDatabase extends RoomDatabase {
   public abstract SongDao songDao();
You can create an instance of MusicDatabase as follows:
 MusicDatabase db = Room
     .databaseBuilder(getApplicationContext(), MusicDatabase.class, "database-name")
Since Room verifies your queries at compile time, it also detects information about which tables are accessed by the query or what columns are present in the response.

You can observe a particular table for changes using the InvalidationTracker class which you can acquire via RoomDatabase.getInvalidationTracker.

For convenience, Room allows you to return LiveData from Query methods. It will automatically observe the related tables as long as the LiveData has active observers.

 // This live data will automatically dispatch changes as the database changes.
 @Query("SELECT * FROM song ORDER BY name LIMIT 5")
 LiveData<Song> loadFirstFiveSongs();

You can also return arbitrary data objects from your query results as long as the fields in the object match the list of columns in the query response. This makes it very easy to write applications that drive the UI from persistent storage.

 class IdAndSongHeader {
   int id;
   @ColumnInfo(name = "header")
   String header;
 // DAO
 @Query("SELECT id, name || '-' || release_year AS header FROM song")
 public IdAndSongHeader[] loadSongHeaders();
If there is a mismatch between the query result and the POJO, Room will print a warning during compilation.

Please see the documentation of individual classes for details.


AutoMigration Declares an automatic migration on a Database. 
BuiltInTypeConverters Flags to turn on/off extra type converters provided by Room. 
ColumnInfo Allows specific customization about the column associated with this field. 
ColumnInfo.SQLiteTypeAffinity The SQLite column type constants that can be used in ColumnInfo.typeAffinity()  
Dao Marks the class as a Data Access Object. 
Database Marks a class as a RoomDatabase. 
DatabaseView Marks a class as an SQLite view. 
Delete Marks a method in a Dao annotated class as a delete method.