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.

Sign up for GitHub

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

Jump to bottom

Consider moving to a database storage instead of using JSON files #325

Open
Octol1ttle opened this issue Jul 20, 2024 · 0 comments
Open

Consider moving to a database storage instead of using JSON files #325

Octol1ttle opened this issue Jul 20, 2024 · 0 comments
Labels
priority: low PRs or issues that have low priority. status: help wanted Issues or PRs that need further investigation. type: feature Features and feature requests.

Comments

@Octol1ttle
Copy link
Member

Right now, all guild and member data is stored in a JSON format. I can go in detail about why this approach is bad, but it all leads down to one thing - inefficiency of JSON compared to databases like SQLite and Postgres. As such, moving data storage to one of these databases would be of great benefit, given that data storage already needs a serious refactor
@Octol1ttle Octol1ttle added status: help wanted Issues or PRs that need further investigation. type: feature Features and feature requests. priority: low PRs or issues that have low priority. labels Jul 20, 2024
@Octol1ttle Octol1ttle mentioned this issue Jul 20, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: low PRs or issues that have low priority. status: help wanted Issues or PRs that need further investigation. type: feature Features and feature requests.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Octol1ttle