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

Cache prepared statements #102

Closed
ajayyy opened this issue Aug 12, 2019 · 6 comments
Closed

Cache prepared statements #102

ajayyy opened this issue Aug 12, 2019 · 6 comments
Labels
Server

Comments

@ajayyy
Copy link
Owner

ajayyy commented Aug 12, 2019

Right now they are created every time they are needed.
@ajayyy ajayyy added the Server label Aug 12, 2019
@NDevTK
Copy link
Contributor

NDevTK commented Aug 12, 2019

What about a in-memory database such as Redis? http://redis.js.org/

@ajayyy
Copy link
Owner Author

ajayyy commented Aug 12, 2019

Sqlite is easier for others to use

@NDevTK
Copy link
Contributor

NDevTK commented Aug 12, 2019

client.set("string key", "string val", redis.print);
does not look hard

@ajayyy
Copy link
Owner Author

ajayyy commented Aug 12, 2019

No, for other people to use this DB in their own projects.

Downloading one .db file and opening it is easy.

@NDevTK
Copy link
Contributor

NDevTK commented Aug 13, 2019

https://redis.io/topics/persistence you can have a file copy of the database

@ajayyy ajayyy mentioned this issue Jul 28, 2020
Closed
@ajayyy
Copy link
Owner Author

ajayyy commented Jul 28, 2020

ajayyy/SponsorBlockServer#109

@ajayyy ajayyy closed this as completed Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Server
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ajayyy @NDevTK