Fix consolidated migration history and SQLite collation rebuilds - #187
Merged
Merged
Conversation
…s during upgrades
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
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.
Consolidated baselines can mark older migrations as applied, but the v13 runner still executed those steps from its precomputed plan. Recheck scope-specific history before each step, support history changes during downgrades, and avoid recording a self-recording baseline twice.
SQLite rebuilds now preserve declared column collations and expose them through metadata. Explicit collation changes retain constraints and roll back on uniqueness violations. Unsupported index-level collations still fail before replacing the table.
Adds regression coverage for scope isolation, transaction modes, rollback, collation parsing and comparison behavior, atomic SQLite identity/key creation, column quoting, and SQL Server/PostgreSQL renamed-table key naming. Updates the 12.1-to-13 migration guide with supported upgrade patterns.
Validation: