sled
sled copied to clipboard
spacejam
the champagne of beta embedded databases
## Expected I have a code that starts up sled in a function, like ```rust let db = sled::Config::new() .path(path) .use_compression(false) .mode(sled::Mode::HighThroughput) .open() .expect("Error opening Key Value store"); watch!(db); ```...
Just falling out of `fn main` seems not to do it in a multi-threaded code: `sled::Db::was_recovered` in version `0.34.7` is still `true` on the subsequent run. Is something special needs...
Shouldn't a v0.35.0 release be made instead, and a new v0.34.X version released with just the backwards-compatible changes?
# Why Currently one can only convert arrays up to a certain limit (32) to an IVec, with this change one can convert from arbitrary arrays. ```rust fn main() {...
Hi! I was wondering, is this on the roadmap for sled at all? I love sled so far but this is kind of a deal breaker for us since we...
The current Python bindings use ctypes which are not necessary on CPython and are slow on PyPy. In addition, the package in it's current form cannot be released to PyPi...
If I fill database more slowly (including when using debug build), I often get smaller database size with the exactly same data (per `sled::Db::checksum`). Can I ask Sled to explicitly...
Inspired by https://github.com/spacejam/sled/issues/1368 I don't know if this is something you care to merge or not, but I've done the work to implement a more "standard" way to interact with...
> the 1.0.0 release date is imminent! just putting the final touches on, while performing intensive testing https://github.com/spacejam/sled/commit/a73ea252aa7969f0a91ed5b9813d0207b53ab9c4 (Jan 24, 8 months ago). Such clauses create appearance of an abandoned...
Current development package version is `0.34.6`, which is similar to the published version. This number used for protecting checking database compatibility. However, actual database format in `main` is already incompatible...