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 cache to database #243

Open
lalalune opened this issue Nov 9, 2024 · 0 comments
Open

Move cache to database #243

lalalune opened this issue Nov 9, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@lalalune
Copy link
Member

lalalune commented Nov 9, 2024

We should move all caching, including token cache, content cache, etc into the database. We can store these in a cache manager which could be connected to the memory manager so we can add to the adapters for each database adapter.

  1. Move all content caching into memory manager and use store cache and retrieve cache calls
  2. Add and test with every database adapter, including sqlite, sqljs and postgres

make sure twitters credentials not broken in tweetcache -- or are saving to db
we should store models somewhere nice
store credentials in db
cache prompts in db?
fix tokencache
content_cache ?

@lalalune lalalune added the enhancement New feature or request label Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant