Skip to content
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

Deno.Kv: ability to retrieve just keys #18968

Open
kitsonk opened this issue May 3, 2023 · 1 comment
Open

Deno.Kv: ability to retrieve just keys #18968

kitsonk opened this issue May 3, 2023 · 1 comment
Assignees
Labels
ext/kv Related to "Deno.openKv()" API suggestion suggestions for new features (yet to be agreed)

Comments

@kitsonk
Copy link
Contributor

kitsonk commented May 3, 2023

Related to #18965

There feels like there is a use case for just enumerating the keys of a .list() function, like for example to be able to retrieve and then delete a set of keys, without needing to allocate all of the values in the runtimes memory.

@bartlomieju bartlomieju added the ext/kv Related to "Deno.openKv()" API label May 3, 2023
@lucacasonato lucacasonato added the suggestion suggestions for new features (yet to be agreed) label May 3, 2023
@miguelrk
Copy link

miguelrk commented Apr 22, 2024

Any news on this? Not only is having to use .list() suboptimal performance wise (having to read keys AND values into memory) but also cost wise (on Deploy). +1 to have an operator for this built-in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ext/kv Related to "Deno.openKv()" API suggestion suggestions for new features (yet to be agreed)
Projects
None yet
Development

No branches or pull requests

5 participants