Skip to content

Conversation

@severo
Copy link
Collaborator

@severo severo commented Apr 8, 2022

instead of keeping a large collection of rows and columns, then compute
the response on every endpoint call, possibly truncating the response,
we now pre-compute the response and store it in the cache. We lose the
ability to get the original data, but we don't need it. It fixes #197.
See
#197 (comment).

BREAKING CHANGE: 🧨 the cache database structure has been modified. Run
20220408_cache_remove_dbrow_dbcolumn.py to migrate the database.

severo added 3 commits April 8, 2022 10:19
instead of keeping a large collection of rows and columns, then compute
the response on every endpoint call, possibly truncating the response,
we now pre-compute the response and store it in the cache. We lose the
ability to get the original data, but we don't need it. It fixes #197.
See
#197 (comment).

BREAKING CHANGE: 🧨 the cache database structure has been modified. Run
20220408_cache_remove_dbrow_dbcolumn.py to migrate the database.
@severo severo changed the title Simplify cache Simplify cache by dropping two collections Apr 8, 2022
@severo
Copy link
Collaborator Author

severo commented Apr 8, 2022

To do, before prodding: backup the prod database, and test locally with the prod database.

@severo severo merged commit 623606d into main Apr 12, 2022
@severo severo deleted the simplify-cache branch April 12, 2022 08:15
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 this pull request may close these issues.

Row too big to be stored in cache

2 participants