Christophe Chevalier

FSE_compress returns 0 even when maxDstSize is still equal to or slightly larger than final compression size

3

While adding more unit tests, I found a corner case when trying to compress a document with a `maxDstSize` which is exactly the expected compressed size (found by a previous...

We currently still support both .NET Standard 2.0 and .NET Framework 4.7.2 for "legacy" platforms, in addition to .NET Core 3.1 / .NET 5.0 Time as passed since the early...

Right now, calling "Resolve" on a subspace location will, by default, use a cached directory subspace (and set a value-check to protect the transaction). When the caller wants to make...

The current way to implement caching in some layers is to use the `\xff/metadataVersionKey` as a quick way to invalid any previously constructed cache in memory. Though this method as...

Replacing Slice with Span<byte>/Memory<byte>

3

When the binding was written, there were no viable solution to work with binary keys: both `byte[]` or `ArraySegment` are to cumbersome to use, and `MemoryStream` is maybe fine for...

Transaction Size does not take into account read and write conflict ranges

1

Looking at the code in fdbclient (`Transaction::commitMutations()`) it looks like starting from API version 300+, the total transaction size is the sum of the mutated key/value (writes), as well as...

Support for OrderBy(..) in Async LINQ queries

2

Currently, the Async LINQ queries to do not support the OrderBy(...) operator. You have to first call `ToListAsync()` and then sort the results in memory (using the regular LINQ-To-Object `OrderBy(...).ToList()`....

After using this for quite a while, I'm making a few changes to the KeyRange and KeySelector API. ## Rationale The main issue is when trying to model open ranges,...

This is tracking PR for the work of rewriting the way FDBFuture\* handles are wrapped to .NET's `Task`, as detailed in #48. _Original work was done in #54 but was...

Opening a named partition starts transactions before being able to specify the default timeout and retry limit

1

Currently, the way to specify default timeout and retry limit settings is to set them on a `IFdbDatabase` instance, and they will be automatically used by all transactions created from...