Skip to content

Name the upgrade step for MySQL schema 16 - #1226

Merged
rmcdaniel merged 1 commit into
mainfrom
fix/schema-upgrade-mysql16
Nov 17, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
fix/schema-upgrade-mysql16

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

Found while preparing 3.12.0 (#1225). Native 3.10/3.11 MySQL databases are at schema 16; 3.12 moves MySQL to 17 (#1224). UPGRADABLE stopped at 15, so starting a 3.12 binary on a 3.11 MySQL database would refuse with unsupported_rust_schema instead of native_schema_upgrade_required. That tells the operator the database is unusable when it only needs schema-upgrade, which already handles 16 → 17.

This PR adds 16 to UPGRADABLE. The marker test now checks that every listed version, when below the current version, names the upgrade step, and asserts the MySQL 16 → 17 case explicitly. MariaDB (15 → 16), PostgreSQL (15 → 16) and SQLite (14 → 15) were already covered.

🤖 Generated with Claude Code

Native 3.10 and 3.11 MySQL databases are at schema 16, and 3.12 moves MySQL
to 17. UPGRADABLE stopped at 15, so a 3.12 binary opened on a 3.11 MySQL
database refused with unsupported_rust_schema instead of
native_schema_upgrade_required, even though schema-upgrade handles 16 -> 17.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel
rmcdaniel added this pull request to the merge queue Nov 17, 2026
Merged via the queue into main with commit c2e523d Nov 17, 2026
64 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant