implement-dao

To implement a DAO with SQLDelight, create a .sqldelight file, define the interface and implementation in separate modules, annotate the impl with @BitkeyInject(AppScope::class), and add a fake in the :fake module. This standardizes boundaries and transaction handling.

The best way to structure SQLDelight DAOs is separating the interface and implementation into distinct modules with a clear boundary. This enforces interface/implementation separation, transaction-aware operations, and DI integration for maintainable Android code.

To create testable fakes for SQLDelight DAOs, implement a fake in-memory storage class in the :fake module with a reset() method. This provides reliable, isolated testing by allowing test doubles to be reset between test runs.

Yes, this DAO approach supports dependency injection in Kotlin by annotating the implementation class with @BitkeyInject(AppScope::class). This integrates the SQLDelight-backed DAO directly into your DI graph for proper transactional usage.

This DAO implementation handles database transactions and errors by enforcing transaction-aware operations and proper error handling via DbError. This ensures consistent transactional boundaries and safe error propagation across your SQLDelight database operations.

You need to separate your DAO interface from its SQLDelight implementation to prevent duplicated code, ensure consistent transaction handling, and enable test-friendly fakes. This clear module boundary isolates database logic for easier maintenance.