[7.x] Allow overriding the MySQL server version for strict mode #32708
Conversation
This file contains 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
GrahamCampbell
changed the title
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.
A PR in response to #32681.
When working with managed MySQL servers from Azure there's quite a peculiar catch: the database servers are behind a proxy and these don't know in advance which version you're connecting to while handshaking.
As a consequence
$connection->getAttribute(PDO::ATTR_SERVER_VERSION)will always yield5.6.42.0regardless of the actual MySQL version (like 8.0.x!), and Laravel is unable to set the correct modes.Since there's no way to circumvent the spoofed server version, a simple
versionconfig -if present- seemed like the cleanest approach to me.