Repository navigation
Docs: clarify 3.1 schema reconciliation behavior - #273
Merged
Merged
Conversation
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
1 participant
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.
Summary
The 3.1 changelog still described schema patch rendering and execution as stubs, and the upgrade guide omitted automatic additive reconciliation. Update both documents to match the merged code: diffs detect modified columns and indexes, bound patches render and apply changes, and a Table version bump without a bespoke upgrade callback adds missing declared columns and indexes by default.
The guide now explains the
reconcilesetting and incomplete-snapshot retry behavior so consumers can review their schemas before upgrading.Validation
Patch,Table::upgrade(),Reconciliation, and their integration tests.git diff --checkpassed.