What problem does it solve? Standard sqflite_common_ffi runs all database operations on a single background isolate, so long write transactions block reads. This Skill explains how to use the experimental sqflite_common_ffi_async package, which backs the sqflite DatabaseFactory API with sqlite_async's connection pool (one writer, several readers) so reads never wait behind writes on Linux, macOS, and Windows. ## Core Features & Use Cases - Concurrent reads via readTransaction: Run read-only queries on a separate connection while a write transaction is still open, using db.readTransaction. - Drop-in DatabaseFactory API: databaseFactoryFfiAsync and databaseFactoryFfiAsyncTest expose the standard sqflite Database API (query, insert, transaction, batch), so existing code works unchanged. - Documented fallbacks and limits: In-memory and read-only databases fall back to databaseFactoryFfi; singleInstance is ignored, there is no logger support, and web is unsupported. - Use Case: A desktop Flutter app must display live query results while a long-running import transaction writes rows; use databaseFactoryFfiAsync with readTransaction so the UI reads are not blocked. ## Quick Start Show me how to open a database with databaseFactoryFfiAsync and run a readTransaction concurrently with a write transaction in my Dart desktop app.
