wasi-keyvalue
wasi-keyvalue copied to clipboard
WebAssembly
What would the recommended way to represent a read-only key-value store (populated from or fronting some other source) with these interfaces--have it export `store` but return errors from `bucket.set` and...
_Originally posted by @Mossaka in https://github.com/WebAssembly/wasi-keyvalue/pull/30#discussion_r1432038530_
Currently, the signature of the atomic increment is ``` increment: func(bucket: bucket, key: key, delta: u64) -> result; ``` I would like to understand the reasoning behind the `delta` argument...
There are many use-cases that would benefit from having a key-value store where keys are not strings but opaque bytes, would there be a particular reason why the type `key`...
This PR incorporates some feedback received on the current draft interface. First off, this changes the cursor for listing keys to be a string instead of a number in order...
I am working on a project which needs to access a key-value store from a Wasi component, but I need an atomic test-and-set operation for my application. Just as an...
E.g. in Cloudflare KV https://developers.cloudflare.com/kv/api/list-keys/: > cursor is a string used for paginating responses.
Please create releases and tag the repository with each version. The recent change from `wasi:[email protected]` to `wasi:[email protected]` means that all `wit-deps update` effectively pulls in the `https://github.com/WebAssembly/wasi-keyvalue/archive/main.tar.gz` file with `0.2.0-draft2`,...
I think we should consider moving `list-keys` into another/a new interface. [Its doc comment](https://github.com/WebAssembly/wasi-keyvalue/blob/6630aef11b53ef7f6ae87d3b7bc3396c24f983cd/wit/store.wit#L104-L119) already lists a number of caveats which reflect the underlying issue that this feature just isn't...
