NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io, #2825 most downloaded on crates.io
Rust Embedded DataBase
Latest stable
4.5.0
Last release 15 days ago
05 Nov 2026
Release timing varies
gaps range from 8 days to 5 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
2 versions withdrawn
withdrawn after publishing
8 years old
79 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Return Err instead of panic'ing when opening a database file with an incompatible file format version
Err instead of panic'ing when opening a database file with an incompatible file format versionWriteStrategysWriteStrategy::Checksum (which is the default)insert_reserve() in certain casesOptimize MultimapTable storage format to use O(k * log(n_k) + v * log(n_v / n_k)) space instead of O(k * log(n_k + n_v) + v * log(n_k + n_v)) space, w
Optimize MultimapTable storage format to use O(k * log(n_k) + v * log(n_v / n_k)) space instead of O(k * log(n_k + n_v) + v * log(n_k + n_v)) space, where k is the size of the stored keys, v is the size of the stored values, n_k is the number of stored keys, n_v is the number of stored values
(), as a valueMultimapTable::range to return an iterator of key-value-collection pairs, instead of key-value pairsWriteTransaction on dropYour coding agent can read these notes before it upgrades. Set up the MCP server →
Add single phase with checksum commit strategy. This is now the default and reduces commit latency by ~2x. For more details, see the design doc and bl
WriteStrategy::Throughput, and can have better performance when writing a large number of bytes per transaction.Fix a bug where re-opening a Table during a WriteTransaction lead to stale results being read
Table during a WriteTransaction lead to stale results being readFix a serious data corruption issue that caused many write operations to corrupt the database
Add information log messages which can be enabled with the logging feature
logging feature[u8; N] typeu64,
2x for u32, and also improves performance.#[derive(Value)] and #[derive(Key)] failing to compile on structs whose lifetimes are
named 'a or 'b; the generated implementations no longer shadow the struct's lifetimes.fixed_width, from_bytes,
as_bytes, or type_name on field types, instead of the Value trait methods. The
generated code now uses fully qualified paths, and no longer requires the Value and Key
traits to be in scope at the derive site.#[redb(crate = "...")] to name the crate the implementations are generated for, when
redb is renamed or present in several versions. Structs with fields require redb 3.0+.TypeName when two field types with different
definitions share a name, such as a user-defined type named String and the built-in
String. User-defined field types (including the chrono types redb provides) are now
tagged in the derived TypeName, so structs containing them change type identity: their
existing tables report TableTypeMismatch and must be migrated. Structs whose fields are
all built-in types are unaffected.#[derive(Value)] on a struct with exactly one field now forwards the field's Value::NICHE,
so Option of such a struct is encoded as Option of the field is. The generated code refers
to Value::NICHE, so such a struct can only be derived against redb 4.4.0 or newer; other
structs are unaffected.Change insert() to return an Option with the previous value, instead of ()
insert() to return an Option<V> with the previous value, instead of ()* Improved documentation
* Initial beta release
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.