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

Move file-backed entries back into the database #3231

Closed
LesnyRumcajs opened this issue Jul 19, 2023 · 0 comments · Fixed by #3320
Closed

Move file-backed entries back into the database #3231

LesnyRumcajs opened this issue Jul 19, 2023 · 0 comments · Fixed by #3320
Assignees

Comments

@LesnyRumcajs
Copy link
Member

Issue summary

Currently, we store a few entries, like GENESIS, HEAD and meta.yaml outside of the database. After the DB re-organization, we have a dedicated column for such data.

share/forest/mainnet
❯ ls
GENESIS  HEAD  meta.yaml  paritydb/

It'd be great to move them into the DB and potentially get rid of the File-backed wrapper. To reduce the SettingsStore trait proliferation, it may make sense to pass to, e.g., ChainStore "another" DB in the form of a trait object. There may be other solutions.

Other information and links

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

Successfully merging a pull request may close this issue.

1 participant