One-to-many relation in Room

Question

I've been using SugarDB for most of my projects in the past. It was easy to use and satisfied most of my requirements but since that project has been abandoned, decided to look at alternatives and Room seems like the best option.

However, some basic things are quite confusing in Room. My Object uses Gson to populate data from a webservice, and as such as links to other objects. As an example, consider the classes below:

@Entity
public class TestModel
{
    @PrimaryKey(autoGenerate = true)
    private int id;
    private String name;
    private String age;
    private List<Book> issuedBooks;
}

public class Book
{
    private String title;
    private int ISBN;
}

Now if my first class is annotated as the Entity, will this automatically treat classes referenced inside it as entities as well?

If I save an object of TestModel, will it save the list of Books with it to the database?

score 24 · Answer 1 · answered Apr 01 '18 at 07:02

24

I guess you can do it this way.

@Entity
public class TestModel {
    @PrimaryKey
    public int id;          // TestModel id
    public String name;
    public String age;
}

@Entity
public class Book {
    @PrimaryKey
    public int id;          // Book id
    public int testModelId; // TestModel id
    public String title;
    public int ISBN;
}

public class TestModelWithBooks {
   @Embedded
   public TestModel testModel;

   @Relation(parentColumn = "id", entityColumn = "testModelId", entity = Book.class)
   public List<Book> books;
}

For their Dao, you can write it this way.

@Dao
public interface TestModelDao {
    @Query("SELECT * FROM TestModel")
    public List<TestModelWithBooks> loadTestModelsWithBooks();
}

answered Apr 01 '18 at 07:02

Cheok Yan Cheng

47,586
132
466
875

2

can this solution be extended when i have several levels for example I have class Person, Person has List of Credit cards, every Credit Card has a list of Banks, Bank has an Adress, Adress has coordinate, coordinate consist of lat and lon. Should i use simple one-to-many approach through foreign keys, or your approach also can work ? – Jenya Kirmiza Jan 01 '19 at 23:26
10

How do you do insert? – Farruh Habibullaev Nov 07 '19 at 23:51
We can review this answer for [Insert relation entities using Room](https://stackoverflow.com/questions/44667160/android-room-insert-relation-entities-using-room) – israteneda Mar 17 '20 at 16:20

score 13 · Answer 2 · answered Jan 25 '18 at 13:22

will this automatically treat classes referenced inside it as entities as well?

No. In fact, I would expect your code to fail to compile. You would need to:

Make Book be an @Entity
Remove issuedBooks from TestModel
Set up a @ForeignKey relationship between Book and TestModel

If I save an object of TestModel, will it save the list of Books with it to the database?

No.

Room is not an ORM. Room is a thin object wrapper around SQLite. @Entity and @ForeignKey model the table structure. IMHO, the simplest way to think of Room as it being DTOs to the database. Your model objects that represent your object graph are not the entities, but instead are built from the entities. This is akin to how responses from a Web service (e.g., Retrofit) are DTOs to the server, and you may need to map from those objects to the "real" model objects that you want to use in the app.

Thanks a lot for clarifying. What ORM would you recommend as an alternative to Sugar? Or should I do a bit of the hard work myself and stick to Room? — Asim, Jan 25 '18 at 13:30
At the moment there are two alternatives [requery](https://github.com/requery/requery) and [objectbox](https://docs.objectbox.io/getting-started) — israteneda, Mar 17 '20 at 16:16

One-to-many relation in Room

2 Answers2