Adding migration to fix mysql silently altering table entries on autoincrement#2192
Merged
Conversation
github-project-automation
Bot
moved this to Todo
in 🥂 JUNE - Bugs & Enhancements - Last Milestones for 1.0
jessevz
approved these changes
Jun 2, 2026
github-project-automation
Bot
moved this from Todo
to Done
in 🥂 JUNE - Bugs & Enhancements - Last Milestones for 1.0
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.
When altering a table and add autoincrement for a column in MySQL, it silently just generates new IDs for entries where the value is 0 (not NULL, but MySQL by default thinks on 0 it should also auto increment). This behavior caused the previous migration to update the Hashtype of MD5 from 0 to 100000.
This migration now fixes the entry in case this happened and sets it back to 0 (which is not conflicting with the autoincrement).