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

Support multiple named database roots (branches) per store #97

Closed
whilo opened this issue Nov 20, 2019 · 2 comments
Closed

Support multiple named database roots (branches) per store #97

whilo opened this issue Nov 20, 2019 · 2 comments
Assignees
Projects

Comments

@whilo
Copy link
Member

whilo commented Nov 20, 2019

I think it would be meaningful to allow a git branching like mechanism to fork the identity of the database into multiple named branches. Right now the root is always stored in konserve under the :db key, but this could be an arbitrarily named :branch-name and we provide a forking function. We should also keep track of all the branches that have been created, e.g. in a separate file that is updated whenever fork is invoked.

@whilo whilo self-assigned this Nov 20, 2019
@kordano
Copy link
Member

kordano commented Nov 20, 2019

Sounds like a good idea. Since I'm re-structuring the db record with cleaner configuration we could add this information into the db as well.

@kordano kordano added this to To do in Development Jun 3, 2020
@kordano
Copy link
Member

kordano commented Feb 1, 2021

We are moving these ideas to our roadmap plans, so I'm closing this issue here.

@kordano kordano closed this as completed Feb 1, 2021
Development automation moved this from To do to Done Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development
  
Done
Development

No branches or pull requests

2 participants