Add design document for migration integrity verification#67
Merged
Conversation
DOCS: Add design document for schema and migration hash verification This document describes the expected behavior for integrity checks during migrate up/down commands, including verification of both the xxhash3 schema checksum and BLAKE3 migration hash against the database's tracking tables. Key contents: - Rationale for two-hash verification approach - Current implementation gaps (schema checksum stored but never verified) - Proposed verification flow for both up and down migrations - Detailed implementation changes needed in tracker, executor, and CLI - Error handling and force flag design
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.
DOCS: Add design document for schema and migration hash verification
This document describes the expected behavior for integrity checks during
migrate up/down commands, including verification of both the xxhash3 schema
checksum and BLAKE3 migration hash against the database's tracking tables.
Key contents: