[BREAKING] fix: 🐛 quick fix to avoid mongodb errors with big rows #201
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
if a row is too big to be inserted in the cache database, we just store
the empty string for each of its cells, and mark it as erroneous. All
the cells are marked as truncated in the /rows endpoints. See
#197.
This commit also contains the first migration script, with instructions
to apply and write them, fixing #200
BREAKING: the cache database structure has changed. Apply the migration
script: 20220406_cache_dbrow_status_and_since.py