SQLite no_std

Note: these bindings are faithful to the base SQLite C-API as much as possible for minimum rust<->c overhead. This, however, means that the bindings are not entirely safe. E.g., the SQLite statement object will clear returned values out from under you if you step or finalize it while those references exist in your Rust program.

SQLite is lite. Its bindings should be lite too. They should be able to be used anywhere SQLite is used, not incur any performance impact, not include any extra dependencies, and be usable against any SQLite version.

This is a fork of vlcn-io/sqlite-rs-embedded with additional features and fixes.

These bindings:

• Do not require the rust standard library
• Work on stable Rust (1.93+ required)
• Use the SQLite memory subsystem if no allocator exists
• Can be used to write SQLite extensions that compile to WASM and run in the browser
• Does 0 copying. E.g., through some tricks, Rust strings are passed directly to SQLite with no conversion to or copying to CString.

Features

The sqlite3_capi crate (and crates that depend on it) require one of the following mutually exclusive features to compile:

• static — Links against a bundled SQLite and generates bindings via bindgen at build time.
• loadable_extension — For writing SQLite loadable extensions. Uses the SQLite API pointer provided by the host instead of linking SQLite directly.

An optional feature is also available:

• omit_load_extension — Disables the sqlite3_load_extension API.

The stable_trap crate (used by sqlite_web) also provides an optional feature:

• nightly — Uses core::intrinsics::abort() instead of inline assembly for the panic abort path. Must be explicitly enabled; it does not auto-detect the compiler.