Fix migration 48 crash by adding missing transfer columns #70
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.
Fix crash in Migration 48 due to missing transfer columns
Description
This PR fixes a crash that occurred during the database migration from version 47 to 48.
The application was throwing an
IllegalStateException: Migration didn't properly handle: transfersbecause thetransferstable schema in the database did not match theOCTransferEntitydefinition.Specifically, the following columns were missing in the migration but expected by the Entity:
tusUploadUrltusUploadLengthtusUploadMetadatatusUploadChecksumtusResumableVersiontusUploadExpirestusUploadConcatChanges
Migration_48.kt: Added the missingALTER TABLEstatements to add the TUS-related columns to thetransferstable.MigrationToDB48Test.kt: Added a new instrumentation test to verify that the migration from version 47 to 48 completes successfully and that the new columns are correctly added while preserving existing data.Verification
MigrationToDB48Test.Related Issue