Automigrate views using new schema for backing table#5441
Merged
Conversation
joshua-spacetime
added
the
bugfix
Shubham8287
reviewed
Jun 26, 2026
joshua-spacetime
force-pushed
the
joshua/fix/migrate-view-backing-table
branch
from
1c388fb to
b25b649
Compare
joshua-spacetime
force-pushed
the
joshua/fix/migrate-view-backing-table
branch
from
b25b649 to
294ae04
Compare
rekhoff
pushed a commit
that referenced
this pull request
Jun 30, 2026
isn't a breaking change because these tables are ephemeral, the schema is not ephemeral, so it does require us to update the schema by dropping and re-adding views once on initial startup. None 1.5 Auto-migration unit tests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of Changes
#5300 changed the backing table schema of views. While this technically isn't a breaking change because these tables are ephemeral, the schema is not ephemeral, so it does require us to update the schema by dropping and re-adding views once on initial startup.
API and ABI breaking changes
None
Expected complexity level and risk
1.5
Testing
Auto-migration unit tests