remove special case for 8M range covers #9752
Merged
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.
Closes #9560 (at least for critical items in the 8M range).
This does not update the database -- the
filename
field is the only field which requires an update, but they are kept as is in case there's any need to use the existing tar offsets. The zip filenames are automatically inferred by the cover id.The following script can be used to generate db statements if we want to update the
filename
field:For the purpose of doing this in a non-breaking way, I've already added a field to the
coverstore.cover
table calledfilename_old
which equals the current value offilename
so if anything were to go wrong, we could overwritefilename
withfilename_old
. After this work is completed, we likely want to delete thefilename_old
column as it takes up necessary space for the ~1M covers where these values have been backed up.Technical
Testing
Screenshot
Stakeholders