foundationdb-dotnet-client icon indicating copy to clipboard operation
foundationdb-dotnet-client copied to clipboard

C#/.NET Binding for FoundationDB Client API

Results 27 foundationdb-dotnet-client issues
Sort by recently updated
recently updated
newest added

Bumps [Newtonsoft.Json](https://github.com/JamesNK/Newtonsoft.Json) from 11.0.2 to 13.0.1. Release notes Sourced from Newtonsoft.Json's releases. 13.0.1 New feature - Add JsonSelectSettings with configuration for a regex timeout Change - Remove portable assemblies from...

dependencies

The library works great, but the documentation in README.MD is horribly outdated. The example code is simply broken. Takes a while for a beginner to start making transactions.

documentation

```bash ➜ foundationdb-dotnet-client git:(aa3d663d) ✗ ./build/FdbShell Connecting to cluster... REMOVED FDB API FUNCTION [1] 504729 abort (core dumped) ./build/FdbShell ➜ foundationdb-dotnet-client git:(aa3d663d) ✗ ./build/FdbTop REMOVED FDB API FUNCTION [1] 504752...

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...

multi_platform
build_env

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...

enhancement
layer:directory

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...

enhancement
api

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...

enhancement
api

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...

api

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()`....

api
linq

FDB isn't the only kv store out there and your implementation to work with tuples for the key is applicable to any kv which accepts key as byte array. We...