Elements of Android Room (Mark L. Murphy)（Z-Library） (1)

# Elements of Android Room — Reading Guide ## 【One-Line Pitch】 A practical, code-first guide to mastering Google's Room persistence library for Android, covering everything from basic entity setup to advanced topics like migrations, full-text search, and reactive queries. Ideal for Android developers who want to move beyond raw SQLite and build robust, testable database layers. ## 【Book Arc】 - **Opening (~0%–10%)**: Introduces Room's place in Android development, the three core components (entities, DAOs, database class), and project setup with Gradle dependencies and minSdk requirements. - **Early (~10%–32%)**: Dives into entity configuration — primary keys, auto-generation, indexes, custom column names, @Ignore, and partial entities — with heavy emphasis on instrumented testing using in-memory databases. - **Middle (~32%–48%)**: Covers DAO return types (ROWIDs, affected row counts), aggregate queries with custom result classes, type converters for custom types, @Embedded objects, and the critical rule against main-thread database access. - **Middle (~48%–60%)**: Explores reactive queries (LiveData, Flow, RxJava), observable query behavior, and ListenableFuture support for asynchronous operations. - **Late (~60%–90%)**: Addresses relationships (one-to-many, many-to-many), the Support Database API, schema migrations, polymorphic entities, and default values. - **Ending (~90%–100%)**: Covers advanced topics: full-text search (FTS), conflict resolution strategies, PRAGMA configuration, and packaged databases. ## 【Key Takeaways】 - **Three pillars of Room** (Early): Entities define your schema, DAOs encapsulate SQL operations, and a @Database class ties them together — understanding this triad is essential before writing any code. - **In-memory databases for testing** (Early): Using Room.inMemoryDatabaseBuilder() gives fast, hermetic tests that don't pollute each other — but they're useless for performance testing since production uses disk. - **Indexing strategy matters** (Early): Primary keys are auto-indexed, but you should add indexes via @ColumnInfo(index=true) for single columns or @Entity's indices property for composite indexes to speed up queries. - **Return values tell you what happened** (Early): @Insert can return ROWIDs (Long or LongArray), @Update/@Delete can return affected row counts (Int) — use these to verify operations succeeded. - **Type converters bridge the gap** (Middle): Custom types like Instant or Location need @TypeConverters to translate to SQLite-friendly types (Long, String) — @Embedded flattens objects into individual columns. - **Main thread access crashes** (Middle): Room throws IllegalStateException if you touch the database on the main thread — always use background threads or reactive patterns. - **Observable queries are powerful but blunt** (Middle): LiveData/Flow deliver fresh results on any table change, even if nothing relevant changed — use distinctUntilChanged() to filter noise. - **Migrations need schema exports** (Late): Exporting schemas as JSON is essential for writing and testing migrations — without them, you're flying blind when your schema evolves. ## 【Reading Tips】 - **Skim the setup chapters** (~0–10%) if you've already added Room to a project — the Gradle snippets are standard, but do note the minSdkVersion 15 requirement and the warning about manifest merger overrides. - **Deep-read the entity and DAO chapters** (~10–32%) — these contain the most reusable patterns: indexing, custom column names, @Ignore, and return value strategies. The test code is worth studying as a template for your own instrumented tests. - **Pay special attention to the main-thread crash test** (~42%) — it's a quick, memorable way to internalize why Room enforces background access. - **The reactive queries section** (~48%) is where you'll find the most practical value — understand the "fresh result without context" limitation early to avoid surprises in production. - **Late chapters on migrations and FTS** are reference material — skim to know what's possible, then return when you actually need to migrate a schema or add search. ## 【Coverage Limits】 Excerpts do not cover the complete code for every sample project or all chapters listed in the table of contents (e.g., detailed migration code, FTS MATCH syntax specifics). Some advanced topics are only outlined in the TOC without full exposition. ##