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

Add option for human readable key encoding #10

Open
kloboves opened this issue May 15, 2022 · 1 comment
Open

Add option for human readable key encoding #10

kloboves opened this issue May 15, 2022 · 1 comment
Assignees

Comments

@kloboves
Copy link

Currently keys are encoded using a binary encoding scheme which makes it very hard to inspect the state of the database. It makes it hard to search for currently stored updates for a certain document (hard to construct the right prefix - for example if using RocksDB with ldb scan tool).

Since the keys are very simple (doc name + clock ID), I think it would be better to give an option to store them in a simple string format (something like :<clock_id> or whatever separator).

This could be easily implemented by exposing the key encoder / decoder as part of the API.

@dmonad
Copy link
Member

dmonad commented May 16, 2022

Sure, feel free to open a PR 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants