SEQUEL SQL for Android Developers
summary
SQL is 50 years old and Android uses embedded SQLite (available since the early 2000s) with limits like concurrent reads but sequential writes, slower disk I/O and small memory budgets on low-end devices. The page shows concrete SQL: CREATE TABLE with primary and foreign keys and cascade rules, warns to avoid SELECT on backend for performance, and demonstrates parameterized queries to prevent injection. Two Android options are compared: Room (ORM) vs SQLDelight, which generates type-safe Kotlin from SQL* so queries become compile-time APIs and reduce runtime surprises.
AI-written summary · about
chapters (13)
- 0:00SQL for Android devs
- 1:52Speaker background and SQL relevance
- 6:49Understanding ORMs and their drawbacks
- 12:03Querying with SELECT
- 14:26Modifying data in SQL
- 17:12Tables keys and relationships
- 26:22Database normalization
- 28:10Performance with indexes
- 32:24SQLite limits on Android
- 34:29Bare metal vs ORM
- 36:58Transactions and consistency
- 38:01SQLite security
- 40:05Summary
