fix: MariaDB 12 uses numeric foreign keys by default#2413
Open
joshbmarshall wants to merge 1 commit into
Open
Conversation
dereuromark
approved these changes
May 22, 2026
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.
MariaDB 12.2 (I think also 12.1) if you do not specify a foreign key name, will use numeric strings ("1", "2", "3" etc)
When you go to drop a foreign key, it puts the constraint name as the key in the array. PHP sees it as a numeric string and changes it to an int.
So e.g. the following would previously fail, with an error that $constraint should be a string, int given:
Should also fix #924