Is there a room for Room?
summary
Compares Google’s Room to requery.io by building an invoices app with ~40 invoice fields and one-to-many advance payments, implements Room entities, DAOs and RxJava returns (Single vs Flowable), and writes SQL queries and relations at DAO level. Uses in-memory DB for instrumentation tests and a migration test that upgrades schema from version 4→5 and verifies the new column value equals 4. Emphasizes alpha release bumps and practical limits. Room vs requery.io migration test sets newField=4
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:13Why Google created Room
- 5:22Setting up Room dependencies
- 6:24Defining entities in Room
- 9:13Handling relations in entities
- 13:32Type converters and embedded objects
- 14:13Creating the Room database
- 16:44Understanding DAOs in Room
- 17:49Writing queries with DAOs
- 23:26Handling relations at query level
- 29:09Testing Room databases
- 31:16Testing database migrations
- 38:39Room vs. Require and future outlook
- 40:29Q&A
