مراقبة الجداول باعتبارها Flow

Re-running a query by hand misses changes. SQLDelight can push fresh results to you whenever the table changes.

Reactive queries need the coroutines-extensions artifact, which adds Flow support on top of your generated queries.

Call asFlow on any select query to get a Flow that re-emits whenever the underlying table is written.

asFlow gives a query holder, so chain mapToList to emit a ready Kotlin list each time the data changes.

For one row use mapToOneOrNull, which emits the row or null and updates automatically as that row changes.

You consume the stream by collecting it. Every insert, update or delete to that table triggers a fresh emission.

Wrap the Flow in a StateFlow so your shared ViewModel holds the latest list as a single source of truth.

On Android, collectAsState turns the StateFlow into Compose state, so the list recomposes automatically on every change.

On iOS you observe the same StateFlow from Swift and update SwiftUI, so both apps stay in sync with the database.

Insert a row anywhere and every active Flow re-emits. The database becomes the live source driving both platforms.

Run mapping off the main thread by passing a background dispatcher, keeping the UI smooth while queries run.

You collect selectAll().asFlow().mapToList(...). When does it emit again?

You turned queries into Flows, mapped them to results, exposed StateFlow, and let both UIs update on every write. Your shared database is now reactive. ✅