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

Replace BoltDB with sqlite #121

Open
Tracked by #292
finn-block opened this issue Feb 5, 2024 · 5 comments · May be fixed by #313
Open
Tracked by #292

Replace BoltDB with sqlite #121

finn-block opened this issue Feb 5, 2024 · 5 comments · May be fixed by #313
Assignees
Labels

Comments

@finn-block
Copy link
Member

sqlite will behave a lot more like postgres and our dev environment should at least roughly match our production environment. ref.

@finn-block finn-block added the bug Something isn't working label Feb 5, 2024
@decentralgabe decentralgabe added enhancement New feature or request server did-dht-2.0 help wanted Extra attention is needed and removed bug Something isn't working labels Feb 7, 2024
@frankhinek
Copy link
Contributor

This would be great as I'd like to explore using something like the following as an alternative way of achieving low latency resolution and high availability for those that don't wish to rely on AWS/GCP cloud services:

@adalundhe
Copy link

I’ll also snag this one of y’all are alright with it!

@adalundhe
Copy link

.take

Copy link

Thanks for taking this issue! Let us know if you have any questions!

@adalundhe
Copy link

Alright! Starting in here - https://github.com/adalundhe/did-dht/tree/main/impl/pkg/storage/db - I'll follow the patterns here and add a sqlite package + tests matching the BoltDB/Postgres tests, get those to pass, then remove/replace the references to BoltDB. Let me know if y'all would prefer a different approach!

@adalundhe adalundhe linked a pull request Oct 31, 2024 that will close this issue
20 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

4 participants