resqlite library
Classes
- Database
- A high-performance SQLite database with reactive queries.
- Diagnostics
- Per-connection diagnostic snapshot.
- ResqliteExtension
- A SQLite loadable extension to register on every resqlite connection.
- ResqliteExtensionRegistrar
- Registrar exposed to ResqliteExtension.onRegister.
- ResultSet
- A query result set backed by a flat values list.
- Row
- A single query result row.
- RowSchema
- Column metadata shared across all rows in a ResultSet.
- StreamEngine
- Stream engine — reactive query lifecycle.
- TableColumnDependency
- Dependency on a fixed set of columns in table.
- TableDependencies
- Dependency value types shared by the native bindings, writer, reader, and stream engine.
- TableDependency
- Table-level dependency.
- Transaction
- A transaction proxy object for executing writes and reads atomically.
- WriteResult
- Result of a write operation returned by Database.execute and Transaction.execute.
Enums
- ResqliteConnectionScope
- Which native resqlite connections should execute registration SQL.
Typedefs
-
ResqliteExtensionEntrypoint
= NativeFunction<
ResqliteExtensionInitNative> - Native function pointer type for a SQLite extension entrypoint.
-
ResqliteExtensionInitNative
= Int Function(Pointer<
Void> , Pointer<Void> , Pointer<Void> ) - Native signature for SQLite loadable extension entrypoints.
- ResqliteExtensionRegister = void Function(ResqliteExtensionRegistrar ext)
- Callback used by extension packages to configure per-connection setup.
Exceptions / Errors
- ResqliteConnectionException
- An error related to database lifecycle — opening, closing, or using a database that is no longer available.
- ResqliteException
- Base exception for all resqlite errors.
- ResqliteQueryException
- An error caused by a SQL query — malformed SQL, constraint violations, or runtime execution failures.
- ResqliteTransactionException
- An error raised by the library's own transaction control (BEGIN, COMMIT, ROLLBACK, SAVEPOINT, RELEASE). These statements are issued by resqlite, not by the caller, so there is no user-written SQL to surface — the operation field identifies which control statement failed and sqliteCode carries SQLite's reason.