Replay: handle multiple column types in the same table changing#3893
Merged
gefjon merged 3 commits intophoebe/replay-handle-delete-of-nonexistent-tablefrom Dec 17, 2025
Conversation
kim
reviewed
Dec 17, 2025
kim
approved these changes
Dec 17, 2025
gefjon
force-pushed
the
phoebe/replay-handle-delete-of-nonexistent-table
branch
from
8513a43 to
9edc066
Compare
gefjon
force-pushed
the
phoebe/replay-multiple-changed-col-types
branch
from
21b3d1d to
63e0692
Compare
Contributor
Author
|
Rebased onto updated #3892 . |
gefjon
merged commit d2dbc5b
into
phoebe/replay-handle-delete-of-nonexistent-table
20 of 22 checks passed
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
Based on #3892 ; begin reviewing at 21b3d1d.
I'll expand on this description later.
API and ABI breaking changes
N/a.
Expected complexity level and risk
3 - we already rewrote this path once or twice before and thought we'd fixed it.
Testing