-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non string keys #8
Comments
I have experimented with a few keyvalue stores (dynamodb, redis, azure cosmos db) and they all seem to accept key as |
I'd use it for embedded use cases for example, sometimes directly store the bytes or abstract it to use data structures that are encoded automatically to an efficient representation. |
Another challenge with byte sequences is that it's not possible to transcode plain bytes to key-value stores which use different character encodings. It looks to me like |
What about supporting both with keys being something like an enum? |
With an enum, using wasi-keyvalue with a backend that needs strings would have to always fail when given bytes. Could you say more about your use case? What kinds of embedded programs would use an external key-value store? What backends would you expect to be used to implement the interface? |
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
needs to bestring
?The text was updated successfully, but these errors were encountered: